Convert Unix timestamps to human-readable dates and vice versa. Live timestamp display.
This free online Unix timestamp converter translates epoch timestamps to human-readable UTC, ISO 8601, and local date/time strings - and converts any date back to a Unix timestamp in both seconds and milliseconds. A live ticker shows the current epoch time updating every second, making it easy to grab the current timestamp at a glance. It is an essential tool for developers working with APIs, databases, log files, or any system that stores time as a numeric epoch value.
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 - the "Unix epoch". It is a single integer that uniquely represents any point in time, which makes it universally used in programming, databases, APIs, server logs, and JWT tokens. For example, the Unix timestamp 1700000000 corresponds to 14 November 2023 22:13:20 UTC.
Paste or type your Unix timestamp into the input field above and this free online Unix timestamp converter will instantly display the corresponding UTC date and time, your local date and time, and the ISO 8601 formatted string. The conversion runs entirely in your browser using JavaScript's Date object, so entered timestamp values are not uploaded for processing.
The original Unix timestamp counts seconds since the epoch. However, many modern languages and APIs (JavaScript's Date.now(), Java's System.currentTimeMillis()) return milliseconds - a value 1,000 times larger. A 10-digit number is almost always seconds (e.g. 1700000000), while a 13-digit number is milliseconds (e.g. 1700000000000). Our converter accepts both formats automatically.
In JavaScript: Math.floor(Date.now() / 1000) gives the current epoch in seconds. In Python: import time; int(time.time()). In PHP: time(). In Linux/Bash: date +%s. All return the current number of seconds since 1 January 1970 UTC.
The "Year 2038 problem" (similar to Y2K) affects systems that store Unix time as a 32-bit signed integer. On 19 January 2038 at 03:14:07 UTC, a 32-bit timestamp overflows and wraps to a large negative number, representing 1901. Modern 64-bit systems are not affected, but older embedded systems and some databases using 32-bit integers could experience issues.