UUID Validator
Validate UUID format/version in bulk for API payload and DB QA
Paste one UUID per line and check valid vs invalid first; version breakdown and fix comparisons are available in Advanced mode.
The full guide also includes pitfalls, worked examples, snippets, FAQs, and related tools for checking results or troubleshooting.
About this tool
Check one UUID per line for hexadecimal grouping, RFC variant and version 1–8. Nil and Max are recognized as special values without a regular version. Advanced options accept compact 32-digit input and UUID URNs; enclosing braces are accepted. Results show lowercase canonical text. These are structural checks: the tool does not validate embedded timestamps, namespace hashes, uniqueness or origin. Input and options are saved in this browser until cleared.
Failure Clinic (Common Pitfalls)
Structural validity is limited
Cause: A v7-shaped value can contain an arbitrary timestamp and a valid-looking v5 can contain an arbitrary hash.
Fix: Verify protocol-specific fields and business constraints in the system that owns the IDs.
Scenario Recipes
Check a mixed-version fixture
Goal: Find unsupported structure before importing test identifiers.
- Paste 550e8400-e29b-71d4-a716-446655440000 and 00000000-0000-0000-0000-000000000000 on separate lines.
- Run validation; expect v7 and Nil.
- Open Advanced and inspect the normalized values and structural scope.
Result: A passing shape does not prove how the ID was produced.
Production Snippets
Example
text
550e8400-e29b-71d4-a716-446655440000 → v7
00000000-0000-0000-0000-000000000000 → NilFrequently Asked Questions
Which UUID values are accepted?
RFC-variant UUIDs with versions 1–8, plus the Nil all-zero and Max all-one special UUIDs. Nil and Max are labeled separately, not as v0 or v15.
Does valid mean the UUID was generated correctly?
It means the text shape, version and variant match the supported scope. Embedded timestamp/hash/application fields, provenance and uniqueness are not verified.
Can I paste uppercase, compact, braced or URN values?
Hexadecimal is case-insensitive. Braces are accepted. Advanced options control 32-digit compact input and urn:uuid: prefixes. Accepted results use lowercase hyphenated text.
Can I check a batch and inspect errors?
Paste one value per line. Blank lines are skipped. Advanced mode shows format, unsupported-version or unsupported-variant feedback and counts for v1–v8.
What happens when I change the input?
Old results are cleared. Run validation again so the displayed result belongs to the current input and options.
Are IDs uploaded or retained?
Validation runs locally and does not send ID contents to a backend. Input and options are stored in this browser’s localStorage; Clear removes the saved draft.
Keep browsing