UUID Generator
Generate random v4 or time-ordered v7 UUIDs in bulk, or decode any UUID to read its version, variant and the time hidden inside it.
How to Use
- Choose Generate to make new UUIDs or Decode to read one you already have.
- To generate, pick the version — v4 (random), v7 (time-ordered) or Nil — and how many you need (1–500). Tick UPPERCASE or {braces} for the Microsoft GUID style.
- Press Generate. Click any row to copy that UUID, or press Copy all for the whole list, one per line.
- To decode, paste a UUID in any common form (with or without hyphens, braces, capitals or
urn:uuid:). The version, variant and any embedded timestamp appear at once. - The coloured digits show which bits are time, version, variant and random; Show Work explains each one.
Worked Example
Decode the version 7 example from RFC 9562: 017f22e2-79b0-7cc3-98c4-dc0c0c07398f.
Drop the hyphens to get 32 hex digits = 128 bits.
The first 12 digits, 017f22e279b0, are the timestamp: hex 017F22E279B0 = 1,645,557,742,000 milliseconds after 1 January 1970 = 22 February 2022, 19:22:22.000 UTC.
Digit 13 is 7 (binary 0111): version 7.
Digit 17 is 9 (binary 1001): it starts with the bits 10, so this is the standard RFC 9562 variant.
What is left is random: 12 bits after the version digit and 62 bits after the variant bits, 74 in all (128 − 48 − 4 − 2).
A version 4 UUID, 550e8400-e29b-41d4-a716-446655440000: digit 13 is 4, digit 17 is a (1010, variant 10). Everything else — 128 − 4 − 2 = 122 bits — is random, so there is no time inside it.
The common mistake: counting characters instead of hex digits. The 13th character of 550e8400-e29b-41d4-… is b, because the first hyphen takes position 9. The version is the 13th hex digit, which is the 15th character: the first digit of the third group.
Show Work
Formulas
Forty Years of 128-Bit IDs
UUIDs began in Apollo Computer’s Network Computing System in the 1980s, which needed identifiers that many machines could create without talking to each other. The 128-bit design combined a timestamp with the machine’s network address — what became version 1. The Open Software Foundation’s Distributed Computing Environment adopted it, and Microsoft used it for the GUIDs in COM.
RFC 4122 (2005) defined versions 1 to 5. Version 4, purely random, won in practice because it needs no clock or network address and reveals nothing. As databases grew, its randomness became a cost: each new key lands at a random place in a B-tree index. Time-ordered schemes such as Twitter’s Snowflake (2010) and ULID (2016) followed, and RFC 9562 (May 2024) replaced RFC 4122 and added versions 6, 7 and 8. PostgreSQL 18 (2025) added a built-in uuidv7() function.
Versions 1 and 6 count time in 100-nanosecond steps from 15 October 1582, the day the Gregorian calendar began; version 7 uses plain Unix milliseconds, which is why it is the one most systems now choose.
About This Tool
This tool generates version 4, version 7 and Nil UUIDs, up to 500 at a time, using the browser’s cryptographic random source (crypto.getRandomValues). Version 7 UUIDs follow RFC 9562 exactly; within one batch, UUIDs made in the same millisecond use the 12 bits after the version digit as a counter (the RFC’s method 1), so the whole list sorts in the order it was made.
Decode reads any UUID: versions 1 to 8, the Nil and Max UUIDs, and the old NCS and Microsoft variants. For versions 1, 6 and 7 it turns the embedded timestamp into a date. Everything runs in your browser; nothing you generate or paste is sent anywhere.
Related tools: Password Generator, Multi-Hash Generator, and JWT Decoder.
Frequently Asked Questions
What is the difference between UUID v4 and v7?
A v4 UUID is 122 random bits plus 6 fixed bits that mark the version and variant. A v7 UUID (RFC 9562, May 2024) starts with a 48-bit Unix timestamp in milliseconds, then 74 random bits. Because the time comes first, v7 UUIDs sort in the order they were made, which keeps database indexes compact; v4 UUIDs land at random places in the index.
Can two UUIDs ever be the same?
In theory yes, in practice no. A v4 UUID has 2122 ≈ 5.3 × 1036 possible values, so you would need about 2.71 × 1018 of them before there is a 50% chance of a single repeat — one billion every second for 86 years. That assumes a good random source; this tool uses crypto.getRandomValues.
How can I tell which version a UUID is?
Look at the 13th hex digit, the first digit of the third group: in 550e8400-e29b-41d4-a716-446655440000 it is 4, so it is a v4 UUID. The 17th hex digit gives the variant: 8, 9, a or b (binary 10xx) means the standard RFC 9562 layout. Count hex digits, not characters — the hyphens are not part of the 128 bits.
Is a GUID the same as a UUID?
Yes. GUID is Microsoft’s name for the same 128-bit identifier, usually written in capitals inside braces, such as {550E8400-E29B-41D4-A716-446655440000}. One trap: when Windows stores a GUID as 16 raw bytes, the first three groups are little-endian, so the bytes on disk start 00 84 0E 55 rather than 55 0E 84 00. The text form is identical.
Should I store UUIDs as text or binary?
Binary where you can. The text form is 36 characters; the binary form is 16 bytes, less than half the size, and indexes faster. PostgreSQL has a native uuid type, SQL Server has uniqueidentifier, and in MySQL use BINARY(16) with UUID_TO_BIN() rather than CHAR(36).
How do I use the UUID Generator?
Just pick your options. The answer shows up right away — there is no button to press. Change anything and it updates by itself.
Do I need to install or sign up for anything?
Not at all — it runs in the browser with nothing to install and no account. After it loads once, it even works without an internet connection.
Is my information private?
Yes. Everything happens in your browser. Nothing you type is sent to a server or saved anywhere.
Common Use Cases
Database primary keys
Use v7 so new rows go to the end of the index like an auto-increment, while any server can create IDs without asking the database. 500 UUIDs from one batch here sort in the order they were made.
Finding when a record was created
Paste a v7 ID from a log or URL into Decode: the first 12 hex digits are the creation time to the millisecond, with no database lookup.
Request and correlation IDs
Tag each API request with a UUID so log lines from five different services can be joined into one trace.
Test fixtures
Generate up to 500 IDs at once for seed data, then Copy all to paste them one per line into a CSV or SQL script.
Idempotency keys
Send a fresh v4 UUID with each payment or order request so a retried request is recognised and not charged twice.
Last updated: