DoItAl

Data utility

UUID Generator & Validator

Generate secure UUID v4 or RFC 9562 UUID v7 locally, with bulk formatting and TXT export. Inspect versions, variants and embedded v7 timestamps without saving a history.

Browser-local • No upload

Loading tool controls…

Local tool controls

Validate and inspect a UUID

UUIDs are identifiers, not passwords or secret tokens. v4 uses secure randomness; v7 embeds your device clock and random bits. Values within one millisecond are not guaranteed to sort by generation order. Collisions are very unlikely, not impossible. No UUID history is stored.

What this tool does

Generates one to 100 UUID v4 or v7 identifiers securely, formats and exports them, and inspects an existing value’s syntax, version, variant and v7 timestamp.

How to use it

  1. Choose version 4 or 7 and a bounded quantity, then generate.
  2. Choose upper/lowercase, hyphens or braces without changing the underlying UUIDs; copy individual/all values or download TXT.
  3. Paste a UUID into the inspector to normalize and check its version/variant, including its embedded time when it is v7.

Worked example

The RFC 9562 example 919108f7-52d1-4320-9bac-f847db4148a8 has version 4 and the RFC variant. Its v7 example 017f22e2-79b0-7cc3-98c4-dc0c0c07398f contains Unix milliseconds 1645557742000, displayed as 2022-02-22T19:22:22.000Z. Uppercase or braces do not create a new identifier.

Processing and explanation

Version 4 uses crypto.randomUUID where available, with a getRandomValues fallback that sets the required bits. Version 7 follows RFC 9562: a 48-bit big-endian Unix millisecond timestamp, version/variant bits and 74 cryptographically random bits. The inspector accepts canonical or compact hex, matched GUID braces and a UUID URN prefix, and recognizes the special nil/max values.

Limits and common mistakes

Generation is v4/v7 only and capped at 100 values. v7 exposes generation time from the device clock; random values within the same millisecond are not monotonically ordered. Collision probability is very low, not zero. Validation checks structure and recognized RFC version/variant bits, not actual origin or uniqueness; legacy variant layouts are labeled and rejected by this RFC validator. UUIDs are not passwords, access tokens or authentication proofs.

Privacy and your input

All inputs and results stay in this browser tab. Dates, time-zone selections, identifiers and file contents are not uploaded, saved in browser storage or included in aggregate analytics. Clipboard copies and downloaded files are managed by your device.

Frequently asked questions

Is UUID v7 a secret?
No. It reveals a timestamp, and identifiers should not replace a suitable secret-token system.
Can the validator confirm a UUID was generated securely?
No. A string can have correct syntax and bits without having come from a secure generator.
Will UUIDs generated together sort in order?
Different v7 millisecond timestamps sort by time in canonical form. Within the same millisecond, random bits do not promise generation ordering.

Material content update: