UUID generator / validator
Create v4 or v7 UUIDs, or look inside one you already have. Understand its version, variant, and embedded v7 timestamp.
Generate UUIDs
Choose random v4 or time-ordered v7 identifiers.
122 random bits. No embedded time.
0 UUIDs · one per line
Validate a UUID
Check its structure, version, and embedded v7 time.
Paste a UUID to check it.
UUIDs stay in page memory. No input is sent to a server or analytics, saved in a URL, or stored in your browser. Copy writes only the selected output to your clipboard.
UUIDv4 or UUIDv7: which should I use?
A UUID is a 128-bit identifier, usually written as 32 hexadecimal digits in 8-4-4-4-12 groups. The version describes how its payload is arranged; the variant identifies the layout family.
- v4 · Random identifiers
- 122 random bits with no embedded creation time. Useful for general identifiers, fixtures, and cases where exposing a timestamp is undesirable. This page uses
crypto.randomUUID(). - v7 · Time-ordered identifiers
- A 48-bit Unix-millisecond timestamp followed by version, variant, and 74 bits available for randomness or sequencing. Useful for database keys where time locality helps, and fixtures that carry a readable clock value.
- Inspect a pasted value
- Validate versions 1–8 and Nil/Max, normalize text, and read v7 time in UTC and Unix milliseconds. Accepts mixed case,
{GUID}wrappers, or aurn:uuid:prefix. Outer whitespace is ignored.
Generate a batch or understand a UUID
Choose v4 or v7, select 1–100 values, then generate and copy one UUID per line. Changing the version clears the previous output. Use Validate this UUID to inspect the first generated value, or paste your own. The v4 and v7 examples are public test values, not newly generated identifiers.
The v7 example 017f22e2-79b0-7cc3-98c4-dc0c0c07398f starts with timestamp 0x017f22e279b0: 1645557742000 milliseconds, or . The next digit, 7, is the version. The fourth group starts with 9 (binary 1001): its top two bits, 10, select the RFC variant. Those fixed version and variant bits leave 74 payload bits.
Time ordering and its limits
This page reads Date.now() separately for each v7 UUID and fills all 74 remaining bits using crypto.getRandomValues(). It uses fresh randomness even when several values share a millisecond; it has no counter or saved generator state. The batch keeps generation order rather than sorting the output.
Byte order, or ordinary lexical order of consistently lowercase canonical v7 strings, follows the encoded timestamp. Same-millisecond values from this generator sort randomly. If the device clock moves backward, later values can sort before earlier ones. Different devices can have different clocks. This tool does not guarantee monotonic order, a global event sequence, or collision-free generation.
The timestamp uses milliseconds since 1970-01-01 UTC, excluding leap seconds. It is an encoded clock reading, not verified creation time. A forged or inaccurate timestamp is still structurally valid. Other v7 implementations may use part of the 74-bit field for counters or sub-millisecond precision; inspecting one value cannot identify that policy.
Validation, uniqueness, and appropriate uses
Validation checks spelling, supported version, and variant bits. It cannot establish entropy, uniqueness, ownership, or authenticity. Nil and Max are special sentinel values, not generated identifiers. Other legacy or reserved variants are outside this validator’s scope. Only v7 timestamps are decoded here; v4 contains no timestamp.
Use UUIDs to identify records, test data, or correlate events. Keep a database uniqueness constraint where duplicates matter, and check your database’s UUID comparison behavior before relying on sort order. UUIDs are not passwords, access tokens, or authorization checks. Public v7 values expose their encoded time; choose v4 when that disclosure is unwanted.
Local processing and privacy
Pasted and generated UUIDs stay in page memory. This tool does not send them to a server, analytics, or logs, or store them in URLs or persistent browser storage. Clear removes pasted input and inspection details; leaving the page clears tool values. Copy buttons explicitly write output to your clipboard, which your device or clipboard manager may retain.
Generation requires browser Web Crypto, with no weak random fallback. Use HTTPS or localhost for native v4 generation. Read the UUID specification, especially the v7 layout and ordering guidance.
Related browser tools
- JWT explorer / creator — Inspect JWT claims and timestamps, create HS256 tokens, and check signatures locally.
- Timestamp converter — Convert Unix seconds, milliseconds, and ISO dates with UTC and local timezone output.