UUID generator
Generate any number of version 4 UUIDs, then copy or download them.
Settings
1 to 1,000
0 generated
Tap a row to copy just that one.
Generating…
How to use
- Enter how many you need (1 to 1000).
- Turn on uppercase or hyphen-free output if your format calls for it.
- Press “Generate again” for a fresh batch.
- Copy one row, copy all of them, or download the batch as a .txt file.
Frequently asked questions
Are these safe to use in production?
Yes. They come from the browser's cryptographic random source (`crypto.randomUUID()` or `crypto.getRandomValues()`) and follow RFC 4122 version 4, including the version and variant bits.
Could two of them collide?
122 of the bits are random, so the probability stays negligible even across billions of values. It is not mathematically zero, though, so keep a unique constraint in the database when absolute uniqueness matters.
Are the generated values logged anywhere?
No. Generating, copying and downloading all happen in the page with no network request. That also means there is no way to recover a batch you closed — save what you need.
Do you support v1 or v7?
Only v4 for now. Version 1 embeds a MAC address and a timestamp, and cases needing time ordering are mostly moving to v7, which is on the list to add.
About the UUID generator
A UUID is what you use when identifiers must not collide and there is no central authority handing them out: database primary keys, trace IDs, filenames, test fixtures, idempotency keys.
Version 4 fills the value with randomness rather than a timestamp or hardware address, so nothing about when or where it was generated can be recovered from it. Sequential public identifiers (1, 2, 3…) leak how much data you hold and let people probe for neighbouring records; a UUID closes that gap too.
When you need a lot of them, set the count, generate once and download the .txt to drop straight into seed data or load-test input.