What exactly is a Unix timestamp?
The number of seconds since 1970-01-01T00:00:00 UTC, not counting leap seconds. The start is the UNIX epoch, and the count ignores the leap seconds added since 1972, which is why it is called POSIX time and why it converts without a table of leap seconds.
Why does my timestamp have 13 digits instead of 10?
Ten digits are seconds and thirteen are milliseconds, which is what JavaScript's Date.now() returns by default. Sixteen digits are microseconds and nineteen are nanoseconds. This page counts the digits and picks the unit, and names the unit above the result so it can be overridden.
What is epoch 0 in my own time zone?
In Seoul, 1970-01-01 09:00:00, because the offset was nine hours ahead of UTC. The instant is the same everywhere; only the wall clock differs. Set the zone selector on the Convert tab to see any zone.
Why is the date one day off from what I expected?
Usually a zone, not arithmetic. A timestamp is an instant with no zone, so it is displayed in one, and a value near midnight lands on a different calendar day in a different zone. Compare the UTC line with the local line to see where the shift happens.
Are leap seconds counted?
No. Unix time follows POSIX, which holds every day at 86,400 seconds. A leap second is absorbed by the system clock instead of appearing in the number, so a conversion never needs a leap second table and never disagrees with the value a server logs.
Does anything get uploaded?
No. Every figure is computed in this tab, the content policy forbids network requests, and there is no server that could receive a timestamp. Only the language, the theme and the last values you typed are kept in this browser.