UUID Generator

Generate random (v4) or time-based (v1) UUIDs instantly.

Configuration

What is a UUID?

A UUID (Universally Unique Identifier), sometimes called a GUID, is a 128-bit value typically rendered as a 36-character string of hexadecimal digits separated by hyphens — for example 550e8400-e29b-41d4-a716-446655440000. UUIDs are designed to be unique without coordination between the systems that generate them, which makes them perfect for primary keys in distributed databases, message identifiers in event streams, idempotency tokens in REST APIs, and stable identifiers for user-uploaded files.

This generator supports two of the most common variants. Version 4 UUIDs are derived from cryptographically random bytes, giving you 122 bits of entropy and a vanishingly small chance of collision even at internet scale. Version 1 UUIDs encode the current timestamp and the MAC address of the generating machine, which makes them sortable by creation time but reveals more about their origin. Pick v4 for opaque identifiers and v1 when chronological ordering matters more than secrecy.

How to use

  1. Choose between Version 4 (random) and Version 1 (time-based).
  2. Set how many UUIDs you need — anywhere from 1 to 50 in a single batch.
  3. Press Generate. The results appear instantly because everything happens in your browser.
  4. Hover any individual UUID to copy it, or use Copy All to grab the entire batch as a newline-separated list.

Common use cases

  • Primary keys for new database tables where auto-incrementing integers leak record counts.
  • Idempotency keys for safe retries of REST and gRPC requests.
  • Tracing IDs propagated across microservices for distributed debugging.
  • Filenames for user uploads to avoid collisions and path traversal attacks.
  • Anonymous device identifiers in analytics pipelines.

Frequently asked questions

Are these UUIDs cryptographically secure?

Yes. Version 4 UUIDs are generated using your browser's crypto.getRandomValues() implementation, which is the same source used for cryptographic key generation in Web Crypto.

Can two random v4 UUIDs ever collide?

In theory, yes. In practice, you would need to generate billions of UUIDs per second for many years before the odds of a collision became measurable. v4 UUIDs are considered safe for production identifiers without coordination.

When should I use v1 instead of v4?

Use v1 when you want time-ordered identifiers and do not mind that they leak the time of creation and (historically) a machine identifier. Modern v1 implementations replace the MAC address with random bytes, but they still expose timing.

What about v6, v7 and v8?

v6 and v7 are newer time-ordered variants that fix the byte ordering issues of v1 so that UUIDs sort correctly in databases. They are useful for primary keys in tables you intend to range-scan. We are planning to add support for these formats.

Advertisement