UUID Inspector guide
Validate canonical UUID syntax and inspect the version nibble, variant bits, nil status, and hexadecimal bytes.
What this tool does
The UUID Inspector accepts the familiar five-group hexadecimal form, optionally surrounded by braces or prefixed with urn:uuid:. It normalizes letters to lowercase, validates the group lengths, identifies an all-zero nil UUID, reads the version nibble, classifies the variant bits, and displays the sixteen bytes in hexadecimal order.
Versions 1 through 8 are reported from the version field. The variant is described as NCS compatibility, RFC 4122/RFC 9562, Microsoft compatibility, or future/reserved according to its leading bits. The inspector reports an unknown or reserved version when the nibble falls outside the currently recognized range.
Syntax and bit inspection cannot prove that an identifier was generated correctly, is globally unique, belongs to a claimed record, or is safe to trust. A person can type a value with valid version and variant bits. Validate identifiers within the application and data model that use them.
How to use it
- Paste one UUID into the input.
- Select Inspect UUID.
- Confirm the normalized value, version, and variant.
- Check nil status and raw bytes if relevant to debugging.
- Copy the normalized UUID for use in a case-consistent workflow.
This tool handles one identifier at a time. Use a schema-aware validator or test suite when validating a database column, API payload, or large collection.
Benefits
- Validates canonical group structure
- Accepts braces and UUID URN prefixes
- Reports recognized version and variant fields
- Detects the special all-zero nil value
- Displays the underlying sixteen bytes
- Performs inspection without a network request
Interpreting the result
Version describes the layout indicated by four identifier bits, not a guarantee about how all remaining bits were produced. Some versions encode time or namespace-derived information; others are random or sortable designs. Use the specification for that version before decoding or making assumptions about embedded data.