UUID / ULID Decoder
Paste any UUID (v1, v3, v4, v5, v6, v7, v8) or ULID to inspect its structure. Extract the creation timestamp from UUID v1/v6/v7 and ULID, see the version and variant, and view the raw hex bytes. Runs entirely in your browser — nothing is uploaded.
🔎
Paste a UUID or ULID above to decode it
How It Works
Paste a UUID or ULID
Paste any UUID (with or without hyphens, any case) or a 26-character ULID. The decoder detects the format automatically.
Review the decoded structure
See the version, variant, embedded timestamp (for v1, v6, v7, and ULID), node/MAC address, and random bits — all extracted and formatted.
Copy any field
Click the copy button next to any field to grab the canonical form, raw hex, extracted timestamp, or random component.
Frequently Asked Questions
Which UUID versions can this decoder parse?
All of them: v1 (timestamp + MAC), v3 (name-based MD5), v4 (random), v5 (name-based SHA-1), v6 (reordered v1), v7 (Unix time + random), and v8 (custom). It also recognizes the nil and max UUIDs defined in RFC 9562.
Can it extract the timestamp from a UUID v7?
Yes. UUID v7 encodes a 48-bit Unix epoch timestamp in milliseconds as its first 48 bits. The decoder pulls this out and displays it as an ISO-8601 date, Unix ms, and a relative time ("2 minutes ago").
Does it also decode ULIDs?
Yes. Paste a 26-character Crockford Base32 ULID and the decoder extracts the 48-bit millisecond timestamp from the first 10 characters and the 80-bit random component from the last 16.
Can I decode UUID v1 to see the original MAC address?
Yes. UUID v1 embeds a 48-bit node identifier, which is traditionally the MAC address of the generating machine (though many libraries now randomize it). The decoder displays it in standard colon-separated hex form alongside the timestamp and clock sequence.
Is anything sent to a server?
No. All parsing runs in your browser — the UUID or ULID never leaves your device. This is important if the identifier corresponds to a real database row or internal resource.