Unix Timestamp Converter

What is Unix time?

Unix time, also called epoch time or POSIX time, counts the seconds since 00:00:00 UTC on January 1, 1970, the Unix epoch. At any moment it is the same number everywhere in the world; time zones only change how that moment is written as a local date and time.

Seconds, milliseconds, microseconds and nanoseconds

Many systems count smaller units: JavaScript and Java use milliseconds, and some databases and logs use microseconds or nanoseconds. Auto-detect reads a value as the unit that puts it within about 3,000 years of 1970: up to 11 digits as seconds, 12 to 14 digits as milliseconds, 15 to 17 as microseconds, and 18 or more as nanoseconds. Choose a unit to read it differently.

Negative timestamps

Moments before the epoch have negative Unix times. For example, −1 is 23:59:59 UTC on December 31, 1969.

Leap seconds

Unix time doesn't count leap seconds: every day is exactly 86,400 seconds long. When a leap second happens, Unix time repeats a second instead of adding one.

The year 2038 problem

Systems that store Unix time as a signed 32-bit integer run out after 2,147,483,647 seconds, at 03:14:07 UTC on January 19, 2038. One second later the value wraps to −2,147,483,648, which reads as December 13, 1901. A 64-bit timestamp lasts for billions of years.

Time zones and daylight saving time

Local dates and times use the IANA Time Zone Database, version 2026e, including historical offsets and daylight saving time rules. When clocks spring forward, a skipped local time moves forward by the length of the gap; when they fall back, you choose which of the two times you mean. To compare UTC with several places at once, use the UTC time converter. See data sources for details.