UUID Generator
Generate 5 random RFC 4122 version 4 UUIDs at once. The input is ignored; run again for a new batch.
How to use the UUID Generator
- 01
Choose the UUID version (v4 or v7) and how many you need.
- 02
The UUIDs appear instantly in the output panel.
- 03
Copy them with one click; press Generate for a fresh batch.
What a UUID is
A UUID (universally unique identifier) is a 128-bit value used to label things, database rows, files, events, messages, API resources, without a central authority handing out IDs. Any machine can mint one independently and trust it will not clash with anyone else's.
How version 4 is built
This generator produces version 4 UUIDs, the most common kind. A v4 UUID is almost entirely random: 122 of its 128 bits come from a random source, with the remaining 6 bits fixed to mark the version and variant. It is written as 32 hexadecimal digits in the familiar 8-4-4-4-12 grouping.
Each batch of five is generated with your platform's cryptographically secure random source, the same one used for security-sensitive randomness, not a predictable pseudo-random function. Press Run again any time for a fresh batch.
How unique they really are
Uniqueness is a matter of probability rather than a hard guarantee, but the numbers are reassuring: with 122 random bits you would need to generate billions of UUIDs before the chance of a single collision became meaningful. For practically every application this is effectively unique.
v4 vs v7
Version 4 is the right default when you just need a unique ID. If ordering matters, version 7 encodes a timestamp in its leading bits so IDs sort by creation time, which keeps database indexes tidier than fully random v4 keys. The Learn article on v4 vs v7 covers the trade-off in depth.
Common uses and one caveat
Common uses include primary keys, idempotency keys that make a request safe to retry, correlation IDs for tracing a request across services, and unique file names. Keep in mind that a v4 UUID is random but not secret, so it should not be used on its own as a security token or password.
Frequently asked questions
What kind of UUIDs are these?
They are RFC 4122 version 4 UUIDs: random identifiers with 122 random bits, generated with a cryptographically strong source.
Are the UUIDs unique?
Collisions are astronomically unlikely. With 122 random bits you would need to generate billions of UUIDs before any realistic chance of a repeat, so they are treated as unique in practice.
Why five at a time?
Five is a convenient batch for most tasks. Press Run again to generate another five whenever you need more.
What is the difference between UUID v4 and v7?
Version 4 is fully random. Version 7 puts a timestamp in the leading bits so the IDs are time-ordered, which improves database index locality. Use v4 for general uniqueness and v7 when sortable IDs help.
Are these generated privately?
Yes. The UUIDs are created in your browser using its built-in secure random generator. Nothing is requested from or sent to a server, so you can even generate them offline.
Can I use a UUID as a password or token?
It is not recommended. A v4 UUID is random but it is meant to be an identifier, not a secret, and it is often logged or exposed in URLs. Use a dedicated password or token generator for secrets.
Sources
Learn more
UUIDv4 vs UUIDv7: Why Time-Ordered IDs Make Better Database Keys
UUIDv4 is random and scatters database indexes; UUIDv7 is time-ordered and inserts in order. Learn the difference and when each one wins.
Base64 Explained: Why Encoding Is Not Encryption
What Base64 actually does, why it makes data about a third larger, when to use it, and why it protects nothing on its own.
URL Encoding Explained: When and Why to Percent-Encode
Why URLs use %20 and other percent codes, which characters are safe, and when to reach for encodeURIComponent instead of encodeURI.
How to Read a JWT, and Why Decoding Is Not Verifying
A JWT is three Base64url parts anyone can read. Learn how to decode one, what each part means, and why decoding proves nothing.
Hashing vs Encryption: What a Hash Can and Cannot Do
Hashing is one-way and keyless; encryption is two-way and needs a key. Learn the difference, why you cannot decrypt a hash, and when to use each.
How Webhook Signatures Work: HMAC, Shared Secrets, and Timing-Safe Checks
How Stripe and GitHub prove a webhook is genuine using HMAC and a shared secret, and the timing-safe comparison most developers get wrong.