Every Question You Have About UUIDs — Answered
UUID generators are one of those tools that developers use constantly but rarely stop to understand. You need a unique ID, you generate a UUID, you move on. This article covers everything — what UUIDs actually are, why they exist, when to use them, and when not to.
—What exactly is a UUID?
UUID stands for Universally Unique Identifier. It is a 128-bit number displayed as a string of 32 hexadecimal characters separated by hyphens in a specific pattern: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
A real UUID looks like this: 550e8400-e29b-41d4-a716-446655440000
The five groups contain 8, 4, 4, 4, and 12 characters respectively, always totaling 32 hexadecimal characters and 4 hyphens. Every UUID you generate follows this exact format regardless of which version you use.
—Why does the world need unique IDs at all?
The moment you have more than one system generating data, you have a collision problem. System A creates a record with ID 1. System B also creates a record with ID 1. When you try to merge the data, you cannot tell which record is which.
Simple sequential integers — 1, 2, 3, 4 — work perfectly in a single database on a single server. They fail immediately when you have multiple servers, microservices, distributed databases, offline-capable mobile apps, or any system where records can be created in more than one place at the same time.
UUIDs solve this because they are generated independently without any central coordination and are statistically guaranteed to be unique. Two different systems generating UUIDs at the same millisecond will produce different values with overwhelming probability.
—What are the different UUID versions?
UUID v1 — Timestamp-based. Generated using the current timestamp combined with the MAC address of the generating machine. The timestamp makes v1 UUIDs sortable by creation time, but the MAC address inclusion raises privacy concerns. The machine that generated a v1 UUID can be identified from the UUID itself.
UUID v3 — Name-based with MD5. Generated by hashing a namespace and a name using MD5. The same namespace and name always produce the same UUID. Useful when you need a deterministic UUID for a known input — for example, always generating the same UUID for a specific URL.
UUID v4 — Random. Generated from random or pseudo-random numbers. This is the version used in the vast majority of applications. It has no structure, no timestamp, no machine identifier — just randomness. The probability of generating the same v4 UUID twice is so astronomically small that it is treated as impossible for practical purposes.
UUID v5 — Name-based with SHA-1. Same concept as v3 but uses SHA-1 instead of MD5. Preferred over v3 because SHA-1 is more collision-resistant than MD5.
For almost every use case, UUID v4 is the correct choice. It is random, it has no privacy implications, and it is supported natively by virtually every programming language and database.
—How unique is “unique enough”?
This question comes up every time someone learns about UUIDs. The numbers are reassuring.
There are 2^122 possible UUID v4 values — approximately 5.3 undecillion unique UUIDs. To put that in perspective: if you generated one billion UUIDs every second, it would take approximately 85 billion years to have a 50 percent chance of generating a single duplicate. The universe is approximately 13.8 billion years old.
UUID collisions are not a real-world concern. They are a theoretical curiosity.
—When should I use a UUID instead of an auto-increment ID?
Use UUID when: you have multiple data sources that need to merge, you are building a distributed system, you are storing IDs in a client application before syncing to a server, you do not want sequential IDs that reveal how many records exist in your database, or you need IDs that are safe to expose in URLs without leaking business information.
Use auto-increment when: you have a simple single-database application, storage space is a concern (UUIDs are 36 characters versus a few digits for integers), query performance on indexed primary keys is critical, or human readability of IDs matters.
UUIDs are not always better than integers. They are better in specific situations. Choosing UUIDs unnecessarily adds storage overhead and can slow down indexed queries in large databases.
—Where are UUIDs actually used in real systems?
More places than most people realize. Every AWS resource — EC2 instances, S3 buckets, Lambda functions — has a UUID as its identifier. Every transaction ID in payment systems uses a UUID or UUID-like identifier. Every session token in web applications is typically a UUID. Every device in an IoT system gets a UUID. Git commit hashes are not UUIDs but serve the same collision-avoidance purpose using a different algorithm.
If you have ever looked at a URL and seen a long string of letters, numbers, and hyphens where you expected to see a sequential number, you were looking at a UUID.
—Frequently Asked Questions
Can I use a UUID as a database primary key?
Yes, and it is common practice. The main tradeoff is storage and index performance. A UUID primary key uses significantly more storage than an integer, and random UUIDs cause index fragmentation in B-tree indexes because new records are inserted at random positions rather than always at the end. UUID v7, a newer version, addresses this by combining timestamp ordering with randomness to maintain insertion order.
Are UUIDs case sensitive?
No. UUID characters are hexadecimal and are case-insensitive. 550E8400-E29B-41D4 and 550e8400-e29b-41d4 represent the same UUID. The standard convention is lowercase, but most systems accept either.
Can I generate UUIDs without an internet connection?
Yes. UUID v4 generation requires only a random number generator, which is available in every programming language and operating system without any network connection. This tool generates UUIDs entirely in your browser with no server communication.
What is a GUID? Is it the same as a UUID?
GUID stands for Globally Unique Identifier and is Microsoft’s implementation of the UUID standard. For all practical purposes, a GUID and a UUID are the same thing. Microsoft tools and documentation use the term GUID; everything else uses UUID.
Is this tool free?
Yes, completely free. UUID generation happens in your browser. No data is sent to any server.
—Generate. Copy. Use.
Click the generate button to create one or multiple UUIDs. Copy any UUID individually or copy all of them at once. Every UUID generated here is a cryptographically random v4 UUID ready to use as a database primary key, session token, transaction ID, or any other unique identifier your application needs.