UUID Generator and Inspector
Generate version 4 and version 7 UUIDs locally under RFC 9562, or paste any UUID into the inspector to see its well-formedness, version, variant, and — for v1 and v7 — the moment it encodes. All randomness comes from this device's cryptographic source; nothing is sent or stored, and a reload wipes everything.
Generator
UUIDs are identifiers, not passwords or tokens; never use one to protect anything. Click any result to load it into the inspector below and verify it in place.
Inspector
How it works and its limits
- Only v4 and v7 are generated: v1 embeds a device identifier and a guessable timestamp; v3 and v5 are name hashes, which belong to a hashing tool; v6 is a reordered v1 for legacy systems; v8 is vendor-defined. The inspector still recognises every version.
- v7 values created in the same millisecond share the same timestamp prefix and differ only in random bits; no ordering is promised within a batch.
- Inspection is strict: only the 36-character hyphenated form or the 32-character hex form is accepted; { } braces and urn:uuid: wrappers are unsupported and rejected.
- The report says "well-formed" only: a well-formed UUID can be forged by anyone, and this tool verifies no authenticity or identity.
- Version 6 reorders the time fields; the inspector names the version but does not decode its timestamp.
- Generated batches and inspected values live in memory only — never in the URL, never in any storage.