Use the free UUID Validator and Parser below: your data never leaves your browser — all work happens on your device, and nothing is uploaded to any server.
UUIDs: the IDs that never need a central registry
Every time you need a unique identifier, you face the same problem: how do you make sure nobody else picks the same one? The classic answer is a central counter, but that requires coordination. UUIDs take the opposite approach. They are 128-bit numbers, generated with enough randomness, or with enough structure, that two independent generators essentially never collide. That is why UUIDs appear everywhere: database keys, file names, session tokens, distributed systems, anywhere uniqueness must work without asking permission.
A UUID is written as 32 hex digits in five groups, 8-4-4-4-12, like 550e8400-e29b-41d4-a716-446655440000. Two of those digits carry meaning. The first digit of the third group is the version, which says how the UUID was made. The first digit of the fourth group encodes the variant, which says which standard it follows. The rest is the actual unique value. This tool reads those digits and tells you the version, the variant, and, for time-based versions, the timestamp hidden inside.
The versions, and when to use each
Version 1 UUIDs embed a timestamp and a hardware address. They are sortable by time, but they leak the machine’s address and the creation time, which is a privacy problem, so they have largely fallen out of favor. Version 4 UUIDs are purely random: 122 bits of randomness from a secure random source. They are the default choice today, and this tool can generate them with your browser’s cryptographic random generator. Version 3 and 5 UUIDs are derived from a name and a namespace by hashing, so the same name always gives the same UUID, which is useful for stable identifiers. Version 6 is a reordered version 1 designed for better database ordering. Version 7, the newest, embeds a Unix timestamp in milliseconds followed by randomness, giving both sortability and privacy, and it is quickly becoming the recommended choice for database keys.
The variant matters less in practice. Almost every UUID you meet is the RFC 4122 variant, recognizable because the fourth group’s first digit is 8, 9, A or B. Older variants exist for historical systems, and a tool that reports the variant is mostly confirming that the UUID is a standard one.
How unique is unique enough
A version 4 UUID has 122 random bits, which means about 5 followed by 36 zeros possible values. The chance of a collision only becomes meaningful after generating around 2.7 quintillion UUIDs, which is far beyond anything any real system does. For practical purposes, UUID collisions do not happen. That is the mathematical bargain at the heart of UUIDs: accept a theoretical collision chance so small it is irrelevant, and in return never coordinate with anyone.
There are two special UUIDs worth knowing. The nil UUID, all zeros, is used as a placeholder meaning “no value”. The max UUID, all ones, is used as an upper bound in some systems. Both are technically valid in format but carry those special meanings, and this tool flags them when you paste one.
Timestamps hidden in time-based UUIDs
Version 1 and 6 UUIDs hide a timestamp measured in 100-nanosecond intervals since 15 October 1582, the start of the Gregorian calendar’s reckoning used by the UUID standard. Version 7 hides a plain Unix timestamp in milliseconds. This tool decodes those timestamps and shows the creation date in UTC. That is useful for debugging: a UUID found in a log can tell you when the record was created, even if the log line itself has no date. It is also a privacy warning: time-based UUIDs leak creation time to anyone who reads them.
If you need sortable IDs and do not want to leak a hardware address, prefer version 7. If you need pure unpredictability, for example for a token that must not be guessable, prefer version 4. If you need the same input to always produce the same ID, use version 5 with a namespace. Matching the version to the job is the main design decision; the rest is just formatting.
Common questions
Are UUIDs secret? No. Version 4 UUIDs are unpredictable, but they are identifiers, not passwords, and they should not be the only protection on anything sensitive. Can two systems generate the same UUID? In theory yes, in practice no: the collision odds are negligible. Why do UUIDs have hyphens? Purely for readability; the value is the same with or without them, though most systems expect the hyphenated form. Is my UUID uploaded? No. Validation, parsing and generation all run in your browser.
Pingback: Validar UUID Online Gratis - Revisa Versión y Variante de tu UUID