The Volade Ecosystem — Web Tool

Free Online UUID Generator

Generate UUIDs (universally unique identifiers) from version 1 to version 8, entirely in your browser. RFC 9562-compliant canonical format, validator with version and variant detection, timestamp decoder, converter (binary, base64, decimal, GUID, URN), batch generation up to 10,000 and TXT, CSV, JSON or SQL export. 100% local, cryptographically secure, no sign-up.

Generate a UUID Validate a UUID
100% local, no upload Cryptographically secure Never stored or sent
The tool

Generate, validate and convert your UUIDs in seconds

Pick a version, set your options, generate. Everything happens locally: your identifiers never leave your device.

UUID Generator & Toolkit

Online Security, Network & Cryptography
Log in

An UUID is not a password. An UUID serves as an identifier (databases, APIs, idempotency), not as an authentication secret: its size is known, its structure is public and it is stored in clear text. For a secret, use our password generator instead.

v4 (random, 122 bits) remains the default choice. Timestamped v7 sorts naturally over time and indexes better in databases. v1/v6 use the system clock and a random node: no information about your device, unlike other tools that read the real MAC.

100% local generation
—

Press "Generate" or re-click a version to create a new cryptographically random identifier, compliant with RFC 9562 / RFC 4122.

Generate a large number of UUIDs (up to 10,000), detect possible duplicates and export to TXT, CSV, JSON or SQL. v4 batches above 5,000 use a worker to keep the page responsive.

100
Generate UUIDs to display the results.

Accepted formats: canonical, hyphen-free, brace-wrapped, URN-prefixed, uppercase/lowercase. The analysis is 100% local.

The results will appear here.

Enter an UUID in any form (canonical, URN, braces, hyphen-free, unbracketed base64 or decimal integer): all conversions update instantly.

Short identifiers (NanoID, short-uuid, truncated MD5) are not RFC UUIDs: their bit count differs.

The conversions appear here.

Comparison result will appear here.

10

Ready-to-use scripts for your projects: regular expressions, code snippets and SQL insertion script.

Generate the SQL script or copy a regular expression.

0,0 0Comments All tools
Free or Premium?

The UUID generator is 100% free, local and unlimited — for everyone. Premium unlocks the entire Volade ecosystem.

Unlimited UUIDs v1 to v8, Nil & MaxFree
Validator, decoder & converterFree
Batches up to 10,000 & TXT/CSV/JSON/SQL exportFree
Encrypted history & synchronizationPremium
Unlock Premium
Features

The most complete UUID toolkit

100% local, cryptographically secure

UUIDs are generated in your browser with crypto.getRandomValues() (and crypto.randomUUID() for v4), never with Math.random(). Nothing is sent, stored or analyzed on a server — ideal for confidential work environments.

Privacy policy

8 versions + validator + decoder

All RFC versions: timestamped v1 and v6, hashed v3/v5, random v4, time-ordered v7, custom v8, plus Nil and Max. The validator detects the version, the variant and the format; the decoder reads the timestamp and every field.

Generate now

Batch & professional exports

Up to 10,000 UUIDs at once, statistics (total, unique, duplicates, entropy), and TXT, CSV, JSON or SQL insertion script exports — ideal for preparing datasets, migrations or tests without any data leakage.

Generate in batch
How it works

A quality UUID in three steps

Choose the version

Random (v4) for simplicity, timestamped (v7) to sort and index efficiently, hashed (v3/v5) for deterministic identity, or custom (v8) for your own fields.

Generate & verify

Each generation is cryptographically random and 100% local. The decoder immediately shows the version, the variant and, for timestamped versions, the exact creation date.

Copy, validate, deploy

Copy the UUID, validate existing identifiers, compare them or convert them (base64, decimal, .NET GUID, SQL…). Everything happens locally, without sign-up.

Reference

UUID version comparison (RFC 9562 / RFC 4122)

VersionStandardTimestampBit sourceTime orderingBest for
v1RFC 9562 / 4122Yes (100 ns, Gregorian offset)Clock + sequence + nodeGlobal chronological orderLegacy compatibility
v2DCE (reserved)YesPOSIX UID—Not supported here (obsolete)
v3RFC 9562 / 4122NoMD5(namespace + name)NoDeterministic identity (MD5, 128 bits)
v4RFC 9562 / 4122NoRandom (122 bits)NoGeneral-purpose identifiers
v5RFC 9562 / 4122NoSHA-1(namespace + name)NoDeterministic identity (SHA-1)
v6RFC 9562Yes (100 ns)Clock + sequence + nodeLocally ordered sequencev1 compatibility + improved ordering
v7RFC 9562Yes (milliseconds)48-bit ms + 74 random bitsOptimal order in the indexModern database keys
v8RFC 9562Depends on your fieldsCustom fieldsDepends on your fieldsProprietary / experimental formats
NilRFC 9562NoAll bits set to 0—"Empty" value / sentinel
MaxRFC 9562NoAll bits set to 1—Maximum value / sentinel
FAQ

Frequently asked questions

What is an UUID?
An UUID (Universally Unique Identifier) is a 128-bit identifier, written as 32 hexadecimal digits grouped as 8-4-4-4-12 (e.g. 550e8400-e29b-41d4-a716-446655440000). It identifies without centralized collision management: each UUID can be created independently, on any machine, with a negligible collision probability.
Which UUID version should I choose?
For a temporary key or log identifier, v4 (random) is the default choice: 122 bits of entropy, no information about the creation time. For a database primary key where ordering and indexing matter, v7 is recommended: its millisecond timestamp makes insertions locally ordered, reducing index fragmentation.
Can an UUID be guessed or exploited?
A v4 UUID generated with a cryptographically secure generator cannot be guessed: the brute-force search time is on the order of 10³⁶ times the age of the universe. However, v1/v6/v7 contain a timestamp: an observer can deduce the exact creation time. This is a design detail, not a vulnerability, but sometimes worth considering for privacy.
Is an UUID a good password?
No. An UUID serves as an identifier: it is structured, often visible in URLs and logs, and stored in clear text. Using an UUID as a password is like displaying the secret. For a login secret or API key, use our password generator instead (128 bits or more, uniform, without structure).
What is the difference between UUID and NanoID / short-uuid?
These short identifiers (21 characters or compressed 128 bits) are recent inventions with their own alphabet and rules: they don't follow an RFC UUID structure (no enforced hyphens, no version field). So they cannot be "analyzed" or converted into an UUID. Our converter flags them precisely to avoid confusion: an RFC UUID always has the 8-4-4-4-12 hexadecimal form.
Why does v1 use a random node and not my MAC address?
The RFC 9562 standard explicitly recommends not using the real MAC address, because it identifies the device and violates privacy. Volade therefore replaces the node with 6 random bytes at each generation: you keep all the properties of v1 (timestamp, uniqueness) without exposing your hardware.
What is an UUID "variant"?
The variant designates how the 128 bits are interpreted, encoded in the two most significant bits of the ninth byte (the first character of the 4th group, e.g. the "a"). The value "10" corresponds to the RFC 4122/9562 format, i.e. the vast majority of UUIDs. Our validator always tells you this variant.
Can the creation date of an UUID be deduced?
Yes, for timestamped versions: the decoder displays the exact date. v1 and v6 count 100 ns intervals since 15 October 1582 (0x01B21DD213814000) and cover ~58,000 years; v7 stores the Unix timestamp in milliseconds directly. v4, on the other hand, reveals no moment.
How much real entropy does a v4 UUID provide?
Exactly 122 bits: 96 bits of random data carried over the first three groups and the last three, minus the 4 version bits and the 2 variant bits of the 128 bits. That's more than enough — delivering 122 bits of true randomness is at the heart of the trust in this identifier.
Are UUIDs really unique?
The collision probability between two v4 UUIDs is about 2⁻¹²². Generating 1 billion UUIDs per second for 86 years would still leave more than 99% chance of no collision. In practice, duplicates only occur in case of a bug (repeated seed, bad implementation) — our Batch tab detects duplicates for you.
How to store an UUID in a database?
Two options: CHAR(36) for readability (readable in logs and exports, a bit more space and compared bytes), or BINARY(16) for performance (16 bytes, more compact indexes). The "Developer" module of this tool produces ready-to-use CHAR(36) SQL scripts, and many then place an index on the column to speed up lookups.
Is an UUID suitable as a primary key?
Yes, but choose the version well. A purely random v4 fragments the B-tree index in InnoDB (scattered inserts) on very large volumes. v7, on the other hand, is timestamped: new values insert at the end of the index, reducing page moves and "page splits", which makes it the recommended choice for large tables.
Does the generator work offline?
Yes, once the page is loaded: all the logic (generation, validation, decoding, conversion, batch, export) is embedded in the browser. No byte is sent to our servers; the exposed APIs are only used for configuration. You can cut the network and keep working.
How many UUIDs can I generate for free?
Unlimited. Simple generation and batch generation (up to 10,000 per operation) are completely free, without sign-up, without quota. Only the wider Volade ecosystem (encrypted history, synchronization) is Premium.

Online UUID generator: v1 to v8, 100% local and RFC 9562 compliant

Volade's UUID generator produces universally unique identifiers directly in your browser, without sign-up and without limits. All standard versions are available: random v4 (122 cryptographically secure bits), v7 timestamped in milliseconds and ordered in time, v1 and v6 with a 100 ns clock compatible with 1582, deterministic v3/v5 via MD5/SHA-1, v8 with custom fields, plus the Nil and Max UUIDs.

Everything runs 100% locally: identifiers are created with crypto.getRandomValues() or crypto.randomUUID(), never with a predictable random function, and never leave your device. Even v1 doesn't expose your MAC address: the node is random, as recommended by the RFC.

Validate, decode and convert any UUID

The validator accepts canonical, hyphen-free, brace-wrapped or URN-prefixed formats and determines in one click the validity, version, variant (NCS, RFC, Microsoft, reserved) and the exact format entered. The decoder spells out every field: time_low, clock_seq, node, and displays the precise creation date for timestamped versions.

The converter turns an UUID into binary (128 bits), standard or URL-safe base64, a 128-bit unsigned integer, a Microsoft/GUID UUID (byte-reversed order) or a normalized canonical form — handy for interfacing with .NET (Guid), Node.js (Buffer) or SQL database systems.

For production: batch, export and SQL

Batch generation produces up to 10,000 UUIDs at once, computes statistics (total, unique, duplicates, entropy) and exports to TXT, CSV, JSON or a ready-to-run SQL script. An UUID comparator and a reference sheet of the 8 versions complete the tool. In short: the most complete UUID toolkit on the market, free, unlimited and confidential.

One premium license, all your web tools

Your Volade subscription unlocks all our web tools, plus the browser, the CMS, the desktop and the scripts — on all your devices.

Go premium See the tools
One licence, the whole premium ecosystem Browser · CMS · Desktop · Mobile · Scripts · API · Tools · Database
One licence, the whole ecosystem Go premium Log in