Paste epoch seconds/ms from JSON and convert them to a human-readable date instantly.
Find when a record was created from a Discord Snowflake or a MongoDB ObjectId.
Detect every timestamp in a pasted log at once and read it in your local time.
Add or subtract from a base time to check cache expiry or token expiration.
Conversion, decoding, and parsing all run inside your browser (client-side). The IDs, logs, and dates you enter are never sent to or stored on a server, so even sensitive internal logs are safe to use.
By digit count. Roughly, up to 11 digits is treated as seconds, 12–13 as milliseconds, 14–16 as microseconds, and 17+ as nanoseconds. All are normalized to milliseconds internally for display.
A Snowflake ID stores milliseconds elapsed since a base time (epoch) in its high bits, but that base differs by issuer. Twitter/X uses 2010-11-04, Discord uses 2015-01-01. Pick the epoch that matches the issuer to get the correct time.
No. Only UUIDv7 (milliseconds) and UUIDv1 (100 ns, 1582 epoch) embed a timestamp. Random versions such as v4 carry no time information, and the tool says so.
No. All processing happens inside your browser, and the IDs and logs you enter are never sent anywhere. Only settings (time zone, theme) are stored locally; the IDs and logs themselves are never saved.