Unix Timestamp Converter
Convert Unix timestamps to dates and back, in any time zone.
Convert a Unix timestamp (epoch time) to a human-readable date and back again, with full time-zone support. Auto-detects seconds, milliseconds and microseconds, shows the current live epoch time, and gives you local, UTC, ISO 8601 and relative-time views. Runs fully in your browser — nothing is uploaded.
How to use Unix Timestamp Converter
Check the live clock
The current Unix time updates every second in both seconds and milliseconds at the top; click it to copy the epoch value instantly in your browser.
Pick a time zone
Search and select any IANA time zone, or stay on Local or UTC, so every converted date in this free Unix timestamp converter reflects the right offset.
Convert timestamp to date
Paste an epoch value into the Timestamp to Date box and it auto-detects seconds, milliseconds, microseconds or nanoseconds and shows the human date.
Convert date to timestamp
Pick a wall-clock date and time in the Date to Timestamp box and instantly get the matching Unix timestamp in both seconds and milliseconds.
Use quick timestamps
Tap a quick pick like Now, one hour ago, one week ago or the Unix epoch zero to load a common epoch value into the converter in a single click.
Read and copy results
See each result in your local zone, UTC, ISO 8601 and relative time, then copy any value to use in databases, APIs, JWTs or log files.
Frequently asked questions
What is a Unix timestamp?
It's the number of seconds since 00:00:00 UTC on 1 January 1970 (the Unix epoch), ignoring leap seconds. Because it's measured from a fixed point in UTC, the same timestamp represents the same instant everywhere — only its human-readable form changes with the time zone.
How do I get the current Unix timestamp?
The live clock at the top of this page shows the current epoch time in both seconds and milliseconds, updating every second — click it to copy. In code you can get it with Math.floor(Date.now() / 1000) in JavaScript, time() in PHP or Python, or date +%s in a Unix shell.
Seconds, milliseconds or microseconds — which one am I looking at?
It's usually told by the length: a 10-digit number is seconds, 13 digits is milliseconds, 16 is microseconds and 19 is nanoseconds. The tool auto-detects this, but you can force a unit with the dropdown if your value is unusual.
Why does the date change when I switch the time zone?
The underlying instant stays the same — only how it's displayed changes. 1700000000 is one exact moment; in Tokyo it reads a few hours later on the clock than in New York. Conversions are DST-aware, so the offset shown reflects daylight saving where it applies.
How do I convert a date in a specific time zone to a timestamp?
Pick the time zone at the top, then enter the wall-clock date and time in the “Date → Timestamp” box. The tool treats those numbers as local to the chosen zone (handling DST correctly) and gives you the matching epoch value in seconds and milliseconds.
What is the Year 2038 problem?
Systems that store Unix time in a signed 32-bit integer can only count up to 03:14:07 UTC on 19 January 2038 — after that the value overflows and wraps to a negative number, misreading the date as 1901. Modern 64-bit systems and most current languages store the timestamp in 64 bits, which pushes the limit billions of years away, so it mainly affects legacy code.
Is my data sent anywhere?
No. All conversions run entirely in your browser using the native Date and Intl APIs. Nothing you type is uploaded, logged or stored.
Related tools — Developer · Time & scheduling
- Crontab Guru — Decode cron expressions & see the next run times.