Timestamp Converter converts between Unix epoch time (seconds or milliseconds), ISO 8601 and a readable date and time in UTC and in your browser's local time zone, in either direction. Up to 10 digits is read as seconds, 11 to 13 as milliseconds; leave the field empty for the current time.
How to read the result
The result shows the same instant in every format side by side, plus a relative description ('3 hours ago') for quick sanity-checking against the current time.
Defender tips
- Store and log timestamps in UTC everywhere in a system, and only convert to a local time zone at the point of display; mixed time zones in logs are a frequent source of confusion during an incident.
- Watch for second-versus-millisecond epoch confusion at API boundaries; a value that looks like a date decades away is almost always the wrong unit, not an actual data error.
FAQ
What is the Year 2038 problem?
Signed 32-bit Unix time overflows in January 2038; systems still using a 32-bit signed integer for epoch seconds will wrap to a negative value at that point. 64-bit systems and this tool are unaffected.
Can it handle timestamps before 1970?
Yes, as a negative epoch value, which is valid and represents a date before the Unix epoch.
Does it account for daylight saving time?
The local time uses your browser's time zone rules, including any daylight-saving change for that date. The UTC and ISO 8601 values have no daylight saving. The tool does not convert to other named time zones.