QR64Code uses `crypto.randomUUID()` in supported browsers. A UUID v4 has a 128-bit layout; after version and variant bits, 122 bits remain random.
What changed in this update?
July 30, 2026
The tool, explanation, limits, sources, and accessible form flow were reviewed together.
How to use it
- 1
Choose how many UUIDs to create.
- 2
Select Generate UUIDs.
- 3
Copy the list or download it as TXT.
Limits and security notes
Collision probability is extremely low, but UUID generation does not replace a unique database constraint. A UUID is not a secret key.
Comparison
| Type | Source | Sortable |
|---|---|---|
| UUID v4 | Random | No |
| UUID v7 | Time + random | Yes |
| Incrementing ID | Database | Yes |
Frequently asked questions
Can UUID v4 collide?
In theory yes; with 122 random bits the probability is extremely low when generation is correct.
Can a UUID be used as a password?
No. A UUID is an identifier, not a password or secret key.
Are values stored?
Generated UUIDs remain in the browser and are not sent to QR64Code servers.