Read the structure of a UUID
Paste one hyphenated UUID and select Inspect UUID. The result separates the normalized identifier, variant, special value and version-position bits. For an ordinary RFC-layout version 7 UUID, it also shows the embedded Unix millisecond value and its UTC representation. Expand the JSON report or download it when you need machine-readable fields.
This tool accepts upper- or lowercase hexadecimal with groups of 8, 4, 4, 4 and 12 digits. Leading and trailing whitespace is ignored. Braces, a urn:uuid: prefix, a compact 32-digit value and multiple identifiers are rejected so the accepted format stays explicit.
Try a UUIDv7 example
Load example replaces the input with 017f22e2-79b0-7cc3-98c4-dc0c0c07398f. Inspect UUID reports the RFC layout, version 7 and Unix time 1645557742000. The UTC timestamp is 2022-02-22T19:22:22.000Z. Changing any input clears the previous report before another inspection.
Interpret version and variant separately
The variant comes from the leading bits of the fourth group. The raw version-position nibble is displayed even for another layout, but it is only interpreted as an RFC version for ordinary RFC-variant values. All-zero and all-one values are identified separately as Nil and Max. A reserved or unassigned pattern is reported as such rather than called a supported generated UUID.
The field definitions and example follow RFC 9562. Timestamp decoding here is deliberately limited to version 7; the result says Not decoded for versions 1 and 6 even though those formats also carry time information. A version 8 value may contain application-defined data that this page cannot interpret.
What inspection cannot establish
An identifier with the expected layout can still be fabricated, duplicated or generated incorrectly. Its bits cannot prove a database record exists or that an embedded time reflects an actual event. The UTC field describes encoded milliseconds, not the local timezone or a verified creation date. The page does not assess randomness or contact a registry.
For raw diagnostic bytes rather than UUID fields, use the Random Byte Generator. Its output is arbitrary binary data; adding hyphens alone does not give it a particular UUID version.





