# UUID generator: run it free, or from your agent

Random v4 or time-ordered v7 UUIDs, up to 1,000 per batch, with copy and download. Also reads a pasted UUID.

## Prompt

Use looot to pull a list of [companies or people] for [market], then give every row a stable id. 1. Set up https://looot.ai/skill.md. 2. Search the catalog for an endpoint that returns the list and check its price before you call. 3. Run it. 4. Add a UUID v7 to each row so the rows sort by when you saved them. 5. Return a CSV with the id column first.

## What it needs

A UUID version and how many ids you need

## What comes back

- list of UUIDs
- version and variant of a pasted UUID
- creation time of a v1, v6 or v7 UUID

## Endpoints and providers

None. The tool on the web page runs in the browser and calls no endpoint.

## What it costs

Nothing. The tool on the web page runs in the visitor's browser: no account, no API call and no limit per hour. The prompt above runs the same job from your own looot account with current data, billed per call.

## Primary keys

Seed a table or a fixture file with ids that never clash across machines.

## Sortable ids

Use v7 so new rows land at the end of an index instead of scattering across it.

## Idempotency keys

Send one fresh id per request so a retried payment or write runs once.

## Read an id

Paste a UUID from a log to see its version and, for v1, v6 and v7, when it was made.

## What is the difference between UUID v4 and v7?

A v4 UUID is 122 random bits. A v7 UUID starts with the Unix time in milliseconds and fills the rest with random bits, so v7 ids sort in the order they were created. Both are defined in RFC 9562.

## Which UUID version should I use for a database key?

v7 is usually the better primary key: new rows go to the end of the index, which keeps inserts fast in Postgres and MySQL. Use v4 when the id must not reveal when it was made.

## Can two generated UUIDs be the same?

In practice, no. A v4 id has 122 random bits, so a collision is far less likely than a hardware fault. This page also keeps v7 ids made in the same millisecond in strict order.

## Are these UUIDs random enough for production?

They come from crypto.getRandomValues, the browser's cryptographic random source, the same one crypto.randomUUID uses. They are fine as ids. Do not use an id as a secret token.

## How many UUIDs can I generate at once?

Up to 1,000 per batch. Press New batch for more. Copy all and the .txt download hold every id in the batch.

## Is a GUID the same as a UUID?

Yes. GUID is the name Microsoft uses for the same 128 bit format. Turn on uppercase and braces to get the form Windows tools often show, such as {6F9619FF-8B86-D011-B42D-00CF4FC964FF}.

## Can I see when a UUID was created?

For v1, v6 and v7, yes. Paste it in Inspect a UUID and the page reads the time stored in the id. A v4 id holds no time.

## Is anything sent to a server?

No. The ids are made and shown in your browser. Nothing is logged or stored.

## Related tools

- /free-tools/jwt-decoder
- /free-tools/unix-timestamp-converter
- /free-tools/base64-encoder-decoder

## Last reviewed

2026-10-14.