UUIDs and batch files are generated locally with secure browser randomness and no MAC address.

Current UUIDv1

Embedded timestamp: The UUID stores a 60-bit count of 100-nanosecond intervals since 15 October 1582.

UUIDv1 contains time information, but its canonical text is not directly sorted by creation time.

Download UUIDv1 batch

What this tool does

Generate RFC 9562 UUID version 1 identifiers containing a Gregorian timestamp, clock sequence and node field.

Copy one UUID or create a locally generated text file containing a larger batch in generation order.

How to use the tool

Use the UUID shown in the first panel or generate another value.
Review the decoded creation time displayed below the UUID.
Choose between 1 and 100,000. One lowercase UUID is written per line in generation order.
Download the generated UUIDv1 text file for compatibility or testing.

Useful applications

Creating compatibility data for systems that explicitly require UUIDv1.
Inspecting and testing timestamp extraction from existing UUIDv1 records.
Preparing fixtures, imports or migrations for legacy UUID workflows.
Producing standards-based examples for documentation and automated tests.

Notes and limitations

UUIDv1 stores a 60-bit Gregorian timestamp in 100-nanosecond units, but its low, middle and high time fields are not arranged for direct textual sorting.
The generator initializes a secure 14-bit clock sequence and random 48-bit node field for the browser session; it never reads a device MAC address.
The node multicast bit is set so the random value cannot be mistaken for an IEEE network-card address. The timestamp may be advanced minimally to preserve generation order.
RFC 9562 recommends UUIDv7 for new systems when UUIDv1 compatibility is unnecessary. UUIDs are identifiers, not secrets or access tokens.

Frequently asked questions

Does this UUID contain my MAC address?

No. The tool creates a cryptographically random node value and sets its multicast bit instead of reading network hardware.

Can UUIDv1 text be sorted chronologically?

Not reliably by ordinary text order because the least significant timestamp field appears first. Use the decoded timestamp or choose UUIDv6 or UUIDv7.

What happens if the device clock moves backward?

The generator changes its clock sequence and continues with a monotonically increasing internal timestamp to reduce duplicate risk.

Should a new application use UUIDv1?

Usually only for compatibility with an existing UUIDv1 workflow. RFC 9562 recommends UUIDv7 for new time-ordered systems.

Are generated UUIDs uploaded?

No. The displayed UUID and normal batch download are generated locally in the browser.