The current time, ticking live — click a chip to copy it.
Timestamp → date
| Detected as | |
|---|---|
| Local time | |
| UTC (ISO 8601) | |
| Relative |
Date → timestamp
| Unix seconds | |
|---|---|
| Unix milliseconds |
Convert Unix timestamps to human dates and dates back to timestamps — seconds or milliseconds, in your local time and UTC, with relative time and a live clock.
100% free · No sign-up · No daily limits · No watermarks · Processed in your browser — files never leave your device
Convert Unix timestamps to human dates and dates back to timestamps — seconds or milliseconds, in your local time and UTC, with relative time and a live clock.
The timestamp 1700000000 converts to Tuesday, 14 November 2023, 22:13:20 UTC — a date the internet actually celebrated, because round epoch numbers are rare. In milliseconds the same instant is 1700000000000: same moment, thousand-fold number, and the converter tells you which one you pasted instead of guessing silently.
A Unix timestamp counts seconds since 1 January 1970, 00:00 UTC (the epoch). The converter multiplies or divides by 1000 to move between the seconds and milliseconds conventions, then renders the instant through your timezone for the local row and through UTC for the ISO 8601 row. Detection is by magnitude: values of a trillion or more are read as milliseconds, smaller values as seconds — the rule that matches how real systems store them. Relative time compares the instant with your device clock.
Seconds — it is 14 November 2023. Milliseconds values for the present era have 13 digits (1700000000000), seconds have 10. The converter detects it by size and tells you which it assumed, so you can spot unit bugs in your own data.
They are probably both right: servers usually log in UTC, while this page shows your local timezone on the first row and UTC on the second. Compare the UTC row with your logs; the local row is the same instant translated for where you are.
Midnight at the start of 1 January 1970 UTC — the zero point from which Unix time counts. It was chosen by the early Unix engineers as a round, recent date, and it stuck: nearly every programming language, database and API on earth can speak it.
Systems storing seconds in a signed 32-bit integer overflow on 19 January 2038 — the “year 2038 problem”. 64-bit timestamps (and milliseconds values) push the limit millions of years out, which is why modern systems are unaffected.
Yes — those are negative timestamps, and the converter accepts them (try -86400 for 31 December 1969, 00:00 UTC). Dates before 1970 matter for birthdays, historical data and anywhere a system naively rejects “impossible” negative values.