The current Unix timestamp, ticking live — plus a two-way converter. Paste any epoch timestamp (seconds or milliseconds, detected automatically) to see it as local time, UTC and ISO 8601, or pick a date to get its timestamp.
📌 Unix time is always UTC — the same instant everywhere on Earth. Timezones only appear when a timestamp is formatted into a human-readable date.
Share:
What is Unix time?
Unix time (also called epoch time or POSIX time) counts the seconds elapsed since the Unix epoch: January 1, 1970 at 00:00:00 UTC. It is a single integer with no timezone, no daylight-saving rules and no calendar quirks, which is why nearly every operating system, database and programming language uses it internally to store points in time.
The conversion is simple arithmetic. A timestamp of 1,793,145,600 means 1,793,145,600 seconds after the epoch: divide by 86,400 seconds per day to get 20,754 days, which lands on October 28, 2026 at 00:00:00 UTC. Going the other way, midnight UTC on January 1, 2026 is 20,454 days × 86,400 s = 1,767,225,600.
Seconds vs milliseconds — why the confusion?
Classic Unix time is measured in seconds, but JavaScript's Date.now() and Java's System.currentTimeMillis() return milliseconds. Mixing them up is one of the most common date bugs: feed a seconds value where milliseconds are expected and every date collapses to January 1970; do the reverse and dates jump tens of thousands of years into the future. The tell is the digit count — current timestamps have 10 digits in seconds and 13 in milliseconds — and this converter uses exactly that to auto-detect which one you pasted.
The year 2038 problem
Older systems store Unix time as a signed 32-bit integer, which maxes out at 2,147,483,647. That value is reached on January 19, 2038 at 03:14:07 UTC — one second later the counter overflows and wraps around to December 1901. Modern 64-bit systems already store timestamps in 64 bits (good for about 292 billion years), but embedded devices, old file formats and legacy databases still carry the 32-bit limit, making 2038 a slow-motion Y2K for unpatched systems.
Frequently asked questions
The live counter at the top of this page shows the current Unix timestamp in seconds, updating every second. It is the number of seconds elapsed since January 1, 1970 at 00:00:00 UTC — as of 2026 the value is around 1.79 billion.
JavaScript: Math.floor(Date.now() / 1000) — note Date.now() itself returns milliseconds. Python: int(time.time()) after import time. Excel: =(A1 - DATE(1970,1,1)) * 86400 converts a date cell A1 to Unix seconds (assumes the cell is in UTC), and =A1/86400 + DATE(1970,1,1) converts back.
No. A Unix timestamp is always counted in UTC and identifies one exact instant worldwide — 1793145600 is the same moment in New York, London and Tokyo. Timezones only come into play when you format the timestamp into a human-readable date, which is why this converter shows both your local time and UTC.
Classic Unix time is in seconds, but JavaScript (Date.now()) and Java (System.currentTimeMillis()) use milliseconds, so both are common in the wild. A current seconds value has 10 digits while milliseconds have 13, and this converter auto-detects which one you pasted from its size.
No. Unix time pretends every day has exactly 86,400 seconds, so the 27 leap seconds added since 1972 are absorbed rather than counted. For everyday timestamps this makes no practical difference — it only matters in scientific applications that need true elapsed atomic time.