UUID v7 Timestamp Decoder
UUID v7 was designed to be sortable, and the trick is simple: its first 48 bits are the creation time in Unix milliseconds. If your system has moved from v4 to v7, every ID you log now doubles as a timestamp — you just need a decoder that pulls it out.
- ✓You see a UUID in a log and want to know if it is one of the new v7 ones — and when it was made.
- ✓Random-looking v4 UUIDs carry no time at all, so a decoder must tell v4 and v7 apart instead of guessing.
- ✓Correlating events across services is much easier once each v7 ID reveals its own creation time.
- ✓Our tool flags v7 (and v1) UUIDs inside any pasted text and ignores v4, so results stay noise-free.
FAQ
Where is the timestamp in a UUID v7?
In the first 48 bits — the first 12 hex characters before the version nibble. Interpreted as a big-endian integer, it is the number of milliseconds since 1970-01-01 UTC.
Can you decode a UUID v4 the same way?
No. A v4 UUID is random; there is no time hidden in it. Any tool that shows a 'date' for a v4 is making it up — ours labels v4 as carrying no timestamp and leaves it out of the results.
What about UUID v1?
v1 also embeds a timestamp (in 100-nanosecond intervals since 1582). The extractor decodes v1 as well and labels it clearly.