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
6ae348d3-fbf4-441a-9049-a8d353d58284 91c44cc0-9d1d-404a-8136-1554d5d2bc05 27f903d1-17d4-49f5-884b-163bfefadfee 4e7514b5-111a-4238-9a39-60cd282b42ff bd0a228d-56bd-4e07-a1bf-a284564c44a6 01cc133e-26d4-4a7d-95ba-f53446f34c3d 2fc9fb71-c1a2-45a9-94ff-1fc643044d9b d837db3a-4835-4eca-aeca-5991ddcbdbf6 25a7363e-6b56-44b2-bb3b-9f70807b1ded 55f7a570-fe1d-4892-8f00-622e032b47f4
// 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

