Choose how many
From 1 to 1,000 UUIDs at once; they come out in increasing order.
Generate version 7 UUIDs, which start with a millisecond timestamp so they sort by creation time. Ideal as database keys. One or a thousand, in your browser.
100% private — everything is generated in your browser with its secure random number generator, and nothing is sent or stored.
Guides: UUID v4 vs v7: what they are and when to use each · Checksums and hashes: how to verify a download with SHA-256
Keep going with your result in another tool. Nothing is uploaded.
From 1 to 1,000 UUIDs at once; they come out in increasing order.
Hyphens, uppercase or braces, as your system needs.
Copy the list or download it as a text file.
To generate a UUID v7, open this page: version 7 is already selected and a batch is listed. Change the quantity if you need more, choose the format and copy the result. The first 48 bits of each UUID are the current Unix time in milliseconds, so the list is in increasing order, and the rest is random. Nothing is sent to a server.
UUID version 7 was standardised in RFC 9562 in 2024. It keeps the familiar 128-bit format, such as 018f1a2b-3c4d-7e5f-8a6b-7c8d9e0f1a2b, but the first 48 bits hold a Unix timestamp in milliseconds, followed by the version digit 7 and random bits. Because the timestamp comes first, sorting UUIDs alphabetically also sorts them by creation time.
| Part | In the example | Meaning |
|---|---|---|
| Timestamp: 48 bits, the first 12 hex digits | 018f1a2b3c4d | Unix time in milliseconds: 1714130992205, which is 2024-04-26 11:29:52.205 UTC |
| Version: 4 bits | 7 | version 7 |
| rand_a: 12 bits, the next 3 hex digits | e5f | random bits, or a counter as in this generator |
| Variant: 2 bits | 8 (binary 10) | the variant of RFC 9562: the fourth group starts with 8, 9, a or b |
| rand_b: 62 bits, the rest | the rest of the fourth group and the whole fifth | random |
The example is an illustrative value, not one generated just now. Its bits add up to 48 + 4 + 12 + 2 + 62 = 128.
The date is in the first 12 hexadecimal digits: the first group and the start of the second, without the hyphen (018f1a2b3c4d in the example). Read them as one hexadecimal number and you have the milliseconds since 1 January 1970 UTC.
const u = "018f1a2b-3c4d-7e5f-8a6b-7c8d9e0f1a2b"; const ms = parseInt(u.replace(/-/g, "").slice(0, 12), 16); // 1714130992205 new Date(ms).toISOString(); // "2024-04-26T11:29:52.205Z"
from datetime import datetime, timezone
u = "018f1a2b-3c4d-7e5f-8a6b-7c8d9e0f1a2b"
ms = int(u.replace("-", "")[:12], 16) # 1714130992205
datetime.fromtimestamp(ms / 1000, tz=timezone.utc) # 2024-04-26 11:29:52.205000+00:00
Python 3.14 also exposes it directly as UUID.time for version 7, and PostgreSQL has uuid_extract_timestamp(), which returns the timestamp of a version 1 or 7 UUID. The time is whatever clock the generating machine had, so treat it as information, not as proof of when something happened.
A B-tree index, used by most databases for primary keys, works best when new rows are added at the end. Random v4 keys land all over the index, which causes page splits, cache misses and fragmentation. Time-ordered v7 keys append mostly at the end, so inserts are faster and the index stays compact, while keys remain globally unique and can still be generated by many servers at once.
RFC 9562 lets a generator use the 12 bits after the version digit as a counter (section 6.2, method 1). This one does: in each new millisecond the counter starts at a random value below 512 and grows by one with every UUID, so a batch always comes out in strictly increasing order. If the counter runs out at 4,095, the timestamp moves forward by one millisecond. We checked it with 10,000 identifiers created at the same frozen millisecond: all different, all increasing, and the embedded time moved ahead by 2 ms. So in very large batches the time inside an ID can run a few milliseconds ahead of your clock.
| Platform | How to get a v7 | Notes |
|---|---|---|
| PostgreSQL 18 | uuidv7() | Time-ordered UUID; uuid_extract_timestamp() reads version 1 and 7. |
| Python 3.14 and later | uuid.uuid7() | UUID.time holds the 48-bit millisecond timestamp. |
| .NET 9 and later | Guid.CreateVersion7() | Follows RFC 9562; the random parts are filled with random data. |
| Web browsers | crypto.randomUUID() | Makes version 4 only, so v7 needs a library or a tool like this one. |
Sources, checked in October 2026: RFC 9562, PostgreSQL UUID functions, Python uuid module, .NET Guid.CreateVersion7 and MDN crypto.randomUUID.
The conversion runs in your browser. What you type, paste or drop is never uploaded, which matters when the text holds tokens, personal data or internal files.
More utilities that also run without leaving your browser.