Skip to content
TextArray
100% local

UUID decoder

Decode a UUID to reveal its version, variant and embedded timestamp.

Input
Output

UUID decoder

Paste any UUID and the decoder tells you what it actually is: its version, its variant and — for time-based UUIDs — the exact moment it was generated. A random-looking string like 018f6d2e-7a00-7000-8000-000000000000 becomes readable, showing that it is a version 7 UUID whose first 48 bits encode a Unix millisecond timestamp you can read as an ISO 8601 date.

The tool recognises every current version. Version 1 and version 6 carry a 60-bit Gregorian timestamp, which is converted back to UTC; version 7 stores plain Unix milliseconds; versions 3 and 5 are name-based (MD5 and SHA-1); version 4 is fully random, and the tool says so rather than inventing a meaning. The special nil (all zeros) and max (all ones) UUIDs are labelled too. The variant field is read from the RFC 4122 layout, so you can tell an RFC UUID from a legacy NCS or Microsoft GUID at a glance.

Paste is forgiving. Surrounding whitespace, curly braces from a C# GUID, a urn:uuid: prefix and uppercase letters are all accepted and normalised to canonical lowercase. Put one UUID per line to decode a whole batch at once; blank lines are skipped and anything that is not a valid UUID gets a short, plain reason — wrong length or an unexpected character — so a bad paste never derails the rest.

Turn on "Show raw fields" when you want the underlying hex: the time bits and the random or node bits, split out for debugging. Everything runs entirely in your browser — no UUID is ever sent to a server.

FAQ

Which UUID versions can it decode?
Versions 1 through 8, plus the special nil and max UUIDs. It reads the version and variant of any of them, and extracts the timestamp from v1, v6 and v7.
How does it read the timestamp?
For v1 and v6 it converts the 60-bit Gregorian clock (100-nanosecond ticks since 1582) back to UTC; for v7 it reads the first 48 bits as Unix milliseconds. Results are shown as ISO 8601.
Can I decode several UUIDs at once?
Yes. Put one UUID per line and each is decoded into its own block. Blank lines are ignored and invalid lines are flagged with the reason, so one bad entry does not stop the others.
Does it accept braces, urn:uuid: and uppercase?
Yes. Curly braces, a urn:uuid: prefix, surrounding spaces and uppercase are all tolerated and normalised to the canonical lowercase 8-4-4-4-12 form.
Is my UUID uploaded anywhere?
No. Decoding happens entirely in your browser and no UUID ever leaves your device.