Create universally unique identifiers for databases, APIs, and distributed systems — one at a time or ten thousand at once. Choose the version, format them the way your system expects with uppercase, hyphen-free, or brace-wrapped output, then copy the list or download it as a text file. Version 4 UUIDs come from your browser's cryptographic random number generator, so they are suitable for primary keys and correlation ids where collisions matter. Version 5 hashes a namespace and a name, which makes it deterministic: the same inputs always produce the same identifier, which is exactly what you want for stable ids derived from URLs, file paths, or record names. Nothing is sent to a server — the identifiers are generated on your own device, which is the only sensible arrangement for values that will end up as keys in your production database.
| Version | Derived from | Repeatable? | Typical use |
|---|---|---|---|
| v1 | Timestamp + clock sequence + node id | No | Time-ordered ids where insert order matters |
| v3 | MD5 of namespace + name | Yes | Legacy — superseded by v5 |
| v4 | Cryptographic randomness | No | The default choice for keys and correlation ids |
| v5 | SHA-1 of namespace + name | Yes | Stable ids derived from a URL, path, or name |
Yes. They are generated with crypto.randomUUID or crypto.getRandomValues, both backed by your operating system's cryptographically secure random source — not Math.random. A v4 UUID has 122 random bits, so a collision is not a practical concern even across billions of values.
Version 5 is deterministic: hashing the same namespace and name always returns the same UUID. That is useful when you need a stable identifier derived from something you already have — a URL, a file path, a product code — so two systems can compute the same id independently without coordinating.
Version 3 is version 5 with MD5 instead of SHA-1. Browsers' Web Crypto API deliberately does not implement MD5, and RFC 4122 already recommends version 5 in its place, so adding a hashing library purely for a deprecated digest is not worth the download. Use version 5 unless you are matching an existing v3 system.
No. Generation happens entirely in your browser using the Web Crypto API. No identifier, name, or namespace you enter is sent anywhere, logged, or stored — which matters, because these values usually become keys in your own database.
Up to 10,000 in a single batch. The limit exists so the page stays responsive; generating far more than that in one go would block the browser tab without giving you anything you could not get from two runs.
Nothing, in practice. GUID is Microsoft's name for the same 128-bit identifier. Windows and .NET tooling conventionally display them wrapped in braces and often in uppercase, which is what the formatting options here produce.
UUIDs are generated entirely in the browser with no library. Version 4 uses crypto.randomUUID() where the page is in a secure context, and otherwise falls back to crypto.getRandomValues() with the version and variant bits set by hand per RFC 4122 — both draw from the same cryptographically secure source. Version 1 composes a 60-bit timestamp counted in 100-nanosecond intervals since the Gregorian epoch of 15 October 1582, a 14-bit clock sequence that increments if the system clock moves backwards, and a random 48-bit node id with the multicast bit set, which RFC 4122 §4.5 prescribes when no MAC address is available. Version 5 hashes the namespace's 16 bytes followed by the UTF-8 encoded name with SHA-1 via the Web Crypto SubtleCrypto API, truncates the digest to 16 bytes, and stamps the version and variant nibbles, making the result deterministic for a given namespace and name. Formatting options transform the canonical lowercase string on output. Version 3 is not offered because it requires MD5, which Web Crypto does not implement and which RFC 4122 already supersedes with version 5.