Unix timestamp converter

Paste a timestamp and see the date in your time zone, in UTC, and in ISO 8601, or type a date and get its timestamp. We detect the unit on our own and give you the code in your language.

—

seconds

—

milliseconds

—

By default, your device’s zone. It applies to all conversions.

10 digits are seconds, 13 milliseconds, 16 microseconds, and 19 nanoseconds. Decimals and negatives are accepted.

Paste a timestamp and you will see the date in your time zone, in UTC, in ISO 8601, and more.

Code for your project

Get the current timestamp, convert it to a date, and do the reverse. It uses the last value you converted above and the chosen zone.

Step by step

How to use it

  1. At the top you see the current timestamp, updated every second. Copy it in seconds or in milliseconds.
  2. Choose the time zone. By default it is your device’s, but you can use any from the list, such as America/New_York or UTC.
  3. In “Timestamp to date”, paste the number. We detect whether it is seconds, milliseconds, microseconds, or nanoseconds by its number of digits.
  4. In “Date to timestamp”, type the date (2023-11-14 19:13:20 or 11/14/2023 7:13:20 PM) or pick it from the calendar.
  5. For many values, use “Batch”: paste a list and download the result as CSV. “Difference” calculates the time between two dates. In “Code for your project” you copy the equivalent in JavaScript, Python, PHP, Go, Java, C#, Ruby, Bash, or SQL.
FAQ

Frequently asked questions

What is a Unix timestamp?

It is the number of seconds that have passed since January 1, 1970 at 00:00:00 UTC, the “Unix epoch”. It does not depend on the time zone: the same number is the same instant all over the world. What changes is how the date is displayed.

How do I know if my timestamp is in seconds or milliseconds?

Count the digits: 10 are seconds (1700000000), 13 are milliseconds (1700000000000), 16 are microseconds, and 19 are nanoseconds. JavaScript and Java use milliseconds; Unix, Python, and PHP usually use seconds. If the detection is not what you expect, choose the unit by hand.

What is the year 2038 problem?

A signed 32-bit integer only goes up to 2147483647, which is January 19, 2038 at 03:14:07 UTC. One second later it overflows and wraps around to a date in 1901 on older systems. 64-bit systems do not have that limit. You can try it with 2147483648.

Why does my date look different from another program’s?

Almost always it is the time zone. The timestamp is the same, but one program shows it in UTC and another in local time. Here you can change the zone and see both at once: the time in the chosen zone and the UTC time.

Can a negative timestamp be converted?

Yes. Negative values are dates before 1970: -1 is December 31, 1969 at 23:59:59 UTC. The browser supports dates between the years -271821 and 275760.

What happens with times that do not exist or repeat because of daylight saving time?

When converting a date to a timestamp we warn you. If the time does not exist in that zone (because the clock moved forward), we use the instant after the jump. If it repeats (when the clock moves back), we use the first occurrence. To avoid doubt, write the date with its offset, for example 2024-11-03T01:30:00-04:00.

How to read a timestamp

The timestamp 1700000000 is November 14, 2023 at 22:13:20 UTC, or 5:13:20 PM in New York (UTC−05:00). In milliseconds it is 1700000000000. Systems store the number because it is short, sortable, and does not depend on any time zone.

Reference values

  • 0 is January 1, 1970 at 00:00:00 UTC.
  • -1 is December 31, 1969 at 23:59:59 UTC.
  • 2147483647 is the last second that fits in a signed 32-bit integer (January 19, 2038).

Timestamps in your programming language

The “Code for your project” panel generates the program to get the current timestamp, convert a timestamp to a date, and convert a date to a timestamp in JavaScript, Python, PHP, Go, Java, C#, Ruby, Bash, MySQL, PostgreSQL, and SQLite, using the last value you converted and the zone you chose. Remember that JavaScript and Java work in milliseconds, while Python, PHP, and Unix use seconds.

Date formats used on the web

  • ISO 8601: 2023-11-14T22:13:20Z, sortable and unambiguous.
  • RFC 2822: Tue, 14 Nov 2023 22:13:20 +0000, the one used by emails and HTTP headers.

Updated on September 29, 2026