How this calculator works
- Step 1Start with the time48 bitsMilliseconds since 1970, so newer IDs sort later.
- Step 2Add randomness74 bitsFrom your browser’s secure random generator.
- Step 3Mark the version4 + 2 bitsThe version digit and the variant bits.
A UUID is a 128-bit identifier that systems can create on their own without asking a central server, with a vanishingly small chance of two being the same.
Worked example: the RFC 9562 sample
017f22e2-79b0-7cc3-98c4-dc0c0c07398f was made at 2022-02-22T19:22:22Z: the time is written in its first 12 hex digits.
- Layout
tttttttt-tttt-7rrr-Vrrr-rrrrrrrrrrrr
- First 12 hex digits017f22e279b0
- As milliseconds1645557742000
- Version digit (13th)7
- VariantRFC 9562
- Made at2022-02-22T19:22:22Z
Reading the result
- Version 7Time-orderedSorts by creation time, which keeps database indexes compact.
- Version 4Fully randomReveals nothing about when it was made.
- Secure randomnessMade with crypto.getRandomValues on your device.
- Not a secretUUIDs are identifiers, not passwords or tokens.
- v7 reveals timeAnyone can read when a version 7 UUID was made.
- Never storedNew UUIDs each time; nothing is saved or sent.
Related developer tools
A UUID is a unique identifier, not a secret. Passwords and hashes serve different purposes.
For a secret, use the password generator. The hash generator fingerprints data, and the Unix timestamp converter reads millisecond timestamps like the one in a version 7 UUID.
Common mistakes
Mistake: Using a UUID as a password-reset or session token.
Instead: Use a dedicated secret token from a security library.
Mistake: Using version 7 where the creation time is private.
Instead: Use version 4 so no time is exposed.
Mistake: Comparing UUIDs case-sensitively.
Instead: Treat upper and lower case as the same value.
Read how we test our calculators, or browse more developer tools.