UUID Validator
Validate one or many UUIDs with a specific reason for any failure, full version/variant/timestamp decode, and an equality checker.
What this tool does
Checks whether one or more UUIDs are genuinely well-formed, and if one isn't, says specifically why -- wrong length, a hyphen in the wrong place, an invalid version nibble, or variant bits that don't match RFC 9562/4122 -- rather than a bare valid/invalid verdict. Every valid UUID also gets decoded: its version and what it means, its variant, the exact embedded timestamp for version 1, 6 and 7, and alternate representations -- plain hex (no hyphens), Base64, a 128-bit integer, and a byte array.
The v1/v6 privacy concern
Version 1 and 6 UUIDs embed the generating machine's node ID and the exact creation timestamp. This tool checks the node field's multicast bit and tells you whether it looks like a real hardware MAC address or a randomly generated stand-in -- either way, exposing a v1/v6 UUID to an untrusted party can leak when and (sometimes) from which machine it was created, a well-documented fingerprinting concern that's a real reason to prefer v4 or v7 for anything user-facing.
Batch validation and duplicate detection
Paste several UUIDs, one per line — a database export, a log file, a CSV column — and each is checked and decoded independently, so you can spot the one malformed row in a list of thousands without checking them by hand. Any UUID that appears more than once in the list (after normalizing format and case) is flagged as a duplicate, useful for catching an accidental copy-paste or a genuine collision in generated data. Results export as a single text file.
Accepted formats, examples, and history
Input is normalized before validation, so a UUID with braces
({550e8400-...}), a urn:uuid: prefix,
no hyphens at all, or any mix of upper/lowercase all validate the
same way a plain hyphenated UUID would. One-click example chips
insert a correctly structured sample of each version (v1 through
v8, plus NIL and MAX) so you can see how each decodes without
needing a real one on hand. A session-only history
keeps the last 8 UUIDs validated, and any valid result can be shown
as a QR code for moving it to another device.
Comparing two UUIDs
Two UUID strings can represent the exact same identifier while looking different on the page — one uppercase, one with braces, one missing hyphens. The equality checker normalizes both before comparing, so you get a straight yes/no on whether they're actually the same UUID, not a string-literal diff that would wrongly say they don't match.
Privacy
Everything runs locally in your browser. The session history
lives only in this tab's memory -- never written to
localStorage or sent anywhere. Nothing is uploaded.