UUID Decoder

Decode UUID components and extract timestamps from time-based UUIDs.

Enter any UUID to see its components. For time-based UUIDs (v1, v7), we'll also extract the timestamp.

UUID Decoder Information

The UUID decoder extracts information embedded within UUIDs. Different UUID versions contain different types of information:

  • Version 1 (Time-based): Contains a timestamp, clock sequence, and node identifier. We can extract the creation time.
  • Version 4 (Random): Contains only random data, so no meaningful information can be extracted beyond the version and variant.
  • Version 7 (Time-ordered): Contains a Unix timestamp in the most significant bits. We can extract this timestamp.

All UUIDs also contain version and variant information in specific bit positions, which this decoder will identify and explain.

UUID Decoder: Understanding What's Inside Your UUIDs

UUIDs (Universally Unique Identifiers) contain more than just random characters. Depending on the UUID version, they can encode timestamps, locations, and other metadata. Our UUID decoder helps you extract and understand this embedded information.

Decoding Time-based UUIDs (Version 1)

UUID version 1 contains several components that can be decoded:

  • Timestamp: The first 60 bits contain a timestamp with 100-nanosecond precision since October 15, 1582.
  • Clock Sequence: A 14-bit value that helps prevent collisions when the clock is set backward.
  • Node ID: A 48-bit value that should be the IEEE 802 MAC address of the computer that generated the UUID.

By extracting the timestamp, you can determine exactly when a v1 UUID was created, which can be valuable for auditing and debugging.

Decoding Time-ordered UUIDs (Version 7)

Version 7 UUIDs are a newer format designed to improve on v1 UUIDs by using Unix timestamps:

  • Timestamp: The first 48 bits contain a Unix timestamp in milliseconds since the Unix epoch (January 1, 1970).
  • Random Data: The remaining bits (after version and variant) are random, providing uniqueness.

Version 7 UUIDs are especially useful for database systems where sorting by creation time is important.

Common Use Cases for UUID Decoding

Decoding UUIDs is particularly useful in these scenarios:

  • Forensic Analysis: Determining when records were created in systems that use time-based UUIDs
  • Debugging: Verifying that UUID generation is working correctly in your applications
  • Data Archaeology: Extracting creation times from legacy data where timestamps weren't explicitly stored
  • System Auditing: Verifying the time sequence of events in distributed systems
  • Documentation: Helping developers understand the structure and meaning of UUIDs in their systems

Technical Details of UUID Decoding

Our decoder performs these technical operations:

  • Extracts the version nibble (the 13th character) to identify the UUID version
  • Extracts the variant bits (from the 17th character) to verify the UUID type
  • For v1 UUIDs: Extracts and converts the 60-bit timestamp to a human-readable date
  • For v7 UUIDs: Extracts and converts the 48-bit timestamp to a human-readable date
  • Breaks down the UUID into its logical components based on its version

Limitations of UUID Decoding

While our decoder can extract a significant amount of information, there are some limitations:

  • Random UUIDs (v4) contain no extractable meaningful data beyond version and variant
  • Some UUID implementations may not strictly follow the RFC specification
  • The node ID in v1 UUIDs might be randomized for privacy reasons, making it impossible to identify the exact source
  • Time precision may vary slightly between different UUID generators