What Does a UUID Decoder Do?
Paste any UUID to instantly decode its version, variant, timestamp, and fields. This free online UUID decoder extracts creation time from time-based UUIDs.
A UUID decoder reads the 128-bit value and interprets it according to its version:
- Format - checks 8-4-4-4-12 structure and RFC compliance
- Version - detects v1, v3, v4, v5, v6, v7, v8
- Variant - validates RFC 9562 / RFC 4122 variant
- Timestamp - extracts Unix time from v7, v1, v6
- Fields - shows node, clock sequence, random data, namespace
Unlike a validator that only says valid/invalid, this tool tells you what's inside the UUID and when it was created.
How to Decode a UUID Online
- Paste your UUID:
0191a2b3-c4d5-7e6f-8a9b-0c1d2e3f4a5b - See instant result: version, variant, timestamp, and field breakdown
- Copy timestamp as ISO, Unix ms, or human-readable date
Works for UUID v7, v1, v6, v4, v3, v5 and GUIDs. Supports lowercase, uppercase, with or without braces.
What Information Can Be Decoded?
The data you get depends on the UUID version. Not every UUID contains a timestamp.
| UUID version | Decodable Information |
|---|---|
| UUID v7 | 48-bit Unix timestamp (ms), version, variant, rand_a, rand_b |
| UUID v1 | Timestamp (100ns Gregorian), clock sequence, node / MAC |
| UUID v6 | Reordered timestamp, version-specific fields, sortable time |
| UUID v4 | Version, variant, 122 random bits (no timestamp) |
| UUID v3 / v5 | Version, variant, namespace + name hash (deterministic) |
A decoder cannot recover data that was never encoded. UUID v4 has no creation time — store created_at separately if you need it.
UUID v7 Decoding: Extract Timestamp
UUID v7 is the most useful to decode. Its first 48 bits are a Unix timestamp in milliseconds, placed at the start for chronological sorting.
0191a2b3-c4d5-7e6f-8a9b-0c1d2e3f4a5b
^^^^^^^^^^^^
48-bit Unix timestamp
This tool converts that value to:
- UTC date/time (ISO 8601)
- Unix milliseconds
- Local time and relative time (e.g., 2 hours ago)
Note: This timestamp is the time the UUID was generated, not necessarily when a database row was committed. In distributed systems, client and server clocks can differ.
Use v7 decoding to debug event ordering, check log timelines, or verify that your database is generating v7 instead of v4.
UUID v1 and v6 Decoding
UUID v1 and v6 are also time-based but use a different layout than v7.
UUID v1 - Original time-based UUID. Contains:
- 60-bit timestamp (Gregorian epoch)
- Clock sequence
- Node ID (historically MAC address, may be random)
UUID v6 - Reordered v1 for better DB sorting. Same fields, different order for improved index locality.
If you expose v1 UUIDs publicly, you may leak creation time and node info. Prefer v4 for public IDs when privacy matters, v7 when you want sortable time without MAC exposure.
What Happens When You Decode UUID v4?
UUID v4 is intentionally opaque:
- 4 bits: version (0100)
- 2 bits: variant
- 122 bits: random data
No timestamp, no node, no sequence to extract.
A decoder will still show:
- Confirmation it's v4
- Variant (should be 8, 9, a, b for RFC compliance)
- Random portion and hex/binary representation
But it cannot tell you when it was created. For creation time, add a created_at column — don't rely on the UUID.
Example that has no hidden date:
550e8400-e29b-41d4-a716-446655440000
This is valid v4, but decoding it won't reveal a timestamp.
UUID Decoder vs UUID Validator
- Validator asks: Is this a correctly formatted UUID? Is version/variant allowed?
- Decoder asks: What version is this? Does it contain a timestamp? When was it created? What fields can I extract?
Use validator to reject bad input. Use decoder to inspect good input during debugging, SRE investigations, or database migrations.
Both tools are complementary. Validate first, then decode.
Common Uses for a UUID Decoder
- Backend engineers - inspect IDs from APIs, queues, or microservices
- SRE / DevOps - decode v7 timestamps when investigating logs
- DBAs - verify app generates expected version (v4 vs v7) and check distribution
- QA - ensure test environment generates correct UUID version
- Security - audit whether v1 UUIDs expose MAC/node info
This is a diagnostic tool — it doesn't need to run on every request.
What This Decoder Doesn't Do
A syntactically valid UUID can still be unusable. This tool does not check:
- Whether the UUID exists in your database
- Whether it is unique in your system
- Who owns the resource
- Authorization or permissions
Decoding shows what the UUID contains, not what it means in your app logic.
FAQ
Can this decoder extract timestamp from UUID v4? No. UUID v4 is 122 random bits — it has no embedded timestamp. Only time-based UUIDs (v1, v6, v7) contain a decodable creation time.
Does it support UUID v7? Yes. Fully supports v7 timestamp extraction (48-bit Unix ms), plus v1, v6, v4, v3, v5, v8. RFC 9562 compliant.
Is this also a GUID decoder? Yes. GUID and UUID use the same 128-bit format. This decodes both.
Does decoding reveal sensitive info? UUID v7 exposes approximate creation time. UUID v1 may expose node/MAC and timestamp. UUID v4 is random and does not expose time or node.
What is the difference between decoder and validator? Validator checks format and validity. Decoder interprets version, variant, timestamp, and fields inside a valid UUID.