Decode Every Timestamp-Carrying ID in a Log File
Modern logs are full of IDs, and a surprising number of them — ULIDs, UUID v7s, ObjectIds, snowflakes, KSUIDs — secretly encode the moment they were created. When timestamps in a log are missing or untrustworthy, the IDs themselves are a second clock hiding in plain sight.
- ✓Log timestamps are in three time zones and two formats, but the IDs never lie about their own order.
- ✓Decoding IDs one by one in five different single-ID tools is exactly the busywork this page removes.
- ✓You get a table: the ID, its type, its creation time in UTC and your local time, and where it appeared.
- ✓Batch mode handles multi-file drops and large pastes; results export to CSV or JSON for your report.
FAQ
Which ID formats are detected?
ULID (26-char Crockford Base32), UUID v7 and v1, MongoDB ObjectId (24-hex, toggleable), Discord/X snowflakes (17–19 digits) and KSUID (experimental). Plain UUID v4 is intentionally skipped — it contains no time.
How large a log can I paste?
Single pastes up to 20,000 characters are free. Larger pastes and multi-file batches are part of the one-time Pro unlock.
Is my log sent to a server?
Never. Scanning and decoding run in your browser with vanilla JavaScript; you can disconnect from the network and it still works.