Skip to content

UUID Generator

In-browser only RFC 9562 crypto.randomUUID()
R RegenerateC Copy
Version
Format
Hyphens
Case
Braces
Quotes

Formatting updates the visible UUID in place. It does not generate a new value.

Generated UUID
Generated in your browser using crypto.randomUUID().
Related tools View all

Overview

Generate and inspect UUIDs, entirely in your browser

Generate universally unique identifiers (UUIDs) instantly in your browser. Supports v1, v3, v4, v5, v6, v7, NIL, and Max. Fully client-side — nothing leaves this page.

  • v1, v3–v7, NIL & Max versions
  • Bulk generation up to 1,000
  • Format controls — hyphens, case, braces
  • Inspector to decode any UUID
  • Export to TXT, CSV or JSON
  • Runs entirely in your browser
  • Runs entirely in your browser — UUIDs never leave your device
  • Uses crypto.randomUUID() and Web Crypto for secure randomness
  • Nothing is uploaded, logged, or stored on a server
  • Deterministic v3/v5 digests computed locally in your browser
  • Database primary keys (v7 for sortable indexes)
  • Idempotency keys for safe API retries
  • Correlation and trace IDs across distributed services
  • Stable deterministic IDs from a name (v3/v5)
  • Placeholder sentinel values (NIL, Max)

Guide

How to Use

  1. 1
    Generate a single UUID

    Open the page and a v4 UUID is already generated. Click Copy to copy it to your clipboard, or press C.

  2. 2
    Switch versions

    Click any version button (v4, v7, v1, v6, v3, v5, NIL, Max) to generate a UUID of that type. The displayed UUID updates immediately.

  3. 3
    Generate in bulk

    Toggle Bulk Mode on. Set your count (or pick a preset like 100 or 1000), then click Generate. Each result has its own copy button.

  4. 4
    Change format

    Use the format controls to toggle hyphens on/off, switch between lowercase and uppercase, add braces, or wrap in quotes. Changes apply instantly to all displayed UUIDs without regenerating.

  5. 5
    Export results

    In bulk mode, click Copy All to copy every UUID, or use the Export menu to copy or download as plain text, CSV, or JSON.

  6. 6
    Decode an existing UUID

    Switch to the Inspect / Decode tab, paste any UUID, and click Inspect. You will see the version, variant, canonical form, and embedded timestamp (for v1, v6, v7).

Reference

UUID Version Comparison

UUID Version Comparison
VersionOrderedDeterministicUses TimeBest For
v1——YesLegacy systems requiring time + node
v3—Yes—Deterministic IDs from name (MD5)
v4———General-purpose random identifiers
v5—Yes—Deterministic IDs from name (SHA-1)
v6Yes—YesSortable IDs (reordered v1)
v7Yes—YesDatabase primary keys, modern apps

Pitfalls

Common Mistakes

  • Using v1 when MAC privacy matters

    UUID v1 can embed a MAC-like node identifier. While this tool uses a random node with the multicast bit set, some v1 implementations may leak real hardware identifiers. Prefer v4 or v7 if privacy is a concern.

  • Assuming v4 is sortable

    UUID v4 is entirely random and has no natural order. If you need sortable IDs for database indexes, use v7 instead — its embedded timestamp ensures chronological ordering.

  • Storing UUIDs as strings when a native type exists

    Most databases (PostgreSQL, MySQL 8+, SQL Server) have a native UUID column type that stores the value as 16 bytes. Storing as a 36-character string wastes space and slows comparisons. Use the native type whenever available.

  • Using a UUID as a security token

    While UUID v4 is cryptographically random, UUIDs are not designed to be secret. They may be logged, indexed, or cached in transit. For security tokens, use dedicated token formats with appropriate entropy and expiration.

Anatomy

Annotated Examples

Real UUIDs of each version with the version nibble, variant bits, and timestamp fields highlighted.

UUID v4 (Random)
550e8400-e29b-41d4-a716-446655440000
Version nibble Variant bits (8/9/a/b)
UUID v7 (Time-ordered)
01890a5d-ac96-774b-bcce-b302099a8057
Timestamp Version nibble Variant bits (8/9/a/b) — 48-bit ms epoch ≈ 2023-07-12T12:34:56.789Z
UUID v1 (Time + Node)
6fa459ea-ee8a-13e4-a044-2e10a2c3d5f0
Timestamp Version nibble Variant bits (8/9/a/b) — Timestamp fields are split across the first three groups.
UUID v3 (MD5 namespace + name)
9073926b-929f-31c2-abc9-fad77ae3e8eb
Version nibble Variant bits (8/9/a/b) — Deterministic — same namespace (DNS) + name ("example.com") always produces this UUID.
UUID v5 (SHA-1 namespace + name)
cfbff0d1-9375-5685-968c-48ce8b15ae17
Version nibble Variant bits (8/9/a/b) — Deterministic — same namespace (DNS) + name ("example.com") always produces this UUID.
NIL UUID
00000000-0000-0000-0000-000000000000
All zeros. Used as a sentinel or placeholder value in tests and migrations.
Max UUID
ffffffff-ffff-ffff-ffff-ffffffffffff
All ones. Used as an upper bound or maximum sentinel value.

Frequently Asked Questions

What is a UUID?
A UUID (Universally Unique Identifier) is a 128-bit label used to identify information in computer systems. UUIDs are standardized by RFC 9562 and are designed to be globally unique without requiring a central registry. They are commonly formatted as 32 hexadecimal digits displayed in five groups separated by hyphens: 8-4-4-4-12.
What is the difference between UUID and GUID?
UUID and GUID (Globally Unique Identifier) are essentially the same thing. "GUID" is the term commonly used in Microsoft/.NET ecosystems, while "UUID" is the standard term used in the RFC specification and most other platforms. The format and generation algorithms are identical.
Which UUID version should I use?
For most use cases, use UUID v4 (random) for general-purpose unique identifiers, or UUID v7 (time-ordered) when you need sortable IDs, especially for database primary keys. Use v3 or v5 when you need deterministic UUIDs derived from a name and namespace. Avoid v1 if you need to hide timing information.
What is UUID v4 and how random is it?
UUID v4 uses 122 bits of cryptographically secure random data (6 bits are reserved for version and variant). When generated with crypto.randomUUID() or crypto.getRandomValues(), the probability of collision is astronomically low — you would need to generate about 2.71 quintillion UUIDs to have a 50% chance of a single collision.
What is UUID v7 and why is it better for databases?
UUID v7 embeds a Unix timestamp (milliseconds) in the first 48 bits, making the IDs naturally sortable by creation time. This is a major advantage for database indexes, especially B-trees, because new records are always appended rather than inserted randomly. This reduces page splits, improves write throughput, and makes range queries on time efficient.
Are UUIDs unique? Is collision possible?
UUIDs are designed to be unique in practice, but collisions are theoretically possible for random versions (v4, v7). The probability is vanishingly small when using a cryptographic random source. For deterministic versions (v3, v5), the same namespace + name will always produce the same UUID, which is by design.
Is it safe to generate UUIDs in the browser?
Yes. Modern browsers provide crypto.randomUUID() and crypto.getRandomValues(), which use the operating system's cryptographic random number generator. Browser-generated UUIDs are equally secure to those generated server-side, with the added benefit that the values never leave your device.
Can I use a UUID as a primary key?
Yes, UUIDs are commonly used as primary keys in databases. UUID v7 is recommended for this purpose because its time-ordered nature is friendly to B-tree indexes. If using v4, be aware that random insertion can cause index fragmentation in large tables. Most databases have a native UUID column type that stores the value efficiently as 16 bytes.
Why do some UUIDs have braces or no hyphens?
Different systems expect different formats. The canonical form uses hyphens (8-4-4-4-12). Microsoft/.NET often wraps UUIDs in braces: {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}. Some databases and APIs accept the 32-character hex string without hyphens. Use the format toggles above to match your target system's convention.
How many UUIDs can I generate at once here?
You can generate up to 1,000 UUIDs in a single batch using bulk mode. All generation happens client-side in your browser, so there is no server-imposed limit. For larger batches, simply generate multiple times and export the results.
What is a NIL UUID?
The NIL UUID is a special form consisting entirely of zeros: 00000000-0000-0000-0000-000000000000. It is defined in RFC 9562 and is used as a sentinel or placeholder value — for example, to indicate "no UUID" or as a default value in database migrations. The Max UUID (all ones: ffffffff-ffff-ffff-ffff-ffffffffffff) is the complementary upper-bound sentinel.