Validate UUIDs and find out what kind they are. Paste one or a whole list and each is checked for format, version and variant, with a plain reason when it fails. Time-based UUIDs — versions 1, 6 and 7 — have their creation time decoded, and nil and max UUIDs are recognized. Braces, uppercase and urn:uuid: are all accepted. It's free, runs in your browser, and nothing leaves your device.
| Version | Based on | Sortable |
|---|---|---|
| 1 | Timestamp + node | No |
| 3 | MD5 of a name | No |
| 4 | Random | No |
| 5 | SHA-1 of a name | No |
| 6 | Reordered timestamp | Yes |
| 7 | Unix ms timestamp + random | Yes |
| 8 | Custom | Depends |
It's the first character of the third group: 4 in xxxxxxxx-xxxx-4xxx-…, for example.
The first character of the fourth group. Standard UUIDs use 8, 9, a or b; other values belong to legacy or reserved layouts.
For versions 1, 6 and 7, yes — the tool decodes it. Version 4 is random and has none.
Yes. UUIDs are case-insensitive, and {…} braces and urn:uuid: are common wrappers.
No. Validation runs in your browser.
A UUID is 32 hexadecimal digits in groups of 8-4-4-4-12. Beyond the format, two fields decide whether it's a standard UUID: the version, the first digit of the third group, and the variant, the first digit of the fourth, which must be 8, 9, a or b for the RFC 9562 layout (earlier RFC 4122). The validator checks both and reports which is wrong, rather than just rejecting the string, and distinguishes missing hyphens, non-hex characters and wrong lengths. It accepts uppercase, braces and the urn:uuid: prefix. The nil UUID (all zeros) and max UUID (all f's), both defined in RFC 9562, are recognized. Versions 1, 6 and 7 carry a timestamp, which is decoded and shown: v7 as Unix milliseconds in its first 48 bits, v1 and v6 as 100-nanosecond intervals since the start of the Gregorian calendar in 1582 — useful when debugging, and a reminder that these UUIDs reveal when they were created. The RFC's own test vectors are part of the tool's tests.