How to convert epoch time to a date
- Paste the timestamp into Timestamp → date. Commas, spaces and underscores are ignored.
- The unit is detected from the number of digits: 10 digits for seconds, 13 for milliseconds, 16 for microseconds and 19 for nanoseconds. You can override it if needed.
- Read the date in your local time zone and in UTC, together with ISO 8601 and RFC 2822 formats, the relative time (such as "in 3 days") and the day of the year.
Where epoch timestamps come from
Server logs, database columns, JWT exp and iat claims, API responses, Kafka messages, file metadata and analytics exports all commonly store times as epoch numbers. They are compact and unambiguous, but impossible to read at a glance. This converter turns them into dates you can reason about, which helps when debugging an expired token, checking when an event happened, or comparing logs across time zones.
Negative values work too: they represent dates before 1970, such as -86400 for 31 December 1969. JavaScript dates support about 275,000 years either side of 1970, so the converter flags anything outside that range.
All conversions use your browser's built-in time zone data and happen locally.
FAQ
How do I convert epoch to a date in Excel?
Use =A1/86400+DATE(1970,1,1) for seconds and format the cell as a date. For milliseconds, divide by 86,400,000 instead. The result is in UTC.
Why is my converted date in 1970 or far in the future?
The unit is probably wrong: a milliseconds value read as seconds lands tens of thousands of years ahead, and seconds read as milliseconds lands in January 1970.
Which time zone is the result in?
Both: your browser’s local time zone and UTC are shown side by side.