Why computers needed a starting line
A date such as “Tuesday, March 12” is meaningful to people, but awkward for a computer to compare or subtract. Unix time turns dates into a single number: the count of seconds from a shared reference point. That makes questions like “Which event happened first?” or “How many seconds passed?” straightforward arithmetic.
The reference point is called the Unix epoch: midnight at the start of January 1, 1970, in Coordinated Universal Time (UTC), the global time standard. It is a convention chosen for computing, not a natural boundary in history. A moment after the epoch has a positive count; one before it has a negative count.
From a number back to a date
A computer can add seconds to the epoch to get a moment, or subtract seconds to work backward. To display that moment as a local clock time, software converts it to a calendar date and applies the relevant time-zone rules. The stored count and the displayed date are therefore different things: the number marks a point on a shared timeline, while the display reflects how people label that point in a particular place.
This representation is useful for ordering logs, measuring elapsed time, and coordinating events across machines. But it does not make calendars or time zones disappear; software still needs rules to translate between a count of seconds and the dates people use.
A convention with practical limits
Unix time is often described as counting seconds, though systems do not all handle leap seconds—the occasional adjustments used to keep civil time aligned with Earth’s rotation—in exactly the same way. For ordinary computing, the epoch offers a simple ruler. Its memorable trick is that a date becomes arithmetic, while the choice of where to put zero remains just that: a choice.
