Skip to content
ConvertPass home

Developer

UUID generator

Create random UUID v4 or time-sortable v7 values without a network call.

This tool processes files and text locally in your browser. Your content is not uploaded or stored by this site.

Loading the workbench…

What this tool does

Version 4 uses crypto.randomUUID. Version 7 encodes Unix time in milliseconds plus random bits, so a batch sorts by creation time. Neither version is a secret. v7 identifiers leak when they were minted.

How to use it

  1. Choose version 4 or version 7.
  2. Set the count.
  3. Choose hyphen and case options.
  4. Copy or download the list.

Supported input

  • A count from 1 to 500, and a labelled version

Output

  • One UUID per line

Privacy

This tool processes files and text locally in your browser. Your content is not uploaded or stored by this site.

ConvertPass does not include your input in analytics, URLs, or error reports. Encoding: ASCII. Limit: 500 UUIDs (2.00 MB).

Limitations

  • Version 1, 3, 5, and 8 are not generated.
  • Version 7 embeds a millisecond timestamp. Do not use it where creation time must stay private.
  • Uniqueness is statistical, not coordinated across devices.

Example

Input
count=2
Output
7f1c3b2a-9d4e-4a6b-8c21-0f5d6a7b8c9d
2a9c1e4f-88b0-4d12-9e33-1a2b3c4d5e6f

The sample IDs are illustrative. Your output will be different every time.

Troubleshooting

crypto.randomUUID or crypto.getRandomValues is missing
Use a current browser on a secure origin (HTTPS or localhost). Version 4 needs randomUUID. Version 7 needs getRandomValues.

FAQ

Are these sequential?

Version 4 UUIDs are random. Do not sort them and expect creation order. Version 7 UUIDs sort by Unix time in milliseconds, then by a short sequence in the same millisecond.

Can I generate UUID v7?

Yes. Switch to Version 7 · time-sortable. The timestamp occupies the high bits, so anyone who sees the ID can recover the minting time to the millisecond. That is why the mode is labelled.

Is a UUID a secret?

v4 UUIDs are hard to guess but they are identifiers, not passwords. Do not use them as API keys if your threat model includes database leaks of those IDs.

Why cap batches at 500?

It keeps the page responsive. Generate another batch if you need more.

Related tools

Related guides

Related formats

Last reviewed 16 August 2026. Report a problem. Reports do not include your input.