Read the guide
Run Python UUID examples, convert an ID to text or hex, save a small batch, and check whether your interpreter supports uuid7.
Generate random v4 UUIDs or time-ordered v7 UUIDs, from one to 1,000 at a time. The UUID generator uses your browser's secure random number generator.
A UUID is 128 bits written as 32 hexadecimal digits in five groups: 8-4-4-4-12.
4) and the variant (the first digit of the fourth group is 8, 9, a, or b).Randomness comes only from crypto.getRandomValues and crypto.randomUUID. Math.random is never used.
xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx, where y is 8, 9, a, or b.Microsoft calls the same thing a GUID (globally unique identifier). GUIDs and UUIDs use the same 128-bit format, and many Windows tools display them in braces, which is what the "Wrap in braces" option is for.
For a database key, compare UUID v4 and v7 for database IDs before choosing time ordering or an embedded creation timestamp. The guide distinguishes the tool's generator behavior from performance that needs testing in your own database.
UUIDs identify records. They do not establish authorization, and a v7 timestamp can expose creation time. RFC 9562 describes the formats and security considerations.
For a secret value rather than a record identifier, generate a random token with a length suited to your application.
To generate values in a script, use the Python UUID examples and check which versions your interpreter supports.
Read the guide
Run Python UUID examples, convert an ID to text or hex, save a small batch, and check whether your interpreter supports uuid7.
Read the guide
Choose UUID v4 or v7 for database IDs and public URLs
Compare UUID v4 and v7 for database keys and public URLs, including timestamp exposure, same-millisecond ordering, and a reproducible ordering example.
A 128-bit identifier written as 36 characters. It is designed to be unique without a central registry.
Choose v4 when you want random identifiers without an embedded creation time. v7 starts with a millisecond timestamp, which can help locality in a time-ordered database index, but exposes approximate creation time. The better primary key depends on the database, index and workload; benchmark your own case.
Yes. Collisions are possible, although properly generated v4 UUIDs have a very large random space. Keep a unique constraint on database identifiers and handle a collision instead of treating uniqueness as guaranteed.
Yes. They come from your browser's cryptographic random number generator and never touch our server.
Often used together with UUID Generator.
Generates secure random tokens and API keys with a chosen length, alphabet, and prefix.