Unix Timestamp Converter
Convert Unix epoch timestamps to human-readable dates, and dates back to timestamps
Current Unix time
—
Seconds
—
Milliseconds
Timestamp to date
Date to timestamp
Which zone the time above is written in.
Auto Unit Detection
Seconds, milliseconds, microseconds or nanoseconds
Local and UTC
See both zones plus ISO 8601 side by side
Live Epoch Clock
The current timestamp, ticking every second
Frequently asked questions
How does the converter know whether my number is seconds or milliseconds?
It counts the digits before the decimal point. Up to 10 digits is read as seconds, 11 to 13 as milliseconds, 14 to 16 as microseconds, and 17 or more as nanoseconds. If that guess is wrong for your data, switch the unit control off "Auto" and pick the unit yourself.
Can I convert a timestamp from before 1970?
Yes. Enter a negative number such as -86400 and it is read as seconds before the epoch, giving 31 December 1969. Negative values always fall into the seconds bucket regardless of digit count.
Is this affected by the year 2038 problem?
No. The 2038 problem is a 32-bit signed integer overflow: systems storing seconds in a 32-bit int run out of room on 19 January 2038. JavaScript stores times as 64-bit floating point milliseconds, so this converter handles dates roughly 273,000 years either side of 1970.
Why do the Local and UTC results differ?
A Unix timestamp is a single instant with no time zone attached. Local renders that instant in your browser's zone, UTC renders the same instant at Greenwich. In the date-to-timestamp section the Local/UTC toggle works the other way round, deciding which zone the wall-clock time you typed belongs to.