Unix Timestamp Converter
Paste an epoch timestamp — seconds, milliseconds or microseconds — or a date string, and get every other representation back, including how long ago it was.
Timestamp or date
Representations
About this tool
A Unix timestamp is a count of seconds since midnight UTC on 1 January 1970, which makes it compact and unambiguous but unreadable. This converter goes both ways: give it a number and it prints the ISO 8601, UTC and local renderings; give it a date string and it prints the epoch numbers. The relative line — 'three days ago' — is usually the one you actually wanted when checking a log line or a token claim.
How to use it
- 1Paste a timestamp or a date, or press Now for the current moment.
- 2Read every representation on the right, including your local time.
- 3Copy the one you need — the labels are aligned for readable copying.
Frequently asked questions
›Seconds or milliseconds — how does it tell?
By magnitude. Ten-digit numbers are read as seconds, thirteen-digit as milliseconds and sixteen-digit as microseconds. That is the same guess every timestamp tool makes, and it is right for any date between 1973 and 5138.
›What is the Unix epoch?
Midnight UTC on 1 January 1970. A Unix timestamp counts the seconds since then, which is why it has no timezone of its own — the timezone only appears when you format it.
›Why does Local differ from UTC?
Local is rendered with your machine's timezone and daylight-saving rules. UTC and ISO 8601 are absolute. If a timestamp looks an hour off, this is almost always why.
›Can I paste a date instead of a number?
Yes. Anything your browser can parse works — 2026-03-14T09:30:00Z, March 14 2026, 2026/03/14 — and you get the epoch numbers back. Ambiguous formats like 03/04/2026 are parsed by browser rules, so prefer ISO.
›What is the 2038 problem?
Systems that store the timestamp as a signed 32-bit integer run out of room on 19 January 2038. Anything using 64-bit integers or JavaScript numbers, this page included, is unaffected.