Unix Timestamp Converter
Paste epoch seconds or milliseconds to see the date in UTC, in ISO 8601 and in your local zone - or type a date to get the timestamp back. The current time is shown live.
Seconds or milliseconds, detected automatically
A ten-digit number is seconds, thirteen digits is milliseconds, and sixteen is microseconds. The converter picks the right unit by magnitude, and you can override it when a value is ambiguous. Getting this wrong is the classic cause of dates landing in 1970 or in the year 54000.
Every representation at once
One conversion gives you the ISO 8601 string, UTC, your local time with its offset, the RFC 2822 form used in HTTP headers, and both the second and millisecond timestamps. A relative reading such as "3 days ago" makes it obvious when a value is stale.
Time zones and why they bite
A Unix timestamp has no time zone: it counts seconds since 1970-01-01 UTC, and the same number is the same instant everywhere. The zone only matters when rendering it. This tool shows UTC and your device's local zone side by side, which is usually enough to spot an off-by-nine-hours bug.
Frequently asked questions
Is anything sent to a server?
No. Nothing you paste leaves your browser. The page loads a small amount of JavaScript, and every calculation happens on your own machine - there is no server to send data to. The conversions are pure arithmetic done in your browser, and the "current time" comes from your own device clock.
Why did my timestamp convert to 1970?
A millisecond value was interpreted as seconds, or the number was truncated. 1970-01-01 is the epoch itself, so tiny values land there. Set the unit explicitly to milliseconds and try again.
What is the year 2038 problem?
Systems that store the timestamp in a signed 32-bit integer overflow on 19 January 2038, wrapping to 1901. Modern platforms use 64 bits and are unaffected, but old embedded systems, some database columns and legacy file formats still carry the limit.
Does a Unix timestamp include leap seconds?
No. Unix time deliberately ignores leap seconds - every day counts as exactly 86,400 seconds. That keeps the arithmetic simple but means Unix time is not a continuous count of physical seconds since 1970.