How Unix Timestamps Work and How to Read Them
A Unix timestamp is the simplest possible way to name a moment: the number of seconds since midnight 1 January 1970 in UTC. It is unambiguous and machine-friendly, which is why APIs, logs, and databases store it - but the human date behind it depends entirely on the time zone you read it in.
This guide explains how to convert in both directions, why the same timestamp is different dates in New York versus Tokyo, and how to avoid the most common off-by-one errors.
What the number means
The timestamp counts seconds since the "epoch" (1970-01-01T00:00:00 UTC). It ignores leap seconds, so each day is exactly 86,400 seconds. A timestamp like 1,700,000,000 is a single instant worldwide; the local date you see depends only on your zone.
Why time zone changes the date
Because the count is measured from UTC, a moment that is 23:00 on one day in UTC can be 04:00 the next day in a zone ahead of UTC, or still the previous day behind it. Always state the zone when you report a converted date, or the number alone is ambiguous.
Seconds versus milliseconds
JavaScript Date.now() returns milliseconds; most APIs and Unix tools use seconds. Mixing the two is the classic bug: feeding milliseconds into a seconds parser lands you in the year 1970. Check the magnitude - a seconds timestamp is ~1.7 billion; a millisecond one is ~1.7 trillion.
Frequently asked questions
Why does the same timestamp show different dates?
Because the timestamp is a single instant measured from UTC, and the local date depends on the zone. Always choose the zone you care about explicitly.
Is it seconds or milliseconds?
Use seconds for most APIs and Unix tools. If the number is around 1.7 trillion, it is milliseconds - divide by 1,000 before converting.
Want to try it?
The Unix Timestamp Converter is free and runs right in your browser (date & time). Open it now and see the guide in action.
Try the Unix Timestamp Converter