Top 3 UUID Decoder Tools Worth Using

Two systems both generate UUIDs, and one of them is producing identifiers that cluster badly in a database index. They look identical — 36 characters, four hyphens — and the difference is one nibble in the thirteenth position.

That nibble is the version, and it changes everything about the identifier’s behaviour. A v4 is random, so it scatters across an index. A v1 or v7 encodes a timestamp, so it sorts roughly by creation time — better for indexing, and a small information leak if the IDs are public. Reading it by eye is possible and error-prone, which is what these tools are for.

How to judge a UUID decoder

Which versions does it know? v1 through v5 is the old set. v6 and v7 arrived with RFC 9562, and v7 is increasingly what new systems generate.

Does it decode the timestamp? For v1 and v7 the creation time is embedded. Extracting it is genuinely useful for debugging and worth knowing about for privacy.

Does it check the variant? Version alone is not validity. The variant bits determine whether the thing is a well-formed RFC UUID at all.

Can it do a batch? One identifier is a curiosity. A column of them is an audit.

The comparison

Facts checked August 2026; tools change. Table covers only the 3 alternatives — our tool gets its own section below.

FastUUID Validator

The most complete on structure. It checks the format, decodes the version and variant bits, and recognises all standard versions — v1, v3, v4, v5, v6 and v7 — plus the special Nil and Max values that trip up naive validators. Everything is processed locally in your browser.

Its standout feature is timestamp decoding for v1 and v7, showing when the identifier was generated. That is the fastest way to confirm what you are looking at: if a timestamp comes out and it matches when the record was created, the version detection is corroborated rather than just asserted. Free, no account.

Online UUID Validator

The most forgiving about input and the best for a list. It validates structure — character set, hyphen placement, version digit, variant bits — against both RFC 4122 and the newer RFC 9562, and accepts UUIDs with or without hyphens, in any case, and in curly-brace GUID format, which saves reformatting values pulled from a .NET system.

Bulk validation is the differentiator: paste a column and check them all at once. It lists support for v1, v3, v4, v5 and v7 plus Nil, so v6 is not mentioned — rare enough that it may not matter, worth knowing if it does. All processing happens in the browser with nothing sent to a server.

APIVoid UUID Decoder

The broadest version coverage, handling v1, v3, v4, v5, v6 and v7, and returning the version, the embedded timestamp and the integer value of the UUID. The integer representation is an unusual inclusion and occasionally exactly what you need when a system stores UUIDs as 128-bit numbers rather than strings.

Free with no account. Its page does not state whether decoding happens in your browser or on their server, which for a UUID is a low-stakes question — but if the identifier is a session token or something similarly sensitive, prefer one of the explicitly client-side options.

UUID Version Detector

Ours identifies which UUID version you have, which is the specific question people arrive with — not “is this valid” but “which of these two systems generated it, and why does one of them behave differently in my index”.

What it does not do: decode the embedded timestamp for v1 and v7, or validate a column in bulk. For confirming when an identifier was created, FastUUID goes further; for auditing a list, the Online UUID Validator does. The current specification is RFC 9562, which superseded RFC 4122 and introduced v6, v7 and v8 — worth a look if you are choosing a version rather than identifying one.

Which one to pick

• Finding out when a v1 or v7 was created — FastUUID.
• Checking a whole column — Online UUID Validator’s bulk mode.
• A v6 UUID, or the integer value — APIVoid.
• A quick answer to “which version is this” — the tool below.

How to do it with UUID Version Detector

1. Open the UUID Version Detector and paste the identifier.
2. Read the version — the thirteenth hex digit, though you should not have to count.
3. If it is v1 or v7, remember the creation time is embedded and therefore public.
4. If your system is generating v4 and suffering index fragmentation, v7 is the usual answer.

The walkthrough is in how to tell which UUID version you have. Other developer tools are in the tools directory.

You might also need

The UUID Generator produces identifiers once you have decided which version you want.

For identifiers that are not UUIDs at all, the Base32 Encoder Decoder covers another format that turns up in the same places.

Frequently asked questions

How do I tell a UUID version by eye?

The first character of the third group is the version digit — ...-4a1b-... is a v4. It works, and miscounting groups is easy enough that a decoder is worth the paste.

Should I use v4 or v7?

v7 if the UUIDs are database keys, because time-ordered identifiers keep index inserts local instead of scattering them. v4 if unpredictability matters more, since a v7 leaks its creation time to anyone holding it.

Is a UUID with a timestamp a privacy problem?

It can be. v1 embeds a timestamp and historically a MAC address; v7 embeds a timestamp. If those identifiers are exposed publicly, you are publishing creation times — usually harmless, occasionally not.

Final thought

Check the version before blaming the database. Index fragmentation, unsortable keys and identifiers that leak creation times all trace back to a choice someone made once, and it takes one paste to find out which choice it was.

Try the free UUID Version Detector