100% local — your data never leaves your browser

UUID Generator — A Hundred Ready to Paste

Generate up to 100 random UUID v4 identifiers at once, made in your browser, ready for a fixture file, a seed script or a batch of test rows.

Instant Private Zero cookies

Count input

UUID output

What this tool does

Ask for a number between 1 and 100, get that many UUIDs.

3
e2f1a7d4-9c3b-4a8e-b6d2-0f5c1e8a4b37
7b3c5d91-2e46-4f0a-8c1d-9a7e3b5f2c60
1d8e4a6b-5f27-4c93-a0e8-3b6d1f4c7a25

One per line, ready to paste into a fixture, a seed file or a test. An option writes them in uppercase, which is what some systems and a few database columns expect.

Made here, seen by nobody

The identifiers come from crypto.randomUUID, in your browser, using the same cryptographic generator that backs the rest of the Web Crypto API. No request goes out, so the values you get have never existed anywhere else — which is not something an online generator that answers from a server can say.

What version 4 is, and is not

  • 122 random bits. Six of the 128 are fixed: four say “version 4”, two more mark the variant. Everything else is drawn at random.
  • No time, no machine. Unlike version 1, it says nothing about when or where it was made. Nothing to leak, nothing to sort by.
  • Not sortable. Consecutive UUIDs land all over the place, which is hard on a clustered index. If you insert millions of rows keyed by UUID, version 7 — time-ordered — is the one to look for, and this tool does not make them.
  • Not a secret. Unguessable in practice, but it travels in URLs and logs. Use it as an identifier; use a real token generator for anything that grants access.

Private by design

Everything runs locally in your browser with JavaScript. Your data is never uploaded, which makes the tool safe for sensitive content, and it keeps working offline.

Frequently asked questions

Which version are these?
Version 4: 122 random bits, six fixed to say “random UUID”. They carry no time and no machine address, so they cannot be sorted by age and they leak nothing about where they were made. If you need identifiers that sort by creation time — a database key, say — you want version 7, and that is a different generator, not an option here.
Are they really random?
They come from `crypto.randomUUID`, which uses the browser’s cryptographic generator, not `Math.random`. The odds of two colliding are the odds of matching 122 random bits: you would need to generate billions of them before it became worth thinking about.
Can I use one as a token or a password?
Not as a password: it has no secret in it and it is often visible in a URL, a log or an email. A version 4 UUID is unguessable in practice, so it is fine as an unlisted link or an idempotency key, but a session token or an API key should come from a token generator, with a length and a lifetime you chose.

Related converters