CONVERT FILES AND TIMES

Unix Timestamp Converter

Convert Unix timestamps in seconds, milliseconds, microseconds or nanoseconds to dates in any time zone, and dates back to epoch time.

Files stay on your device

1 Timestamp or date

Converted in your browser. Nothing is sent to a server.
THREE SMALL STEPS

How to convert a Unix timestamp to a date

  1. 01

    Enter a timestamp

    Paste a Unix timestamp or select “Use current time”. The unit is detected from the number of digits.

  2. 02

    Choose a time zone

    The date is shown in UTC and in the time zone you select, which starts as the time zone of your device.

  3. 03

    Convert a date back

    Switch to “Date to timestamp”, enter a date and time, and copy the timestamp in seconds or milliseconds.

BEFORE YOU START

Good to know

Seconds or milliseconds

Up to 11 digits are read as seconds, 12 to 14 as milliseconds, 15 to 17 as microseconds and longer numbers as nanoseconds. You can also choose the unit yourself.

Daylight saving time

When clocks go back, a local time happens twice and the earlier moment is used. A time skipped when clocks go forward is flagged.

Leap seconds are not counted

Unix time treats every day as exactly 86,400 seconds, like most operating systems and programming languages.

QUESTIONS

Frequently asked questions

How can I tell seconds from milliseconds in a Unix timestamp?

For dates near the present, seconds commonly have 10 digits and milliseconds 13. Select the unit explicitly when converting, especially for historical or far-future dates. A timestamp identifies an instant; the chosen time zone changes how that instant is displayed.

What is a Unix timestamp?

The number of seconds since 1 January 1970 at 00:00:00 UTC, also called epoch time. At a given moment, it is the same everywhere in the world.

How do I get the current timestamp in code?

In JavaScript, use Math.floor(Date.now() / 1000). In PHP, use time(). In Python, use int(time.time()).

What happens to Unix time in 2038?

Systems that store timestamps as signed 32-bit integers overflow on 19 January 2038 at 03:14:07 UTC. 64-bit timestamps, as used here, are not affected.