What is a UUID?
A UUID (Universally Unique Identifier) is a 128-bit ID written as 36 characters — for example 550e8400-e29b-41d4-a716-446655440000. It is so unlikely that two random UUIDs ever match that developers use them as database keys, file names, session IDs and API identifiers without a central counter. The point is decentralisation: any device, anywhere, can generate an ID that will not clash with any other ID generated anywhere else. Our UUID Generator creates them in your browser, one at a time or in batches of up to 100.
UUID v4 — random
UUID v4 is the usual choice: 122 random bits, generated with secure randomness. The "4" in the version position — the 13th character — marks it as v4. Because the bits are random, two v4 UUIDs will essentially never match: the chance of a collision is so small that you would need to generate billions of UUIDs per second for a century to expect one. Use v4 whenever you need a fresh, unpredictable ID — for a database row, a file name, a session token or an API key.
UUID v1 — time-based
UUID v1 embeds the current date and time plus a device identifier, so it is unique and also sortable by time — IDs generated later sort after IDs generated earlier, which is useful for database indexes. The "1" in the version position marks it as v1. The trade-off is privacy: a v1 UUID reveals when it was created and, in the original design, the device's MAC address. Modern generators use a random node instead of the real MAC address. Use v1 when time-ordering matters, and v4 when it does not.
How to read a UUID
A UUID has five groups separated by hyphens: 8-4-4-4-12 characters. The first group is time or random data, the second and third are more time or random data, the fourth starts with the variant (usually 8, 9, a or b), and the fifth is the node. In 550e8400-e29b-41d4-a716-446655440000, the "4" in "41d4" tells you it is v4, and the "a" in "a716" tells you the variant. You do not need to read a UUID by eye — the validator in the generator decodes the version, variant and, for v1, the exact date and time hidden inside it.
Formatting: hyphens, case and braces
The same UUID can be written several ways: with hyphens (550e8400-e29b-41d4-a716-446655440000), without hyphens (550e8400e29b41d4a716446655440000), in lowercase or UPPERCASE, and with or without braces {550e8400-e29b-41d4-a716-446655440000}. Only the formatting differs — the 128-bit value is the same, and most systems accept any of them. Use the hyphenated lowercase form in text and documents, the compact form when a system asks for 32 characters, and braces when a system (like .NET) expects them.
Validating a UUID
Paste any UUID into the validator to check it: the tool confirms the format, tells you the version and variant, and for v1 shows the exact date and time it was created. A UUID that fails validation usually has the wrong length, a missing group, or a character outside 0–9 and a–f. Copying a UUID from a log file often adds a stray space or a line break — trim those first. If a system rejects your UUID, check whether it wants hyphens, braces or uppercase before you assume the value is wrong.
Where UUIDs are used
UUIDs are everywhere in software. Databases use them as primary keys, so records can be created on any device and merged later without clashes. Web apps use them as session IDs and API tokens. File systems and cloud storage use them as file names, so two users uploading "photo.jpg" never overwrite each other. Operating systems use them to identify disks and partitions. If you have ever seen a long string of letters and numbers in a URL or a settings file, it was probably a UUID.