UUID v1 · TIME-BASED · PRIVACY INSPECTOR

UUID v1 Generator

Generate UUID v1 identifiers with a privacy-safe randomized node, inspect timestamps and clock sequence values, analyze node exposure and export UUID v1 results directly in your browser.

Privacy-safe node: This generator does not use your hardware MAC address.

Generated UUID v1

Generated UUID v1 values will appear here.

What is UUID v1?

UUID v1 is a time-based UUID format. It stores a 60-bit timestamp, a clock sequence and a 48-bit node identifier inside a 128-bit UUID.

The timestamp uses 100-nanosecond intervals from the UUID Gregorianepoch of October 15, 1582. This makes it possible to recoverapproximate creation time directly from the identifier.

Why Does UUID v1 Expose Time?

Unlike UUID v4, UUID v1 is not purely random. Its timestamp is partof the UUID structure. Anyone who has the UUID can decode thattimestamp if they know the UUID v1 format.

UUID v1 and MAC Address Privacy

Traditional UUID v1 implementations can use a machine's MAC addressas the node identifier. This can expose information about thegenerating system.

This generator intentionally uses a randomized node identifier withthe multicast bit set. Your hardware MAC address is therefore notinserted into the generated UUID.

UUID v1 vs UUID v6 and UUID v7

UUID v1 is an older time-based design. UUID v6 rearranges thetimestamp fields to improve lexical ordering, while UUID v7 usesUnix milliseconds and random data and is designed for moderntime-ordered identifiers.

When Should You Use UUID v1?

  • Legacy systems requiring UUID v1 compatibility
  • Existing databases using time-based UUIDs
  • Distributed systems that already expect UUID v1
  • Testing UUID v1 parsing and timestamp extraction
  • Applications that specifically require UUID v1 semantics

When Should You Avoid UUID v1?

  • When creation time should remain hidden
  • When a hardware MAC must never be exposed
  • When natural lexical ordering is important
  • For new database designs where UUID v7 is more appropriate

Frequently Asked Questions

UUID v1 is a time-based UUID format that contains a 60-bit timestamp, a clock sequence and a 48-bit node identifier.

UUID v1 uses a 60-bit timestamp representing 100-nanosecond intervals since October 15, 1582, the UUID Gregorian epoch.

Traditional UUID v1 implementations can use a MAC address as the node identifier. This generator uses a randomized node identifier with the multicast bit set, so it does not expose your hardware MAC address.

Yes. The timestamp is embedded in the UUID and can be decoded into a human-readable date and time.

The clock sequence helps avoid duplicate identifiers when the system clock moves backward or when the node identifier changes.

UUID v1 contains time information, but its timestamp fields are arranged in the traditional UUID layout rather than in a directly lexicographically sortable order. UUID v6 and UUID v7 are better choices when natural string sorting is important.

UUID v1 always exposes its embedded timestamp. Traditional implementations may also expose a MAC address. This generator uses a randomized node identifier to avoid exposing a hardware MAC address.

Yes. You can generate a batch of UUID v1 identifiers and inspect their timestamp ordering and node information.

UUID v1 can be useful for compatibility with existing systems. For new applications requiring time ordering, UUID v7 is generally a more modern choice because it combines a Unix millisecond timestamp with random data.