By MixKhazana Research Team · Updated 24 October 2026
Photo: Shixart1985 / Wikimedia Commons, CC BY 2.0
Generate up to 500 UUIDs at once — random v4 or time-ordered v7 — validate any UUID, decode embedded timestamps, and export as TXT, JSON or SQL. No sign-up, nothing leaves your browser.
Tip: v7 IDs sort by creation time — ideal for database primary keys.
🔍 UUID Validator & Analyzer
Paste any UUID to check it — version, variant, and (for v1/v7) the exact creation timestamp hidden inside.
💻 Generate UUIDs in code
Prefer your own stack? These snippets produce the same RFC 4122 v4 UUIDs:
A UUID (Universally Unique Identifier) is a 128-bit ID written as 32 hexadecimal digits in the familiar 8-4-4-4-12 shape, for example 6ec0bd7f-11c0-43da-975e-2a8ad9ebae0b. It is designed to be unique across space and time without any central registry — two servers on opposite sides of the planet can mint IDs independently and never collide. That makes UUIDs the default choice for database primary keys, distributed systems, session tokens, order IDs and file names.
v4 vs v7 — which version should you use?
v4 — Random
v7 — Time-ordered
How it works
122 bits of pure randomness
48-bit millisecond timestamp + 74 random bits
Sortable?
No — random order
Yes — sorts by creation time
Best for
Tokens, session IDs, anything where you want zero time information leaked
Rule of thumb: reaching for a database primary key? Pick v7 — sequential inserts keep your B-tree index compact instead of fragmenting it the way random v4 keys do. Need an unguessable token or just a plain unique ID? v4 is the safe default.
Why bulk generation matters
Seeding a test database, generating fixture data, or migrating a table to UUID keys means you need hundreds of IDs at once — not one at a time. Generate the batch here, then export it:
.txt — one UUID per line, ready for scripts and config files.
.json — a JSON array, ready to paste into seed files or API payloads.
.sql — an INSERT statement skeleton for a table with an id column.
Formats: uppercase, compact and braces
Different platforms insist on different shapes: Windows/.NET tooling often expects {braces} and UPPERCASE, URLs prefer the compact 32-character no-hyphen form, and most APIs accept plain lowercase. The format options above cover all three — pick once, generate, done.
Private by design
UUIDs frequently end up as primary keys, API tokens and correlation IDs inside databases and logs. This generator uses your browser's cryptographic random source (crypto.getRandomValues) and never sends anything to a server — your IDs never transit a third party.
❓ UUID FAQ
How unique is a UUID v4 really?
122 bits of randomness give about 5.3 × 10³⁶ possible values — you would need to generate roughly 2.7 quintillion UUIDs for even a 50% chance of a single collision. Treat collisions as impossible in practice.
v4 vs v7 — which for database primary keys?
v7. Its leading timestamp means new IDs sort chronologically, so inserts land near the end of the index instead of scattering randomly and fragmenting it — noticeably kinder to PostgreSQL and MySQL.
Can I use UUIDs in URLs?
Yes. The hyphenated form is URL-safe; the 32-character no-hyphen form is even shorter. Avoid the brace-wrapped form in URLs ({ and } need percent-encoding).
Are UUIDs secret? Can one be a token?
A v4 UUID (122 random bits from a cryptographic source) is unguessable, so it works as a reset link or API key. But UUIDs are identifiers, not secrets by design — never use a v1 UUID for security, since it embeds your MAC address and timestamp.
What is the nil UUID?
00000000-0000-0000-0000-000000000000 — all zeros, used as a null/empty placeholder where a UUID value is required but none exists yet.
Does this generator upload anything?
No. Generation is 100% local via the Web Crypto API. Nothing is transmitted, logged or stored — it even works offline once the page has loaded.
Disclaimer: The information and estimates on this page are for general guidance only and are not professional financial, legal or medical advice — always verify with official sources before acting. Photos on this page are copyright-free originals, credited to the photographer and source with the licence noted.