A Unix timestamp is not calculated, it is translated: the integer already holds the instant, and the job is to read it back as a date the eye can use. The Unix Timestamp Converter does that read in both directions. Type 1789689600 into the timestamp-to-date mode and the result block reads the same instant six ways: an ISO line, a UTC line, a local line, a readable line, a date line and a time line, and together they fix the instant at Friday, September 18, 2026 at 00:00 UTC. The reverse mode takes a date and a time the way a wall clock shows them and returns the integer in seconds and in milliseconds. A live line at the top of the page counts the current timestamp in seconds, updated once per second, and every readback line and every output has its own copy button, so the integer or the string leaves the browser as one paste.
The article proceeds in this order: the epoch and the unit the integer counts; the six readback lines of the timestamp-to-date mode; the local-time parse of the reverse mode; the digit-count rule that decides seconds versus milliseconds; the same instant read on two clocks in two timezones; and the places where the integer leaves the browser and travels.
The Epoch and the Unit the Integer Counts
The integer counts elapsed seconds from one fixed origin: January 1, 1970 at 00:00:00 UTC, the Unix epoch. The number 0 is the epoch itself, negative integers read the time before it, and every civil day adds exactly 86400 to the count; the counter does not insert leap seconds, so the arithmetic stays linear. 1789689600 is 20714 days after the origin: 86400 times 20714 lands exactly on that integer, with no remainder, which is why the readback falls on a clean midnight of September 18, 2026 in UTC. The same instant has a second writing, the millisecond one: multiply by 1000 and the instant is 1789689600000. One instant, two integers, the unit moved by a decimal position rather than the moment moving. A rounder example makes the unit visible: 315532800 is exactly ten years after the epoch, January 1, 1980 at 00:00:00 UTC, the count crossing the leap years 1972 and 1976 on the way.
Timestamp to Date: The Six Readback Lines
The six lines are six clocks reading one instant, not six different instants. The ISO line writes 2026-09-18T00:00:00.000Z, the Z marking the UTC zone in the string itself. The UTC line reads Fri, 18 Sep 2026 00:00:00 GMT. The local line follows the browser zone: the same integer reads 09:00 on September 18 in a browser sitting in Tokyo and 20:00 on September 17 in a browser sitting in New York. The readable, date and time lines render in the site locale; in English the readable line gives Friday, September 18, 2026, 12:00:00 AM. Each line is one format for the same moment, chosen for one destination: ISO for APIs and logs, UTC for comparisons across zones, local for the reader, readable for display, and date or time when only one part is needed. Every line has its own copy button, so the format travels alone.
Date to Timestamp: The Local-Time Parse
The reverse mode takes the wall clock, not the integer: a date field and a time field, parsed as local time in the zone the browser is in. The wall clock September 18, 2026 at 12:00 reads as 1789732800 in a browser in UTC, as 1789700400 in a browser in Tokyo, and as 1789747200 in a browser in New York on daylight time. Three different integers for one wall clock, separated by exactly the zone offsets: the same 12:00 on the wall is 03:00 in UTC in Tokyo and 16:00 in UTC in New York. The output lists both units at once, seconds and milliseconds, seconds being the milliseconds divided by 1000 and floored, so the two lines are the same instant written twice. This mode is the seam where a deadline written as a date becomes the exact instant the day starts, the question the future date article carries: a future date with its start moment pinned down.
The Digit Count Decides Seconds or Milliseconds
The converter does not ask for the unit; it reads the digit count. Ten digits or fewer read as seconds, eleven to thirteen digits read as milliseconds. Both windows reach the same horizon, the year 2286: 9999999999 as seconds is November 20, 2286 at 17:46:39 UTC, and 9999999999999 as milliseconds is that same instant written with the extra three zeros. The millisecond window starts at 10000000000, which as milliseconds is April 26, 1970 at 17:46:40 UTC, so every millisecond value written since that day reads into the right unit, and the 13-digit values of recent years sit unambiguously inside the millisecond window. The one narrow gap is early 1970: 1000000000 has ten digits, so it reads as seconds, which is September 9, 2001 at 01:46:40 UTC, not the sixteen minutes and forty seconds after the epoch that the same digits would mark if they were milliseconds. The rule trades one deliberate misread in the first quarter of 1970 for a unitless input field that reads modern values without a hint.
The Same Instant on Two Clocks
The timestamp carries no zone; the readback does. The anchor instant 1789689600 sits at 00:00 on September 18 in UTC, at 02:00 in Berlin on summer time, at 09:00 in Tokyo, and at 20:00 on September 17 in New York. The integer is one number in every one of those zones; the wall clock is where the zone enters. That separation is what makes spans safe: 1789732800 minus 1789689600 is 43200 seconds, 12 hours, the same difference in every zone, because both integers live on the same UTC axis. The Date Calculator in difference mode reports the same span between two dates in days, and the date difference article walks that mode end to end; the timestamp version of the same subtraction is plain integer arithmetic, no calendar in between.
Where the Integer Travels
Outside the converter the integer is the currency of the machine: APIs return it, server logs stamp it, file systems store it, databases sort on it, and the wall clock is rendered from it at read time in whatever zone the reader is in. The seam with the date is where the zone enters and the errors happen. A birth date of January 15, 1990 at local midnight is 632361600 read in UTC and 632329200 read in Tokyo, a nine-hour gap in the integer for one wall clock. The Age Calculator reads the date, not the integer, and keeps the local midnight as the birth instant; the age article explains why the local-midnight parse is the difference between a correct age and an off-by-one day. At the far end of the planning chain, the dates that start as integers leave the browser: a 30-year loan taken at 36 on January 15, 2026 pays off at 66 on January 15, 2056, the Loan Calculator carries that schedule, and the Retirement Planner carries the retirement date the same way, each writing its end dates back to the wall clock at the end.