A Unix timestamp counts the seconds that have passed since 00:00:00 UTC on 1 January 1970, a moment known as the Unix epoch. Computers, databases and APIs store time this way because a single number is easy to compare and sort. This converter turns a timestamp into a readable date in both UTC and your own time zone, and turns a date back into a timestamp.
How to use it
- Paste a timestamp into the first box. The tool detects whether it is in seconds (10 digits) or milliseconds (13 digits).
- Or pick a date and time in the second box to get its timestamp.
Seconds vs milliseconds
Unix systems and most server languages, such as PHP and Python’s time.time(), work in seconds. JavaScript’s Date.now() and Java’s System.currentTimeMillis() return milliseconds. If a date comes out in the year 50,000 or in January 1970, you have probably mixed the two up.
The year 2038 problem
Older systems store the timestamp as a signed 32-bit integer, which runs out at 03:14:07 UTC on 19 January 2038. Modern systems use 64-bit numbers, which last for billions of years.
Frequently asked questions
Do Unix timestamps include time zones?
No. A timestamp is always UTC. The time zone only matters when you display it, which is why this tool shows both UTC and your local time.
Do leap seconds count?
No. Unix time ignores leap seconds, so every day is exactly 86,400 seconds.