Unix Timestamp Converter

  • Tested against Python's own calendar and the POSIX formula with 614 timestamps from year 1 to 9999
  • Checked by Wayne Bickerton
  • Sources: The Open Group
  • Updated November 11, 2026

A Unix timestamp, also called epoch time or POSIX time, counts the seconds since midnight Coordinated Universal Time (UTC) on January 1, 1970. Paste one to see the date and time it stands for, in UTC and in your own time zone, or enter a date and time to get the timestamp. The box starts on the current time.

UTC date and time
November 14, 2023, 22:13:20

1700000000 seconds since the Unix epoch is Tuesday, November 14, 2023, 22:13:20 UTC.

Your time zone Shown in your browser
In milliseconds 1700000000000
ISO 8601 2023-11-14T22:13:20Z

What is a Unix timestamp?

It is the number of seconds since 00:00:00 UTC on January 1, 1970, a moment called the Unix epoch. The POSIX standard defines it so that every day is exactly 86,400 seconds. Leap seconds are not counted, so a timestamp is not quite the true number of seconds that have passed.

The same moment has the same timestamp everywhere in the world; only the clock time differs by time zone. Some programs count in milliseconds instead: 1,000 times bigger, 13 digits for today’s dates. POSIX defines the count from 1970 on; dates before 1970 are negative numbers on most systems, and this converter counts them the same way.

Source The Open Group · POSIX.1-2024 Base Definitions, 4.19 Seconds Since the Epoch ↗

How to convert a Unix timestamp to a date

date = January 1, 1970 + timestamp ÷ 86,400 days

Here it is with your numbers:

  1. Whole days since January 1, 1970: 1700000000 ÷ 86,400, rounded down, = 19,675 days.
  2. Seconds left over: 1700000000 − 19,675 × 86,400 = 80,000.
  3. Day 19,675 counted from January 1, 1970 is Tuesday, November 14, 2023.
  4. 80,000 seconds is 22 h 13 min 20 s, so the time is 22:13:20 UTC.

It means 1700000000 seconds after midnight UTC on January 1, 1970, not counting leap seconds.

Unix timestamp examples

TimestampUTC (ISO 8601)Note
01970-01-01T00:00:00ZThe Unix epoch
10000000002001-09-09T01:46:40ZOne billion seconds
12345678902009-02-13T23:31:30ZThe “1234567890” moment
17000000002023-11-14T22:13:20Z1.7 billion seconds
20000000002033-05-18T03:33:20ZTwo billion seconds
21474836472038-01-19T03:14:07ZThe year 2038 problem: the largest signed 32-bit number

What is the year 2038 problem?

The largest number a signed 32-bit integer can hold is 2³¹ − 1 = 2,147,483,647, and as a timestamp that is 03:14:07 UTC on January 19, 2038. Software that keeps the timestamp in such a number can’t count one second further: the next value it can hold is −2,147,483,648, which is 20:45:52 UTC on December 13, 1901. A 64-bit number goes far past the year 9999.

FAQs

What is meant by epoch time?

Epoch time is another name for a Unix timestamp: the number of seconds since 00:00:00 UTC on January 1, 1970, the Unix epoch. Every day counts as exactly 86,400 seconds, so leap seconds are left out.

Source The Open Group · POSIX.1-2024 Base Definitions, 4.19 Seconds Since the Epoch ↗

How much is 1 hour in Unix time?

3,600 seconds. A minute is 60, an hour 3,600 and a day 86,400, so one hour later the timestamp is 3,600 bigger.

How can I convert Unix time to human-readable time?

Paste it into the box above. By hand, divide by 86,400: the whole number is the days since January 1, 1970, and what is left over is the seconds since midnight UTC. 1,000,000,000 is 11,574 days and 6,400 seconds: 01:46:40 UTC on September 9, 2001.

Sources

Related calculators