UUID Generator

Development

UUID v4, v7, ULID, Nano ID

  • Runs in your browser
  • Nothing is sent to a server
  • No sign-up

Identifier Type

(max. 100)

Format comparison

Format comparison
FormatLengthSortableIdeal use
UUID v436 charsNoGeneral identifiers
UUID v736 charsYesDB with B-tree indexes
ULID26 charsYesCompact alt. to UUID v7
Nano ID21 charsNoURLs, slugs, tokens

UUID Generator: v1, v4, v5 and v7 in a Single Click

UUIDs (Universally Unique Identifiers) are 128-bit strings guaranteed to be unique in the world without central coordination. Standard for record IDs in databases, tokens, event IDs, and any case requiring a unique ID without collision.

Our generator supports the most useful variants: UUIDv4 (random, most common), UUIDv1 (time + MAC), UUIDv5 (deterministic from name + namespace), and UUIDv7 (time-ordered, ideal for DBs). Generate individually or in bulk (up to 1000).

For architects designing distributed systems, developers choosing UUIDs for their applications, or DBAs migrating from auto-increment. Instant generation, no server.

How does it work?

  1. Select UUID version

    v4 for general use (random), v7 for DBs (sortable), v5 for deterministic IDs (from name).

  2. Choose quantity

    Generate 1, 10, 100, or up to 1000 UUIDs at once. Useful for seeding data.

  3. Copy the results

    Copy individual UUID or the entire list. Available in different formats (with hyphens, without, uppercase).

Frequently Asked Questions

Which UUID version should I use in 2026?

For new DBs: UUIDv7 (2024 standard, sortable by time, more efficient in B-tree indexes). For general use: UUIDv4 (random, no leaks). For deterministic IDs (same input, same UUID): UUIDv5.

How many UUIDv4 can I generate before collision?

UUIDv4 has 122 random bits (128 - 6 for version and variant). Probability of collision after generating N UUIDs = N²/(2 × 2^122). To have 50% probability of collision, you'd need to generate 2.71 × 10^18 UUIDs. Practically zero risk.

Is it safe to use UUIDs as security tokens?

UUIDv4 has 122 bits of entropy — sufficient security if generated with crypto.getRandomValues(). BUT: some implementations use Math.random() which is not cryptographic. Always verify your library uses secure random. Ours uses Web Crypto API.

See all tools