ToolzUUID Generator
Generate cryptographically random UUIDs, one or in bulk.
What you are getting
These are version 4 UUIDs — 128-bit identifiers where 122 of those bits are random. They are produced by your browser’s crypto.randomUUID(), which draws from the same cryptographically secure random source used for encryption keys, not from Math.random(). That distinction matters if an identifier being guessable would be a problem.
Will two of them ever collide?
In practice, no. With 122 random bits you would need to generate on the order of a billion UUIDs per second for about 85 years before a single collision became likely. For any normal application — database primary keys, request ids, filenames, idempotency keys — you can treat them as unique without coordinating with a central server, which is the whole point of using them.
When a UUID is the wrong choice
Random UUIDs are not sortable and have poor locality, so using one as a clustered primary key in a large table can fragment the index and hurt insert performance. If you need time-ordered identifiers, look at UUIDv7 or ULID instead. They are also long and awkward to read aloud or type by hand, so they make poor user-facing codes.