Unix Timestamp Converter (Epoch ↔ Date)

Enter a timestamp to see it as a date in your local time and in UTC, or enter a date to get its timestamp. The tool tells 10-digit (seconds) and 13-digit (milliseconds) values apart on its own.

Current Unix timestamp (seconds)
-
Milliseconds: -

Timestamp → Date

Unit

Date → Timestamp

Seconds (10 digits)
-
Milliseconds (13 digits)
-

How to use the Unix Timestamp Converter

  1. The current Unix timestamp updates live at the top of the page. Copy it in seconds or milliseconds with one click.
  2. Type a number in Timestamp → Date to see it in your device's local time, in UTC, in ISO 8601 format, and as a relative time such as "3 d ago".
  3. The unit is picked from the number of digits, but you can choose Seconds or Milliseconds yourself if you need to.
  4. In Date → Timestamp, pick a date, a time and a time zone (your device's zone or UTC) to get the value in seconds and in milliseconds.

What is a Unix timestamp (epoch time)?

A Unix timestamp is the number of seconds since 00:00:00 UTC on January 1, 1970, a moment known as the Unix epoch. It is the same number everywhere in the world, whatever the time zone, so server logs, databases and API responses use it to store dates.

  • 0 → 1970-01-01 00:00:00 UTC
  • 1,000,000,000 → 2001-09-09 01:46:40 UTC
  • 1,700,000,000 → 2023-11-14 22:13:20 UTC

Because the value carries no time zone, the same timestamp shows a different clock time depending on where you are. For example, 1,700,000,000 is 5:13:20 PM on November 14, 2023 in New York (EST) and 9:13:20 AM on November 15 in Sydney (AEDT).

10-digit vs. 13-digit timestamps

A 10-digit number counts seconds. A 13-digit number counts milliseconds (thousandths of a second). Linux, PHP and Python's time functions usually give seconds, while JavaScript's Date.now() and Java's System.currentTimeMillis() give milliseconds. Divide a millisecond value by 1,000 to get seconds.

EnvironmentGet the current timestampUnit
JavaScriptDate.now()Milliseconds
Pythontime.time()Seconds (decimal)
JavaSystem.currentTimeMillis()Milliseconds
Linux shelldate +%sSeconds
MySQLUNIX_TIMESTAMP()Seconds

Converting a timestamp to your local time

A timestamp always counts from UTC. To get local time, add or subtract your UTC offset. For example, Eastern Standard Time is UTC−5, British Summer Time is UTC+1 and Australian Eastern Standard Time is UTC+10. Offsets change when daylight saving time starts or ends, and this converter applies your device's daylight saving rules for you. The result is labeled with the offset that applies on that date.

In Excel or Google Sheets, =(A1/86400)+DATE(1970,1,1) turns a timestamp in seconds into a UTC date: divide by the number of seconds in a day (86,400), then add January 1, 1970. Format the cell as a date and time. To shift it to a fixed offset, add hours as a fraction of a day, for example -5/24 for EST or +10/24 for AEST. Spreadsheets don't adjust for daylight saving automatically.

What is the Year 2038 problem?

Older systems that store timestamps as signed 32-bit integers top out at 2,147,483,647, which is 03:14:07 UTC on January 19, 2038. One second later the value overflows to a negative number and the date jumps back to December 1901. This is called the Year 2038 problem. Modern operating systems and programming languages use 64-bit integers, so they aren't affected.

Frequently asked questions

How do I tell if a timestamp is in seconds or milliseconds?
For current dates, a 10-digit value is in seconds and a 13-digit value is in milliseconds. In Auto mode, this converter treats any value of 100 billion or more as milliseconds.
Why is my converted time off by a few hours?
The time was probably read as UTC in one place and as local time in another. The gap equals your UTC offset, for example 5 hours in New York in winter or 1 hour in London in summer.
Can I convert dates before 1970?
Yes. Dates before 1970 have negative timestamps. For example, -86400 is 00:00 UTC on December 31, 1969.
Does Unix time include leap seconds?
No. By definition, Unix time ignores leap seconds, so this converter treats every day as exactly 86,400 seconds.
Does daylight saving time affect the result?
The timestamp itself doesn't change. Only the local clock time shown for it does. The converter applies your device's daylight saving rules for each date, and the UTC result is never affected.

Last updated: 2026-11-21