Tools
Unix timestamp converter
Convert a Unix timestamp (epoch time) into a human-readable date in UTC, your local time zone, and ISO 8601, or go the other way and turn any date and time into epoch seconds and milliseconds. Seconds versus milliseconds are detected automatically. Everything runs in your browser; no timestamp is ever uploaded or stored.
Current Unix time
Seconds
—
Milliseconds
—
Timestamp to human date
Paste a Unix timestamp. Seconds and milliseconds are auto-detected by magnitude, or force a unit below.
Human date to timestamp
Pick a date and time (read in your local time zone) to get its epoch in seconds and milliseconds.
Every conversion runs locally in your browser with the native Date and Intl APIs. No timestamp is ever sent to a server.
Working with epoch time
Unix time is the lingua franca of software clocks. Server logs, JWT expiry claims, database created_at columns, cron schedules, and analytics events all tend to store an instant as a single integer: the count of seconds (or milliseconds) since the 1970 epoch. It is unambiguous and free of time-zone confusion, which makes it ideal for storage but hard to read at a glance.
That is where a converter earns its keep. When you are staring at 1752624000 in a log line and trying to correlate it with a bug report, you need the wall-clock time in your own zone, and the UTC value your teammate three continents away will recognise. Pasting the number here gives you both instantly, along with a copy-ready ISO 8601 string for pasting back into code or tickets.
The most common footgun is the seconds-versus-milliseconds mismatch: multiply by a thousand in the wrong place and your date lands in 1970 or the year 55,000. This tool detects the likely unit by magnitude and shows which it chose, and you can override it when your data is unusual.
Frequently asked questions
- What is a Unix timestamp?
- A Unix timestamp (also called epoch time) is the number of seconds that have elapsed since 00:00:00 UTC on 1 January 1970, not counting leap seconds. It is a compact, time-zone-independent way to store an instant in time, which is why logs, databases, and APIs use it everywhere.
- Seconds or milliseconds: how does auto-detect decide?
- By magnitude. A 10-digit value like 1752624000 is seconds (year 2025); a 13-digit value like 1752624000000 is milliseconds. This tool treats any value of 1e12 or larger as milliseconds and everything else as seconds. If your data sits in an unusual range, switch the unit toggle to force seconds or milliseconds.
- Why do the UTC and local times differ?
- A timestamp is a single instant, but humans read it in a time zone. UTC is the universal reference; your local time applies your browser’s time-zone offset (including daylight saving time) on top of it. This tool shows both, plus the resolved IANA zone name from the Intl API, so you always know which offset was used.
- What is the ISO 8601 format shown here?
- ISO 8601 is the international standard for writing dates and times, e.g. 2025-07-16T00:00:00.000Z. The trailing Z means UTC (Zulu time). We also give an ISO string with your numeric offset, like 2025-07-16T05:30:00+05:30, which is handy when a system needs the local offset preserved.
- Does this send my data anywhere?
- No. Every conversion is computed in your browser with the built-in JavaScript Date and Intl APIs. There are no network requests, no logging, and no storage. The tool works fully offline once the page has loaded.
- What range of dates can it handle?
- JavaScript can represent any instant within roughly ±271,821 years of 1970 (±8.64e15 milliseconds). Values outside that range, or non-numeric input, are rejected with an inline message instead of producing an invalid date.