What Is a UUID?
Updated 2026-07-04 · By the MakeToolz team
Quick answer: A UUID is a 128-bit value used as a unique identifier, so two things never clash. Version 4 UUIDs are random and look like 3f2504e0-4f89-41d3-9a0c-0305e82c3301. You can create one on any machine with no central server, which is why databases and apps rely on them.
The name stands for universally unique identifier. It is a way to give something an ID that is almost certain to be one of a kind, even when thousands of computers are minting IDs at the same moment without talking to each other.
What the letters and the shape mean
UUID stands for universally unique identifier. Microsoft calls the exact same thing a GUID, or globally unique identifier, so if you see either word, they mean the same 128-bit value.
A UUID is a 128-bit number written as 32 hexadecimal characters, split into five groups by hyphens in an 8-4-4-4-12 pattern. That fixed shape, like 3f2504e0-4f89-41d3-9a0c-0305e82c3301, makes a UUID easy to spot in a log, a URL, or a database column. Hexadecimal just means each character is one of 16 values, 0 through 9 and a through f.
The versions, and why version 4 wins
There are several types of UUID, and each fills the 128 bits a different way:
- Version 1 mixes the time and the computer's network address. It is unique but can leak when and where it was made.
- Version 4 is almost entirely random. This is the one you will see most often.
- Version 5 is built from a name plus a namespace, so the same input always gives the same UUID.
- Version 7 is newer and puts a timestamp at the front, so the IDs sort in time order while staying unique.
Version 4 is the default for most apps because it needs no clock, no hardware address, and no coordination. Two fixed markers tell software it is a version 4, and the other 122 bits are random. Our UUID generator makes version 4 UUIDs by default.
Why UUIDs almost never collide
With 122 random bits, the number of possible version 4 UUIDs is astronomically large. The pool is so big that generating a duplicate by chance is effectively impossible in normal use. You would need to produce billions of UUIDs every second for many years before a single clash became likely.
This is the whole appeal. A regular auto-incrementing ID (1, 2, 3, and so on) only works if one server hands out the numbers, or two servers will both create a "row 5". A UUID lets any machine, phone, or offline app create an ID on its own and trust it will not overlap with anyone else's.
Where UUIDs show up
- Database keys. Each row gets a UUID, so records created on different servers never fight over the same ID, which makes merging and syncing data far easier.
- File and upload names. Naming an upload with a UUID stops two files called "photo.jpg" from overwriting each other.
- Request and session IDs. A UUID tags one action or one login so you can trace it through logs across many services.
- Offline and mobile apps. A phone with no signal can create records with UUIDs, then sync them later with no ID conflicts.
- Distributed systems. Message queues and event streams use UUIDs so every event has a unique handle.
How to create a UUID
You do not need to write code. Open the free UUID Generator, choose how many you want, and click generate. It creates one or hundreds at a time using your browser's real randomness, with options for uppercase or removing the hyphens. Everything runs locally, so nothing is sent to a server.
People Also Ask
Is a UUID the same as a GUID?
Yes. UUID is the general term and GUID is Microsoft's name for the same thing. Both describe a 128-bit identifier written in the same 8-4-4-4-12 hex format. You can treat the two words as interchangeable.
Can two UUIDs ever be the same?
In theory yes, but the odds are so small they do not matter in real use. A version 4 UUID has 122 random bits, which is a vast number of possibilities. You would have to generate an unrealistic volume of them before a collision became plausible.
Are UUIDs secret or secure?
No. A UUID is an identifier, not a password. It is fine to show one in a URL, a log, or an API response. Because a version 4 UUID is random and hard to guess it adds a little obscurity, but never rely on it as a secret or access token on its own.
What is the difference between UUID v1, v4, and v7?
Version 1 is based on the time and the machine's network address. Version 4 is random and reveals nothing about when or where it was made. Version 7 is time-ordered, so the IDs sort roughly by creation time while staying unique. Version 4 is the common default; version 7 is gaining popularity for database keys.
Why do apps use UUIDs instead of simple numbers?
Because simple auto-increment numbers need one central place to hand them out, which breaks when many servers or offline devices create records at once. UUIDs let any machine mint an ID independently with no coordination and almost no chance of overlap, which makes syncing and scaling far simpler.
How many characters is a UUID?
A standard UUID is 36 characters: 32 hexadecimal digits plus four hyphens. If you strip the hyphens it is 32 characters. Some systems store it as a raw 128-bit value, which takes 16 bytes and is more compact than the text form.
Are UUIDs case sensitive?
No. The hex letters can be written in uppercase or lowercase and still mean the same value. Lowercase is the common convention, but a tool that outputs uppercase produces an equally valid UUID.
Can I use a UUID as a primary key in a database?
Yes, and many teams do. It removes the need for a central ID counter and prevents conflicts when data comes from multiple sources. The trade-off is that random UUIDs can be less efficient to index than sequential numbers, which is one reason time-ordered version 7 UUIDs were created.
Need one right now? The free UUID Generator creates a single UUID or a whole batch in your browser, with uppercase and no-hyphen options, so you can drop a guaranteed-unique ID into your code or database in seconds.