Decode UUIDs online and understand their version, variant, timestamp, bit structure, information exposure and identifier type. Analyze UUID v1, v3, v4, v5, v6, v7 and v8 directly in your browser.
A UUID Decoder is a developer tool that examines the structureof a Universally Unique Identifier and explains what informationis encoded in its 128 bits.
Unlike a simple UUID validator, a decoder does more than determinewhether the string looks correct. It identifies the UUID version,variant and version-specific fields, and explains what informationcan and cannot be recovered from the identifier.
UUID v4 is primarily random. A decoder can identify its version and variant and explain that most of its remaining bits represent random data. Unlike UUID v1, v6 and v7, UUID v4 does not contain an embedded creation timestamp.
UUID v7 contains a 48-bit Unix timestamp in milliseconds at the beginning of the UUID. This timestamp can be converted into a human-readable date and time without querying an external service.
UUID v1 and UUID v6 contain a 60-bit timestamp based on the UUIDepoch. They also contain a clock sequence and node field. The nodefield may historically correspond to a MAC address, although modernimplementations can use a random node identifier.
It depends on the UUID version. Random UUIDs such as v4 reveal very little beyond their version and variant. Time-based UUIDs such as v1, v6 and v7 can expose timing information. A v1 or v6 node field may also contain an identifier that resembles a MAC address.
A UUID Decoder examines the 128-bit structure of a UUID and explains its version, variant, encoded fields and information that can be derived from the identifier.
Depending on the UUID version, a decoder can identify the version and variant, recover timestamps from time-based UUIDs, inspect clock sequence and node fields in applicable versions, and explain whether the remaining data is random or derived from a namespace and name.
Some UUID versions contain timestamp information. UUID v1 and v6 contain timestamps based on the UUID epoch, while UUID v7 contains a Unix millisecond timestamp. UUID v4 does not contain a creation timestamp.
No. UUID v4 is primarily generated from random data and does not contain an embedded creation timestamp.
No. UUID v3 and v5 are name-based UUIDs derived using hashing. The original name cannot be recovered from the UUID alone.
UUID v1 contains a 48-bit node field. Historically this field could contain a MAC address, but modern implementations may use a randomly generated node identifier instead.
UUID v4 is primarily random, while UUID v7 contains a Unix millisecond timestamp followed by random data. UUID v7 therefore carries creation-time information and has time-ordered characteristics.
Yes. You can paste multiple UUIDs separated by new lines, commas or semicolons and decode them together.
No. Decoding is performed locally in your browser. The UUID values do not need to be sent to a server.
The NIL UUID contains all zero bits, while the MAX UUID contains all one bits. They are special UUID values rather than ordinary generated identifiers.