UUID Validator & Decoder

Paste a UUID or GUID to check it and see what is inside: version, variant, timestamp and more.

Accepts hyphenated, 32 hex digits, {braces}, urn:uuid:, any case. Try a fresh v7.

Valid 1ce58b51-1e2e-4682-8044-76a855e8feed

Version 4 Random
1ce58b511e2e random_a
4 ver
682 random_b
804476a855e8feed var + random_c
Version4 Random
VariantRFC 9562 (formerly RFC 4122 / DCE 1.1) (bits 10)

Version 4 UUIDs carry 122 random bits and no other information. There is no timestamp to recover.

Formats

Standard (lowercase) 1ce58b51-1e2e-4682-8044-76a855e8feed
Uppercase 1CE58B51-1E2E-4682-8044-76A855E8FEED
Microsoft GUID (braces) {1CE58B51-1E2E-4682-8044-76A855E8FEED}
URN urn:uuid:1ce58b51-1e2e-4682-8044-76a855e8feed
32 hex digits 1ce58b511e2e4682804476a855e8feed
Base64 (RFC byte order) HOWLUR4uRoKARHaoVej+7Q==
128-bit integer (decimal) 38410245544338685061156153354055384813
.NET Guid.ToByteArray() (hex) 518be51c2e1e8246804476a855e8feed
.NET Guid bytes (Base64) UYvlHC4egkaARHaoVej+7Q==

API: /api/decode/1ce58b51-1e2e-4682-8044-76a855e8feed

How to decode a UUID

Every RFC 9562 UUID stores its version in the 13th hex digit and its variant in the top bits of the 17th digit:

xxxxxxxx-xxxx-Mxxx-Nxxx-xxxxxxxxxxxx
             M = version (1-8)   N = variant (8, 9, a, b = RFC 9562)
Version digitMeaningContains a timestamp?
1Gregorian time-basedYes (100 ns since 1582)
2DCE SecurityPartial
3Name-based, MD5No
4RandomNo
5Name-based, SHA-1No
6Reordered Gregorian timeYes (100 ns since 1582)
7Unix Epoch timeYes (ms since 1970)
8CustomOnly if your format has one

Variant digit

BinaryHex digitVariant
0xxx0 - 7Reserved, NCS backward compatibility
10xx8 - bRFC 9562 (the standard variant)
110xc - dReserved, Microsoft backward compatibility
111xe - fReserved for future definition

The decoder never throws on odd input: unknown versions, legacy variants and the special nil (00000000-…) and max (ffffffff-…) UUIDs all produce a readable result.

Learn more in UUID versions explained.