Unix Timestamp Converter

Convert epoch seconds or milliseconds to a readable date, and back

About this tool

Unix time counts the seconds since 1 January 1970 UTC, which makes it compact and unambiguous for machines and unreadable for people. Logs, JWT claims, database columns and webhook payloads all use it, often with no clue whether the number is seconds, milliseconds or microseconds.

Paste any of them here. The tool detects the unit from the magnitude, then shows the ISO 8601 string, the UTC and local renderings, the relative distance from now and the value converted to the other units — and it runs the conversion in reverse for a date you type.

When to use it

  • Reading the exp, iat or nbf claim you just pulled out of a token
  • Working out when a log line or captured request was actually written
  • Checking whether an API returned seconds or milliseconds before you multiply by 1000
  • Converting a date into the epoch value a query parameter or filter expects

Worked example

Input

1516239022

Output

ISO 8601   2018-01-18T01:30:22.000Z
UTC        Thu, 18 Jan 2018 01:30:22 GMT
Seconds    1516239022
Millis     1516239022000

Ten digits are read as seconds and thirteen as milliseconds, so both 1516239022 and 1516239022000 resolve to the same instant.

Frequently asked questions

How do I tell seconds from milliseconds?

Count the digits. Present-day epoch seconds are 10 digits, milliseconds are 13 and microseconds are 16. This tool applies the same rule and tells you which unit it picked.

Which time zone does the readable date use?

Both. UTC is shown because that is what the epoch value means, and your browser's local time is shown next to it so you can match it against what you see in a dashboard.

What is the year 2038 problem?

Systems that store Unix time in a signed 32-bit integer overflow on 19 January 2038. Anything storing the value in 64 bits — including JavaScript, which uses a double — is unaffected.

Related tools