UUID v7 Generator & Timestamp Decoder

Generate UUID v7 identifiers per RFC 9562 in bulk, and decode the embedded millisecond timestamp back to a readable date. Runs entirely in your browser.

Generate

Count Format

Generated UUIDs

—

Decode timestamp from a UUID v7

Decoded timestamp

—

How to use

Choose how many IDs you need and the output format.
Click Generate UUID v7 — IDs appear instantly, generated with the Web Crypto API.
Copy the result, or paste a v7 UUID below to decode its embedded timestamp.

Use cases

Sortable, time-ordered primary keys for databases and event logs.
Message and job IDs that correlate with when they were created.
Migrating away from v4 when ordering or recency matters.

About UUID v7

UUID v7 is a time-ordered UUID format standardized in RFC 9562: the first 48 bits carry a millisecond timestamp, and the remaining bits are random, with fixed version and variant bits. Unlike random v4 UUIDs, v7 values increase over time, so they sort chronologically and play much better with B-tree indexes in databases — avoiding the page splits and cache misses that random keys cause. This tool generates v7 UUIDs in bulk and decodes the embedded timestamp back to a readable date.

Reach for v7 when you need primary keys or IDs that benefit from insertion-order sorting — database tables, event logs, message queues, and job IDs — especially when you are migrating away from v4. One caveat: the timestamp has millisecond precision, so IDs generated within the same millisecond are not strictly monotonic; if you need exact ordering, add a sequence or use v7's optional counter bits. The generator runs entirely in your browser using the Web Crypto API, so no data leaves your machine.

Why time-ordered identifiers matter

A v7 UUID begins with a 48-bit big-endian millisecond timestamp. Because primary key indexes are B-trees, random keys scatter inserts across the whole index, causing page splits and cache misses; time-ordered keys append near the end. On a large insert-heavy table this is the difference between an index that stays in memory and one that does not.

The timestamp is also recoverable: decoding a v7 UUID tells you exactly when it was created, which is useful when debugging without a timestamp column.

Collision resistance

The random bits after the timestamp guarantee uniqueness within the same millisecond, and the monotonic variant additionally guarantees ordering for ids minted in the same millisecond. Two processes generating v7 ids concurrently will not collide.

Frequently Asked Questions

How do I generate a UUID v7?

Click Generate to create a new UUID v7. You can generate a batch of up to 100 at once. Each UUID contains a timestamp component encoding the creation time, allowing you to sort records by creation order.

Can I decode a UUID v7 to find when it was created?

Yes. Paste any UUID v7 into the decoder and it extracts and displays the embedded timestamp, showing the exact creation date and time in UTC.

Is my data sent to a server?

No. Every tool on jsonversal runs entirely in your browser using the Web Crypto API, File API, and Clipboard API. Nothing is ever uploaded — not even the JSON you paste in.

Do I need an account or API key?

No signup, no email, no API key. All tools are free to use with no signup required.

Can I use these tools offline?

Yes. Once the page loads, all tools work offline. There are no external API calls or CDN dependencies at runtime.

🔒

Your data never leaves your device

All processing happens in your browser. No uploads, no tracking, no servers. Your API keys, configs, and private payloads stay private — 100% client-side.