How it works
A version 4 UUID is 122 random bits, with 4 bits fixed to say “version 4” and 2 bits fixed to say “variant 1”. This page fills 16 bytes from crypto.getRandomValues, sets those bits, and prints the 8-4-4-4-12 hex form.
Bulk generation is that draw repeated. The list is not stored and not uploaded. A password with a character set you choose is the password generator, not a UUID.
Formula
- Version
the first hex digit of the third group is 4 - Variant
the first hex digit of the fourth group is 8, 9, a, or b
Worked examples
All zeros, after the bits are set
Sixteen zero bytes become 00000000-0000-4000-8000-000000000000. Real draws are not zeros. The fixed digits are the point of the example.
A batch of five
The box lists five identifiers, one per line. Copy all puts that whole list on the clipboard.
| Group | Hex digits | Meaning |
|---|---|---|
| 1 | 8 | Random |
| 2 | 4 | Random |
| 3 | 4 | Version 4, then random |
| 4 | 4 | Variant, then random |
| 5 | 12 | Random |
Common questions
Are the identifiers uploaded?
No. They are generated in your browser and forgotten when you leave the page.
Is version 4 the right one?
Use it when you want a random id and do not need the id to encode a time or a name. It is the usual choice for database keys and request ids.
Can two of them match?
In a list of 100, a collision is not a practical concern. The space is 122 random bits. This is still software randomness, not a hardware token.
Why is the list capped at 100?
That is enough to seed a test fixture and small enough to copy. Generate again if you need more.