Unix time counts seconds (or milliseconds) since 1970-01-01 00:00:00 UTC. ISO 8601 is the canonical string representation — 2026-05-15T12:34:56Z. Most APIs use one or the other; sometimes both, in adjacent fields. This tool parses any of them and shows the rest, with a relative-time hint for sanity-checking.
Unix time converter
Unix time is the number of seconds (or milliseconds) since 1970-01-01 UTC. ISO 8601 is the human-and-machine-friendly string format. Convert in both directions.
Unix time converter
Parse a Unix timestamp (seconds or milliseconds) or any ISO 8601 date into local time, UTC, and back. The clock in the stat strip ticks in real time.
Input Unix s, Unix ms, or ISO 8601
Unix seconds
1780483213
Unix milliseconds
1780483213000
Local (UTC)
Jun 3, 2026, 10:40:13 AM
UTC
Wed, 03 Jun 2026 10:40:13 GMT
ISO 8601
2026-06-03T10:40:13.000Z
Relative
just now
Current Unix
1780483213
Common use cases
Debugging API responses
Server returned 1715241000 — you need to know what day that is in your timezone before you can reason about the bug.
Setting expiry deadlines
JWT exp, cache Expires headers, scheduled jobs — all want Unix seconds. Compute once, paste everywhere.
Auditing log timestamps
Logs in UTC, you’re in CET, the incident report needs the timeline in local time. Convert without spreadsheet math.
How to use this tool
- 1 Paste a number (seconds or ms — we detect by magnitude) or an ISO 8601 string.
- 2 Read both formats below; the relative hint tells you how far from now it is.
- 3 Use the Use now buttons to start from the current moment in any format.
Frequently asked questions
How do you tell seconds from milliseconds?
Magnitude heuristic — values above ~10^12 are treated as ms (years 2001+), values below as seconds. Edge cases can fool it; paste an ISO string when in doubt.
What timezone do you use?
Your browser’s. Local time is rendered with Intl.DateTimeFormat; UTC is computed by Date#toUTCString; ISO 8601 is timezone-independent and always includes the Z suffix.
Does this handle leap seconds?
JavaScript Date doesn’t — it treats every day as exactly 86,400 seconds. For nanosecond-precision astronomical work you need a TAI-aware library; for everything else, you can ignore this.