A batch of five IDs
Five database keys are needed for seed data.
- Count: 5
- Lowercase with hyphens
- Result: five distinct v4 UUIDs
Each value is 36 characters long, including four hyphens, and the version nibble is always 4.
This UUID generator creates version 4 identifiers using the browser’s cryptographic random number generator. Values are generated locally, never stored, and can be copied as a list for tests, seed data or database keys.
Your data is processed locally in your browser and is not uploaded to our server.
Enter a whole number between 1 and 100.
xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx
A v4 UUID contains 122 random bits. The version nibble is fixed to 4, and the variant bits are set to 10xx, which is why the first character of the fourth group is always 8, 9, a or b.
crypto.randomUUID() or crypto.getRandomValues()
The tool uses the browser’s cryptographic API. It does not use Math.random, so identifiers are suitable for unguessable keys, not just display values.
Five database keys are needed for seed data.
Each value is 36 characters long, including four hyphens, and the version nibble is always 4.
A system stores identifiers without hyphens.
The compact form carries the same 128 bits; only the presentation changes.
UUID v4 values are hard to guess but are not designed as passwords or API tokens. Use a dedicated secret generator for credentials.
With 122 random bits, the chance of generating the same UUID twice is astronomically small. Duplicate protection in a database is still a good safeguard.
The generator caps a batch at 100 identifiers so the page stays responsive. Generate another batch if you need more.
A 128-bit identifier with 122 random bits. Its version field is 4 and its variant bits mark it as an RFC 4122 UUID.
They are generated with the browser’s cryptographic random generator, which is appropriate for identifiers. They are not intended to replace cryptographic secrets.
Yes. Disable “Hyphens” to get a compact 32-character hexadecimal string with the same bits.
No. They are generated in your browser and are not sent to a server or saved.
Those characters encode the UUID variant bits. The fixed prefix is part of the RFC 4122 format, not a random coincidence.