What Is a Unix Timestamp?

What Is a Unix Timestamp?

If you’ve looked at a database, an API response, or a log file, you’ve seen a number like 1750000000 sitting where a date should be. That’s a Unix timestamp — and it’s how computers have counted time for over 50 years.

What it is

A Unix timestamp is the number of seconds since January 1, 1970, 00:00:00 UTC — the “Unix epoch.” Right now it’s somewhere north of 1.75 billion.

Why 1970? The original Unix developers picked a round, recent date as the starting point. It stuck, and now it’s the universal reference — every timezone, language, and database can agree on it because it’s just a number.

Why programmers love it

  • Timezone-free: the same timestamp means the same instant everywhere. 1750000000 is the same moment in Tokyo and New York — display it in any timezone later.
  • Sortable and comparable: chronological order is numeric order. No date-parsing ambiguity (03/04/2026 — March or April?).
  • Compact: one integer replaces a formatted date string.

The practical bits

  • Seconds vs milliseconds: JavaScript and many systems use millisecond timestamps (13 digits, e.g. 1750000000000). Divide by 1000 (or drop three zeros) to get seconds. Mismatching the two is the #1 timestamp bug.
  • 2038 problem: 32-bit systems storing signed seconds will overflow in January 2038. Modern 64-bit systems are fine for billions of years.
  • Negative timestamps mean dates before 1970.

Converting

The Unix timestamp converter translates in both directions instantly: paste a timestamp and see the human date in your local timezone (or UTC), or pick a date and get its timestamp. It also shows the current timestamp live — handy for API debugging when you need “now” as a number.