UUID v6 Generator
Generate time-ordered UUID v6 identifiers instantly. Encodes a reordered timestamp for lexicographic sorting (RFC 9562) — entirely in your browser.
Part of WebEasier's UUID Generator suite — the most complete UUID toolkit on the web.
UUID v6 Generator
Timestamp + Random Node ·crypto.getRandomValues()
All UUIDs generated locally in your browser. Node field uses a cryptographically random 48-bit value (not a real MAC address).
Your UUID v6 values will appear here.
Set a quantity and click Generate.
What is a UUID v6?
A UUID v6 (version 6) is a time-ordered UUID defined by RFC 9562. It stores a 60-bit timestamp in the most-significant bits by reordering fields from v1, then adds a version=6 nibble and standard variant. The 13th character is always '6'.
Version Bit
13th char = '6'
xxxxxxxx-xxxx-6xxx-yxxx-…
Timestamp
60-bit
100ns intervals since
15 Oct 1582
Node Field
48-bit
MAC address or random (this tool uses random)
Standard
RFC 4122
IETF specification
What is a UUID v6?
UUID version 6 is the modern time-ordered UUID format from draft RFC 9562. It takes the same components as UUID v1 (timestamp, clock sequence, and node) but rearranges the timestamp bits so that lexicographic sorting of the entire identifier matches chronological order.
Because the most‑significant bits are the timestamp, UUID v6 works well with B-tree indexes, time-series databases, and any system that benefits from naturally sortable keys.
Like v1, v6 includes a 48‑bit node field (this tool uses a random value to protect privacy) and a 14‑bit clock sequence. It is not suitable for secret tokens.
For fully random identifiers, see our UUID v4 Generator; for deterministic name-based IDs, use UUID v5.
UUID v6 Format
32 bits
16 bits
16 bits
16 bits
48 bits
The 13th character is always 6 for version 6.
The 17th character contains the RFC 4122 variant bits.
Security Note
UUID v6 is deterministic and embeds time information. Do not use it for secrets, passwords, or tokens. Use a cryptographically random identifier instead.
UUID v6 Field Anatomy
Every UUID v6 is composed of five fields; the first three hold a reordered timestamp.
| Field | Bits | Description | Fixed value? |
|---|---|---|---|
time_high |
32 | Highest 32 bits of the reordered timestamp | No — changes per generation |
time_mid |
16 | Middle 16 bits of the reordered timestamp | No — changes per generation |
time_low_and_version |
16 | Lowest 12 bits of timestamp plus version nibble 0110 |
Version nibble always 6 |
clock_seq_and_reserved |
16 | 14-bit clock sequence + 2 variant bits (10) per RFC 4122 |
Variant bits always 10 |
node |
48 | Random 48-bit value (multicast bit set) for privacy | Regenerated each batch |
Decoded Timestamp of Last Generated UUID v6
Generate a UUID above to decode its timestamp →
Example UUID v6 Values Generated Now
Fresh UUID v6 examples generated client-side on page load. Click any to copy.
How UUID v6 Generation Works
UUID v6 generation follows RFC 9562. The algorithm captures the current time as a 60-bit integer counting 100-nanosecond intervals since October 15, 1582, then rearranges the timestamp bits so the most significant bits sort chronologically and inserts the version 6 nibble.
Because JavaScript's Date.now() has only millisecond resolution, this tool adds a sub-millisecond counter to simulate the finer granularity required by the spec, preventing duplicate timestamps within the same millisecond.
- Get current time in 100ns intervals since 15 Oct 1582
- Split into
time_low,time_mid,time_hi - Set bits 12–15 of
time_hito0001(version 1) - Generate cryptographically random 14-bit clock sequence
- Set variant bits to
10(RFC 4122) - Generate random 48-bit node (multicast bit set to 1)
- Format as
xxxxxxxx-xxxx-1xxx-yxxx-xxxxxxxxxxxx
When to Use UUID v6
UUID v6 is the modern time-ordered version optimized for lexicographic sorting. Use it whenever time-ordering matters:
When NOT to Use UUID v6
Do not use UUID v6 for session tokens, CSRF tokens, API keys, or any security credential. The predictable timestamp component reduces the search space, making brute-force attacks feasible. Use UUID v4 for security-sensitive identifiers.
UUID v6 vs Other UUID Versions
Understand when to choose UUID v6 over other versions.
| Version | Generation Method | Sortable? | Private? | Best For |
|---|---|---|---|---|
| v1 | Timestamp + MAC/random node | By timestamp | No (reveals time) | Time-ordered logging, Cassandra |
| v2 | DCE Security (POSIX UID/GID) | Partial | No | Legacy DCE systems |
| v3 | MD5 hash of namespace+name | No | Deterministic | Name-based IDs (MD5) |
| v4 | Fully random (122 bits) | No | Yes | General purpose — use our UUID v4 tool |
| v5 | SHA-1 hash of namespace+name | No | Deterministic | Name-based IDs (SHA-1) |
| v6 | Reordered timestamp (RFC 9562) | Lexicographically | No | Sortable replacement for v1 |
| v7 | Unix ms timestamp + random (RFC 9562) | Lexicographically | Partial | Modern database-friendly sortable IDs |
For most new projects, UUID v7 is the recommended sortable alternative to v6. For random/anonymous IDs, choose UUID v4. See the complete UUID versions guide on our main UUID Generator page.
Frequently Asked Questions
Everything you need to know about UUID v6 and this generator.
1 to signal it is not a real hardware address — exactly as RFC 4122 recommends for environments without MAC access. No identifying information about your device is ever used.
Complete UUID Tools Directory
WebEasier hosts a full ecosystem of UUID-related developer tools.
UUID Validation
UUID Parsing
UUID Formatting
UUID Conversion
Developer UUID Generators
Alternative ID Generators
25+ UUID & ID Tools
WebEasier is building the most complete UUID tools ecosystem on the web.
View All ToolsExplore All Free Developer Tools
QR codes, barcodes, image tools, converters and more — all free, all client-side.