UUID Generator

Generate random UUIDs (version 4, per RFC 4122) individually or in bulk, instantly in your browser. Create unique IDs for database records, API tracing, or test fixtures, with hyphen-free or uppercase formatting options and no sign-up needed.

Result

Usage examples

Creating unique IDs for database records

When you need several unique IDs for test data or dummy records, generate exactly as many as you need in one go.

Issuing IDs for API request tracing

Generate a UUID to use as a request ID for tracing, and paste it straight into your code.

Using a hyphen-free format in variable names

Turn off "Include hyphens" to get a 32-character format with no hyphens, which is easier to use in filenames or variable names.

Seeding a batch of mock user accounts for a test suite

Generate a few dozen UUIDs at once and paste them into a seed script or fixtures file so each mock account gets a realistic, unique primary key without writing a generator yourself.

Creating a one-off idempotency key for an API call

Generate a single UUID to send as an Idempotency-Key header on a payment or write request, so retried requests are safely deduplicated by the server instead of creating duplicate records.

Producing uppercase UUIDs to match a legacy system's format

Turn on "Uppercase" when you're integrating with an older system, driver, or database column that expects UUIDs formatted like 3F2504E0-4F89-11D3-9A0C-0305E82C3301 instead of lowercase.

Downloading a batch of IDs to hand off to another team

Generate a large batch, then use the download button to save them as a .txt file you can attach to a ticket or import into a spreadsheet, instead of copying a long block of text by hand.

Frequently asked questions

Are the generated UUIDs sent to a server?

No. UUIDs are generated entirely in your browser and are never sent to a server.

What version of UUID does this generate?

Version 4 (v4) UUIDs, which are based on randomness. It uses your browser's built-in cryptographically secure random number generator.

Could the generated UUIDs collide with each other?

A version 4 UUID has 122 random bits, so the chance of a collision is practically negligible.

How many can I generate at once?

You can generate up to 100 at a time.

What does a UUID's format actually mean?

A standard UUID is 32 hex digits arranged as 8-4-4-4-12 groups separated by hyphens, for example 3f2504e0-4f89-11d3-9a0c-0305e82c3301. A few of those bits are reserved: one group of digits encodes the UUID version (4, in this case), and a couple of bits encode the "variant," which identifies the layout standard being used. The rest of the bits carry the actual random or time-based data.

Why not just use v1 or v7 UUIDs instead of v4?

Version 1 UUIDs embed the generating machine's MAC address and a timestamp, which can leak information about the device and network that created them — a real privacy concern. Version 7, standardized more recently in RFC 9562, is time-ordered, which makes it friendlier to database index locality since newly inserted rows sort naturally by creation time. Version 4 avoids the privacy issue of v1 and is simpler and more universally supported than v7, which is why it's the most common general-purpose choice and what this tool generates.

Can I rely on a v4 UUID being globally unique forever?

Not with absolute mathematical certainty, but close enough for virtually any practical purpose. With 122 random bits, you'd need to generate billions of UUIDs per second for around a hundred years before the probability of a single collision became meaningful — far beyond the scale most applications will ever reach.

Are UUIDs generated here cryptographically secure?

Yes. The randomness comes from crypto.randomUUID(), which is backed by your browser's cryptographically secure pseudorandom number generator (CSPRNG) — the same category of randomness source used for generating encryption keys, not the weaker Math.random().

Is it safe to use a UUID as a security token or session ID?

A v4 UUID's randomness is strong enough to resist guessing, but UUIDs are designed as identifiers, not as a dedicated secrets format — they're often logged, displayed in URLs, or stored in plaintext, which is fine for an ID but risky for something meant to stay secret. For session tokens, API keys, or password reset tokens, it's safer to use a purpose-built secret generator and treat it with the handling a credential deserves.