Convert Unix timestamps to human-readable dates and vice versa. Supports seconds and milliseconds.
A Unix timestamp (also called Epoch time or POSIX time) counts the number of seconds since January 1, 1970, 00:00:00 UTC. It provides a single integer that unambiguously represents a point in time, regardless of time zones.
| Timestamp | Date | Event |
|---|---|---|
| 0 | Jan 1, 1970 | Unix epoch start |
| 1000000000 | Sep 9, 2001 | Billennium |
| 2147483647 | Jan 19, 2038 | Y2K38 (32-bit overflow) |
32-bit systems store timestamps as a signed integer that maxes out at 2,147,483,647 (Jan 19, 2038). After that, it overflows to a negative number. Most modern systems use 64-bit timestamps, which last until the year 292 billion.
Unix time does not count leap seconds. Each day is exactly 86,400 seconds. When a leap second occurs, the Unix clock repeats a second.
Enter a Unix timestamp (seconds or milliseconds since Jan 1, 1970 UTC) to convert to a human-readable date, or enter a date to get the timestamp.
Unix Timestamp = number of seconds since 1970-01-01 00:00:00 UTC (epoch). JavaScript uses milliseconds. Current timestamp increments by 1 each second.
Timestamp 1744531200 = 2025-04-13 00:00:00 UTC. The current timestamp is approximately 1.78 billion. The "Year 2038 problem" occurs when 32-bit timestamps overflow.
Store timestamps in UTC, convert to local time on display. JavaScript: Date.now() returns milliseconds, PHP: time() returns seconds. The 2038 problem (32-bit overflow) is already being addressed by 64-bit systems.