UUID Generator

Generate cryptographically secure UUID v4 (GUID) strings in bulk. Customize hyphens, uppercase or lowercase, braces, and copy to clipboard instantly.

Free, no sign-upRuns in your browserUpdated November 2026
Quick Bulk Presets
Sample Generated UUID v4
f47ac10b-58cc-4372-a567-0e02b2c3d479
Version: UUIDv4 (Random) Entropy: 122 Bits CSPRNG
1 Generated

How to use the UUID Generator

  1. Choose the Quantity of UUIDs you need (from 1 up to 500 in a single click).
  2. Select between Lowercase (standard Unix/Linux) or Uppercase (Windows GUID) formatting.
  3. Toggle hyphens on or off, or wrap entries in curly braces or quotes for JSON/SQL insertion.
  4. Click GENERATE UUIDs to refresh values with 122 bits of cryptographic entropy.
  5. Click Copy to Clipboard or Download .txt to export your generated identifiers.

What is a UUID (Universally Unique Identifier)?

A Universally Unique Identifier (UUID), also referred to by Microsoft systems as a Globally Unique Identifier (GUID), is a 128-bit label standardized by the Internet Engineering Task Force (IETF) in RFC 4122. In software engineering and database architecture, UUIDs serve as primary keys that are guaranteed to be unique across all devices, servers, and networks without requiring a centralized registration authority or coordinating database server.

When printed in standard human-readable text, a UUID is represented as 32 hexadecimal digits displayed in five hyphenated groups separated by the 8-4-4-4-12 pattern:

Standard UUID Format: xxxxxxxx-xxxx-Mxxx-Nxxx-xxxxxxxxxxxx (36 total characters)

Anatomy of a Version 4 UUID

While UUID specifications define multiple versions (Version 1 is timestamp-based, Version 3 and 5 are MD5/SHA-1 namespace hashes), Version 4 (UUIDv4) is by far the most ubiquitous because it is generated entirely from pseudo-random or cryptographically random bits:

  • 122 Bits of Pure Entropy: Out of the 128 total bits, 6 bits are fixed to define the version and variant. The remaining 122 bits are completely random.
  • The Version Nibble (M): In the third group (-4xxx-), the first character is always a literal 4, identifying it as a Version 4 UUID.
  • The Variant Nibble (N): In the fourth group (-Nxxx-), the first character is restricted to 8, 9, a, or b, signifying the RFC 4122 standard layout (binary 10xx).

The Astronomical Mathematics of Collision Probability

The total number of possible UUIDv4 combinations is 2122, which equals approximately 5.3 × 1036 (5.3 undecillion possibilities). To put this incomprehensible number in perspective:

UUIDs GeneratedMathematical Collision ProbabilityReal-World Comparison
1 Billion UUIDs~1 in 10,000,000,000,000,000,000Less than the odds of getting hit by a meteorite
100 Trillion UUIDs~1 in 1,000,000,000One in a billion chance
1 Billion/sec for 100 Years~1 in 1,000,000,000Virtually impossible

Because collision odds are effectively zero, distributed microservice architectures can generate primary database keys locally across thousands of decoupled servers without checking for duplication.

UUIDv4 vs. Auto-Incrementing Database IDs

Historically, relational databases like MySQL and PostgreSQL used sequential auto-incrementing integer IDs (1, 2, 3...). While simple, sequential IDs present severe security and scaling flaws:

  1. Information Scraping Vulnerability: If a customer accesses invoice /invoice/1004, they immediately know you have only had 1,004 invoices, and can iterate the URL to scrape competing customer data. UUIDs (/invoice/7c9e6679-7425-40de-944b-e07fc1f90ae7) are impossible to guess.
  2. Multi-Master Sharding: With auto-incrementing IDs, two distributed database shards cannot insert rows independently without generating identical IDs. With UUIDs, sharded clusters generate globally distinct rows with zero communication latency.

Frequently asked questions

What is the difference between a UUID and a GUID?
They are virtually identical. UUID (Universally Unique Identifier) is the open IETF standard term, while GUID (Globally Unique Identifier) is Microsoft’s corporate terminology.
How many bits are in a UUID v4?
A UUID is 128 bits long. In version 4, 6 bits are reserved for metadata (version 4 and RFC 4122 variant), leaving 122 bits of pure cryptographic randomness.
Can two generated UUIDs ever collide?
While theoretically possible, the mathematical probability of two UUIDv4 strings colliding is so microscopically close to zero that it is considered impossible in practical computing.
Should I use uppercase or lowercase UUIDs?
RFC 4122 specifies that UUIDs should be output in lowercase. However, Microsoft Windows, COM objects, and Microsoft SQL Server traditionally display them in uppercase.
Are UUIDs good for database primary keys?
Yes, especially for distributed systems and public APIs. However, because UUIDv4 is non-sequential, consider indexing with UUIDv7 or using specialized UUID storage types in Postgres to avoid B-tree index fragmentation.
Are these UUIDs generated using secure randomness?
Yes. This generator uses the browser’s native crypto.randomUUID() and crypto.getRandomValues() CSPRNG APIs.

Last reviewed November 2026. Results are estimates for information only — see our disclaimer.