How to use this UUID generator

Choose how many UUIDs you need — one, or a batch of up to 50. Tick UPPERCASE if your system expects capital letters, and untick hyphens if it wants the compact 32-character form. Press Generate and the batch appears in the panel, one UUID per line; changing an option re-generates it instantly. Copy All puts the batch on your clipboard; Download saves it as a text file.

What is a version 4 UUID?

Quick answer: A version 4 UUID is a 128-bit identifier built from random data, written as 36 characters — e.g. 3f6b2a90-4c1d-4e5f-8a2b-0d9c7e6f5a41. The 4 marks the version; 122 of the 128 bits are random, so duplicates are practically impossible.

UUID stands for Universally Unique Identifier, a format standardised by RFC 4122 and updated by RFC 9562. The idea: anyone can mint an identifier that is unique for all practical purposes, without asking a central authority for one. Other versions exist — v1 from a timestamp and machine address, v3 and v5 from hashes of names — but v4, pure randomness, is what most software means by “a UUID”: no coordination, no clock, no registration.

The anatomy of a v4 UUID

A UUID is displayed as five groups of hexadecimal digits separated by hyphens — 8, 4, 4, 4 and 12 digits, 36 characters in total. In version 4, two of those digits are not random at all:

GroupDigitsWhat it holds
18Random data
24Random data
34Starts with 4 — the version marker — then random data
44Starts with 8, 9, a or b — the variant marker — then random data
512Random data

The leading 4 in group three is the version field; group four’s first digit encodes the variant (top bits fixed to 10). Those markers are how software recognises a v4 UUID. Everything else — 122 bits — is random.

Where the randomness comes from

A UUID is only as good as its randomness, so this generator uses your browser’s cryptographic random source. Modern browsers provide crypto.randomUUID(); where that is unavailable, the tool fills 16 bytes with crypto.getRandomValues() and sets the version and variant bits itself. It never uses Math.random() — built for games and animations, its output can be predicted.

Can two v4 UUIDs ever collide?

Honestly: not mathematically impossible, just so unlikely that engineers build systems on the assumption it never happens. There are 2122 — about 5.3 × 1036 — possible v4 UUIDs. Because of the birthday effect, the chance of a duplicate reaches 50% only after roughly 2.7 quintillion (2.7 × 1018) have been generated; at a billion per second, that takes about 85 years. Be wary of any tool promising “guaranteed unique” — “practically impossible to duplicate” is the accurate claim.

Where v4 UUIDs are used

  • Database primary keys. Rows can be created on any server or device and merged later without key clashes — the classic reason to choose UUIDs over auto-increment numbers.
  • Idempotency and request IDs. APIs attach a UUID to each request or payment, so a retry is recognised and never processed twice.
  • Files and object storage. Random names stop uploads overwriting each other and make file URLs impractical to guess.

Uppercase and no-hyphen formats

Neither option changes the identifier — only how it is written. Some older systems store UUIDs in uppercase, and some APIs and database columns expect the compact 32-character form. If a system rejects your UUID, matching its expected case and hyphen style is the first fix; hyphens go back after the 8th, 12th, 16th and 20th characters.

Honest limitations, and your privacy

This tool generates version 4 only, in batches of up to 50 per press — press Generate again for more. If you need time-ordered (version 1 or 7) or name-based (versions 3 or 5) identifiers, you will need a different generator. crypto.randomUUID() needs a current browser on a secure (HTTPS) page; the fallback covers older browsers. Nothing generated here is stored or transmitted — UUIDs exist only in your tab until you copy or download them.