UUID & GUID Generator (RFC 4122 Master Suite)

Create cryptographically secure, time-ordered, or namespace-based Universally Unique Identifiers (UUIDs) across all official versions (v1, v3, v4, v5, v6, v7) with custom formatting and batch generation.

V4: 100% Cryptographically random (RFC 4122 standard recommendation).

What is this tool?

The UtilityHub Master UUID & GUID Generator is a professional engineering utility designed to generate Universally Unique Identifiers based on the official RFC 4122 and upcoming RFC standards. In modern software architecture, microservices design, and database engineering, UUIDs (128-bit numbers) serve as globally unique primary keys and session tokens without requiring a central database authority to allocate auto-incrementing integers.

Unlike traditional sequential IDs (like 1, 2, 3...), UUIDs prevent enumeration attacks where malicious actors guess successive record URLs. Furthermore, in distributed systems where database shards exist across global cloud regions, offline nodes can independently generate collision-free identifiers without network coordination delays.

100% Client-Side Privacy Guarantee: All UUID calculations, random number generation (via Web Crypto API CSPRNG), and hashing functions run completely inside your browser engine. Your generated keys, names, and hashes never leave your local machine or touch any server.

How to Use

  1. 1

    Select Version Specification

    Choose between UUID v4 (random), v7 (Unix Epoch time-sorted), v1/v6 (timestamp based), or v3/v5 (namespace string hash).

  2. 2

    Customize Output Formatting

    Toggle options for uppercase letters, hyphen removal, surrounding curly braces, or set batch generation up to 100 UUIDs.

  3. 3

    Copy or Download Results

    Click individual copy icons, copy all generated UUIDs at once, or export the batch directly as a .TXT file.

The Science & Logic Behind It

The Structure of a 128-bit UUID

A standard UUID is represented as a 32-character hexadecimal string divided into five groups separated by hyphens in the format 8-4-4-4-12 (total 36 characters including hyphens):

xxxxxxxx-xxxx-Mxxx-Nxxx-xxxxxxxxxxxx
  • M (Version Digit): Specifies the UUID specification version (e.g. 4 for Version 4, 7 for Version 7).
  • N (Variant Digit): Specifies the layout variant (usually 8, 9, A, or B corresponding to the 10xx binary RFC 4122 variant).

Comprehensive Version Comparison Benchmark

Version Mechanism Database Index Friendliness Primary Best Use Case
UUID v1 60-bit Gregorian Timestamp + MAC Address / Node Poor (Random prefix) Legacy systems requiring host node identification.
UUID v3 MD5 Hash of Namespace UUID + Name String Poor (Static hash output) Deterministic IDs for legacy MD5 hashed objects.
UUID v4 122 Bits Cryptographic CSPRNG Randomness Moderate (Random B-Tree page splits) General purpose security tokens, API keys, session IDs.
UUID v5 SHA-1 Hash of Namespace UUID + Name String Poor (Static hash output) Deterministic mapping of URLs, domain names, or user IDs.
UUID v6 Reordered v1 timestamp (High-to-Low) Good (Time-sorted) DB migration from v1 wanting B-Tree index ordering.
UUID v7 48-bit Unix Epoch Timestamp + 74-bit CSPRNG Random Excellent (Optimal DB locality) Modern SQL/NoSQL primary keys (PostgreSQL, MySQL 8+).

Mathematical Collision Probabilities (UUID v4)

The total number of unique UUID v4 keys is 2122 (approximately 5.3 × 1036, or 5.3 Undecillion). To illustrate how impossible a random collision is: if you generated 1,000,000,000 UUIDs every second for 85 consecutive years, the probability of encountering a single duplicate collision is roughly 50%.

Practical Use Cases

  • Distributed Database Primary Keys: Using UUID v7 as primary keys in PostgreSQL or MySQL avoids B-Tree index fragmentation while allowing distributed client nodes to generate IDs without central DB sequence locks.
  • Preventing Insecure Direct Object References (IDOR): Replacing integer URLs like /api/invoice/4589 with /api/invoice/9b1deb4d-3b7d-4144-963f-76a039323516 prevents attackers from scraping sequential invoice IDs.
  • Idempotency Tokens for Payments: E-commerce APIs use UUID v4 headers (X-Idempotency-Key) so duplicate HTTP requests caused by network retries do not charge credit cards twice.
  • Unique File Storage Naming: Uploaded images are renamed to UUID v4 on cloud buckets (AWS S3, Firebase) to prevent file overwrites when two users upload files with identical names like photo.jpg.

Frequently Asked Questions