Runs in your browser. Nothing you enter is uploaded or stored.
To generate a UUID, open the free UUID Generator above, choose random version 4 or time-ordered version 7, set how many you need, up to 1,000, and press Run. Each one is created with your browser’s secure random generator. You can switch to upper case, remove the hyphens or wrap them in braces, and there is a check mode that validates pasted UUIDs and tells you their version, variant and, for version 7, the time they were created.
Last updated: 11 November 2026. Written by Saad Raza.
Key takeaways
- A UUID is a 128-bit identifier, written as 32 hexadecimal digits in five groups, for example 550e8400-e29b-41d4-a716-446655440000. It is designed so that two systems can create identifiers without coordinating and still almost never collide.
- Version 4 is random, with 122 random bits. Version 7 starts with a millisecond timestamp followed by random bits, so values sort in the order they were created.
- A UUID is an identifier, not a secret. It is not a password and should not be used as a security token on its own.
- Time-ordered UUIDs are friendlier to databases, because new rows are added at the end of an index instead of in random positions.
- The tool uses the Web Crypto random generator in your browser. Nothing is uploaded or stored.
What a UUID is and where you meet it
UUID stands for universally unique identifier, and is also called a GUID in some Microsoft systems. You see UUIDs as record IDs in databases, as file and session names, as order and tracking references, as device and install identifiers in apps, and in tag manager and analytics setups where an event or a client needs a unique ID. WordPress plugins, headless CMS platforms, e-commerce systems and APIs use them widely, and structured data and feeds sometimes need a stable unique ID for an item.
The main benefit is that you can generate one anywhere, without asking a central server, and be confident it is unique. The chance of two random version 4 UUIDs colliding is so small that it can be ignored in practice, even with billions of records.
How to use the UUID Generator
- Choose what to do: generate random UUIDs (version 4), generate time-ordered UUIDs (version 7), or check and inspect UUIDs.
- For generation, enter how many you need, from 1 to 1,000. The tool already shows a set of 10 when the page loads.
- Choose the format: Upper case, Keep hyphens and Wrap in braces. Some systems expect no hyphens or braces, and some databases are happy with either.
- Press Run, then copy the list or download it as a text file.
- To check existing values, choose check mode, paste up to 2,000 UUIDs, one per line, and press Run. Curly braces, hyphen-free values and the urn:uuid: prefix are all accepted.
Version 4 or version 7
| Version 4 | Version 7 | |
|---|---|---|
| What it contains | Random bits | A millisecond timestamp, then random bits |
| Random bits | 122 | 74 |
| Sorts by creation time | No | Yes |
| Database index friendliness | Scatters inserts | Appends inserts |
| Reveals creation time | No | Yes, to the millisecond |
| Best for | General use, when time should stay private | Record IDs in busy databases, logs and events |
The trade-off is privacy. A version 7 UUID contains the time it was made, so do not use it where the creation time should stay hidden, for example in a public link that identifies a private record. In that case, use version 4.
A worked example
The example switches to check mode with five lines. The first, 550e8400-e29b-41d4-a716-446655440000, is a valid version 4 UUID in the standard variant and is noted as random. The second, 018f3a2e-7b3c-7d2a-9c11-2f6a5b8e4d10, is valid version 7, and the tool reads the timestamp from its first 48 bits and reports that it was created on 2 May 2024 at 16:41:15 UTC. The third has curly braces and capital letters, {123E4567-E89B-12D3-A456-426614174000}, and is accepted as a valid version 1 UUID.
The fourth is the nil UUID, 00000000-0000-0000-0000-000000000000, which the tool recognises as the special all-zero value. The fifth, not-a-uuid, is rejected with the reason that a UUID needs 32 hex digits. The summary shows 5 checked, 4 valid and 1 invalid. In generation mode, the summary tells you the number made, the version, and the random bits in each: 122 for version 4 and 74 for version 7.
Using UUIDs well
- Store them efficiently. Many databases have a native UUID type that uses 16 bytes. Storing them as text uses more space and is slower to compare.
- Do not use them as secrets. Anyone who has the value can use it. For passwords and tokens, use the password generator, which makes strong random strings and shows their entropy.
- Prefer version 7 for primary keys. It keeps inserts ordered. Use version 4 where you do not want the time to show.
- Keep the format consistent. Choose upper or lower case and hyphens or none, and stick with it, since many systems compare IDs as text. Lower case with hyphens is the most common.
- Never reuse a UUID for a different record. Once an ID has been used in a URL or a feed, keep it stable.
- Do not put them in page URLs for SEO. Readable slugs are better for users and search engines. Make them with the SEO slug generator, and keep the UUID as an internal ID.
UUIDs in marketing and analytics
A UUID can name a campaign, an experiment, an order or a lead so that data from different systems can be joined without clashes. For event tracking, naming events and IDs consistently matters, so decide the format before you start. If you pass an ID in a link, remember that special characters should be encoded: UUIDs contain only letters, digits and hyphens, so they are safe in a URL, but other values you combine with them may not be. Use the URL encoder and decoder for those, and the UTM bulk builder for tagged campaign links.
If you move UUIDs between a spreadsheet and a script, the JSON to CSV converter handles the format, and the remove duplicate lines tool confirms that a list has no repeats. To fingerprint a value rather than identify it, use the hash generator. For tracking and data problems in a live site, an SEO audit that includes analytics review can find where IDs are being lost.
Limits
The generator creates version 4 and version 7 UUIDs. It does not create version 1, 3, 5, 6 or 8, although the check mode can read the version of any standard UUID. For version 7 it uses the current time in milliseconds and keeps a batch in order, but values made in the same millisecond are ordered only within one batch, not across separate runs. It needs a browser with the Web Crypto random generator, which all current browsers have. The check mode validates the format and reads the version and variant, but it cannot know whether the ID exists anywhere. It accepts up to 2,000 values per run, and generation is limited to 1,000 at a time. Everything is processed in your browser, and nothing is sent to a server.
Questions about the UUID Generator
What is a UUID?
A 128-bit identifier written as 32 hex digits in the pattern 8-4-4-4-12. It lets different systems create unique IDs without checking with each other.
What is the difference between UUID version 4 and version 7?
Version 4 is entirely random. Version 7 begins with a timestamp, so values sort by creation time, which suits database keys, but it reveals when the ID was made.
Can two UUIDs be the same?
In theory yes, in practice no. The chance of a collision between random version 4 UUIDs is so small that it is ignored even for very large systems.
Is a UUID the same as a GUID?
Yes. GUID is the name used in many Microsoft systems for the same 128-bit identifier, sometimes written in capitals and curly braces.
Are the UUIDs stored or sent anywhere?
No. They are generated in your browser with its secure random generator, and nothing is stored or uploaded.
If you want help with tracking, data and technical SEO, see my SEO services or ask for a free audit. You can also browse the other free technical SEO tools.
Request received
Thank you! Saad will contact you within the next 24 hours.
Keep an eye on your phone and inbox.
