UUID v7 Generator — Sortable UUID with Timestamp
Generate RFC 9562 compliant UUID v7 values — time-ordered UUIDs with a 48-bit Unix timestamp embedded in the most significant bits. Perfect for database primary keys and distributed systems. 100% client-side — nothing is stored or transmitted.
How to Use the UUID v7 Generator
- Enter the count of UUIDs you want to generate (1-100).
- Click "Generate" to create time-ordered UUID v7 values.
- View the embedded timestamp shown below each UUID — the exact moment it was created.
- Copy individually using the copy button next to each UUID, or "Copy All" for the batch.
Why Use UUID v7
UUID v7 (defined in RFC 9562) solves the biggest problem with traditional UUID v4: they're not sortable. Because UUID v7 embeds a 48-bit Unix timestamp in milliseconds in the most significant bits, UUIDs generated later are always greater than earlier ones. This means:
- Database-friendly: B-tree indexes stay efficient without random page splits
- Naturally sorted: No need for a separate timestamp column for ordering
- Globally unique: Collision probability is negligible (74 random bits)
- Privacy-safe: No MAC address or node ID exposure like UUID v1
Frequently Asked Questions
UUID v7 is a time-ordered UUID format from RFC 9562. It uses 48 bits for a Unix timestamp in milliseconds, followed by 74 bits of cryptographic randomness. The result is a UUID that's globally unique, sortable by creation time, and compatible with standard UUID formats.
UUID v4 uses all 128 bits for randomness — it has no timestamp. UUID v7 dedicates 48 bits to a timestamp and 74 bits to randomness. This makes v7 sortable while still being globally unique. v4 UUIDs appear random and cannot be ordered by creation time.
The first 48 bits of a UUID v7 represent a Unix timestamp in milliseconds — the number of milliseconds since January 1, 1970 (UTC). This tool shows the decoded timestamp next to each generated UUID so you can verify the embedded time value.
Use Cases
Database Primary Keys
Use as primary keys in PostgreSQL, MySQL, or MongoDB for time-ordered, unique identifiers.
Event Sourcing
Generate sorted event IDs that naturally preserve chronological order across distributed systems.
API Resource IDs
Expose time-ordered IDs in REST APIs without leaking sequential counters.
Log Correlation
Correlate log entries across microservices using the embedded timestamp in each UUID.