← All tools/Generators/Text/UUID Generator
UUID Generator
Random UUID version 4 identifiers — generated in your browser, ready to copy.
Generated locally with your browser’s cryptographic random source — nothing is sent anywhere. UUIDs are random, not sequential, so they do not sort by creation time.
Your UUIDs
How it works
Method: each UUID is a version 4 UUID under RFC 4122 — 122 random bits from the browser’s cryptographic random source (crypto.getRandomValues). The 13th hex digit is always 4 (the version) and the 17th is 8, 9, a or b (the variant). Format: 8-4-4-4-12 hex digits with hyphens (36 characters), or 32 hex digits without.
A UUID is a 128-bit label, written as 32 hexadecimal digits — the characters 0–9 and a–f. Version 4 means the value is random: 122 of the 128 bits come from the browser’s cryptographic random source, and the other 6 bits are fixed so that any reader can tell which version it is. The 13th hex digit is always 4, marking version 4, and the 17th hex digit is always 8, 9, a or b, marking the standard variant. The hyphens are only separators: the grouped form 8-4-4-4-12 is 36 characters long, and removing the hyphens leaves the same 32 digits. Nothing about a UUID says when it was made or what it belongs to — it carries no timestamp, no name and no counter, so two UUIDs made a second apart are as unrelated as two made a year apart. That is the point: a random 122-bit space is so large that generating the same one twice is, for practical purposes, impossible.
Worked example: asking for 5 UUIDs with hyphens gives five lines like 2aa1ac84-47fe-4f51-87f0-178b1f8e8bed — 36 characters, the 13th hex digit is 4 and the 17th is 8, 9, a or b. Asking for 10 without hyphens gives ten 32-character lines instead. Every click of Generate new produces a fresh set.
Worked example 2: asking for 3 UUIDs without hyphens gives three 32-character lines, each a fresh random value such as 9f4e2a1b3c8d4e6f9a2b7c1d5e8f0a3b (example only — your run will differ). Count the characters: 32, with no hyphens. With hyphens, the same value reads 9f4e2a1b-3c8d-4e6f-9a2b-7c1d5e8f0a3b — 36 characters, the 13th hex digit 4 and the 17th 9. There are 2¹²², about 5.32 × 10³⁶, possible version 4 UUIDs, so a set of three has no realistic chance of repeating a value you generated before.
Common mistakes
Do not use a UUID as a password or a secret: it is an identifier, not a credential, and anyone who sees it can use it as a key. Do not store a UUID as a number either — the hex digits include letters, and a database column that strips leading zeros or treats the value as an integer will corrupt it; store it as text, exactly as generated. Do not sort UUIDs and expect creation order: version 4 values are random, so the newest record is not the last one in the list — if you need ordering, use version 7 or keep a separate created-at timestamp. Do not reuse one UUID for two different things, even inside the same project: the whole value of a UUID is that each thing gets its own, and sharing one across a user and an order invites exactly the mix-up it exists to prevent. And do not hand-type a UUID from a screenshot: copy it with the button instead — a single mistyped hex digit points at a different record, or at none at all.
Frequently asked questions
What is a UUID?
A Universally Unique Identifier — a 128-bit label written as 32 hex digits, usually grouped 8-4-4-4-12 with hyphens. They are used as database keys, file names and request IDs because the chance of two random ones colliding is effectively zero.
What does version 4 mean?
Version 4 means the UUID is random: 122 of its 128 bits come from a random source. Other versions are based on time (v1), a namespace and a name (v3/v5), or a timestamp plus randomness (v7).
Are these UUIDs really random?
Yes — they use your browser’s cryptographic random source (crypto.getRandomValues), the same source behind secure web features. They are not seeded from the time or from Math.random.
Can two UUIDs be the same?
In practice, no. With 122 random bits there are about 5 × 10³⁶ possible version 4 UUIDs — you would need to generate about a billion a second for a century before a collision became likely.
With or without hyphens?
The same UUID either way — hyphens are only separators. Use hyphens for database keys and logs (the standard form), and no hyphens when a compact 32-character token is easier, for example in a URL or file name.
More tools
Tell us what you think
Loving this tool, or stuck on something? Tell us — it takes a minute.
We’ll only use your name and email to reply if needed. The tool and page are filled in for you.