UUID Decoder & Analyzer
Paste any UUID to decode its structure and extract hidden information. This tool identifies the UUID version (1-5), variant, and for time-based UUIDs, reveals the precise creation timestamp and originating machine details.
About UUID Structure
A UUID (Universally Unique Identifier) is a 128-bit number used to uniquely identify information. The structure includes version and variant bits that determine how the UUID was generated.
- Version 1: Time-based using MAC address and timestamp
- Version 3: Name-based using MD5 hashing
- Version 4: Random generation
- Version 5: Name-based using SHA-1 hashing
How the UUID Decoder Works
This decoder parses a UUID's 128-bit structure and extracts meaningful information from its component fields. It reads the version bits, variant bits, and—for version 1 UUIDs—the embedded timestamp.
The tool breaks down the UUID into its RFC 4122 structure: time_low (32 bits), time_mid (16 bits), time_hi_and_version (16 bits), clock_seq_hi_and_reserved (8 bits), clock_seq_low (8 bits), and node (48 bits).
UUID v1 structure decoded:
time_low
32 bits
time_mid
16 bits
time_hi_and_version
16 bits (includes version)
Real Use Cases
Forensic timestamp extraction
A security analyst finds a v1 UUID in logs and needs to determine exactly when an event occurred, down to the 100-nanosecond interval.
Debugging UUID generation
A developer suspects their UUID library is generating incorrect version bits and uses the decoder to verify the structure.
Learning UUID internals
A computer science student studying distributed systems wants to understand how the 128 bits are actually allocated and used.
Node identifier analysis
A network engineer examines the node field of v1 UUIDs to identify which machine in a cluster generated a particular record.
Variant compatibility check
Someone integrating with a legacy system needs to verify whether the UUIDs use RFC 4122 variant or the older Microsoft variant.
Clock sequence debugging
A developer troubleshooting duplicate v1 UUIDs checks the clock sequence field to see if it's incrementing correctly between generations.
What to Know Before Using
Version 1 timestamp extraction: Only v1 UUIDs contain timestamps. For v3, v4, or v5 UUIDs, the timestamp field will be null because those bits are used for random data or hash output.
UUID epoch: Version 1 timestamps count 100-nanosecond intervals since October 15, 1582 (the Gregorian calendar reform date), not the Unix epoch of 1970. This tool converts to standard UTC dates automatically.
Node identifier privacy: Modern v1 UUID implementations often use random node identifiers instead of MAC addresses to prevent tracking. Don't assume the node field reveals actual hardware.
Little-endian storage: UUID v1 timestamps are stored in little-endian byte order within the UUID. This tool handles the byte-swapping automatically when extracting the timestamp.
FAQ
What information can I extract from a UUID?
From any UUID: version number, variant type, node identifier, and clock sequence. From version 1 UUIDs specifically: the exact timestamp when it was generated (down to 100-nanosecond precision).
Why does my v4 UUID show no timestamp?
Version 4 UUIDs are random—the bits that would be a timestamp in v1 are just random numbers in v4. There's no meaningful timestamp to extract. Only version 1 (and some version 2) UUIDs contain time information.
What does the variant field tell me?
The variant indicates which UUID specification the identifier follows. RFC 4122 (modern standard) uses variant bits 8, 9, A, or B. Microsoft's older format uses C, D, E, or F. This affects compatibility with different systems.
Can I determine which computer generated a UUID?
For old v1 UUIDs (pre-2000s), the node field might contain the MAC address, which could identify the network interface. Modern implementations use random node values for privacy, making this impossible.
What is the clock sequence used for?
The 14-bit clock sequence prevents collisions when multiple UUIDs are generated at the same timestamp (common on multi-core systems). It should increment each time the clock appears to go backward or multiple UUIDs are generated in the same 100ns interval.
How accurate is the extracted timestamp?
The timestamp is precise to 100 nanoseconds (10 million ticks per second). However, actual system clock resolution is typically much coarser (milliseconds). The precision is there, but the accuracy depends on the generating system's clock.
Other Free Tools
UUID Generator
Free UUID Generator
UUID Validator
UUID Validator & Checker
UUID Version Converter
UUID Version Converter (v3, v5)
Bulk UUID Generator
Bulk UUID Generator for Mass Production
Nil/Empty UUID Generator
Nil UUID & Custom Pattern Generator
ASCII to Hex Converter
ASCII to Hex Converter: Text to Hexadecimal Translator
Barcode Generator
Free Barcode Generator
Binary to Text Converter
Binary to Text Converter
Free Printable Calendar Maker
Create & Print Your Custom Calendar
Pie Chart Maker
Free Pie Chart Maker Online