Unix Timestamp Converter
Paste a Unix timestamp and see the human-readable date and time instantly - or type a date and get the timestamp back. Auto-detects whether your number is in seconds, milliseconds, or microseconds.
That was
All formats
Timeline ?
Y2K38 ? - January 19, 2038, when 32-bit timestamps overflow.
Paste one timestamp or date per line. Accepts Unix seconds, milliseconds, microseconds, and ISO date strings.
Learn more: Unix time, epochs, and the Year 2038 problem
How Unix timestamps and precision work
Wikipedia defines Unix time as the number of non-leap seconds since 00:00:00 UTC on 1 January 1970. For example, 1700000000 is 22:13:20 UTC on 14 November 2023.
In Auto mode the converter reads the size of the number. Below 10 billion is seconds, below 10 trillion is milliseconds and anything larger is microseconds. That matches 10-digit, 13-digit and 16-digit timestamps. Negative numbers are judged by size, so dates before 1970 work.
GPS and NTP epochs, and what the converter does not correct
The epoch selector shifts by a fixed gap. GPS time counts from 6 January 1980, which is 315,964,800 seconds after the Unix epoch, so a GPS value of 0 converts to 1980-01-06. NTP counts from 1 January 1900, as Wikipedia's NTP entry notes, so an NTP value of 2,208,988,800 is the Unix epoch.
The shift is only the epoch gap. Per Wikipedia's leap second entry, GPS time is not adjusted for leap seconds, and TAI is always exactly 19 seconds ahead of it. The converter applies no leap-second correction, so a GPS-derived date is off from UTC by the leap seconds added since 1980.
Well-known timestamps
These are the values people most often search for, with the UTC date each one lands on. Paste any of them into the converter to see the other formats.
| Timestamp | UTC date and time | Day | Why it matters |
|---|---|---|---|
| 0 | 1970-01-01T00:00:00Z | Thursday | The Unix epoch |
| 946684800 | 2000-01-01T00:00:00Z | Saturday | Y2K, 1 January 2000 |
| 1000000000 | 2001-09-09T01:46:40Z | Sunday | One billion seconds |
| 1234567890 | 2009-02-13T23:31:30Z | Friday | The counting sequence |
| 1500000000 | 2017-07-14T02:40:00Z | Friday | One and a half billion |
| 1600000000 | 2020-09-13T12:26:40Z | Sunday | One point six billion |
| 1700000000 | 2023-11-14T22:13:20Z | Tuesday | One point seven billion |
| 2000000000 | 2033-05-18T03:33:20Z | Wednesday | Two billion seconds |
| 2147483647 | 2038-01-19T03:14:07Z | Tuesday | Largest signed 32-bit value |
Link to this tool
Sharing or citing this calculator? Copy a link in the format you need.
https://bentoutils.com/apps/unix-timestamp-converter/<a href="https://bentoutils.com/apps/unix-timestamp-converter/">Unix Timestamp Converter</a>[Unix Timestamp Converter](https://bentoutils.com/apps/unix-timestamp-converter/)<a href="https://bentoutils.com/apps/unix-timestamp-converter/"><img src="https://bentoutils.com/public/og/unix-timestamp-converter-v1.png" alt="Unix Timestamp Converter" width="600" height="315"></a>Unix Timestamp Converter. BentoUtils. October 5, 2026. https://bentoutils.com/apps/unix-timestamp-converter/A day is 86,400 seconds, so adding 86,400 to a timestamp moves it forward one day in UTC. A week is 604,800 seconds.
The Year 2038 problem is an overflow, not a leap-second issue
The largest value a signed 32-bit integer can hold is 2,147,483,647. Wikipedia's Year 2038 entry puts that at 03:14:07 UTC on 19 January 2038. One second later such a counter wraps to 20:45:52 UTC on 13 December 1901.
The same entry says a signed 64-bit value moves the wraparound about 292 billion years away. Leap seconds are a separate matter: Unix time handles them by repeating a second rather than changing the count.
NTP has its own rollover. Its 32-bit seconds field rolls over every 136 years, with the first rollover on 7 February 2036.
Batch conversion and the range of dates
Batch mode takes one value per line, either a number or date text such as 2023-11-14. Lines it cannot read, including numbers too large for a date, show as unrecognised. A JavaScript Date holds at most 8.64 quadrillion milliseconds either side of 1970, as MDN explains.
The CSV export puts quotes around any input that contains a comma, so "Nov 14, 2023" stays in one column.
FAQ
How do I tell if a timestamp is in seconds or milliseconds?
Check the size. Ten digits like 1700000000 is seconds, 13 digits like 1700000000000 is milliseconds and 16 digits is microseconds. Auto mode applies these thresholds: below 10 billion is seconds and below 10 trillion is milliseconds.
Will the Year 2038 problem affect JavaScript's Date object?
No. MDN says a Date holds up to 8.64 quadrillion milliseconds either side of 1970, which reaches the year 275760. The problem affects systems that store Unix time in a signed 32-bit integer.
Why does GPS time not match UTC exactly?
GPS time is not adjusted for leap seconds, so it drifts from UTC each time one is added. This converter only shifts by the epoch gap, so GPS-derived dates are off from UTC by the leap seconds added since 1980.