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

Current UUIDv7

Embedded timestamp: The first 48 bits store Unix time in milliseconds.

Download UUIDv7 batch

Create RFC 9562 UUID version 7 identifiers whose leading 48 bits contain Unix time in milliseconds.

Copy one UUID or generate a locally created text file containing a larger monotonic batch.

UUIDv7 stores a 48-bit Unix timestamp in milliseconds and uses version 7 plus the RFC variant bits.
This implementation initializes the remaining 74 bits with secure randomness and increments that field when multiple UUIDs are created without a later clock value.
Lexicographic ordering applies to canonical lowercase UUID strings generated by this browser process; distributed systems still need their own ordering semantics.
UUIDv7 is an identifier, not automatically a password, access token or proof of authenticity. Values are generated locally and are not sent to petuja.tools.

What information does UUIDv7 reveal?

It exposes an approximate creation time in milliseconds because the timestamp is stored in the first 48 bits.

Are UUIDv7 values globally unique?

They are designed to make collisions extremely unlikely, but no finite random identifier scheme can provide an absolute mathematical guarantee.

Why are UUIDs generated in the same millisecond still ordered?

The tool increments the 74-bit post-timestamp field when the clock has not advanced, producing strictly increasing values within this process.

What happens if the device clock moves backwards?

The generator keeps the last used timestamp and advances its monotonic field until the clock catches up.

Are generated UUIDs uploaded?

No. Single UUIDs and batch files are created locally in the browser with Web Crypto.