Quick Answer
Press Generate to make random version 4 UUIDs such as 3f2b8c9e-7d41-4a6b-9c0e-5b1d2a7f8e64. Choose how many you need, up to 1,000, and whether you want uppercase letters, no hyphens or braces. Paste any UUID into Check a UUID to see if it is valid and which version it is.
Embed this calculator
Adjust the size if needed, then copy the code below into your page or blog. The calculator will load in an iframe and stay updated automatically.
Table of Contents
- UUID Generator
- Quick Answer
- Related Calculators
- How This UUID Generator Works
- How to Use the UUID Generator
- How a Version 4 UUID Is Made
- Key Terms
- Worked Example
- Real-Life Examples
- UUID Version 4 vs Version 7
- UUID Parts
- Tips for Using UUIDs
- Common Mistakes to Avoid
- Frequently Asked Questions
- References & Sources
How This UUID Generator Works
A UUID (universally unique identifier), also called a GUID in Microsoft tools, is a 128-bit label used to name records, files, devices and messages without a central list. Version 4 UUIDs are random, so anyone can make one at any time with a tiny chance of a clash.
Features:
- Bulk: 1 to 1,000 UUIDs at once, one per line.
- Formats: lowercase or uppercase, with or without hyphens, or in braces.
- Secure randomness: from your browser's cryptographic generator.
- Checker: validate a UUID and read its version and variant.
How to Use the UUID Generator
- Enter how many UUIDs you need.
- Choose lowercase or uppercase letters.
- Choose the format: standard, no hyphens or braces.
- Press Generate and copy the list.
- Optionally paste a UUID into Check a UUID to validate it.
How a Version 4 UUID Is Made
- Size: 128 bits, written as 32 hex digits in groups of 8, 4, 4, 4 and 12.
- Version: the first digit of the third group is always 4.
- Variant: the first digit of the fourth group is 8, 9, a or b for standard UUIDs.
- Random bits: the other 122 bits are random, giving 2 to the power 122 possible values.
- Standard: the layout is defined in RFC 9562, which replaced RFC 4122 in 2024.
Key Terms
- UUID: universally unique identifier, a 128-bit label.
- GUID: globally unique identifier, Microsoft's name for a UUID.
- Version: which method made the UUID, shown by one digit.
- Variant: which layout the UUID follows, shown by the next group's first digit.
Worked Example
Read the UUID 3f2b8c9e-7d41-4a6b-9c0e-5b1d2a7f8e64.
- Groups: 3f2b8c9e, 7d41, 4a6b, 9c0e, 5b1d2a7f8e64 (8-4-4-4-12)
- Third group starts with 4, so it is version 4 (random)
- Fourth group starts with 9, so the variant is the standard RFC 9562 one
- Without hyphens it is 32 characters long, with the same digits in the same order
Real-Life Examples
- Database keys: make 100 IDs for test records in one click.
- File names: name uploads so they never collide.
- Windows and .NET: copy a GUID in braces for a registry or project file.
- APIs: send a new UUID as a request ID to trace each call.
UUID Version 4 vs Version 7
- Version 4: fully random apart from 6 fixed bits; the most common choice.
- Version 7: starts with a Unix timestamp in milliseconds, so new IDs sort after older ones, which suits database indexes.
- Both: are 128 bits, use the same text format, and are defined in RFC 9562.
UUID Parts
Layout from RFC 9562.
| Group | Hex digits | What it holds |
|---|---|---|
| 1 | 8 | Random |
| 2 | 4 | Random |
| 3 | 4 | Version digit 4, then random |
| 4 | 4 | Variant (8, 9, a or b), then random |
| 5 | 12 | Random |
Tips for Using UUIDs
- Store them as text or binary: 36 characters with hyphens, or 16 bytes as binary.
- Case does not matter: lowercase and uppercase mean the same UUID; lowercase is the usual style.
- Not secret: UUIDs identify things; do not use them as passwords.
- Sorting: version 4 UUIDs are random, so they do not sort by time. Version 7 adds a timestamp for that.
Common Mistakes to Avoid
- Using UUIDs as passwords. They are identifiers, not secrets.
- Typing them by hand. One wrong digit makes a different UUID; copy and paste.
- Expecting time order from version 4. Random UUIDs do not sort by creation time.
- Mixing formats in one system. Pick hyphens or no hyphens and stay consistent.
- Using a weak random source. Use a secure generator, like the one in this tool.
Frequently Asked Questions
A 128-bit identifier written as 32 hex digits, such as 3f2b8c9e-7d41-4a6b-9c0e-5b1d2a7f8e64.
Yes. GUID is the name Microsoft uses for the same 128-bit identifier.
Each has 122 random bits, so the chance of two matching is extremely small in practice.
Up to 1,000.
Yes. Choose No hyphens under Format.
Paste it into Check a UUID. The table shows if it is valid and its version.
No. They are made in your browser and not stored.
It is the version digit. Version 4 means the UUID is random.
RFC 9562, published in 2024, which replaced RFC 4122.
A special UUID with all 128 bits set to zero, written 00000000-0000-0000-0000-000000000000. It is often used to mean no value. The checker recognises it.
Either works as long as you are consistent. Hyphens make UUIDs easier to read, while removing them saves 4 characters. Many databases also have a dedicated UUID type that stores the 16 bytes directly.
In theory yes, but with 122 random bits the odds are so small that it is not a practical concern for normal systems, as long as a good random source is used.
Version 4 UUIDs are random, so every press of Generate gives a completely new set.
References & Sources
| Source | Used For | Link |
|---|---|---|
| IETF RFC 9562, Universally Unique IDentifiers (UUIDs) | UUID layout, versions 4 and 7, and variants. | https://www.rfc-editor.org/rfc/rfc9562 |
| MDN Web Docs, Crypto.randomUUID() | The browser function used to make version 4 UUIDs. | https://developer.mozilla.org/en-US/docs/Web/API/Crypto/randomUUID |