Invalid UUID Format – Check UUID Syntax Online

Local only

Explain the UUID validator's canonical format check with a real invalid input.

10 chars · 1 line

Needs attention

Invalid UUID format

UUID validation

Why is this UUID format invalid?

A canonical UUID contains 32 hexadecimal characters separated into 8-4-4-4-12 groups. VetaTool first checks that exact textual layout before reading version or variant bits, so arbitrary text and incomplete identifiers fail as an invalid UUID format. This tool is free to use. No account or payment is required.

Last updated

What you can do here

  • Canonical 8-4-4-4-12 UUID validation
  • UUID version inspection
  • RFC 4122 variant checking
  • Nil UUID recognition
  • Uppercase hexadecimal support
  • Browser-local validation

Steps

  1. Paste the UUID text into the validator.
  2. Check whether it follows the 8-4-4-4-12 hexadecimal layout.
  3. Fix textual formatting before interpreting version or variant bits.

Canonical UUID text has a fixed shape

The validator expects hexadecimal digits in five groups separated by four hyphens. Characters outside 0-9 and A-F, missing groups, extra text, or an otherwise different layout fail the format check.

A format pass only means the text can be inspected further. Version and RFC variant checks are separate steps.

Invalid UUID format example

The input does not have canonical UUID structure.

UUID input

not-a-uuid

Validation result

Invalid UUID format

Common questions

Frequently asked questions

How many characters are in a canonical UUID?

There are 36 visible characters including four hyphens: 32 hexadecimal characters in 8-4-4-4-12 groups.

Does a canonical shape guarantee a valid RFC UUID?

No. VetaTool also inspects the version nibble and RFC 4122 variant range after the format matches.

Debugging a specific UUID issue? Browse UUID troubleshooting.