What's a UUID?
A UUID (also called a GUID) is a 128-bit ID written as 32 hex characters, like
3f2b6c1e-8d4a-4a7b-9c2d-8e1f0a2b3c4d. Anyone can create one without asking a central server, and the chance of two
random UUIDs ever colliding is practically zero.
How to use it
- Pick v4 (random) or v7 (time-ordered) and how many you need (up to 100).
- Press Generate (Ctrl + Enter). Copy one, Copy all (one per line) or Download
them as
uuids.txt. - Uppercase and Hyphens change how they're written, not the IDs themselves. Your options are remembered.
v4 or v7?
| Version | Made from | Best for |
|---|---|---|
| v4 | 122 random bits | General IDs, tokens, anything where order doesn't matter |
| v7 | A millisecond timestamp + random bits | Database primary keys: new IDs sort after old ones, which keeps indexes fast |
A v7 UUID reveals roughly when it was created. Use v4 if that matters.
Example
0190f5a4-5c2e-7b3a-9d41-6f0e2c8a1b7d is a v7 UUID: the 7 at the start of the third group is the version, and the
first 12 hex digits (0190f5a45c2e) are the creation time in milliseconds.
FAQ
Are these UUIDs secure and unique?
They use your browser's cryptographic random generator (crypto.getRandomValues), the same quality used for keys and
tokens. We never upload or store the IDs you generate.
Uppercase or lowercase?
Both are valid and mean the same UUID. Lowercase is the standard way to write them (RFC 9562); some Microsoft tools show GUIDs in uppercase.
Why are v7 UUIDs from one batch in order?
Within the same millisecond a 12-bit counter goes up with each ID, so a batch is strictly increasing, like the RFC recommends for database keys.