UUID Parser
Parse Nil, Max, and UUID versions 1 through 8 into normalized text, bytes, version, variant, semantic kind, and available time or DCE fields.
Description
Parse a canonical UUID into normalized text, its 16 byte values, the version nibble, and the variant.
The UUID textual form contains structural information in fixed bit positions. This parser accepts the canonical 8-4-4-4-12 hexadecimal form, normalizes letters to lowercase, and exposes fields that help diagnose which UUID family produced a value.1
When to use UUID Parser
Use the parser while debugging identifiers, checking migrations, inspecting unknown UUIDs, or confirming that a generator set expected version and variant bits.
How UUID Parser works
After validating the hyphenated hexadecimal layout, the parser removes hyphens and converts each pair of digits to one byte. The high nibble of byte 6 is the version; the leading pattern of byte 8 identifies the NCS, RFC, Microsoft, or future-reserved variant.1
How the UUID parsing function processes input
- Verify exactly 32 hexadecimal digits in the 8-4-4-4-12 layout.
- Normalize hexadecimal letters to lowercase.
- Convert each digit pair into one of 16 bytes.
- Read version bits 48–51 and classify the variant from the leading bits of byte 8.
Limitations and assumptions
- A syntactically valid UUID is not proof that it was generated correctly or is unique.
- Version interpretation is most meaningful for the RFC variant; other variants may define different subtypes.
- Parsing does not authenticate, resolve, or look up the identifier.
Alternative or Complementary approaches
Use UUID Validator for a simple yes/no check. Use the v4 or v7 generator when creating new identifiers.
References
-
RFC 9562: Universally Unique IDentifiers (UUIDs) — RFC Editor
Similar or alternative tools
- UUID v4 Generator
Generate random-layout UUIDs.
- UUID v7 Generator
Generate time-ordered UUIDs.
- UUID Validator
Validate or inspect a UUID using the complementary operation.