Free UUID Generator Online: v1, v4, v7 + Decoder, No Signup

A UUID (Universally Unique Identifier) is a 128-bit value written as 32 hexadecimal digits — something like 550e8400-e29b-41d4-a716-446655440000. It exists to solve one problem: how do separate systems create identifiers that never collide, without a central counter? Database rows, API keys, session tokens, file uploads, order numbers — whenever two machines must agree on a unique ID without talking to each other, a UUID is the standard answer. This guide explains the versions, when to use each, and how to generate them free without signing up.

What is a UUID, exactly?

The 128 bits are grouped into five hyphen-separated blocks: 8-4-4-4-12 hex digits. A few of those bits are reserved — the version field says which generation scheme produced the ID (1, 4, 7…), and the variant field marks it as an RFC 9562 UUID. The remaining ~122 bits carry the payload: a timestamp, a machine identifier, randomness, or a combination, depending on the version.

The current standard is RFC 9562, published in May 2024, which retired the old RFC 4122 and officially standardized UUID v7. Microsoft's GUID is the same 128-bit format under a different name — anything that parses a GUID parses a UUID, and vice versa. The practical takeaway: “UUID” and “GUID” are interchangeable labels for one format.

UUID versions: v1 vs v4 vs v7 — which should you use?

The version digit (the first character of the third block) tells you how the ID was built. Here is what each one actually does:

v7 is the right default for new work in 2026. Because the timestamp leads the ID, v7 values sort in creation order — a database B-tree index stays compact and inserts stay fast, instead of scattering randomly across the index the way v4 does. Major frameworks and databases have been adopting v7 since RFC 9562 landed, and for primary keys it is strictly better than both predecessors. Reach for v4 only when you specifically want no timestamp embedded in the ID (public-facing tokens, for example). v1's day is over: it was designed before anyone worried that broadcasting your network card's MAC address in every database key was a bad idea.

How to generate a UUID in four steps

1. Pick the version. v7 for database keys and anything time-ordered, v4 for random tokens, v1 only if a legacy system demands it.
2. Set the count. One for a quick key, or hundreds at once for test data, fixtures, or coupon codes.
3. Generate. The IDs are produced on your device with the browser's cryptographic random source — nothing travels over the network.
4. Copy or download. Grab them from the list or download as a text file, ready to paste into code, SQL, or a spreadsheet.

Try it now with ToolsOfWeb's free UUID generator — v1, v4, and v7, bulk generation, a built-in decoder, no account, no upload.

What does the UUID decoder tell you?

Paste any UUID into the decoder and it breaks the 128 bits back into their meaning: the version and variant fields, the timestamp rendered as a human date (for v1 and v7), the node or MAC address (v1), and the random section. It is the fastest way to answer “what is this ID?” — debugging a foreign key, checking whether an ID you received is v4 or v7, or confirming that a token someone handed you isn't secretly a v1 leaking their server's MAC address.

Generate UUIDs in code: Python, JavaScript, Java

Every mainstream language ships UUID generation in its standard library — no package to install:

import uuid
print(uuid.uuid4())   # random v4
print(uuid.uuid7())   # time-ordered v7 (Python 3.14+)

crypto.randomUUID(); // v4, e.g. "3f6d9a1c-…"

import java.util.UUID;
UUID id = UUID.randomUUID(); // v4

Note that crypto.randomUUID() and UUID.randomUUID() produce v4. For v7 in code, use a dedicated library (or upgrade to a runtime that supports it) — or just generate what you need in the browser tool above.

Three gotchas worth knowing

v1 leaks your MAC address. Every v1 UUID embeds the generating machine's network hardware address plus the exact creation time. Publishing v1 IDs in URLs or APIs hands out both pieces of information for free. If you inherit a system using v1, treat those IDs as mildly sensitive.

v7 timestamps are visible too. The millisecond timestamp is a feature for sorting, but anyone holding a v7 ID can read exactly when it was created. Fine for order numbers and event logs — think twice before using v7 for things where creation time should stay private.

Uppercase IDs cause phantom duplicates. The spec says hex is case-insensitive, but string equality in code and some database collations is not. One service storing 550E8400… and another storing 550e8400… will disagree about whether the row exists. Standardize on lowercase everywhere and normalize on input.

FAQs

For more free utilities, see ToolsOfWeb's JSON Formatter and JWT Decoder.