Runs in your browser. Your files and text never leave your device - nothing is uploaded.
Generate UUIDs and GUIDs Online
The Tools Kit’s free UUID Generator creates random version 4 UUIDs or time-sortable version 7 UUIDs, from a single ID up to 500 in one click. Each value is a standard 128-bit identifier in the 36-character 8-4-4-4-12 format, ready to use as a database key, an object or file ID, or a GUID in Windows and .NET code.
Everything happens in your browser. The random bits come from crypto.getRandomValues, the Web Crypto API’s secure random source, and no UUID is sent to a server, stored or logged. Switch on uppercase or curly braces when a system expects the GUID style, then copy one value or the whole list.
How to Use the UUID Generator
- 1
Choose a version
Pick v4 - random for fully random UUIDs, or v7 - time-sortable for UUIDs that begin with a millisecond timestamp and sort in creation order. v4 is selected by default.
- 2
Choose how many
Use the How many? menu to generate 1, 5, 10, 25, 50, 100 or 500 UUIDs in one batch. It starts at 5.
- 3
Generate the UUIDs
Click Generate UUIDs. Each identifier appears on its own row; click again for a fresh batch.
- 4
Format and copy
Tick Uppercase or Wrap in braces (GUID style) if your system expects that format, then use Copy on a single row or Copy all to copy the whole list, one UUID per line.
There is no sign-up and no limit on how many batches you generate.
UUID v4 vs v7 vs GUID
All three are the same 128-bit identifier in the same 8-4-4-4-12 format. What differs is how the bits are filled, and that decides how well they behave as a database key.
| Property | UUID v4 | UUID v7 | GUID |
|---|---|---|---|
| What fills it | 122 random bits | 48-bit timestamp + 74 random bits | Microsoft’s name for the same standard |
| Sortable by time | No | Yes, to the millisecond | Depends on version |
| Database index behavior | Random inserts fragment the index | Inserts append, like an auto-increment key | As per its version |
| Leaks creation time | No | Yes, the timestamp is readable | Depends on version |
| Typical use | Public IDs and anything where unpredictability matters | Primary keys, event logs, anything inserted in volume | .NET and Windows APIs |
The practical rule: use v7 for database primary keys, and v4 when the identifier is exposed publicly and its creation time should stay private. Either way, a UUID is an identifier, not a secret. For API keys or account credentials, generate a long random string with the password generator instead, and if you need to prove a request really came from you, sign it with the HMAC generator.
Reading a UUID
| Position | Characters | Meaning |
|---|---|---|
| Overall | 36 | 32 hex digits plus 4 hyphens |
| Group pattern | 8-4-4-4-12 | The canonical hyphenated form |
| 15th character | 1 | The version digit: 4 for random, 7 for time-sortable |
| 20th character | 1 | The variant: 8, 9, a or b for the RFC 9562 layout |
In a v7 UUID the first 12 hex digits, ignoring the hyphen, are a Unix timestamp in milliseconds. Take a value that begins 01a0fc7c-4e00-7: the hex number 01a0fc7c4e00 equals 1,790,942,400,000, which is 2 October 2026 at 12:00:00 UTC. Paste that number into the Unix timestamp converter to turn any v7 prefix into a readable date. A v4 UUID has no such field; apart from the version and variant characters, every digit is random.
UUIDs often travel inside JSON request bodies and token claims. When you are debugging one, the JSON formatter makes nested IDs easy to spot, and the JWT decoder shows the jti or sub claim where many systems store a UUID.
How Likely Is a UUID Collision?
A version 4 UUID has 122 random bits, giving about 5.3 × 1036 possible values. The risk grows with the square of how many you generate, so it is small but not zero at extreme volumes: generating a billion UUIDs a second for a century (about 3.16 × 1018 UUIDs) works out to roughly a 61% chance of at least one collision somewhere in that set, and the 50% mark arrives after about 86 years. For virtually any real application, even one issuing millions of IDs a day, the probability is astronomically small.
Problems in practice come from a broken random source, never from exhausting the space, which is why this generator uses the browser’s cryptographic crypto.getRandomValues rather than Math.random. A v7 UUID has fewer random bits (74), but its timestamp means two values can only collide if they are created in the same millisecond.
This tool does not create the name-based versions 3 and 5, which produce the same UUID every time from a namespace and a name by hashing them with MD5 or SHA-1. If you only need a repeatable fingerprint of some text rather than a UUID, the MD5 hash generator or the SHA-256 hash generator will do that directly.
Common uses
- Primary keys for database rows, especially v7 for tables that grow quickly
- IDs created on the client or across several services without a central counter
- Bulk test and seed data, using a batch of up to 500 copied in one go
- Correlation and request IDs that tie log lines together across systems
- GUIDs for .NET, COM, Windows registry entries and installer packages
- Unique file names, object storage keys and idempotency keys
For more hashing, encoding and token utilities, browse all security tools.
UUID terms explained
| Term | What it means here |
|---|---|
| UUID | Universally Unique Identifier: a 128-bit value written as 32 hex digits in the 8-4-4-4-12 pattern |
| GUID | Globally Unique Identifier, Microsoft’s name for the same 128-bit standard, often shown in braces |
| RFC 9562 | The 2024 IETF standard that defines UUID versions, including v4 and v7; it replaced RFC 4122 |
| Version digit | The 15th character of the string: 4 for a random UUID, 7 for a time-ordered one |
| Variant | Two fixed bits that mark the RFC layout; they make the 20th character 8, 9, a or b |
| Unix epoch milliseconds | Milliseconds since 1 January 1970 UTC; the first 48 bits of a v7 UUID |
| CSPRNG | A cryptographically secure random number generator; in browsers this is crypto.getRandomValues |
Frequently Asked Questions
A UUID (universally unique identifier) is a 128-bit value written as 36 characters: 32 hexadecimal digits split 8-4-4-4-12 by four hyphens, such as 9b2e4c1a-7f3d-4a8e-b5c6-0d1e2f3a4b5c. Because any system can create one without asking a central server, UUIDs are widely used as database keys and object IDs.
A v4 UUID fills 122 bits with random data, so it reveals nothing and has no order. A v7 UUID puts a 48-bit Unix millisecond timestamp first and fills the remaining 74 bits with random data, so v7 values sort by creation time and insert neatly into database indexes, at the cost of revealing when they were made.
Yes. GUID is Microsoft’s name for the same 128-bit identifier, with the same length and 8-4-4-4-12 layout. Windows and .NET tools often show GUIDs in uppercase and wrapped in curly braces, which you can reproduce here with the Uppercase and Wrap in braces options.
In theory yes, in practice no. A v4 UUID has 2^122, about 5.3 × 10^36, possible values. You would need to generate about a billion UUIDs every second for roughly 86 years to reach a 50% chance of a single duplicate. Real collisions come from broken random number generators, which is why this tool uses crypto.getRandomValues.
No. Every UUID is created in your browser with the Web Crypto API’s crypto.getRandomValues. Nothing is sent to a server, saved or logged, and the list disappears when you reload or close the page.
Up to 500 per click. The How many? menu offers 1, 5, 10, 25, 50, 100 and 500, and you can click Generate UUIDs as often as you like. Copy all copies the whole batch with one UUID per line, ready to paste into a script, spreadsheet or seed file.
Use v7. Its timestamp prefix means new keys land at the end of a B-tree index instead of at random positions, which reduces page splits and fragmentation compared with v4. Use v4 when the ID is public and you do not want it to reveal its creation time.
Yes. The first 12 hex digits, ignoring the hyphen, are the Unix time in milliseconds. For example, a v7 UUID that starts 01a0fc7c-4e00 holds 0x01a0fc7c4e00, which is 1790942400000 milliseconds, or 2 October 2026 at 12:00:00 UTC.
Across different milliseconds, yes, and the batch is listed in the order it was generated. UUIDs created within the same millisecond share a timestamp and differ only in their random bits, so their order among themselves is arbitrary; this tool does not add the optional monotonic counter that RFC 9562 allows.
Tick Uppercase to switch the hex letters to A-F, and tick Wrap in braces (GUID style) to add curly braces around each value. Both options change the current list instantly, and Copy and Copy all copy exactly what is shown.
No. It generates version 4 (random) and version 7 (time-ordered) only. Version 1 embeds a timestamp and often a MAC address, while versions 3 and 5 are derived by hashing a namespace and name with MD5 or SHA-1, so they need a name as input rather than random bits.
It is not recommended. A v4 UUID from a secure generator is hard to guess, but RFC 9562 advises against relying on UUIDs as security credentials, and a v7 UUID exposes its creation time and has fewer random bits. Use a purpose-built random password or secret instead.
Related developer tools
Reviewed by Raja Jahangir · Last reviewed: October 7, 2026
What is a UUID?
A UUID is a 128-bit identifier written as 36 characters in the pattern 8-4-4-4-12, such as 3f2b8c1e-4a5d-4e7f-9b0a-1c2d3e4f5a6b. UUIDs are generated independently with no central coordinator, and the space is large enough that random v4 collisions are not a practical concern.
What is the difference between UUID v4 and v7?
UUID v4 is fully random, which makes it unpredictable but poorly ordered - random inserts fragment database indexes. UUID v7 puts a millisecond timestamp in the leading bits, so v7 values sort chronologically and index far better, while keeping enough randomness to stay unguessable.
Is a GUID the same as a UUID?
Yes, in practice. GUID is Microsoft's name for the same 128-bit identifier standard that everyone else calls a UUID, and the two are interchangeable in format and length. GUIDs are sometimes displayed wrapped in braces, but the underlying value is identical.
