Skip to main content
ToolSmartly

UUID Generator: Create Unique IDs Instantly

Do you need unique identifiers for your databases or applications without risking collisions? Our online UUID generator allows you to create UUID v4, v7, ULID, NanoID, or secure tokens instantly with a single click. Completely free and 100% client-side, our tool ensures total privacy with no data transfer to any server. Developers, take advantage of a fast and reliable solution to validate and inspect your identifiers while maintaining the integrity of your systems.

Identifier type
Output format
UUID
Examples: 550e8400-e29b-41d4… 00000000-0000-0000… 550e8400-e29b-41d4…
Generate then inspect: UUID v4 UUID v7
Space = regenerate

History

No identifiers generated yet.
Hover to reveal.

What is a UUID and what is it used for?

A UUID (Universally Unique Identifier) is a 128-bit identifier standardized by RFC 4122, represented as 32 grouped hexadecimal characters (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx). The probability of collision is statistically negligible: for UUID v4, you would need to generate 2.71 quintillion UUIDs to have a 50% chance of a collision.

UUID v4 vs UUID v7

UUID v4 is entirely random (CSPRNG) — ideal for web resource identifiers where order doesn't matter. UUID v7 is the new version (RFC 9562, 2024): the first 48 bits encode the Unix timestamp in milliseconds, making UUIDs naturally sortable. It's the recommended choice for database primary keys (better B-tree indexing performance).

ULID and NanoID: modern alternatives

ULID (Universally Unique Lexicographically Sortable Identifier) encodes a timestamp in 48 bits + 80 random bits in 26 Crockford Base32 characters — lexicographically sorted, URL-safe. NanoID is a compact alternative to UUIDs: 21 characters by default, customizable alphabet, 5× faster than UUID v4 and ideal for short URLs.

UUID v4, v7, ULID or NanoID: which one?

Every identifier is generated in your browser with the cryptographic random generator crypto.getRandomValues(), the same one used for encryption keys. Three modes: generate (1 to 100 identifiers), validate a UUID, or inspect it to read its version, variant and, for a v7, its creation time.

How to use it

  1. Choose the identifier type and output format: standard, upper case, no hyphens, braces, URN or SQL-ready.
  2. Set the count (up to 100), generate, then copy the list.
  3. For an existing UUID, paste it into “Validate” or “Inspect”.

Comparison

TypeShapeTime-orderedUse
UUID v436 characters, 122 random bitsnothe standard, accepted everywhere
UUID v736 characters, millisecond timestamp + randomyesdatabase primary keys (more compact indexes than v4)
ULID26 base-32 charactersyesreadable, sortable identifiers
NanoID21 characters by defaultnoshort identifiers in URLs
Tokenrandom stringnosecret tokens, test API keys

Version 7 is defined in RFC 9562 (2024), which replaces RFC 4122. Because its first characters encode the date, it reveals when the identifier was created: prefer v4 if that should not be exposed.

Frequently asked questions

Can two v4 UUIDs ever be the same?

In theory yes, in practice no: with 122 random bits, you would need to generate around 100 trillion UUIDs to have a one-in-a-billion chance of a duplicate.

Can I use a UUID as a password or secret token?

A v4 UUID generated here is unpredictable, but its format is recognisable and it is not designed as a secret. For a token, use the Token type; for a password, the password generator.

Why are v7 UUIDs better for databases?

Because they are generated in increasing order. New rows are added at the end of the index instead of being scattered across it, which keeps B-tree indexes compact and inserts fast.