Unix Timestamp
See the current epoch time tick live, and convert any Unix timestamp — in seconds or milliseconds — into UTC and your own timezone.
Paste a Unix timestamp above to see it in UTC and your local time.
What is a Unix timestamp?
A Unix timestamp — also called epoch time — is simply the number of seconds since 1970-01-01 00:00:00 UTC, not counting leap seconds. Because it's a single integer with no timezone attached, it's the most portable way to store and compare points in time. Many languages and databases use milliseconds instead — the same count multiplied by 1000.
The Year 2038 problem — the day 32-bit time runs out
For decades, Unix time was stored in a signed 32-bit integer. That data type can hold a maximum value of 2,147,483,647 — and that many seconds after the epoch lands on a very specific instant:
03:14:07 UTC · Tuesday, 19 January 2038
One second later, the counter has no bigger number to move to, so it overflows: it wraps around to the most negative value it can hold and is suddenly interpreted as 13 December 1901. Time, from the computer's point of view, jumps backwards by 136 years. This is often nicknamed the “Epochalypse” — the 32-bit sibling of the Y2K bug.
Why unmigrated database fields are the real risk
The problem isn't only old operating systems — it's the database columns that store epoch seconds. A classic example is the MySQL TIMESTAMP type, which is internally a 32-bit value and only spans 1970-01-01 to 2038-01-19 03:14:07 UTC. Any row you try to write beyond that instant either overflows, wraps to 1901, or is rejected outright. The same applies to any custom INT column that someone used to store a Unix timestamp years ago and never revisited.
The fix is migration: move those fields to a 64-bit integer (BIGINT) or a dedicated date/time type such as DATETIME / TIMESTAMPTZ. A signed 64-bit counter pushes the overflow roughly 292 billion yearsinto the future — comfortably past any deadline worth worrying about. The catch is that this migration has to happen deliberately, table by table, well before 2038 — which is why it's worth flagging now.
FAQ
- Seconds or milliseconds — which does the converter expect?
- By default it auto-detects: large values (13-digit-ish) are read as milliseconds, shorter ones as seconds. You can force either unit with the toggle if a value is ambiguous.
- Does my timestamp get sent anywhere?
- No. The page is fully static and all conversion happens in your browser — nothing you paste leaves your device.