Unix Timestamp Converter

Convert a Unix timestamp (seconds or milliseconds) to a readable date in your local time zone, UTC and ISO 8601, or turn a date into a timestamp. Seconds and milliseconds are detected automatically from the number of digits.

Current Unix timestamp

โ€”seconds
โ€”milliseconds (ms)

Timestamp โ†’ date

โ€”

Date โ†’ timestamp

โ€”Seconds
โ€”Milliseconds

iPhone app ยท Free to downloadGIF Keyboard & Search - GIFFFFind, save and share GIFs in seconds.View on the App Store

About the Unix Timestamp Converter

A Unix timestamp (Unix time, epoch time, POSIX time) is the number of seconds that have passed since January 1, 1970 at 00:00:00 UTC. Because it is the same everywhere in the world regardless of time zone, it is the de facto standard for storing points in time in databases, logs and APIs.

JavaScriptโ€™s Date.now() and Javaโ€™s System.currentTimeMillis() return milliseconds (13 digits), while Linux date +%s, PHP time() and Python int(time.time()) return seconds (10 digits). This converter picks the unit from the number of digits.

How to use

  1. The current timestamp is shown at the top; tap Copy to copy it.
  2. Paste a number into Timestamp โ†’ date to see the date in your local time zone, in UTC, in ISO 8601 format and how long ago (or from now) it is.
  3. If the unit is detected wrongly, pick Seconds / Milliseconds / Microseconds yourself.
  4. In Date โ†’ timestamp, choose a date, time and time zone, or paste a date string, to get the value in seconds and milliseconds.

Worked examples

Read a 10-digit number from a log

Input
1700000000
Result
UTC 2023-11-14 22:13:20 ยท ISO 8601 2023-11-14T22:13:20Z
The headline shows it in your time zone, e.g. Tuesday, November 14, 2023 at 5:13:20 PM in New York (2023-11-14T17:13:20-05:00).

The 13-digit 1700000000000 gives the same moment because the tool detects milliseconds by length. A reader in Sydney or London sees a different local line, but the UTC row is identical everywhere.

Midnight on New Year's Day as a timestamp

Input
Date string 2026-01-01 00:00, time zone: your device (New York)
Result
1767243600 (ms 1767243600000)
2026-01-01T05:00:00Z

Choose UTC as the time zone and the same text gives 1767225600, five hours earlier. Writing an offset, as in 2026-03-15T14:30:00Z โ†’ 1773585000, overrides the selected zone, which is the safest way to share a moment across teams.

An impossible date and the 32-bit limit

Input
2026-02-30 10:00 / timestamp 2147483647
Result
Couldnโ€™t read that date.
2147483647 โ†’ UTC 2038-01-19 03:14:07

February 30 is rejected rather than silently rolled over to March 2. 2147483647 is the largest signed 32-bit integer; anything that stores time in 32 bits overflows one second later.

Telling units apart by the number of digits

UnitDigits (today)Example
Seconds101790812800
Milliseconds131790812800000
Microseconds161790812800000000
Nanoseconds191790812800000000000

All the examples above are October 1, 2026, 00:00:00 UTC.

The year 2038 problem

Older systems that store timestamps as signed 32-bit integers overflow at 03:14:07 UTC on January 19, 2038, when the value passes 2,147,483,647, and jump back to 1901. Systems that use 64-bit integers or milliseconds donโ€™t have this problem.

FAQ

Does a timestamp have a time zone?

No. A timestamp is an absolute moment counted in UTC, so it has the same value in New York and London at the same instant. A time zone only matters when you display it as a date.

Can timestamps be negative?

Yes. Dates before 1970 are negative. For example, -86400 is December 31, 1969 at 00:00 UTC.

Which date formats can I paste?

ISO 8601 (2026-10-01T09:00:00Z or with an offset such as -05:00), 2026-10-01 09:00:00, 2026/10/01 09:00 and most formats your browser understands. Without an offset, the selected time zone is used.

Are leap seconds counted?

No. By definition Unix time ignores leap seconds, so every day is exactly 86,400 seconds. Almost all operating systems and programming languages work the same way.

How do I convert a timestamp in Excel or Google Sheets?

Spreadsheet dates count days, so divide seconds by 86,400 and add the epoch: =A1/86400+DATE(1970,1,1) gives the UTC date and time (format the cell as date-time). For milliseconds use =A1/86400000+DATE(1970,1,1). Add or subtract your UTC offset in hours divided by 24 for local time, and check the result against this tool's UTC row.