Skip to content
codevory

Unix Timestamp Converter

Convert Unix timestamps to dates and dates to timestamps. Seconds, milliseconds, microseconds and nanoseconds are detected, and the current Unix time is always shown.

Unix Timestamp Converter: the tool

Dates without an offset are read on the clock of this time zone.

Current Unix time

Seconds
…
Milliseconds
…
ISO 8601
…

Timestamp to date

Enter a timestamp to see the date.

Date to timestamp

Enter a date such as 2024-05-02 13:45:00 or 2024-05-02T13:45:00+02:00.

How to use Unix Timestamp

  1. To convert a timestamp, type it in the first box. The unit (seconds, milliseconds, microseconds or nanoseconds) is detected from its size, and you can force one with the unit menu.
  2. You get the date in UTC and in the time zone you selected, a readable form and how long ago or from now it is.
  3. To convert a date, type it in the second box, for example 2024-05-02 13:45:00. A date without an offset is read on the clock of the selected time zone.
  4. Press Now in either box to fill in the current time. The top card always shows the current Unix time in seconds and milliseconds.

Example

The same moment as a timestamp in seconds and as a date, and the famous 32-bit limit.

1714657530 read as seconds
UTC         2024-05-02T13:45:30.000Z
Paris       2024-05-02T15:45:30.000+02:00
New York    2024-05-02T09:45:30.000-04:00
2024-05-02 13:45:30 UTC as a timestamp
Seconds       1714657530
Milliseconds  1714657530000
2147483647, the largest signed 32-bit value
2038-01-19T03:14:07.000Z

About this tool

A Unix timestamp counts the time elapsed since 00:00:00 UTC on 1 January 1970, the Unix epoch, not counting leap seconds. It does not contain a time zone: the same number means the same instant everywhere, and the time zone only matters when you display it as a calendar date.

Systems count in different units. Unix and most APIs use seconds (10 digits today), JavaScript and Java use milliseconds (13 digits), and some databases and tracing tools use microseconds or nanoseconds. The tool guesses the unit from the size of the number: below 10^11 it is seconds, below 10^14 milliseconds, below 10^17 microseconds, otherwise nanoseconds. If a value is read wrongly, choose the unit yourself.

The supported range is the years 0001 to 9999, and a value outside it is reported instead of giving a wrong date. Negative timestamps are dates before 1970. Time zone rules, including daylight saving time, come from your browser's copy of the IANA time zone database.

How the unit is detected

Size of the numberRead asTypical digits today
Below 100 billion (10^11)Seconds10
Below 100 trillion (10^14)Milliseconds13
Below 10^17Microseconds16
10^17 and aboveNanoseconds19

Frequently asked questions

What is a Unix timestamp?

The number of seconds since 1 January 1970 at 00:00:00 UTC. It is a simple, time-zone-free way to store an instant, which is why databases, logs and APIs use it.

Is a timestamp in seconds or milliseconds?

Both exist. A 10-digit value is almost certainly seconds and a 13-digit one is milliseconds. The tool detects this and says which unit it used, and you can override it.

What is the year 2038 problem?

Systems that store the timestamp in a signed 32-bit integer run out at 2147483647, which is 19 January 2038 at 03:14:07 UTC, and wrap to a date in 1901. Modern systems use 64 bits and are not affected.

Does a timestamp depend on the time zone?

No. It always refers to UTC. The time zone only changes how the date is written, which is why the converter shows the same instant in UTC and in your selected zone.

Does the converter handle leap seconds?

Unix time ignores them: every day has exactly 86,400 seconds. The tool follows that convention, so a time such as 23:59:60 is rejected as invalid.

Are the dates sent to a server?

No. Conversion uses only your browser, and nothing is uploaded.