Timestamp Converter
Unix time in both directions, with seconds-vs-milliseconds auto-detected.
Current Unix time:
paste a timestamp above
Unix seconds: —
Converted on your device.
Timestamp landmarks
| Timestamp | Moment |
|---|---|
| 0 | Jan 1, 1970 — the epoch |
| 1000000000 | Sep 9, 2001 — billennium |
| 1234567890 | Feb 13, 2009 — the party one |
| 2000000000 | May 18, 2033 |
| 2147483647 | Jan 19, 2038 — 32-bit overflow |
Common questions
What is a Unix timestamp?
The number of seconds elapsed since January 1, 1970 UTC (the "epoch") — the universal way computers store moments in time, immune to time zones and date formats. Right now it's a ten-digit number a little over 1.7 billion.
Why does my timestamp have 13 digits?
It's in milliseconds — JavaScript and many APIs use ms. Up to ten digits reads as seconds; anything longer reads as milliseconds (a number that big can't sanely be seconds — it would mean year 2286+). The converter auto-detects.
What is the year 2038 problem?
Systems storing timestamps as signed 32-bit integers overflow on January 19, 2038, at 03:14:07 UTC — the timestamp exceeds 2,147,483,647 and wraps negative. Modern 64-bit systems are fine for the next 292 billion years.
Why do my local and UTC times differ?
A timestamp is an absolute moment; the two lines show that same moment expressed in your time zone and in UTC. Logs and databases usually speak UTC, which is why "the error happened at 3 PM" rarely matches what the log says.