Convert

Convert a Unix timestamp

One number in, every useful reading of it out.

A ten-digit number is read as seconds and a thirteen-digit one as milliseconds, which covers both conventions without a switch. Input it cannot read is reported as such instead of being guessed at as 1970.

Unix time counts seconds since 1 January 1970 UTC and contains no time zone at all. The ISO line and the UTC line are the same instant for everyone; the local line is that instant on this device’s clock, which is why two people can read different times off one timestamp and both be right.

Dates go through the browser’s own parser. A date without an offset — “2026-11-20” — is UTC by the ECMAScript standard, while “2026-11-20T10:00” is local. That difference surprises people, so the output always shows the UTC line and the local line next to each other.

Questions

Why does my timestamp show the wrong day?

Almost always a time zone: the instant is the same, but the local line is your zone’s clock. Compare against the UTC line.

Seconds or milliseconds?

Ten digits is seconds, thirteen is milliseconds. Both are accepted and the output shows both.

Will this keep working after 2038?

Yes. The 2038 problem belongs to 32-bit signed time in C. JavaScript dates are 64-bit and reach the year 275760.

Is anything sent?

No. The conversion is arithmetic in the tab.

More text and code