Developer Utilities
4 min read• Published 11/10/2026Unix Epoch Time: How Timestamps and Daylight Saving Time Work
Understanding seconds since January 1, 1970, UTC offsets, and the Year 2038 Problem
Executive Summary
Unix time represents the total seconds elapsed since January 1, 1970 00:00:00 UTC. Discover how it solves timezone chaos and how to convert it across world cities.
## What Is Unix Epoch Time?
Unix time (also known as POSIX time or Epoch time) is an unambiguous system for tracking a point in time. It is defined as the number of non-leap seconds that have elapsed since the **Unix Epoch**: midnight Coordinated Universal Time (00:00:00 UTC) on **January 1, 1970**.
Because Unix timestamps are stored as a single integer, computers can compare, sort, and subtract dates across any international boundary without dealing with local daylight saving time rules or timezone shifts.
### The Year 2038 Problem (Y2038)
Systems that store Unix timestamps as a signed 32-bit integer will overflow at **03:14:07 UTC on Tuesday, 19 January 2038** (when the count exceeds 2,147,483,647). After this second, the integer wraps around to -2,147,483,648, representing the year 1901.
Modern 64-bit operating systems and database architectures (such as PostgreSQL and 64-bit Node.js) store timestamps as signed 64-bit integers, pushing the expiration date approximately 292 billion years into the future.
Frequently Asked Questions
Does Unix time count leap seconds?
Unix time ignores leap seconds. Each day is treated as having exactly 86,400 seconds. When UTC introduces a leap second, the clock repeats or steps back to stay synchronized.
How do I convert a Unix timestamp to human-readable date in JavaScript?
In JavaScript, pass the timestamp multiplied by 1000 into the Date constructor: new Date(timestamp * 1000).toLocaleString().