UUID (Universally Unique Identifier, RFC 4122) is a 128-bit identifier displayed as 32 hexadecimal digits in five groups: xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx. UUID v4 generates all 122 variable bits randomly, making it the standard choice for unique IDs that require no central registry.
What is a UUID?
A UUID (Universally Unique Identifier) is a 128-bit label used to identify information in computer systems. The standard format is 32 hexadecimal digits displayed in five groups separated by hyphens:
xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx
UUID v4 is the most widely used version. All 122 variable bits are randomly generated, making collisions statistically impossible in practice. It is used for database primary keys, session tokens, file names, and distributed system IDs.
UUID v4 vs other versions
- v1 — Based on timestamp + MAC address. Predictable, not recommended for security-sensitive IDs.
- v3 / v5 — Deterministic, namespace-based (MD5 or SHA-1). Used when you need the same ID for the same input. This tool supports v5.
- v4 — Randomly generated. The default choice for database keys and unique tokens.
- v7 — Timestamp-sortable random UUID. Increasingly used in databases for index efficiency.
This generator supports v1, v4, v5, and v7 above — pick a version from the selector, and for v5 provide a namespace and name.
Use cases
- Database primary keys (PostgreSQL
uuidtype, MongoDB ObjectId alternative) - REST API resource identifiers (
/users/550e8400-e29b-41d4-a716-446655440000) - Session and token IDs
- Idempotency keys for payment APIs
- File names for uploaded assets
Frequently Asked Questions
What is a UUID v4?
UUID v4 is a randomly generated 128-bit identifier formatted as five hyphen-separated groups of hexadecimal characters (e.g. 550e8400-e29b-41d4-a716-446655440000). All 122 variable bits are randomly generated, making it the most commonly used UUID version for generating unique IDs without a central registry.
Are the generated UUIDs truly unique?
Yes. This tool uses crypto.randomUUID(), which relies on the browser's cryptographically secure random number generator. The theoretical chance of generating two identical UUID v4 values is approximately 1 in 5.3 × 10³⁶ — effectively zero in any practical scenario.
What is the difference between UUID and GUID?
GUID (Globally Unique Identifier) is Microsoft's name for the same concept. UUID and GUID refer to the same 128-bit identifier format defined by RFC 4122. The terms are interchangeable in practice.
What is UUID v7 and how is it different from v4?
UUID v7 encodes a millisecond-precision Unix timestamp in the first 48 bits, making UUIDs time-sortable. This improves database index performance because new rows are always appended at the end of an index rather than inserted in random positions. Use v7 when you need sortable IDs; use v4 when ordering does not matter. Read more: UUID v4 vs v7 explained.
Can I use a UUID as a database primary key?
Yes. UUID v4 is widely used as a primary key in PostgreSQL (uuid type), MySQL, and MongoDB. The main trade-off is index fragmentation — because v4 values are random, each insert goes to a random B-tree position, which can slow inserts at high volume. UUID v7 avoids this by being time-sortable.
Is my data sent to a server?
No. UUID generation happens entirely in your browser using the native crypto.randomUUID() API (v4) or the Web Crypto SubtleCrypto API (v1, v5, v7). Nothing is transmitted to any server.
Is UUID v5 deterministic?
Yes. UUID v5 is generated from a namespace UUID plus a name string, hashed with SHA-1. The same namespace and name always produce the exact same UUID — useful for generating a stable, repeatable ID for a given input (e.g. a URL or domain name) without needing to store a lookup table. UUID v4 and v7 are random and not repeatable.
Does UUID v1 use my real MAC address?
No. RFC 4122 allows a real network-card MAC address in the node field, but browsers have no access to it. This tool generates a random 48-bit node ID instead, with its multicast bit set (per RFC 4122 section 4.5) to mark it as randomly generated rather than hardware-derived — so UUID v1 values from this tool are not traceable to a real device.
Last updated: July 2026