UUID Generator
Generate universally unique identifiers for development, testing, and data workflows.
Result
Your result
No result yet
Generate to see your result
Choose your options below — no signup required.
Example output
A few results generated by this tool.
- 6997e713-74ef-4b27-82c8-c262ac9959d8
- b8d5ba1a-25d3-4fbe-8ceb-d76c3639b0c9
- de5c8af7-cc38-458c-b022-2c40d37d2b05
- 6d7711c9-20d8-4d24-b4ab-0c45c1110423
- 1a0f9aea-9364-4317-907a-943084820ff8
How it works
Choose how many UUIDs you need and an output format, then generate. Every value is a random UUID v4 created with Ruby's secure random generator and formatted for the option you pick.
Useful for
- Creating test records
- Seeding development data
- Naming API resources
- Public identifiers
- Fixture data
A quick tip
Generate a fresh UUID for every record that needs a stable public identifier; do not reuse one across unrelated entities.
What a UUID is
A UUID is a 128-bit identifier written as 32 hexadecimal digits in five groups. Version 4 UUIDs are random rather than sequential, which makes them useful as public identifiers that do not reveal creation order or record count. This tool produces v4 values only.
How to generate a UUID
Set the count, choose Standard, Uppercase, No hyphens, or URN, and generate. Standard output is 36 characters with hyphens; the no-hyphen form is 32 characters for systems that store a compact string. Copy the batch into fixtures, a migration, or a seeding script.
Limits and boundaries
Random v4 values are not sortable and do not encode a timestamp, so they are a poor fit for a clustered primary key in some databases. They are not secrets: do not use a UUID as an API token, a password reset code, or anything that must be unguessable. Uniqueness is probabilistic, so your schema should still enforce a unique constraint.
UUID formats
The table shows the four output formats and where each one is usually required. Pick the format the receiving system expects rather than converting later.
| Format | Example | Length | Typical use |
|---|---|---|---|
| Standard | 550e8400-e29b-41d4-a716-446655440000 | 36 | Databases, APIs |
| Uppercase | 550E8400-E29B-41D4-A716-446655440000 | 36 | Legacy systems |
| No hyphens | 550e8400e29b41d4a716446655440000 | 32 | Compact storage |
| URN | urn:uuid:550e8400-e29b-41d4-a716-446655440000 | 45 | URIs and XML |
UUIDs in a schema
Many teams keep an internal integer key and add a UUID as a public column, which preserves fast joins while hiding record counts. If the UUID is the primary key, check how the database stores it: a native UUID type takes 16 bytes, while a text column costs 36 bytes plus index overhead.
FAQ
Which UUID version does this generate?
Version 4, the random format defined by RFC 4122. The tool does not generate time-ordered v7 values.
Are generated UUIDs actually unique?
Collisions are statistically negligible, but uniqueness is not guaranteed by generation. Add a unique constraint in the database.
Can I use a UUID as an API key or password?
No. UUIDs are designed to be unique, not secret. Use a dedicated token with enough entropy for credentials.
Why is my UUID not sortable by creation time?
Version 4 values are random. If you need time order, use a timestamp column or a v7-style identifier.
Can I get a UUID in uppercase or without hyphens?
Yes. Choose the Uppercase or No hyphens format before generating, or convert the result downstream.