Unix Timestamp Converter
Epoch to human-readable date — local, UTC, and ISO 8601 — and back, with seconds/milliseconds auto-detection and a live current timestamp.
How to use this tool
- Paste a Unix timestamp — seconds and milliseconds are auto-detected — to see the date in your local time, UTC, and ISO 8601.
- Or go the other way: pick a date and time to get its epoch value.
- The live current timestamp at the top is one click to copy.
How it works
Unix time counts seconds since January 1, 1970 UTC (the 'epoch') with no timezone or daylight-saving component — the same instant is the same number everywhere on Earth, which is why databases and APIs store it. Confusion enters at display time: JavaScript uses milliseconds (13 digits) while most Unix systems use seconds (10 digits); the tool auto-detects which you pasted.
Unix time counts seconds since 1970-01-01 00:00:00 UTC (the epoch), ignoring leap seconds. Ten-digit values are seconds; thirteen digits are milliseconds (what JavaScript's Date.now() returns) — the tool detects which you pasted from the magnitude and says so.
Frequently asked questions
What was the 'year 2038 problem'?
Signed 32-bit timestamps overflow on January 19, 2038 (at 03:14:07 UTC). Modern 64-bit systems are unaffected — their range extends billions of years — but embedded systems storing time in 32 bits still need auditing.
Is my timestamp in seconds or milliseconds?
Current dates are ~10 digits in seconds (1.7–1.8 billion) and ~13 digits in milliseconds. The tool auto-detects by magnitude and labels its assumption.
What was the Unix epoch?
Midnight UTC on January 1, 1970 — the zero point from which Unix time counts. Negative timestamps represent dates before it.
What is the year-2038 problem?
Systems storing Unix time in a signed 32-bit integer overflow on January 19, 2038. Modern 64-bit systems (and this tool) are unaffected.