Developer
Encoders, converters & dev utilities
Convert Unix Timestamp to Date & Time
A Unix (epoch) timestamp is the number of seconds since 1970-01-01T00:00:00Z (UTC), and this converter turns it into a human-readable date in UTC, your local time, and any timezone you pick. Unix time is absolute and ignores leap seconds, so the same integer means the same instant everywhere. Worked example: 1700000000 is 2023-11-14T22:13:20Z. The tool also auto-detects whether your value is in seconds or milliseconds — a 13-digit number is treated as milliseconds (the single most common epoch mistake) — and shows an ISO-8601 / RFC-3339 string plus a relative "time ago". Everything runs in your browser. Free, no login.
Unix time = seconds since 1970-01-01T00:00:00Z (UTC); ignores leap seconds — one integer, one instant
- Byte-exact worked example: 1700000000 → 2023-11-14T22:13:20Z (UTC)
- In JavaScript: new Date(1700000000 * 1000) — the Date constructor takes milliseconds, so multiply by 1000
- Auto-detect: a 10-digit value is seconds, a 13-digit value is milliseconds (override available)
- Output shown in UTC + local + a chosen IANA timezone, with an ISO-8601 / RFC-3339 string; 100% client-side
Frequently asked questions
How do I convert a Unix timestamp to a date?
Paste the epoch value and the tool interprets it as seconds since 1970-01-01T00:00:00Z (UTC) and renders the corresponding date in UTC, your local time, and any timezone you select. For example 1700000000 converts to 2023-11-14T22:13:20Z. In code you would write new Date(1700000000 * 1000) in JavaScript, because the Date constructor expects milliseconds. It all runs in your browser with no upload.
Is my timestamp in seconds or milliseconds?
You can tell from the number of digits, and it is the #1 epoch foot-gun. A present-day timestamp in seconds has 10 digits (e.g. 1700000000), while the same instant in milliseconds has 13 digits (1700000000000). If you feed a 13-digit millisecond value into a seconds field you land tens of thousands of years in the future. This converter auto-detects by magnitude and lets you override the guess.
Why is the timestamp in UTC and not my local time?
Unix time is defined as seconds since the epoch in UTC, so the raw integer has no timezone — it is an absolute instant. To make it useful the tool shows it in UTC (the canonical value), in your browser local time, and in any IANA timezone you choose, with daylight-saving handled by the timezone database. That way there is no ambiguity about which wall-clock time the timestamp represents.