---
title: "How to generate UUIDs in bulk (v4 and v7) | ToolSugar"
description: "Generate random v4 or time-ordered v7 UUIDs in bulk, up to 1000 at a time, and learn which version fits a database key or a test fixture."
canonical: https://toolsugar.com/blog/how-to-generate-a-uuid
image: https://toolsugar.com/og.png
---

# How to generate a UUID, one or a thousand at a time

Updated 2026-11-09

To generate a UUID, ask for a 128-bit random or time-based identifier and copy it. UUID Generator makes version 4 and version 7 UUIDs in your browser, from one up to 1000 per click, using the browser's secure random source. Nothing is uploaded. Pick the version that fits how you will store the IDs.

[Open UUID Generator](https://toolsugar.com/tools/uuid-generator)

## Generate UUIDs in four steps

The result is a plain list, one UUID per line, ready to paste into a script or a spreadsheet.

1. Choose v4 for random IDs or v7 for time-ordered IDs.
2. Enter how many you need, from 1 to 1000.
3. Press Generate.
4. Press Copy to take the whole list.

## Choose between v4 and v7 for a database

A v4 UUID is almost entirely random. It is a good default when you only need uniqueness. As a primary key it scatters new rows across an index, which can slow inserts in a large table.

A v7 UUID starts with a millisecond timestamp. New IDs sort after older ones, so inserts land at the end of the index and a sorted list follows creation order roughly. The rest of the bits are random.

## What a UUID looks like

A UUID has 32 hex digits in five groups, split by dashes, as in 8-4-4-4-12. One digit in the third group names the version, so you can tell v4 from v7 by eye. A 4 starts that group in a v4 UUID, and a 7 starts it in a v7 one.

## Use bulk UUIDs for test data

Generate a thousand IDs, paste them into a seed file, and give each fixture row its own key. Because each click makes new values, run the tool once per seed set and save the output. Keep the list in version control next to the seed script so every teammate loads the same IDs. Regenerating the list later gives different values, and any foreign key that points to an old ID would then break.

Do not use a UUID as a secret. It identifies a record. It does not prove who is asking for it. Collisions are possible in theory but not in practice for random v4 values, since 122 bits are random. For v7, the random bits are what keep two IDs made in the same millisecond apart. Sorting v7 strings as plain text also works, because the timestamp comes first and hex digits sort in order. Store the value in a native UUID column when your database has one, which takes 16 bytes instead of the 36 characters of the text form.

## Questions

### Is a UUID the same as a GUID?

In practice, yes. GUID is the name Microsoft uses for the same 128-bit format.

### Can I generate more than 1000 at once?

Not in one click. Press Generate again and copy each batch, or combine batches in your editor.

### Does a v7 UUID reveal when it was made?

Yes. The first part holds a millisecond timestamp, so anyone can read the creation time. Use v4 if that matters.

[Open UUID Generator](https://toolsugar.com/tools/uuid-generator)

## Related guides

- [How to generate a strong random password](https://toolsugar.com/blog/how-to-make-a-strong-password)
- [How to encode and decode Base64 online](https://toolsugar.com/blog/how-to-encode-and-decode-base64)
- [How to decode a JWT and read its claims](https://toolsugar.com/blog/how-to-decode-a-jwt)
- [How to write a cron expression for any schedule](https://toolsugar.com/blog/how-to-write-a-cron-expression)