RFC 9562 Compliant · All 8 Versions

UUID Generator

Generate random UUIDs instantly — v1, v4, v7, and all 8 versions including UUIDv4, UUIDv7, GUID, and Nil. Bulk export, validate, and decode. Runs entirely in your browser — your random UUID generator with zero server calls.

Only need one version? Try the dedicated UUID v4 or UUID v7 generator.

Bulk Generation
Validate UUID
★ 100% Free & Online ✓ No Signup 🔒 Browser-Only · Zero Server Calls ★ RFC 9562 Compliant

The Basics

What is a UUID?

A UUID (Universally Unique Identifier), also called a GUID (Globally Unique Identifier) in Microsoft/.NET contexts, is a 128-bit number used to generate a unique, random ID for any resource — a database row, API object, session, or file — without any central authority handing out IDs. Any computer can independently generate a random UUID or random GUID and trust it will not collide with an identifier generated anywhere else.

Every UUID is 32 hexadecimal digits in an 8-4-4-4-12 pattern — 36 characters total:

f47ac10b-58cc-4372-a567-0e02b2c3d479

RFC 4122 (2005) introduced versions 1–5. RFC 9562 (May 2024) superseded it and formally added v6, v7, and v8. You will also see the term GUID (Globally Unique Identifier) in Microsoft/.NET contexts — it is the same standard with a byte-order difference in some implementations.

Microsoft / .NET / COM
Need a GUID Generator?
Generate a new GUID online — same 128-bit standard, .NET & COM byte-order framing. Free, instant, browser-only.
Generate GUID →

Version Guide

Which UUID version should you use?

UUID v7 (UUIDv7) is now the recommended default for database primary keys — it embeds a millisecond Unix timestamp so IDs sort by creation time and index far more efficiently in a B-tree than a random ID. PostgreSQL 18 ships native uuidv7() support. UUID v4 (UUIDv4, uuid4) remains the right pick for opaque tokens, random IDs, and secrets where you do not want to expose creation time. Need a new GUID instead? Select v4 above — a GUID and a UUID v4 are the same 128-bit random identifier.

VersionBased OnTime-SortableBest ForStatus
v1Timestamp + MACPartiallyLegacy distributed systemsAvoid (MAC leak)
v3Namespace + name (MD5)NoDeterministic IDs, legacyUse v5 instead
v4122 bits randomNoTokens, secrets, random IDs, GUIDs (UUIDv4, uuid4)Recommended
v5Namespace + name (SHA-1)NoDeterministic, reproducible IDsRecommended
v6Reordered timestamp + randomYesv1 migration pathRFC 9562
v7Unix ms timestamp + randomYesDatabase primary keys (UUIDv7, uuid7)Recommended 2026
v8Custom layoutDependsApplication-defined schemasExperimental
Nil / MaxAll-zero / all-FPlaceholders and testingSpecial values

v1–v5 defined in RFC 4122 (2005). v6, v7, and v8 defined in RFC 9562 (May 2024).

Use Cases

What are UUIDs used for?

UUIDs are the default unique ID generator solution anywhere a system needs collision-free random IDs without central coordination — the foundation of modern distributed software. A UUID is also the format behind every GUID, random ID, and randomly generated identifier across the web.

🖺

Database Primary Keys

Unique row identifiers that work across shards and replicas without a shared sequence generator.

🔗

API Resource IDs

REST and GraphQL object identifiers that do not expose sequential counts to clients.

Distributed Systems

Microservices and offline-first apps can generate IDs independently with no database round-trip.

🔒

Session Tracking

Session tokens, request IDs, and trace IDs across logs and distributed tracing systems.

📁

File Naming

Collision-free names for uploads, generated assets, and object storage buckets.

🧪

Test & Mock Data

Collision-free placeholder IDs, random ID generator output for test suites, and database seed data.

Collision Probability

How unique is a UUID, really?

A UUID v4 has 122 bits of actual randomness. That gives roughly 5.3 × 10³⁶ possible values.

5,316,911,983,139,663,491,615,228,241,121,400,000
Possible UUID v4 values. This is why UUID is the world’s most reliable random ID generator — if every person on Earth generated 600 million random IDs each, the probability of a single collision would still be around 50%.

Practically speaking, treat v4 collisions as a non-event at any realistic scale. One important caveat: a UUID is not a cryptographic secret. It is built for uniqueness, not unguessability under attack. Never use a UUID alone as an auth token or password.

Developer Reference

Generate a UUID in your language

Every major language has a native implementation to get a UUID, create a random ID, or build a unique ID generator into your own app:

🔒

This Online UUID Generator Runs Entirely in Your Browser

Every UUID produced here is created client-side using your browser’s built-in crypto.getRandomValues(). Nothing is transmitted anywhere. No UUIDs are logged, stored, or sent to any server. No account required. Open your browser’s Network tab and check for yourself.

FAQ

Frequently asked questions

itemtype=”https://schema.org/FAQPage”>
UUIDs are used anywhere a system needs a unique identifier without coordinating with a central authority — database primary keys, API resource IDs, session tokens, distributed event IDs, file names, and message queue IDs are the most common applications.
They are the same 128-bit identifier standard. GUID (Globally Unique Identifier) is the term Microsoft uses in .NET, COM, and Windows implementations. Some Microsoft implementations differ in byte-order representation, but for practical purposes the terms are interchangeable.
Use UUID v7 for new database primary keys — it is time-sortable and B-tree friendly. Use UUID v4 for opaque tokens and secrets. Avoid v1 for user-facing projects because it embeds the generating machine’s MAC address.
Mathematically yes. Practically no, at any realistic scale. UUID v4 has 2 to the power of 122 possible values. To reach a 50% collision probability you would need to generate 1 billion UUIDs every second for roughly 100 years.
No. A UUID is designed for uniqueness, not cryptographic security. Do not use it as a standalone password, API secret, or auth token. Use a dedicated secret generator for anything that must be unguessable under adversarial conditions.
Yes. All versions conform to RFC 4122 (v1, v3, v4, v5) and RFC 9562 (v6, v7, v8), which superseded RFC 4122 in May 2024. The browser’s crypto.getRandomValues() API is used for all random components.
Yes — click Bulk Generate to create up to 1,000 UUIDs at once and export them as plain text, JSON, or CSV.
A UUID is 32 lowercase hexadecimal digits in five groups separated by hyphens: 8-4-4-4-12. It is always 36 characters including hyphens, or 32 without. The 13th character identifies the version; the 17th identifies the variant.