Unix Epoch Time Explained

What Is Unix Epoch Time?

Unix epoch time (also known as POSIX time or Unix time) is a system for tracking time as a running count of seconds since the Unix epoch: January 1, 1970, 00:00:00 UTC. At that exact moment, the epoch value was 0. One minute later it was 60, one hour later 3600, and one day later 86400.

Why January 1, 1970?

The date was chosen by the early Unix developers at Bell Labs. When Ken Thompson and Dennis Ritchie designed the original Unix system in the late 1960s, they needed a reference point. The choice of 1970 was pragmatic — it was a round, recent date that allowed the 32-bit signed integer they used for storage to span a reasonable range into the future (until 2038).

How Epoch Time Works

Epoch = 0           → 1970-01-01 00:00:00 UTC
Epoch = 86400       → 1970-01-02 00:00:00 UTC
Epoch = 1000000000  → 2001-09-09 01:46:40 UTC
Epoch = 1700000000  → 2023-11-14 22:13:20 UTC

Every timestamp is simply the count of seconds from that origin. Negative values represent dates before 1970. The system is timezone-agnostic because it always counts from UTC, making it ideal for storing and comparing times across distributed systems.

Seconds vs Milliseconds

While the traditional Unix epoch counts seconds, many modern environments (JavaScript, Java, certain databases) use milliseconds since the epoch. A seconds-based timestamp has 10 digits (e.g., 1700000000), while a milliseconds-based one has 13 digits (e.g., 1700000000000). Always check which unit a system expects to avoid off-by-1000 errors.

Why It Matters

Epoch time is the lingua franca of time representation in computing. APIs exchange it, databases index it, log files record it, and cron jobs schedule around it. Understanding epoch time is fundamental to debugging any time-related issue.