Unix Timestamp Converter
Turn a Unix timestamp into a readable date in your time zone, UTC and ISO 8601, or pick a date and get its timestamp. It works out whether you pasted seconds, milliseconds, microseconds or nanoseconds.
Current Unix time
…
Milliseconds
…
Timestamp → date
Date → timestamp
What a Unix timestamp is
A Unix timestamp counts the seconds since 00:00:00 UTC on 1 January 1970, ignoring leap seconds. It has no time zone: the same number is the same instant everywhere. That is why databases, logs and APIs store time this way and only convert to local time for display.
Seconds or milliseconds?
Unix tools, most APIs and JWTs use seconds (10 digits today). JavaScript's Date.now() and Java use milliseconds (13 digits). Python's time.time_ns()and Go give nanoseconds (19 digits).
Mixing them is a classic bug: a seconds value read as milliseconds lands in January 1970, and a milliseconds value read as seconds lands tens of thousands of years from now. This converter guesses the unit from the number of digits and says which it used.
The year 2038 problem
Systems that store the timestamp in a signed 32-bit integer overflow at 2147483647, which is 03:14:07 UTC on 19 January 2038. After that the value wraps to a negative number, back in 1901. Modern 64-bit time types don't have this problem, but old databases, embedded devices and file formats can.