Timestamp Converter
Convert Unix timestamps to readable dates and back, with a live current timestamp and timezone support.
...
About the Timestamp Converter
Unix time counts the seconds since midnight UTC on January 1, 1970. It is how computers store moments in time: database rows, log lines, JWT expiry claims, and API responses all use it, because a single number is unambiguous in a way that “3pm on Tuesday” never is.
The cost is that humans cannot read it. This tool converts in both directions: paste a timestamp from a log or token and see it as a local date, UTC, ISO 8601, and relative time; or pick a date and get the timestamp to put in your code. The current timestamp ticks at the top, ready to copy.
Both seconds (10 digits) and milliseconds (13 digits) are detected automatically, since JavaScript uses milliseconds while almost everything else uses seconds, and mixing them up produces dates in 1970 or the year 56,000.
Reach developers and designers who use these tools every day. Privacy-first, no trackers.
Frequently asked questions
Why does my timestamp show a date in 1970?
You probably have a value in seconds being read as milliseconds, or a small number that is not a timestamp at all. A timestamp for recent dates has 10 digits in seconds or 13 in milliseconds.
Are Unix timestamps timezone dependent?
No, and that is their point. A timestamp identifies one instant, the same everywhere. Only the human readable representation changes with timezone, which is why this tool shows both your local time and UTC.
What happens in 2038?
Systems storing timestamps as signed 32 bit integers overflow on January 19, 2038. Modern systems use 64 bit integers and are fine for billions of years. If you maintain old C code or embedded systems, this is worth checking.