Timestamp (Unix) Converter

What is a Unix timestamp?

How it is calculated

A Unix timestamp counts the seconds elapsed since 1970-01-01 00:00:00 UTC. If you enter only digits (optionally with a leading minus sign or a decimal part, which is cut to the whole second), the tool reads them as seconds and formats that moment in UTC: date and time, ISO 8601 form and weekday. If you enter anything else, such as a date string, it is parsed as a date and turned into a timestamp. Text it cannot parse produces an invalid message. All output is in UTC, with no local time zone or daylight saving applied, and the tool uses seconds, not milliseconds. A millisecond value with 13 digits is more than 12 digits long and gives no result.

Worked example

Enter 1700000000. The tool treats it as 1,700,000,000 seconds after 1970-01-01 00:00:00 UTC. That is 19,675 whole days plus 22 hours 13 minutes 20 seconds. The Unix value stays 1700000000, the UTC time is 2023-11-14 22:13:20 UTC, the ISO form is 2023-11-14T22:13:20+00:00, and the weekday is Tuesday.

Try this example →

Common mistakes

  • Pasting a 13-digit millisecond timestamp from JavaScript. Divide it by 1000 first.
  • Reading the UTC output as local time. Your own zone may differ by several hours, which can even change the date.
  • Entering a date string without a time zone and assuming it is local. Check what the parser produced.
  • Expecting a number of more than 12 digits to work. Negative values (-86400 is 1969-12-31 00:00:00 UTC) and decimals such as 1700000000.5 (read as 1700000000) are accepted, but longer numbers give no result.

About this calculator

This converter moves between a Unix timestamp — the number of seconds elapsed since midnight UTC on January 1, 1970, the "epoch" — and a human-readable date, in both directions, showing the result in both UTC and ISO 8601 format. Computers store and compare dates internally as this single incrementing number precisely because it avoids time zone and calendar ambiguity; the readable date you see is just a display conversion applied to it.

Developers use it constantly when debugging APIs, log files or database records that store dates as raw timestamps, since a value like 1755561600 is meaningless to read at a glance but instantly clear once converted. It's also used to construct a specific timestamp for testing, to check when a token or session expires, or to translate a timestamp from one system's log into the local date and time it actually corresponds to.

Was this helpful?

You can pick up to 3 reactions.

Comments (1)

  • Editorial team

    Going from a date to a timestamp, state the time zone yourself, for example 2026-03-01 09:00 +03:00, because a bare date string is interpreted by the server and may not match your local clock. A quick scale check helps too: a 10-digit value is seconds, a 13-digit one is milliseconds, so divide that by 1,000 before entering it. Where does your timestamp come from, a log file, a database or an API?

Popular calculators

All Calculators