What a UUID is
A UUID is a 128-bit identifier written as 32 hexadecimal digits, usually grouped as 8-4-4-4-12 and separated by hyphens. Its purpose is to let independent systems each mint identifiers that will not collide, without coordinating through a central authority. That makes UUIDs the default choice for primary keys in distributed databases, message IDs, session tokens, file names, and any situation where two machines need to generate unique references at the same time.
How version 4 works
This tool generates version 4 UUIDs, which are almost entirely random. Of the 128 bits, 6 are fixed to mark the version and variant, leaving 122 bits of randomness. The bits come from crypto.getRandomValues, the browser's cryptographically secure generator, not from a timestamp or MAC address like version 1. That means a v4 UUID reveals nothing about when or where it was created — a privacy advantage — and cannot be guessed or enumerated by an attacker.
Why collisions are effectively impossible
With 122 random bits, there are more than five undecillion possible values. The probability of two randomly generated v4 UUIDs colliding is so small that you could generate a billion per second for a hundred years and still have a negligible chance of a single duplicate — the famous birthday-paradox math still leaves you astronomically safe. In practice this means you can generate UUIDs on many machines simultaneously and treat every one as globally unique without checking a central registry.
Formatting options
Different systems expect different formatting. The canonical form is lowercase with hyphens, which is what most databases and APIs use. Some systems, particularly Microsoft ecosystems, prefer uppercase. Others strip the hyphens to save space in URLs or storage. This tool lets you toggle both so the output drops straight into your code, migration script, or config file. Generate twenty at once when you need to seed test data or pre-allocate a batch of identifiers.
Privacy notes
Everything runs in your browser. No UUID is sent to a server, saved, or logged, so the identifiers you generate here are yours alone and cannot be linked back to you. If you generate a token you intend to keep secret, that local-only behavior is exactly what you want — there is no network path through which it could leak.