🔒  100% client-side · Your data never leaves this browser · No uploads, no tracking

💡 Why this exists

Primary keys, request IDs, trace IDs — every developer generates UUIDs daily. Online generators that run on servers are fine for random strings, but deterministic teams want crypto-secure, version-controlled, testable generation that also works in CI pipelines via URL deep links.

Generated UUIDs will appear here...

Validate a UUID

Capability Info

IDuuid.generate
Version1.0.0
Statusstable
CategoryGenerators
Contractno side effects, local, no AI
RuntimeBrowser, Node, Edge, Worker
Consumesoptions (version, count, uppercase)
Producesuuids[]

UUID Versions Explained

🎲 v4 — Random

122 random bits. The most common choice for database keys and identifiers. Crypto-secure via crypto.getRandomValues.

🕒 v7 — Time + Random

48-bit timestamp + random suffix. Time-ordered: sorts chronologically, ideal for indexes.

📅 v1 — Time-based

Timestamp + clock sequence + node. Historically common; leaks creation time and MAC-ish entropy — prefer v4/v7 for new systems.

✅ Validation

Format check (8-4-4-4-12 hex), version and variant detection, nil-UUID detection.

🛡️ Security note: v4/v7 use the platform CSPRNG, never Math.random().

AI is probabilistic. Your tools shouldn't be.

Frequently Asked Questions

Are the UUIDs cryptographically secure?

Yes — v4 and v7 use the platform CSPRNG (crypto.getRandomValues), never Math.random().

Which versions are supported?

v4 (random), v7 (time+random, sortable) and v1 (time-based), with bulk generation up to 5000 at once.

Why prefer v7 over v1?

v7 is time-ordered like v1 but uses random entropy instead of leaking MAC-derived node data, and plays better with database index locality.

Can it validate any UUID?

Yes — paste any UUID to check format, detect its version (1/3/4/5/7), RFC 4122 variant and nil-UUID status.

Tools we recommend

Deploy this tool on Vercel · Ship faster with Cursor · Your static site on Cloudflare

Copied to clipboard!