Unix Timestamp Converter
Convert Unix epoch timestamps (seconds or milliseconds) to readable dates in UTC and your local time, or convert a date back to a timestamp.
Convert Unix epoch timestamps (seconds or milliseconds) to readable dates in UTC and your local time, or convert a date back to a timestamp.
A Unix timestamp counts the seconds since 1 January 1970 UTC. Developers meet them in logs, databases and APIs.
Paste a timestamp in seconds or milliseconds, or a date string, and see it as Unix seconds and milliseconds, UTC (ISO 8601), your local time and a relative description.
1700000000 = 2023-11-14T22:13:20.000Z
Unix time counts elapsed seconds since 00:00:00 UTC on 1 January 1970, the epoch, and deliberately ignores leap seconds, so every day is exactly 86,400 seconds. Many systems store the same moment in different units: seconds in most databases and JWT claims, milliseconds in JavaScript and Java, and sometimes microseconds or nanoseconds elsewhere. This tool guesses the unit by magnitude, treating values with an absolute value below 100 billion as seconds, which covers dates up to the year 5138.
Timestamps themselves carry no time zone. The zone only appears when you format them, which is why the tool shows the UTC value in ISO 8601 form with a trailing Z next to your browser local time. A common mistake is passing a local date string without an offset and assuming it is UTC; the browser parser interprets such strings in local time. Signed 32-bit systems overflow at 03:14:07 UTC on 19 January 2038, a limit that does not apply to JavaScript dates.
Numbers with an absolute value under 100 billion are treated as seconds, larger numbers as milliseconds.
The time zone set in your browser, shown next to the label.
ISO 8601 such as 2024-05-01T10:30:00Z works best. Other formats depend on your browser's date parser.
No. It runs in your browser.
No. Unix time treats each day as exactly 86,400 seconds, so leap seconds are absorbed rather than counted. This keeps arithmetic simple but means it can differ slightly from atomic time.
Yes. Dates before the epoch are represented as negative numbers, and the tool accepts them. Very large values outside the JavaScript date range of about 8.64 quadrillion milliseconds report an out-of-range error.