UUID Generator

Version 4 random and version 7 time-ordered UUIDs, singly or in bulk.
Client-side · verifiable
How this tool works

A UUID is 128 bits written as 32 hex digits in five groups. Two versions matter today:

  • Version 4 is 122 random bits plus 6 fixed bits marking the version and variant. Collisions are so unlikely that you can generate ids on many machines at once without coordination.
  • Version 7 (RFC 9562, 2024) puts a 48-bit millisecond timestamp first, then random bits. Ids sort by creation time, which keeps database indexes compact and makes “newest first” queries trivial.

This page uses crypto.randomUUID() for v4 where the browser supports it, and builds v7 from Date.now() plus crypto.getRandomValues(). The anatomy line under the list shows which hex digits are the timestamp, the version nibble and the variant bits.

Security note

What leaves your browser

UUIDs are generated locally. Nothing is transmitted. Remember that a v7 UUID reveals its creation time; use v4 where that would be sensitive.

FAQ
v4 or v7?

v7 for database primary keys and anything you sort or paginate. v4 when creation time must not be inferable or when you need maximum entropy per id.

Can a UUID be used as a password or token?

A v4 UUID has 122 random bits, which is strong, but its format is predictable and easy to spot in logs. Prefer the API key generator for secrets.

Are these globally unique?

Practically yes. The chance of two v4 UUIDs colliding among a billion generated is about one in a quintillion.

Why uppercase or braces?

Some systems, notably Microsoft ones, display GUIDs in uppercase within braces. The value is identical; only the formatting changes.