UUID v7, v6 & v1 Generator

Generate time-ordered RFC 9562 UUID v7, v6, and v1 keys locally in your browser.

No uploadsNo sign-upInstant results
UUID v7 (Recommended) · v6 · v1Monotonic Sub-ms Bulk Batches100% Local • Zero Uploads
Generate Time-Ordered UUIDs
Offline engine ready100% private in-browser workspace • Zero cloud uploads
100% Private • Zero Server File Uploads

Why Use Utiliome's Free UUID v7, v6 & v1 Generator?

Built from the ground up for strict privacy, instant execution, and zero friction. No subscriptions, paywalls, or account registrations required.

RFC 9562 Versions 7, 6, and 1

Implements 48-bit Unix millisecond UUID v7, field-reordered 60-bit Gregorian UUID v6, and legacy split-timestamp UUID v1 per RFC 9562 Sections 5.1, 5.6, and 5.7.

Sequential B-Tree Index Locality

Places most-significant timestamp bits first in UUID v7 and v6 so new records append to the rightmost B-tree leaf page in PostgreSQL, MySQL InnoDB, and SQLite.

74-Bit CSPRNG Tail & Random Nodes

Populates UUID v7 rand_a and rand_b via Web Crypto crypto.getRandomValues and sets RFC 9562 multicast-bit random 48-bit node IDs in v1/v6 with zero MAC leakage.

100% Local In-Browser Execution

Mints single or bulk time-ordered keys directly in browser memory with zero network calls or server logging—ready for schema migrations and benchmark fixtures.

Utiliome vs Traditional Cloud Alternatives

Compare our local-first WebAssembly engine against legacy cloud tools.

Feature Utiliome (Local Browser) Legacy Cloud Converters
Time-Ordered RFC 9562 Versions Generates UUIDv7 (48-bit Unix ms), UUIDv6 (60-bit reordered Gregorian) & UUIDv1 Supports legacy UUIDv1 only without modern B-tree-optimized UUIDv7/v6
Database B-Tree Index Locality Monotonically increasing big-endian timestamp prefixes prevent PostgreSQL/MySQL page splits Random UUIDv4 keys cause severe index fragmentation on large tables
Custom Timestamp Seeding & Bulk Export Mint keys for current time or a custom ISO date in bulk (Raw, JSON, CSV, SQL) Current timestamp only with single-ID copying
Privacy-Safe Random Node Bits Uses CSPRNG multicast node bytes by default — never leaks hardware MAC addresses Exposes host MAC address or static predictable node identifiers
How it works

How to Use UUID v7, v6 & v1 Generator in 3 Easy Steps

No software installation required. Everything runs directly inside your web browser.

1

Choose Time-Based Version (v7, v6, or v1)

Select UUID v7 for modern Unix Epoch millisecond database keys, UUID v6 for sortable Gregorian timestamps, or UUID v1 for legacy system compatibility.

2

Configure Batch Size & Formatting

Specify how many ordered identifiers to mint and choose canonical hyphenated, compact 32-hex, uppercase, braced, or structured batch formatting.

3

Copy or Download Ordered Keys

Copy lexicographically sorted UUID batches to your clipboard or export them for relational database seeding, event-store fixtures, and migration scripts.

Comparing Time-Ordered UUID v7, v6, and v1 Outputs Across Timestamps

Quick Answer: For the exact same instant, UUID v7 places a 48-bit big-endian Unix millisecond integer in its leading 12 hex digits, UUID v6 places a 60-bit big-endian Gregorian timestamp in its leading 15 hex digits (around the version nibble), and legacy UUID v1 puts the low 32 timestamp bits first—wrapping lexicographical sort order every 429.5 seconds.

Seeing all three time-based RFC 9562 versions side by side across two timestamps two minutes apart illustrates why UUID v7 and UUID v6 preserve strict chronological sort order while UUID v1 fragments database indexes.

Consider the RFC 9562 reference instant 2022-02-22T19:22:22.000Z (Unix Epoch 1,645,557,742,000 ms = 0x017f22e279b0; Gregorian 100-ns count 138,648,505,420,000,000 = 0x1ec9414c232ab00) and a second timestamp 120 seconds later at 2022-02-22T19:24:22.000Z (Unix 0x017f22e44e70; Gregorian 0x1ec941509b93700):

# T + 0s   (2022-02-22T19:22:22.000Z)
UUID v7 : 017f22e2-79b0-7cc3-98c4-dc0c0c07398f
UUID v6 : 1ec9414c-232a-6b00-b3c8-9f6bdeced846
UUID v1 : c232ab00-9414-11ec-b3c8-9f6bdeced846

# T + 120s (2022-02-22T19:24:22.000Z)
UUID v7 : 017f22e4-4e70-7a19-8f21-4b90e12c5d3a   (017f22e4 sorts AFTER 017f22e2)
UUID v6 : 1ec94150-9b93-6700-b3c8-9f6bdeced846   (1ec94150 sorts AFTER 1ec9414c)
UUID v1 : 09b93700-9415-11ec-b3c8-9f6bdeced846   (09b93700 sorts BEFORE c232ab00!)

Because UUID v1 stores time_low (the fastest-changing 32 bits of the 100-nanosecond clock) in octets 0–3, its leading 8 hex digits overflow every 2^32 x 100 ns = 429.4967296 seconds (~7 minutes 9.5 seconds), jumping back to 00000000-... and scattering inserts across historical B-tree pages. Both UUID v7 and UUID v6 store the most-significant timestamp bits in octets 0–5, making raw byte order (memcmp) and ASCII lexicographical order monotonically increasing:

[
  "0195a0b4-3c10-71a4-9c02-54e81a09f3b1",
  "0195a0b4-3c11-78f0-a41d-8e2c77140b6e",
  "0195a0b4-3c12-732b-89e5-1c4f0a68d290"
]

To verify or extract the exact UTC creation timestamp from any generated v7, v6, or v1 identifier, paste the key into the UUID Parser & Decoder.

RFC 9562 Bit Layouts for UUID v7, v6, and v1 & B-Tree Page-Split Mechanics

Quick Answer: UUID v7 combines a 48-bit big-endian Unix Epoch millisecond timestamp with version 0111, variant 10, and 74 CSPRNG/counter bits (rand_a and rand_b). UUID v6 and v1 both encode a 60-bit 100-ns Gregorian timestamp, 14-bit clock sequence, and 48-bit multicast-random node ID, differing only in timestamp field order.

RFC 9562 formalizes all three time-based UUID versions in network byte order (big-endian) while explicitly recommending UUID v7 (Section 5.7) over UUID v1 (Section 5.1) and UUID v6 (Section 5.6) for new implementations.

UUID v7 (RFC 9562 Section 5.7) — 48-bit Unix Epoch ms + 74-bit CSPRNG/counter
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                           unix_ts_ms                          |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|          unix_ts_ms           |  ver  |        rand_a         |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|var|                        rand_b                             |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                            rand_b                             |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Bits 0-47  : unix_ts_ms (unsigned ms since 1970-01-01T00:00:00Z)
Bits 48-51 : ver = 0111 (0x7)      Bits 52-63 : rand_a (12 bits)
Bits 64-65 : var = 10              Bits 66-127: rand_b (62 bits)

UUID v6 (RFC 9562 Section 5.6) — Reordered 60-bit Gregorian 100-ns clock
Bits 0-31  : time_high (most-significant 32 bits of 60-bit Gregorian timestamp)
Bits 32-47 : time_mid  (middle 16 bits of 60-bit Gregorian timestamp)
Bits 48-51 : ver = 0110 (0x6)      Bits 52-63 : time_low (low 12 bits)
Bits 64-65 : var = 10              Bits 66-79 : clock_seq (14 bits)
Bits 80-127: node (48-bit random multicast node ID, octet 10 LSB = 1)

UUID v1 (RFC 9562 Section 5.1) — Legacy split 60-bit Gregorian 100-ns clock
Bits 0-31  : time_low (low 32 bits) | Bits 32-47 : time_mid (middle 16 bits)
Bits 48-51 : ver = 0001 (0x1)       | Bits 52-63 : time_high (top 12 bits)
Bits 64-65 : var = 10               | Bits 66-79 : clock_seq (14 bits)
Bits 80-127: node (48-bit random multicast node ID, octet 10 LSB = 1)

Epoch Arithmetic, Sub-Millisecond Monotonicity, and Node Privacy

  • Unix vs Gregorian Epochs: UUID v7 counts milliseconds from 1970-01-01T00:00:00Z (valid until August 10889 AD). UUID v1 and v6 count 100-nanosecond intervals since the Gregorian reform epoch 1582-10-15T00:00:00Z (an offset of 122,192,928,000,000,000 ticks or 0x01b21dd213814000 before the Unix Epoch, rolling over around 5236 AD).
  • Same-Millisecond Ordering (RFC 9562 Section 6.2): Within a single millisecond tick, UUID v7 provides 12 + 62 = 74 bits (1.89 x 10^22 combinations) of collision resistance. Generators can either fill all 74 bits from Web Crypto crypto.getRandomValues or treat the 12-bit rand_a field as a randomly seeded monotonic counter supporting up to 4,096 strictly increasing keys per millisecond on a single worker.
  • MAC Address Replacement (RFC 9562 Section 6.10): Rather than leaking a device's physical IEEE 802 MAC address in v1 or v6, compliant client-side generators populate the 48-bit node field with CSPRNG bytes and set the multicast bit (node[0] |= 0x01), guaranteeing zero collision with globally administered NIC addresses.

Why Time-Ordered Keys Eliminate B-Tree Page Splits

Relational storage engines organize primary-key indexes as B-trees of fixed-size pages (8 KB in PostgreSQL, 16 KB clustered index pages in MySQL InnoDB, 4 KB in SQLite). Random keys touch cold leaf pages across the entire keyspace, forcing mid-tree page splits, ~50–67% page fill density, and heavy WAL/buffer-pool churn. Because UUID v7 and UUID v6 carry big-endian timestamps in their leading bytes, newly minted rows always append to the rightmost active leaf page already resident in L1/RAM cache—achieving near-BIGSERIAL insert throughput while preserving decentralized client-side ID generation. Always store them in 16-byte binary form (uuid in PostgreSQL, BINARY(16) in MySQL, BLOB in SQLite).

UUID v7, v6 & v1 vs UUID v4 Generator: Which UUID Tool Do You Need?

Quick Answer: Use UUID v7 in this generator for new database primary keys, event logs, and high-throughput distributed writes. Use UUID v6 only when migrating legacy UUID v1 systems that depend on 60-bit Gregorian fields, and switch to the UUID v4 Generator whenever creation timestamps must remain completely unguessable and private.

Selecting between time-ordered UUID versions and sibling RFC 9562 utilities depends on index locality, legacy compatibility, and timestamp privacy requirements:

Feature UUID v7 (This Tool) UUID v6 & v1 (This Tool) UUID v4 Generator UUID Parser & Validator
Timestamp Encoding 48-bit Unix Epoch milliseconds 60-bit Gregorian 100-ns ticks (1582 epoch) None (zero timestamp bits) Decodes timestamps (Parser) / Audits syntax (Validator)
Random / Node Bits 74 bits CSPRNG (rand_a + rand_b) 14-bit clock seq + 48-bit random multicast node 122 bits Web Crypto CSPRNG Inspects bit fields without minting new IDs
Lexicographical Sort Monotonic chronological (memcmp-safe) Monotonic in v6; wraps every 429.5s in v1 Uniformly unordered N/A (read-only analysis)
SQL B-Tree Write Profile Appends to rightmost hot leaf page Appends in v6; random page splits in v1 Random leaf inserts and page splits at scale N/A
Best Fit Greenfield PostgreSQL, MySQL, SQLite PKs & Kafka events Drop-in v1-to-v6 migrations & legacy connectors Public slugs, correlation IDs, S3 keys, opaque IDs Debugging production IDs & validating bulk imports

Routing Across the Utiliome UUID Suite

  • Use UUID v7 here for virtually all new relational tables, append-only audit logs, and distributed message streams where decentralized generation and sequential B-tree locality are both required.
  • Use UUID v6 or v1 here only when interfacing with existing systems built around 60-bit Gregorian clocks, clock sequences, or legacy v1 schemas (preferring v6 whenever byte-sortable indexing is needed).
  • Switch to UUID v4 Generator when generating public URL identifiers, request/trace IDs, or bulk random fixtures where exposing the exact millisecond a resource was created is undesirable.
  • Switch to UUID Parser & Decoder to unpack an existing v7, v6, or v1 string back into its ISO-8601 UTC timestamp, clock sequence, and node bits, or UUID Validator to verify bulk UUID datasets against RFC 9562 rules.
FAQ

UUID v7, v6 & v1 Generator FAQ and Technical Guide

Everything you need to know about using Utiliome's free online uuid v7 generator.

Should I use UUID v7 or UUID v6 for new PostgreSQL and MySQL primary keys?

Use UUID v7 for all greenfield tables. RFC 9562 explicitly recommends Version 7 over Versions 1 and 6 because it uses standard Unix Epoch milliseconds instead of 1582 Gregorian 100-nanosecond offsets and dedicates 74 bits per key to CSPRNG entropy rather than a static 48-bit node and 14-bit clock sequence. That 74-bit random tail prevents collisions across thousands of ephemeral serverless functions or containers without coordination. Use UUID v6 only when migrating an existing UUID v1 codebase that specifically relies on 60-bit Gregorian fields.

What happens if multiple UUID v7 keys are generated within the same millisecond?

Even within an identical 48-bit millisecond tick, UUID v7 provides 74 remaining payload bits (12-bit rand_a and 62-bit rand_b), giving 1.89 x 10^22 possible values per millisecond. Under RFC 9562 Section 6.2, generators can also increment a randomly initialized monotonic counter in rand_a for same-millisecond calls on the same node, preserving strict sub-millisecond sort order for up to 4,096 keys per millisecond while keeping 62 bits of CSPRNG unpredictability in rand_b.

Do UUID v1 or UUID v6 keys generated here reveal my computer's MAC address?

No. Browsers isolate hardware MAC addresses from web applications, and RFC 9562 Section 6.10 recommends using cryptographically random 48-bit node identifiers instead of IEEE 802 MAC addresses. This generator sets the multicast bit (least-significant bit of octet 10) to 1 on random node bytes so generated v1 and v6 keys never leak hardware identity and cannot collide with physical network interface cards.

Is it safe to expose UUID v7 primary keys directly in public REST URLs?

UUID v7 is resistant to enumeration or guessing attacks because each ID carries up to 74 bits of CSPRNG entropy, making adjacent records impossible to predict. However, anyone who sees a UUID v7 in a URL can decode its first 12 hex digits to read the exact UTC millisecond the record was created—which can reveal account signup timing or order velocity trends. If creation-time privacy matters on public endpoints, keep UUID v7 as your internal clustered primary key and expose a secondary random UUID v4 or opaque public ID externally.

When will the 48-bit Unix millisecond timestamp in UUID v7 run out?

An unsigned 48-bit integer holds up to 281,474,976,710,655 milliseconds after 1970-01-01T00:00:00Z, meaning UUID v7 timestamps will not overflow until August 2, 10889 AD. By comparison, the 60-bit 100-nanosecond Gregorian timestamp used by UUID v1 and UUID v6 overflows around 5236 AD.