Unix Timestamp Converter
Convert Unix epoch timestamps to human-readable dates and back — in seconds, milliseconds, microseconds or nanoseconds, in any time zone.
Current Unix timestamp
Seconds
Milliseconds
Timestamp to date
Date to timestamp
100% private: everything runs in your browser and nothing is uploaded.
How to Convert a Unix Timestamp
No sign-up, no installation — it works right here in your browser.
- Step 1:Paste a timestamp in seconds, milliseconds, microseconds or nanoseconds — the unit is detected automatically, or choose it yourself.
- Step 2:Read the date in your time zone, UTC, ISO 8601 and RFC 2822 formats, and switch the time zone to see it anywhere in the world.
- Step 3:To go the other way, pick a date and time below and copy the resulting Unix seconds or milliseconds.
Unix Timestamp FAQ
What is epoch time?
Epoch time is the number of seconds elapsed since the Unix epoch, 1 January 1970 at 00:00:00 UTC. For example, 1735689600 is 1 January 2025 at midnight UTC.
How do I know if a timestamp is in seconds or milliseconds?
Count the digits. Current timestamps have 10 digits in seconds, 13 in milliseconds, 16 in microseconds and 19 in nanoseconds. The converter detects this automatically.
Do Unix timestamps depend on time zones?
No. A Unix timestamp always refers to the same instant worldwide. Time zones only matter when you display it as a calendar date, which is why you can switch the zone without changing the number.
What is the year 2038 problem?
Systems that store the timestamp as a signed 32-bit integer can only count up to 2,147,483,647 seconds, which is reached on 19 January 2038 at 03:14:07 UTC. After that the value overflows. Using 64-bit integers avoids the problem.
How do I get the current timestamp in code?
In JavaScript use Math.floor(Date.now() / 1000), in Python int(time.time()), in PHP time(), in Java Instant.now().getEpochSecond() and in a Unix shell date +%s.
What Is a Unix Timestamp?
A Unix timestamp, also called epoch time or POSIX time, counts the seconds that have passed since 00:00:00 UTC on 1 January 1970, ignoring leap seconds. Because it is a single number with no time zone, it is the standard way to store and exchange moments in time in databases, log files, APIs, JWT claims, cron jobs and analytics events. Many systems use finer precision: JavaScript and Java work in milliseconds (13 digits), while Python, Go, databases and tracing tools often use microseconds (16 digits) or nanoseconds (19 digits).
This free epoch converter detects the unit automatically from the number of digits and shows the date in your local time zone or any IANA time zone, in UTC, as ISO 8601 and RFC 2822 strings, as relative time and as the day of the year. The reverse converter turns a calendar date and time into Unix seconds and milliseconds, correctly handling daylight saving time for the selected zone. A live clock shows the current timestamp, ready to copy. Note that 32-bit systems storing seconds in a signed integer will overflow on 19 January 2038 — the year 2038 problem — while 64-bit timestamps are safe for billions of years.