Seconds since 1 January 1970, 00:00 UTC, live, with converters in both directions.
Milliseconds
Timestamp to date
Date to timestamp
/
Type a city, a country or a zone such as “CET” or “Tokyo”.
Batch converter
Timestamps become UTC dates; ISO 8601 dates become Unix seconds (a date without an offset is read as UTC).
Signed 32-bit Unix time runs out at 03:14:07 UTC on 19 January 2038 (2,147,483,647 seconds); systems that store time in 64 bits are not affected.
How it works
What Unix time is
Unix time (also epoch or POSIX time) counts the seconds since 00:00:00 UTC on 1 January 1970, ignoring leap seconds. It is the same number everywhere on Earth at the same moment, which is why software stores time this way and converts it to a local time only for display.
JavaScript and many APIs use milliseconds (13 digits today); some databases and logs use microseconds (16 digits) or nanoseconds (19 digits). The converter detects the unit from the number of digits, and you can always see which one it used.
Questions
Good to know
What is the current Unix timestamp?
It is the live number at the top of this page: the seconds elapsed since 1 January 1970 at 00:00 UTC, checked against Hourora’s server.
Does Unix time include leap seconds?
No. Every Unix day is exactly 86,400 seconds, so the count skips over leap seconds; that keeps date arithmetic simple.
What is the year 2038 problem?
Systems that store Unix time as a signed 32-bit number overflow at 03:14:07 UTC on 19 January 2038 and jump back to 1901. Modern systems use 64-bit time, which lasts for billions of years.