Pick UUID v4 for fully random identifiers or UUID v7 for time-ordered IDs that sort chronologically — ideal for database primary keys. This tool uses crypto.getRandomValues (Web Crypto API), so the output is cryptographically secure.
10 V4 UUIDs
f92be5b9-b4e8-46aa-bcfd-845320c89710 901ed0c8-07c4-46f5-9d50-ec93590fc87a 876d802f-88d3-4c60-bfa0-449fe3c10b7b f8cf3149-8c40-41c0-84ee-ad6f796668cb bcc749e1-f829-43a8-9a28-dd9a6d278e32 4f3e9bcb-6668-4a40-8c22-0c701eb7573a fb852bd0-91aa-445b-b4d0-54de4b37fd8d f8027b03-edaf-4196-8d07-b70314df2c2e d1987ed8-6c13-42e7-97d3-a869dbd5c0f9 618e1292-707d-4d4c-8065-3427f3c5e22f
// faq
Frequently asked questions
- What is a UUID?
- A Universally Unique Identifier is a 128-bit value formatted as 32 hexadecimal digits in five groups (8-4-4-4-12). UUIDs are designed to be globally unique without a central authority.
- What is the difference between UUID v4 and UUID v7?
- v4 is fully random. v7 embeds a Unix millisecond timestamp in the first 48 bits followed by random data, so v7 UUIDs sort chronologically — ideal for database primary keys because they preserve insertion order and improve B-tree locality.
- Should I use UUIDs as database primary keys?
- Yes for distributed systems, offline sync, and public APIs where you don't want to expose sequential IDs. Prefer UUID v7 (or ULID) over v4 for indexed columns to avoid write amplification from random inserts.
- Are the UUIDs generated here cryptographically random?
- Yes. This tool uses the browser's crypto.getRandomValues (Web Crypto API), which is a cryptographically secure random source. Nothing is sent to a server.
- How likely is a UUID collision?
- For v4, the collision probability is negligible: you'd need to generate roughly 1 billion UUIDs per second for 85 years to have a 50% chance of a single collision. Safe for any practical workload.
// related

