Unix Timestamp Converter
Translate between epoch time and human-readable dates in both directions.
What is a Unix timestamp?
Unix time counts the seconds elapsed since 00:00:00 UTC on 1 January 1970, ignoring leap seconds. It is the same instant everywhere on Earth, which is why it is the standard way to store time in databases and APIs — you store one number and render it in each user's own time zone.
Seconds or milliseconds?
Unix time is traditionally seconds, but JavaScript's Date.now() returns milliseconds. A quick sanity check: 10-digit values are seconds, 13-digit values are milliseconds. Mixing the two produces dates in 1970 or in the year 55,000 — one of the most common date bugs around.
The 2038 problem
Systems that store epoch seconds in a signed 32-bit integer overflow on 19 January 2038. Modern 64-bit platforms are unaffected, but embedded devices and some legacy databases still are. If you maintain older infrastructure, it is worth checking how timestamps are stored.
Why leap seconds are ignored
Unix time assumes every day has exactly 86,400 seconds. When a leap second is inserted, systems typically repeat or smear the extra second rather than advancing the counter, so the mapping between epoch and UTC stays continuous.