UUID Generator

Generate, validate, and inspect UUIDs in v4 and v7 formats. Bulk-generate up to 100 at a time.

About This Tool

You are setting up a new microservice and need primary keys that won't collide across databases, regions, or teams — without coordinating through a central ID server. That is the exact problem UUIDs solve, and this tool generates them instantly in your browser.

Two versions are supported: Version 4 (random) and Version 7 (time-ordered). UUID v4 draws 122 random bits from crypto.getRandomValues(). The collision probability? You would need to generate 2.71 x 10^18 UUIDs (2.71 quintillion) before reaching a 50% chance of a single duplicate. UUID v7 embeds a 48-bit Unix millisecond timestamp in the most significant bits, giving UUIDs natural chronological ordering — ideal for B-tree-indexed database primary keys where insert performance matters. Convert embedded timestamps with our Timestamp Converter.

Generate a single UUID or bulk-generate 5, 10, 50, or 100 at once. Copy individually, copy all, or download the list as a text file. The Validate section lets you paste any string to check validity and detect the version. For v7 UUIDs, the embedded timestamp is extracted and displayed.

All generation uses the Web Crypto API and runs entirely client-side. No UUIDs are sent to or stored on any server. For content-derived identifiers, see our Hash Generator or Password Generator.

How to Use

  1. Select UUID v4 or UUID v7 using the badges at the top.
  2. Click a generate button (1, 5, 10, 50, or 100) to create UUIDs.
  3. Hover over any UUID and click the copy icon to copy it. Use Copy All or Download for bulk export.
  4. To validate a UUID, paste it into the Validate UUID input. The tool shows whether it is valid and which version it is.
  5. Press Ctrl+Shift+C to copy all generated UUIDs.

About This Tool

View all 20 UUID guides →

FAQ

What is the difference between UUID v4 and v7?

UUID v4 is purely random (122 random bits). UUID v7 encodes a millisecond-precision timestamp in the first 48 bits, followed by random bits. V7 UUIDs sort chronologically, making them better for database indexes.

Can UUIDs collide?

In theory, yes. A UUID v4 has 122 random bits. You would need to generate about 2.71 x 10^18 (2.71 quintillion) UUIDs before the birthday paradox gives you a 50% chance of one collision. For practical purposes, that probability is negligible.

Are these UUIDs cryptographically secure?

The random bytes are generated using crypto.getRandomValues(), which is a cryptographically secure random number generator. However, UUIDs are not designed to be secret tokens -- use a dedicated token generator for that purpose.

When should I use UUID v7?

Use v7 when UUIDs will be used as database primary keys, especially with B-tree indexes. The time-ordered nature of v7 reduces index fragmentation and improves insert performance compared to random v4 UUIDs.

Is my data safe?

Yes. UUIDs are generated using the Web Crypto API (crypto.getRandomValues()) in your browser. No network requests are made — you can verify this in your browser's DevTools Network tab.

Related Tools