⏱️ Unix Timestamp Converter
Epoch to date and back — paste 1720224000 or 1720224000000, get the human-readable moment in your timezone and UTC instantly.
Timestamp → date
Date → timestamp
How the unix timestamp converter works
Unix time counts seconds since 00:00:00 UTC on 1 January 1970 (the "epoch"), ignoring leap seconds. The converter auto-detects the unit: values above 100 billion are treated as milliseconds — the JavaScript convention — since 100 billion seconds wouldn't occur until the year 5138. Conversion happens with the browser's own Date engine, in your local timezone and UTC side by side.
The classic debugging trap: a timestamp that renders as 1970 means you passed seconds where milliseconds were expected (or a date 50,000 years out means the reverse). The auto-detection here shows which unit was assumed so you can spot exactly that mismatch.
Frequently asked questions
What is Unix time?
The number of seconds elapsed since 00:00:00 UTC on 1 January 1970, excluding leap seconds. It is the near-universal machine representation of a moment in time — databases, APIs and logs all speak it.
Seconds or milliseconds — how do I tell?
Length: current Unix time is 10 digits in seconds and 13 in milliseconds. JavaScript uses milliseconds; most Unix tools and APIs use seconds. This converter auto-detects and tells you which it assumed.
What is the year 2038 problem?
Systems storing Unix time as a signed 32-bit integer overflow on 19 January 2038 at 03:14:07 UTC. Modern 64-bit systems are unaffected — their range extends billions of years.
Does Unix time include leap seconds?
No — by definition every Unix day is exactly 86,400 seconds. When a leap second occurs, Unix time repeats or smears a second rather than counting it. For civil timekeeping this almost never matters.
Is the timestamp converted locally?
Yes — the browser's own Date engine does the conversion on your device. Nothing you paste is transmitted.