Unix Timestamp Converter — Epoch to Date and Back
Convert Unix timestamps to human dates and back, in seconds, milliseconds or microseconds.
🔒 Runs in your browser — files never uploaded ⚡ No signup 💯 Free
Timestamp → date
Date → timestamp
Convert a Unix timestamp into a readable date, or a date into a timestamp. The current epoch time ticks at the top of the page, ready to copy.
The tool detects whether your number is in seconds, milliseconds or microseconds and tells you which it assumed — the single most common source of "why is this date in the year 56,000" confusion.
How to use Timestamp Converter
- Paste a timestamp in the left panel to see it as a date in UTC, ISO 8601 and your local time zone.
- Or pick a date in the right panel to get the timestamp.
- Choose how to interpret the date — your local zone or UTC.
Seconds, milliseconds or microseconds
A Unix timestamp counts from 1 January 1970 UTC. The unit depends on where it came from: PHP, Python and most databases use seconds (10 digits today), JavaScript's Date.now() uses milliseconds (13 digits), and some tracing systems use microseconds (16 digits). Feed a 13-digit value into a seconds-based converter and you land tens of thousands of years in the future. We count the digits and say which unit we used.
Time zones
A Unix timestamp is always UTC — it has no time zone. The zone only matters when converting to or from a human-readable date. That is why the same timestamp shows a different wall-clock time in Tokyo than in New York, and why storing timestamps rather than local date strings avoids an entire category of bug.
The year 2038 problem
Systems storing timestamps in a signed 32-bit integer overflow on 19 January 2038, wrapping to 1901. Any modern 64-bit system is unaffected, but the issue still appears in embedded devices and legacy database columns.
Frequently asked questions
Is my timestamp in seconds or milliseconds?
Count the digits. Ten digits is seconds (PHP, Python, most databases), thirteen is milliseconds (JavaScript), sixteen is microseconds. The tool detects this and tells you which it assumed.
Do Unix timestamps have a time zone?
No — they are always counted from 1 January 1970 UTC. Time zones only apply when converting to or from a human-readable date, which is why storing timestamps avoids a whole category of bug.
What is the year 2038 problem?
Systems storing timestamps in a signed 32-bit integer overflow on 19 January 2038 and wrap around to 1901. Modern 64-bit systems are unaffected, but it still appears in embedded devices and legacy database columns.