RFC 9562 • Time-Ordered Primary Keys 100% Client-Side

UUID v7 Generator & Timestamp Inspector

Generate time-ordered RFC 9562 UUID v7 identifiers for database B-tree indexes, export batches, and inspect embedded timestamps.

Need UUID v4 / v1? Open Full Suite →

UUID v7 Timestamp Inspector & Bit-Field Breakdown

Version / Variant
v7 · RFC 9562
Decoded UTC Timestamp
2026-11-15T16:33:08.749Z
unix_ts_ms (48 bits)
1794760388749 (0x01a1e00e308d)
rand_a · rand_b
766c · a939a09432489b5d

UUID v7 vs UUID v4: Database B-Tree Index Performance (RFC 9562)

Because random UUID v4 values distribute inserts uniformly across the entire 128-bit keyspace, high-write PostgreSQL and MySQL InnoDB tables suffer severe B-tree index fragmentation, buffer pool cache misses, and write amplification. RFC 9562 solves this by placing a 48-bit Unix epoch millisecond timestamp at the front of UUID v7, restoring sequential append locality while preserving global uniqueness across distributed nodes.

Frequently Asked Questions

Clear, concise answers to common questions about Base64 decoding, encoding, and specifications.

UUID v7 encodes a 48-bit Unix millisecond timestamp in its most significant bits followed by random bits. Because IDs are naturally time-ordered, PostgreSQL, MySQL InnoDB, and SQLite B-tree indexes append sequentially instead of triggering random page splits and write amplification.