Skip to main content

Developer Tools · No account required

Generate UUIDv4 and UUIDv7 Identifiers

Generate up to 1,000 random UUIDv4 or time-ordered UUIDv7 identifiers using browser cryptographic randomness.

Instructions, examples and limitations ↓

What this tool does

Create a batch of standards-shaped UUIDv4 or UUIDv7 identifiers using cryptographically random browser bytes. Version 4 emphasizes random identifiers; version 7 starts with a Unix millisecond timestamp for time-oriented database ordering.

Enable JavaScript to use the local processing controls. Instructions and examples are available below.

Practical guide

Generate UUIDv4 and UUIDv7 Identifiers

By MultiZest · Updated

How to use this tool

  1. Choose UUIDv4 or UUIDv7 according to your application’s expected format.
  2. Enter a count from 1 to 1,000 and generate the batch.
  3. Copy or download the newline-separated identifiers. Generate a new batch when you need fresh values.

Worked example

For ten independent fixture records, choose UUIDv4 and count 10. For a system expecting timestamp-prefixed identifiers, choose UUIDv7, then validate that the receiving database supports that version.

Version bits and random bits

The generator sets the version and variant bits and fills the remaining random portion with crypto.getRandomValues. UUIDv7 also encodes the current Unix timestamp in its first 48 bits.

Identifiers within the same millisecond have random ordering. This implementation does not use a monotonic counter and does not promise that a batch will be lexicographically sorted. A clock adjustment can also affect time order.

Uniqueness is not authorization

Random identifiers have a low collision probability, not a mathematical guarantee of uniqueness. Use a database uniqueness constraint where collisions must be handled.

UUIDv7 reveals approximate creation time. Neither UUID version should replace an application’s authentication or authorization checks. Use a secret-token workflow for access credentials.

Choose identifiers around the system receiving them

For test fixtures and ordinary independent records, UUIDv4 is a familiar random identifier format. UUIDv7 includes a timestamp prefix and can be useful in systems that deliberately use time-oriented identifiers. Choose the version your database, API or library expects instead of assuming all UUID strings are interchangeable.

Generate only the batch you need and keep it with the corresponding test data. If you paste the same identifier into several records, generating a random batch did not prevent that duplication. The destination should still enforce the uniqueness rules appropriate to its data model.

Do not treat an identifier as a secret

UUIDs help distinguish records. They are not a replacement for authorization checks on a route or database query. UUIDv7 also reveals approximate creation time through its timestamp component, which can matter if a public identifier is meant to conceal when a record was created.

Within one millisecond, this generator uses random remaining bits rather than a monotonic counter. Do not infer a strict order among those values from their text alone. Review the database’s storage type and indexing behavior, and keep a uniqueness constraint where a collision must be handled rather than merely assumed impossible.

Questions and troubleshooting

Are UUIDv7 values sorted within the same millisecond?

Not necessarily. Their timestamp prefix matches, while the remaining bits are random. This generator has no monotonic counter.

Are generated UUIDs stored by MultiZest?

No. They are generated in browser memory and are only persisted when you copy or download them.

Can I use a UUID as a password-reset secret?

Use a dedicated secure token workflow with appropriate entropy, expiration and server-side validation. An identifier’s appearance or uniqueness does not by itself make it suitable as an access credential.

Continue with a related tool

Sources and further reading

Found an error or an unclear instruction? Report it. Read our editorial policy and privacy policy.