Seconds vs milliseconds
Classic Unix time is seconds since 1970-01-01 UTC (about 10 digits today). Many APIs and JavaScript Date values use milliseconds (13 digits). This tool detects both.
Tool
Convert Unix epoch timestamps to human dates and back, instantly, in any timezone.
10 digits = seconds · 13 digits = milliseconds
Interpreted in your selected timezone above
Convert Unix epoch timestamps to human dates and back, in any timezone, instantly and privately.
Logs, APIs, and JWTs often store time as seconds or milliseconds since 1970-01-01 UTC. Tokitool’s Unix Timestamp Converter turns those numbers into readable dates (and the reverse) with IANA timezone display so you can sanity-check “what local time was that?” without sending values to a remote converter.
Classic Unix time is about 10 digits today (seconds). JavaScript Date.now() style values are often 13 digits (milliseconds). If you paste a 13-digit value and get a date in the year 50,000, you treated milliseconds as seconds. This tool detects both, but double-check the unit when a log line is ambiguous.
exp/iat, and server logs.When timestamps sit inside JSON, format the payload first with the JSON Formatter, then convert the fields you care about. Everything stays in the tab.
Classic Unix time is seconds since 1970-01-01 UTC (about 10 digits today). Many APIs and JavaScript Date values use milliseconds (13 digits). This tool detects both.
Pick any IANA timezone to display the human-readable side. The underlying epoch value is still absolute UTC-based time, only the presentation changes.
Conversion runs locally. Nothing you type is logged or uploaded, which matters when timestamps appear in logs, tokens, or forensic notes.
1970-01-01 00:00:00 UTC. Negative timestamps are before that instant; not all systems support them equally.
ISO 8601 is a standard machine-friendly string. Locale display follows the timezone you pick for human reading.