How to use the uuid generator
- Choose how many IDs you need.
- Toggle uppercase, braces or hyphens as required by your target system.
- Click Generate.
- Copy all of them at once, or download as a text file.
A version 4 UUID is 122 bits of randomness, formatted as 8-4-4-4-12 hexadecimal digits. It is not sequential, carries no timestamp and no machine identity, so it is safe to expose in URLs and safe to generate on any client without coordination.
The practical consequence is collision risk. Generating 2.7 × 1018 v4 UUIDs before a 50% chance of any collision is what makes them usable as primary keys, seeded by a database that also enforces uniqueness. For IDs that appear in URLs and should not be guessable, the randomness is the point.
Formats and conventions
- Lowercase with hyphens — the canonical RFC form, accepted everywhere.
- Uppercase — what many Windows and SQL Server systems expect.
- No hyphens — compact 32-character form used by some APIs and storage layers.
- Braced — the
{…}form some Windows registries and COM APIs require.
This tool uses crypto.randomUUID() where available and the Web Crypto random source otherwise, so the values are cryptographically random rather than merely pseudo-random. If you need sortable IDs, prefer ULID or a database-native sequence: v4 ordering is meaningless.
Frequently asked questions
Are these real v4 UUIDs?
Yes — 122 random bits with the version and variant fields set correctly, generated from the browser's CSPRNG.
Can two generated IDs collide?
Effectively never: you would need billions of IDs before the probability becomes worth considering.
Are UUIDs safe in URLs?
Yes. They reveal nothing about your data or your traffic volume, unlike sequential integer IDs.
Do I need version 7 instead?
v7 is time-ordered and better for database index locality. This page generates v4, which is the right default for opaque identifiers.