Timestamp Converter

Unix time counts the seconds since midnight UTC on 1 January 1970. 1789287420 is that many seconds later: 08:17:00 UTC on Sunday, 13 September 2026.

Because it is a single number with no time zone attached, logs, databases and APIs use it to record when something happened. Many count milliseconds instead, and some microseconds or nanoseconds, which is why the same moment turns up with 10, 13, 16 or 19 digits.

• Paste a timestamp: a Unix time in any unit, an ISO 8601 date such as 2026-09-13T08:17:00Z, or the date of an email or HTTP header such as Sun, 13 Sep 2026 08:17:00 GMT. Every other form appears at once.
• The unit of a Unix time is read from its length. If the guess is wrong, choose it under Unit, where Windows FILETIME is offered as well.
• Time zone is the zone the result is shown in, and the one a date without an offset is read in. It starts at this device's zone.
• With the field empty the page shows the time now, second by second. Now puts the current Unix time into the field.

• Unix time has no leap seconds. Every day counts exactly 86,400 seconds, so a time of 23:59:60 cannot be written as a Unix timestamp and is refused.
• A signed 32-bit Unix time runs out at 03:14:07 UTC on 19 January 2038. Later times are flagged, because older systems store them wrongly.
• A date without an offset means different moments in different places. It is read in the chosen time zone, and a local time that a clock change skips or repeats is flagged.
• A browser's calendar reaches 100,000,000 days either side of 1970. Beyond that the page says so rather than guessing.