Unix Timestamp Converter
Convert Unix epoch timestamps to human-readable dates and back — in seconds or milliseconds, local time or UTC. Free and instant, everything runs in your browser.
Current Unix time
Timestamp → date
Date → timestamp
How to use the Unix Timestamp Converter
- Paste a timestamp. Type or paste any Unix timestamp into the first field. Leave the unit on Auto and the tool detects whether it is in seconds (10 digits) or milliseconds (13 digits).
- Read the date. The converter instantly shows the moment in your local time zone, in UTC, as an ISO 8601 string, and as relative time such as "3 hours ago".
- Convert the other way. In the second section, pick any date and time (optionally interpreted as UTC) to get its Unix timestamp in both seconds and milliseconds, with one-click copy buttons.
About this tool
A Unix timestamp (also called epoch time or POSIX time) is the number of seconds that have elapsed since 00:00:00 UTC on 1 January 1970. It is the standard way computers store points in time: databases, log files, APIs and programming languages such as JavaScript, Python, PHP and Java all use it. This epoch converter translates those raw numbers into readable dates and converts calendar dates back into timestamps — handy for debugging logs, writing queries or setting expiry times.
The converter also shows the live current Unix time, ticking every second, and handles negative timestamps for dates before 1970. All conversions are computed locally in your browser using your system clock and time zone; nothing you type is uploaded, stored or logged anywhere.
Frequently asked questions
What is the difference between seconds and milliseconds timestamps?
Classic Unix time counts whole seconds since the 1970 epoch and currently has 10 digits. JavaScript's Date.now(), Java's System.currentTimeMillis() and many APIs count milliseconds instead, producing 13-digit numbers. The Auto mode detects the unit from the number of digits: 13 or more digits are treated as milliseconds.
Can I convert dates before 1970?
Yes. Dates before 1 January 1970 UTC simply have negative timestamps. For example, -86400 is 31 December 1969 at 00:00 UTC. Enter any negative number and it converts normally.
What is the Year 2038 problem?
Systems that store Unix time in a signed 32-bit integer overflow at 03:14:07 UTC on 19 January 2038 (timestamp 2147483647). Modern 64-bit systems and this converter are unaffected — you can convert timestamps far beyond 2038.
Why do local time and UTC show different values?
A timestamp identifies one absolute instant, but that instant reads differently on clocks around the world. The local row uses your device's time zone (including daylight saving), while UTC is the universal reference with no offset. Both rows describe the exact same moment.