Your data is never sent to any server.
The UUID generator creates universally unique identifiers, v4 (random) or v7 (time-sortable), one at a time or in batches of up to 100. Copy them individually or all at once, ready for your code or database.
They’re generated in your browser with secure cryptography.
What it’s for
- Databases: generate unique primary keys without coordinating sequences across servers.
- Development and testing: seed fixtures and test data with realistic identifiers in bulk.
- APIs and distributed systems: uniquely identify requests, events or resources across services.
- Traceability: use UUID v7 for identifiers that also preserve creation order.
How to use UUID Generator
- 1
Choose the UUID version
UUID v4 generates fully random identifiers; UUID v7 embeds a timestamp, making them sortable in chronological order.
- 2
Set how many you need
Type the amount (1 to 100) to generate them in bulk, handy for seeding test data or reserving identifiers.
- 3
Generate the UUIDs
Press “Generate UUIDs” and the numbered list appears instantly. Regenerate as many times as you like.
- 4
Copy one or all
Each UUID has its own copy button, and “Copy all” sends them to your clipboard one per line.
Frequently asked questions
What is a UUID?
A 128-bit universally unique identifier, shown as 36 hex characters with hyphens. The odds of generating two identical ones are so tiny they're considered unique in practice.
What's the difference between UUID v4 and v7?
v4 is fully random. v7 starts with a Unix timestamp, so UUIDs generated later are "greater", which improves performance as a database primary key.
When should I use v7 instead of v4?
Use v7 for database primary keys and records ordered by creation; indexes perform better with increasing values. Use v4 when you don't want to leak timing information.
Are the UUIDs generated here cryptographically secure?
Yes. They're generated with the browser's cryptographic generator (crypto.randomUUID / getRandomValues), the same randomness backend libraries use.
Can there be collisions between UUIDs?
In theory yes, in practice no. With UUID v4 you'd have to generate billions per second for decades to have any meaningful chance of a collision.