UUID v6 Generator
Generate time-sortable v6 UUIDs — v1's fields reordered for index locality, decoded live, entirely on this device.
Decoded fields
- Timestamp
- —
- 100-ns ticks
- —
- Clock sequence
- —
- Node
- —
A fresh random node per UUID — never a hardware MAC address (RFC 9562 §6.10).
Press ? for shortcuts
Do it offline:$ npx uuid v6
How to use it
- Generate 1 to 100,000 v6 values; batches over 10,000 run in a background worker.
- Read the decoded timestamp, clock sequence and node in the strip beneath the output.
- Copy or download the batch — all five family notations apply to v6 as well.
UUID v6 is v1 with its timestamp written high bits first, so values finally sort in time order. Everything else — the clock sequence, the node, the Gregorian epoch — stays where v1 put it. Generate up to 100,000 here, then compare the decoded twin pair in the examples.
How it works
Take a v1 value and reorder one field: the 60-bit tick count, stored low-32/mid-16/high-12 in v1, becomes high-32/mid-16/low-12 in v6. The clock sequence and node do not move.
That single swap makes the encoded bytes big-endian in time, so v6 sorts chronologically as text while staying decodable by anything that knows v1's fields.
Examples
1f188205-ca76-6000-ab0d-0f1e2d3c4b5aversion = v6
timestamp = 2026-07-25T12:00:00.000Z
clock sequence = 11021
node = 0f:1e:2d:3c:4b:5aA fixed v6 vector decoded — hold onto these three field values for the next example.
5ca76000-8820-11f1-ab0d-0f1e2d3c4b5aversion = v1
timestamp = 2026-07-25T12:00:00.000Z
clock sequence = 11021
node = 0f:1e:2d:3c:4b:5aThe identical instant, sequence and node as example 1 — the same fifteen timestamp digits dealt out in the opposite order.
Every example on this page is executed against the same engine that powers the tool, on every build.
Gotchas worth knowing
Node behavior differs from v1 here
RFC 9562 lets v6 keep v1's node for continuity, but the generator on this page draws fresh random node bits for every value instead — decode a batch and watch the last block change.
Common errors
100,000 is the browser-side cap — need more? script it: `npx uuid v6`- Each version's refusal names its own CLI verb, so the escape hatch is copy-paste ready.
Count must be a whole number between 1 and 100,000.- Guards state arriving from links and storage; the field itself never lets it happen.
FAQ
What is the difference between v6 and v1?
Field order, nothing more: both carry the same Gregorian timestamp, clock sequence and node. v6 leads with the high timestamp bits so that text order equals time order.
Should I use v6 or v7?
v7 for anything new — Unix milliseconds plus randomness is simpler. v6 earns its keep when v1-shaped fields must survive, like migrating keys an existing decoder still inspects.
How widely is v6 adopted?
The narrowest of the new RFC 9562 versions: libraries ship it, including the one here, but most new designs skip to v7 — as the RFC itself suggests.