UUID / ID Generator

What is a UUID?

A UUID (Universally Unique Identifier) is a 128-bit identifier standardized by RFC 4122 and its successor RFC 9562, formatted as 32 hexadecimal digits in the pattern 8-4-4-4-12 (for example, 550e8400-e29b-41d4-a716-446655440000). The most widely used variant is UUID v4, which fills 122 of the 128 bits with cryptographically random data, reserving 6 bits for version and variant markers. This yields 2¹²² possible values -- roughly 5.3 x 10³⁶ -- making the probability of two independently generated UUIDs colliding so vanishingly small that it is treated as zero for all practical purposes. UUID v7, introduced in RFC 9562, embeds a Unix millisecond timestamp in the first 48 bits so that IDs are naturally time-sortable while still containing enough randomness to be globally unique. Other versions include v1 (MAC address + timestamp) and v5 (deterministic, derived from a namespace and name via SHA-1). This generator runs entirely in your browser using the crypto.getRandomValues() Web Crypto API, so no identifiers ever leave your machine.

Common Use Cases for UUIDs

The most frequent application is as a database primary key. Unlike auto-incrementing integers, UUIDs reveal nothing about row count or insertion order, which prevents enumeration attacks where an attacker increments an ID to access other users' records. In distributed systems, multiple servers, edge functions, or microservices can generate IDs independently without coordinating through a central authority, eliminating a single point of failure. API request tracing relies on correlation IDs -- typically UUID v4 -- injected at the API gateway and propagated through every downstream service so that a single search surfaces the complete request path across logs. Payment platforms like Stripe and PayPal require idempotency keys (often UUIDs) to ensure that retried requests do not result in duplicate charges. UUIDs are equally useful as session tokens, file names in object storage buckets (preventing collisions when thousands of users upload simultaneously), message queue deduplication keys in systems like Kafka or SQS, and temporary resource identifiers for presigned URLs or short-lived access grants. In frontend applications, UUID v4 is commonly used to generate stable React list keys for dynamically created elements without depending on array indices.

UUID vs Other Identifier Formats

UUID v4 is the safe default, but it is not always the best choice. Auto-increment IDs are compact and fast for indexed lookups, yet they expose business data -- a competitor can estimate your order volume by creating two accounts a week apart and diffing the user IDs. UUID v7 solves a key UUID v4 weakness: because v4 values are random, inserting them as a clustered primary key in PostgreSQL or MySQL causes B-tree page splits and write amplification. UUID v7's time-ordered prefix keeps inserts sequential. ULID (Universally Unique Lexicographically Sortable Identifier) offers similar time-sorting in a shorter, Crockford Base32 encoding (26 characters vs. 36), making it popular in DynamoDB and other systems where key length matters. Nano ID is a 21-character, URL-safe string using a 64-character alphabet, which provides roughly 126 bits of entropy in fewer characters than a UUID -- ideal for short URLs and client-generated tokens. CUID2 is specifically designed for horizontal scaling, using a hash-based approach that resists collision even under high-concurrency ID generation. Snowflake IDs, pioneered by Twitter and used by Discord, pack a timestamp, machine ID, and sequence number into a 64-bit integer, giving time-sortability with the storage efficiency of a bigint column. Choose UUID v4 when broad compatibility matters, UUID v7 or ULID for time-sorted database keys, Nano ID when brevity counts, and Snowflake when you need a compact numeric ID at massive scale.