UUID Generator

What Is a UUID?

A UUID (Universally Unique Identifier) is a 128-bit label used to identify information in computer systems without requiring a central coordinating authority. Defined by RFC 4122, UUIDs follow a standardized format of 32 hexadecimal digits arranged in five groups separated by hyphens: xxxxxxxx-xxxx-Mxxx-Nxxx-xxxxxxxxxxxx, where M indicates the version and N indicates the variant. The resulting 36-character string (including hyphens) looks like 550e8400-e29b-41d4-a716-446655440000. UUIDs are fundamental to modern software architecture, serving as the glue that holds distributed systems together.

UUID Versions Explained

The UUID specification defines five versions, each using a different generation strategy. Version 1 (v1) combines a timestamp with the generating machine's MAC address, producing time-ordered identifiers that can reveal network information. Version 2 (v2) is a DCE Security variant rarely used in practice. Version 3 (v3) generates deterministic UUIDs by hashing a namespace and name with MD5. Version 4 (v4) is the most popular version, constructed entirely from random or pseudo-random numbers, offering 122 bits of randomness. Version 5 (v5) is similar to v3 but uses SHA-1 instead of MD5 for the hash. This tool generates v4 UUIDs, which are the standard choice when you need identifiers that cannot be predicted or traced back to the generating system.

When to Use UUIDs

UUIDs solve the problem of generating unique identifiers without coordination between systems. They are essential in several common scenarios. As database primary keys in distributed systems, UUIDs allow each node to generate IDs independently without risking collisions, eliminating the bottleneck of a centralized ID generator. In API design, UUIDs serve as idempotency keys that let clients safely retry requests without causing duplicate operations. Microservice architectures rely on UUIDs for correlation IDs that trace requests across service boundaries. Message queues use them to deduplicate events. File systems use them for partition identifiers. Every major cloud platform, from AWS to Azure, uses UUIDs extensively in their APIs.

Collision Probability

UUID v4 provides 122 bits of randomness, yielding approximately 5.3 x 10³⁶ possible values. To put this in perspective, if you generated one billion UUIDs every second, it would take about 100 years to have even a 50% chance of producing a single duplicate. The birthday paradox tells us you would need roughly 2.71 x 10¹⁸ (2.71 quintillion) UUIDs before reaching that threshold. For all practical purposes, UUID v4 collisions do not happen. Even generating a million UUIDs per second for a century gives a collision probability smaller than the chance of being struck by a meteorite.

UUID Format Deep Dive

The 8-4-4-4-12 hexadecimal format encodes 128 bits of data. In a v4 UUID, the 13th character is always 4, indicating the version. The 17th character is always one of 8, 9, a, or b, encoding the variant field that identifies this as an RFC 4122 UUID. The remaining 122 bits are cryptographically random. When stored in a database, UUIDs can be kept as 16-byte binary values for space efficiency, or as the 36-character string form for human readability. Some databases like PostgreSQL have native UUID column types that store them efficiently as 128-bit values with built-in indexing support.

Frequently Asked Questions

What is a UUID?

A UUID is a 128-bit identifier formatted as 32 hex digits in five groups (8-4-4-4-12). Defined by RFC 4122, UUIDs are designed to be globally unique without a central authority.

What is the difference between UUID v1 and UUID v4?

UUID v1 uses timestamps and MAC addresses, making it partially predictable. UUID v4 is entirely random with 122 bits of entropy, providing no traceable information about when or where it was generated.

Can two UUID v4 values collide?

Theoretically yes, but the probability is negligibly small. With 5.3 x 10^36 possible values, you would need quintillions of UUIDs before a collision becomes remotely likely.

Should I use UUIDs as database primary keys?

UUIDs are ideal for distributed databases where nodes generate IDs independently. They are larger than integers and can fragment indexes, so weigh these tradeoffs for your use case.

Are UUIDs case-sensitive?

No. RFC 4122 states that UUIDs are case-insensitive. Lowercase is the conventional format, but uppercase is equally valid and represents the same identifier.