Unix Timestamp Converter

Convert Unix timestamps in seconds, milliseconds, microseconds or nanoseconds to dates and back, and translate ISO 8601, RFC 2822, Excel, Windows FILETIME, .NET ticks and other date formats, in any time zone.

Converter Time & Date Updated Oct 3, 2026
Learn how this works
How to Use
  1. Paste a timestamp or a date into the box: a Unix number, an ISO 8601 or RFC 2822 date, or an HTTP header date. Press Now for the current moment.
  2. Numbers are read by their length: 10 digits as seconds, 13 as milliseconds, 16 as microseconds, 19 as nanoseconds. Choose Read as to force a unit or to read Excel, FILETIME, .NET ticks and other formats.
  3. Pick the time zone to show the local time in. Dates typed without an offset are read in that zone.
  4. Copy any format from the list on the right. The timeline shows where the moment sits against the 32-bit limits of 1901, 2038 and 2106.
Input
auto-detect
for local time
in that zone
Presets
Every format
Unix seconds
—
UTC
—
Weekday
—
From now
—

Worked Example

1700000000 has 10 digits, so it is seconds. Divide by the 86,400 seconds in a day: 1,700,000,000 ÷ 86,400 = 19,675 whole days with 80,000 seconds left over. 80,000 seconds is 22 hours, 13 minutes and 20 seconds.

Day 19,675 after 1 January 1970 is 14 November 2023, and since day 0 was a Thursday, 19,675 mod 7 = 5 days later is a Tuesday. So the timestamp is Tuesday 14 November 2023, 22:13:20 UTC, which is 17:13:20 in New York (UTC−5 in November).

The common mistake: milliseconds read as seconds. The same moment in JavaScript is 1700000000000 (13 digits). Read as seconds, that is 1,000 times further from 1970, a date more than 53,000 years in the future. If a converted date lands in the far future or in January 1970, check the unit before anything else.

Show Work

Enter a timestamp or date above to see the conversion.

Formulas

Days and time of day
days = ⌊t ÷ 86400⌋, rest = t mod 86400
t in seconds
Weekday
(days + 4) mod 7
0 = Sunday; 1 Jan 1970 was a Thursday
Units
ms = s × 103 · µs = s × 106 · ns = s × 109
Windows FILETIME
t × 107 + 116,444,736,000,000,000
100 ns steps since 1 Jan 1601
Excel serial
t ÷ 86400 + 25569
1900 system, dates after 1 March 1900
Julian Day
t ÷ 86400 + 2,440,587.5
Days since noon, 1 Jan 4713 BC

Why 1970?

Early Unix, written at Bell Labs from 1969, counted time in sixtieths of a second from 1 January 1971, which a 32-bit counter would have exhausted in under three years. In the early 1970s the count was changed to whole seconds and the epoch moved to the round date of 1 January 1970 UTC, giving about 68 years in each direction. POSIX later fixed the definition: every day is exactly 86,400 seconds, so leap seconds are left out.

Other systems picked other starting points. Windows counts 100-nanosecond steps from 1601, the start of the 400-year Gregorian cycle in which it was designed; .NET counts the same steps from year 1; Apple’s Cocoa counts seconds from 2001; Excel counts days from 1900 and, to stay compatible with Lotus 1-2-3, still treats 1900 as a leap year, which it was not. Every format in the list on the right describes the same instant from a different zero.

About This Tool

This converter reads Unix time in any unit, ISO 8601, RFC 2822 and HTTP dates, and the timestamps used by Excel, Windows, Active Directory, .NET, Chrome and macOS, and writes the same moment in all of them, with the local time in any time zone. It keeps whole nanoseconds, so 19-digit values are converted without rounding, and it shows how the number was read and every step of the conversion.

Everything runs in your browser; nothing you paste is sent anywhere.

Related tools: Timezone Converter, Date Calculator, and World Clock.

Frequently Asked Questions

What is a Unix timestamp?

The number of seconds since 00:00:00 UTC on 1 January 1970, the Unix epoch. It is the same everywhere in the world at a given moment, which is why logs, databases and APIs use it. JavaScript, Java and many APIs count in milliseconds instead (13 digits), and some systems use microseconds (16) or nanoseconds (19).

Why does my timestamp give a date in the year 55,000?

It is in milliseconds but was read as seconds. 1700000000000 is 14 November 2023 as milliseconds, but as seconds it lands more than 53,000 years in the future. Auto-detect avoids this by counting digits; if a system really means seconds, divide by 1,000.

What is the year 2038 problem?

Older software stores Unix time in a signed 32-bit integer, which runs out at 2,147,483,647: 03:14:07 UTC on Tuesday 19 January 2038. One second later it wraps to −2,147,483,648, which reads as 13 December 1901. Unsigned 32-bit values last until 7 February 2106. Modern systems use 64 bits, which last for about 292 billion years.

What does the Z in an ISO 8601 date mean?

Z means UTC (it comes from the military name “Zulu” time). 2023-11-14T22:13:20Z and 2023-11-14T17:13:20-05:00 are the same moment. A date written without Z or an offset says nothing about its time zone, so this tool reads it in the zone you have selected and says so.

Do Unix timestamps count leap seconds?

No. Unix time treats every day as exactly 86,400 seconds, so the 27 leap seconds added since 1972 are not counted; during a leap second the clock repeats or smears a second. That keeps date arithmetic simple, at the cost of being up to 27 seconds off true elapsed atomic time across decades.

How do I use the Unix Timestamp Converter?

Simply type or paste your value and read the result, which refreshes the instant you change something. There is nothing to submit and nothing to wait for.

Do I need to install or sign up for anything?

Not at all — it runs in the browser with nothing to install and no account. After it loads once, it even works without an internet connection.

Is my information private?

Yes. Everything happens in your browser. Nothing you type is sent to a server or saved anywhere.

Common Use Cases

Reading API responses and logs

An API returns "created": 1700000000; paste it to get Tuesday 14 November 2023, 22:13:20 UTC, or 17:13:20 in New York.

Database values

A 13-digit value in a JavaScript or Java database column is milliseconds: 1700000000000 is the same moment as 1700000000.

Windows and Active Directory

An LDAP lastLogon of 133444736000000000 is a FILETIME (100 ns steps since 1601), which is also 14 November 2023 22:13:20 UTC.

Spreadsheets

Excel stores that moment as 45244.925926: days since 1900 with the time as a fraction.

Testing the 2038 limit

Check whether a date fits a signed 32-bit field: 2,147,483,647 is the last second, 03:14:07 UTC on 19 January 2038.

Last updated: