Skip to content
SUMILORASUMILORA

UUID generator

Developer tools

Generate one or many. Nothing is sent anywhere — the randomness comes from your own operating system.

Runs in your browser

Nothing is uploaded. The work happens on your own device, so your file or text never reaches us.

About this tool

v7 is usually the better database key

v4 is 122 random bits. Two consecutive v4s are unrelated, so rows inserted together land in unrelated places in a B-tree index. That scatters writes across the index and fragments it — a real cost on a large, busy table.

v7 puts a millisecond timestamp in the leading bits, so UUIDs generated together sort together and inserts stay at the end of the index, the way an auto-increment key does. It was standardised in RFC 9562 in 2024 for exactly this reason.

The trade-off: a v7 reveals roughly when it was created. If that is sensitive, use v4.

The generator here also adds the RFC’s optional counter, so UUIDs made within the same millisecond still sort in the order they were created.

On collisions

v4 has 122 random bits. To reach a 50% chance of a single collision you would need about 2.7 × 10¹⁸ of them.

At a million a second that is roughly 85,000 years. Collisions are not a practical concern; weak randomness is. These use crypto.getRandomValues, which draws on the operating system’s CSPRNG, not Math.random.

Questions

Should I use UUID v4 or v7?

v7 for database keys — it indexes far better. v4 when the creation time must not be inferable from the id.

Are these random enough?

Yes. They use crypto.getRandomValues, backed by the operating system’s cryptographic random source, not Math.random.

Are they generated on your server?

No. They are generated in your browser from your own operating system random source, so we never see them and there is no request to log.

Related tools