How it works
Unix time counts the seconds since 1 January 1970 at 00:00:00 UTC, called the epoch. It ignores time zones and leap seconds, so one number means the same instant everywhere. To show it as a date, the tool adds the seconds to the epoch and formats the result in UTC, as ISO 8601, and in your device time zone.
Some systems count milliseconds instead (JavaScript, Java) or microseconds and nanoseconds. The tool guesses the unit from the size of the number: below 100,000,000,000 it reads seconds (up to the year 5138), below 100,000,000,000,000 milliseconds, below 100,000,000,000,000,000 microseconds, and anything bigger nanoseconds. A 10-digit number is seconds and a 13-digit number is milliseconds. You can choose the unit yourself if the guess is wrong, for example for a millisecond value from before March 1973.
The second panel turns a date and time into a timestamp, read as UTC or in your device time zone. The third panel shows the current time as a timestamp. The relative line ("2 years ago") compares with the clock on your device.
Many older systems store the timestamp in a signed 32-bit integer. Its largest value, 2,147,483,647, is 19 January 2038 at 03:14:07 UTC. One second later it overflows to a negative number, which is the year 2038 problem. Modern 64-bit systems are not affected.
Check it by hand: 1,700,000,000 seconds divided by 86,400 seconds in a day is 19,675 whole days, with 80,000 seconds left over. 19,675 days after 1 January 1970 is 14 November 2023. The 80,000 seconds are 22 hours (79,200) and 800 seconds, which is 13 minutes 20 seconds, so the time is 22:13:20 UTC.
Date (UTC) = 1970-01-01 00:00:00 + timestamp seconds Milliseconds = seconds × 1,000 Timestamp = (date and time in UTC − 1970-01-01 00:00:00 UTC) in seconds Signed 32-bit limit = 2^31 − 1 = 2,147,483,647
Worked example
1700000000 seconds after the epoch is 2023-11-14T22:13:20Z, a Tuesday. The same instant in milliseconds is 1700000000000. The date 2026-10-14 00:00:00 UTC is 1791936000.
The 32-bit limit 2147483647 is 2038-01-19T03:14:07Z, and the unsigned 32-bit limit 4294967295 is 2106-02-07T06:28:15Z.
Good to know
- Unix time ignores leap seconds, so it is not a count of every physical second. For nearly all software this does not matter.
- Auto-detection is a guess from the size of the number. Millisecond stamps before March 1973 and second stamps after the year 5138 look like other units. Pick the unit by hand for those.
- Local time uses the time zone of your device and its current rules, including daylight saving. Old dates use today's rules for your zone, as browsers do.
- The relative text and the current time come from your device clock. If that clock is wrong, so are they.
- Dates must fall within the range JavaScript supports, about 270,000 years either side of 1970.
Questions people ask
How do I convert a Unix timestamp to a date?
Paste the number in the first panel. A 10-digit number is read as seconds, a 13-digit number as milliseconds. The date appears in UTC, ISO 8601 and your local time.
How do I tell if a timestamp is in seconds or milliseconds?
By length. Seconds are 10 digits for dates between 2001 and 2286, milliseconds are 13 digits for the same dates. This tool uses the size of the number to decide and lets you override it.
What is epoch time?
It is the count of seconds since 1 January 1970 00:00:00 UTC, the Unix epoch. A timestamp of 0 is that moment, and negative numbers are dates before it.
What is the year 2038 problem?
Systems that store Unix time in a signed 32-bit integer run out after 03:14:07 UTC on 19 January 2038 (2147483647 seconds). The next second wraps to a negative number and a date in 1901. 64-bit systems do not have this limit.
How do I get the current Unix timestamp?
Use the Current timestamp panel here, or type now in the first panel. In code, JavaScript uses Math.floor(Date.now() / 1000), Python uses int(time.time()) and Linux shells use date +%s.
Does a Unix timestamp have a time zone?
No. It counts from an instant in UTC, so it is the same everywhere. A time zone only matters when you show it as a calendar date or turn a local date into a timestamp.
Is 1700000000000 seconds or milliseconds?
It has 13 digits, so it is milliseconds. Divide by 1,000 and you get 1,700,000,000 seconds, the same moment: 14 November 2023, 22:13:20 UTC.
Part of the guide: Date calculators: days between dates, days until, age and weeks, Developer and design tools: QR codes, passwords, JSON, colors and timestamps