Unix Timestamps Explained (Epoch Time in Plain English)

A Unix timestamp is the number of seconds elapsed since midnight UTC on January 1, 1970 — a moment called the Unix epoch. That's the whole idea: instead of juggling years, months, days, hours, and time zones, a single integer pins down an exact instant. 0 is the epoch itself; 1,000,000,000 was September 9, 2001; numbers around 1.78 billion land in 2026.

Computers love this format because comparing two moments becomes comparing two numbers, and the duration between them is simple subtraction. That's why timestamps fill log files, APIs, databases, and file metadata everywhere.

The classic gotcha: Unix time is traditionally in seconds, but JavaScript's Date.now() and many APIs report milliseconds. A current timestamp in seconds has 10 digits; in milliseconds, 13. Treat one as the other and your date lands in 1970 (milliseconds read as seconds) or some fifty-thousand years in the future (the reverse).

If a conversion gives you a nonsense date, check the digit count first. The timestamp converter on this site auto-detects the unit by length, but when writing code you'll multiply or divide by 1,000 yourself.

A Unix timestamp is always anchored to UTC — the same instant everywhere on Earth. The number doesn't change when you cross time zones; only the human-readable rendering does. 1,780,000,000 seconds is one specific moment, displayed as one wall-clock time in New York and another in Tokyo.

This is exactly why systems store timestamps and convert to local time only at display. Storing 'wall clock' times without zone info is how bugs like double-booked meetings and daylight-saving-time chaos happen. Rule: store UTC timestamps, render local.

Older systems store Unix time as a signed 32-bit integer, which maxes out at 2,147,483,647 — corresponding to 03:14:07 UTC on January 19, 2038. One second later, the value overflows and wraps to 1901. Modern 64-bit systems have effectively solved this (their limit is hundreds of billions of years away), but embedded devices, old file formats, and legacy databases still carry the risk.

One more nuance for the curious: Unix time officially ignores leap seconds — each day is defined as exactly 86,400 seconds, and the occasional leap second is absorbed rather than counted. For virtually all everyday purposes this never matters, but it explains tiny discrepancies in scientific timekeeping contexts.