Unix Timestamp and Date Debugger
Convert Unix timestamps to readable dates and back, with seconds and milliseconds told apart and every major time zone shown.
Convert between Unix time, ISO 8601, local time and relative time, with seconds and milliseconds told apart.
Reading
6 days ago
10 digits, read as seconds
Around the world
Generating...About the unix timestamp and date debugger
The mistake that costs the most time with timestamps is the unit. Seconds and milliseconds are both just digits, and reading one as the other lands you in 1970 or in the year 56000. This counts the digits and tells you which it assumed, instead of guessing silently.
It also shows the same instant in every major time zone and as relative time, which is usually what you actually wanted to know: not the exact date, but whether the token expired an hour ago or expires tomorrow.
How to use it
- 1Paste a timestamp or any date string.
- 2Check the reading note to confirm the unit was interpreted correctly.
- 3Read the conversions and the relative time.
- 4Copy the ready made snippet for JavaScript, Python, Go or SQL.
Questions
How do I tell seconds from milliseconds?
Count the digits. Ten digits is seconds and covers dates up to 2286. Thirteen digits is milliseconds. This tool applies that rule and states which one it used.
What is the year 2038 problem?
A signed 32 bit integer runs out at 03:14:07 UTC on 19 January 2038. Systems still storing Unix time in 32 bits will overflow to a negative number and jump to 1901.
Why does my timestamp show a different date than my server?
Almost always a time zone difference. Servers usually run in UTC while your browser shows local time. Store in UTC, convert only for display.
Is a Unix timestamp affected by daylight saving?
No. It counts seconds since 1970 in UTC and never jumps. Only the formatted local time changes, which is exactly why storing UTC is the right choice.