UUID Generator

Generate cryptographically secure UUIDs in your browser. Supports both UUID v4 (fully random) and UUID v7 (timestamp-ordered, RFC 9562). Bulk generation up to 1000 at once with multiple formatting options.

Generated UUIDs 0 items

About UUIDs

A UUID (Universally Unique Identifier) is a 128-bit value used to identify information uniquely across distributed systems without coordination. The probability of generating two identical UUIDs is so low that they can be safely treated as unique in practice.

UUID v4 — random

UUID v4 is generated entirely from random bits (with 6 bits reserved for version and variant markers). It produces unpredictable, unguessable identifiers — ideal for security tokens, session IDs, and any case where you want collision resistance without leaking generation order.

UUID v7 — timestamp-ordered

UUID v7, standardized in RFC 9562 (2024), embeds a Unix millisecond timestamp in the leading 48 bits, followed by random bits. Because the high-order bits monotonically increase with time, v7 UUIDs sort naturally by creation order. This makes them dramatically better as database primary keys: B-tree indexes stay locality-friendly, and inserts cluster at the end of the index instead of fragmenting it like v4.

When to use which

Formatting options

The standard form uses 8-4-4-4-12 hexadecimal digits separated by hyphens. The no-hyphens form (32 contiguous hex characters) is common in URL paths and filenames. Uppercase is sometimes required by legacy systems. The braces form ({xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}) is the canonical Microsoft / C# representation.

Frequently Asked Questions

Are these UUIDs cryptographically secure?
Yes. v4 uses the browser's native crypto.randomUUID(), and v7 uses crypto.getRandomValues() for the random portion. Both draw from the OS-level CSPRNG.
Do you store any of the generated UUIDs?
No. Generation runs entirely in your browser. Nothing is logged, sent, or persisted on any server.
Why is UUID v7 better for database keys than v4?
v4 is fully random, so consecutive inserts hit random pages of a B-tree index, causing fragmentation and write amplification. v7 keys are time-ordered, so inserts append to the end of the index — much friendlier to cache and disk locality. This often translates to measurable INSERT throughput gains in PostgreSQL, MySQL, and SQL Server.
Can a UUID v7 leak the creation time?
Yes. The first 48 bits of a v7 UUID encode the Unix millisecond timestamp. If timing information is sensitive (e.g. account creation order), prefer v4.
What happens if my browser does not support crypto.randomUUID?
The tool falls back to a manual implementation built on crypto.getRandomValues(), which is supported in all modern browsers (Chrome, Firefox, Safari, Edge).