05 / Test Data / uuid-generator

UUID Generator

Bulk UUID v4 generation.

ReadyLocal processing
05 · Workspace

How to use

  1. 01Set how many UUIDs you need (1 to 10,000).
  2. 02Tick Uppercase if your system expects capital hex digits, or untick Hyphens for the compact 32-character form.
  3. 03Press Generate. The values appear one per line, with a count in the panel header.
  4. 04Press Copy all, or Download TXT to save them as uuids.txt. Clear empties the list.

What is this tool?

This tool generates version 4 UUIDs in bulk, up to 10,000 at a time. Each value has the standard 8-4-4-4-12 layout, with the version and variant bits set as RFC 4122 (now RFC 9562) defines for random UUIDs. You can switch to uppercase or remove the hyphens to match what your database or API expects. The values come from the browser's Math.random function. They are fine for test fixtures, seed data and correlation IDs, but they aren't cryptographically secure, so don't use them as secrets or session tokens. Everything is generated locally.

Anatomy of a UUID v4

A UUID is 128 bits written as 32 hexadecimal digits in five groups: 8-4-4-4-12. In a version 4 UUID, almost all of those bits are random, and only 6 are fixed. The first digit of the third group is always 4, the version. The first digit of the fourth group is always 8, 9, a or b, the variant. So in 3f2b8c1e-9d4a-4b7e-a1c2-5e6f7a8b9c0d, the 4 in 4b7e and the a in a1c2 identify it as a standard random UUID.

That leaves 122 random bits. That's enough that duplicates are practically impossible at test-data volumes, which is why v4 is the default choice when you need IDs without a central counter. A quick sanity check for any value you're given is that the third group starts with 4. If it starts with 1 or 7, it's a different version.

UUID v4 vs v7: which should you use?

This tool generates v4 only. Version 7, standardized in RFC 9562, puts a millisecond Unix timestamp in the first 48 bits, followed by random bits. Because v7 values sort by creation time, they keep B-tree indexes compact when used as database primary keys, and you can read the creation time from the ID. Random v4 values insert at scattered positions in an index, which can cost write performance on very large tables.

For test fixtures, mock payloads and correlation IDs, v4 is the simpler choice and reveals nothing about when it was created. If you're testing code that expects time-ordered IDs, such as cursor pagination keyed on the primary key, generate v7 values in your application instead.

Hyphens, uppercase and storage formats

The canonical form is lowercase with hyphens, 36 characters long, and most libraries accept uppercase input as well. Removing hyphens gives a 32-character string, which some systems store compactly or use in URLs and filenames. Databases with a native UUID type, such as PostgreSQL, accept all of these forms. Microsoft tools often display GUIDs in uppercase, sometimes in braces.

Common use cases

  • Seeding primary keys in test databases and fixtures
  • Creating correlation or request IDs for log tracing tests
  • Generating unique filenames or object keys in scripts
  • Building parametrized API test payloads that need many distinct IDs
  • Testing that an input field or API validates UUID format, including uppercase and hyphen-free forms

FAQ

Which UUID version does this generate?

Version 4, the random variant. Every value has 4 as the first digit of its third group.

Can I generate UUID v7 or v1 here?

No. The tool only generates v4. Time-ordered v7 values need to come from your application or a library that supports RFC 9562.

Are the UUIDs guaranteed to be unique?

Not mathematically, but with 122 random bits, a collision at test-data volumes is so unlikely that it can be ignored in practice.

Are these UUIDs cryptographically secure?

No. They are generated with Math.random, which is fine for test data but not for secrets, password-reset tokens or session IDs. For those, use crypto.randomUUID() or your platform's secure generator.

Can I remove the hyphens or use uppercase?

Yes. Untick Hyphens for the 32-character form, and tick Uppercase for capital hex digits.

Is a GUID the same as a UUID?

Yes. GUID is Microsoft's name for the same 128-bit identifier format, so these values work wherever a GUID is expected.

Is anything sent to a server?

No. UUIDs are generated entirely in your browser.