UUID Inspector

Read the version, variant, and timestamp behavior of an existing UUID or GUID

Note: This inspector reads the UUID structure only. A valid version nibble does not prove that an upstream system used the identifier correctly.

Inspect an existing UUID or GUIDPaste a UUID, confirm the canonical shape, read the version and variant, and decode the timestamp when the layout actually carries time data

The page accepts lowercase, uppercase, braces, and urn:uuid: prefixes, then normalizes the UUID before inspection.

UUID or GUID input

Normalized UUID

What It Shows

The page normalizes the UUID, reads the version nibble and variant bits, and decodes the timestamp only for layouts that actually carry one. That makes it easier to tell whether you are looking at a random UUID, a legacy time-based UUID, or a newer sortable layout like UUID v7.

Inspect an Existing UUID

Paste the UUID exactly as you received it from a log, API payload, or database row.
Click Inspect UUID to normalize the shape and read the version and variant.
Review the timestamp panel only when the version actually carries time data.
Use the related generators when you decide you need a different identifier layout.

Timestamp-Bearing Versions

UUID v1 and v6 carry a Gregorian timestamp derived from the older UUID epoch. UUID v7 carries a Unix millisecond timestamp. UUID v4 does not expose a timestamp and is effectively random.

FAQ

Does a valid UUID shape mean the upstream system is correct?

No. It only means the string matches a known UUID layout. It does not prove application semantics.

Why decode timestamps at all?

Because time-bearing UUIDs often show up in logs and database keys, and the embedded time helps explain ordering behavior.

What if I need a sortable ID but not a UUID?

Compare UUID v7 with ULID. Both are sortable, but ULID uses a different text alphabet and is not a UUID.