How to use
- Paste a timestamp, or tap Now for the current one.
- Leave the unit on Detect from the length, or choose seconds, milliseconds, microseconds or nanoseconds.
- Read the date in UTC, in your time zone and as ISO 8601.
- To go the other way, choose Date → timestamp.
How Unix time works
- Unix time counts the seconds from 00:00:00 UTC on 1 January 1970, called the epoch.
- Every day counts as exactly 86,400 seconds, so leap seconds are ignored.
- Times before 1970 are negative.
timestamp = days since 1970-01-01 × 86,400 + seconds since midnight (UTC)
Examples
- 1700000000 is 22:13:20 UTC on Tuesday 14 November 2023 (ISO 8601: 2023-11-14T22:13:20Z).
- 1700000000123 has 13 digits, so it is read as milliseconds: 2023-11-14T22:13:20.123Z.
- −86400 is 00:00:00 UTC on 31 December 1969.
- 00:00 UTC on 1 January 2026 is 1767225600.
Famous timestamps
| Timestamp | Date and time (UTC) |
|---|---|
| 0 | 1970-01-01 00:00:00 |
| 1,000,000,000 | 2001-09-09 01:46:40 |
| 1,234,567,890 | 2009-02-13 23:31:30 |
| 2,000,000,000 | 2033-05-18 03:33:20 |
| 2,147,483,647 | 2038-01-19 03:14:07 |
| −2,147,483,648 | 1901-12-13 20:45:52 |
Seconds or milliseconds?
| Digits in a current timestamp | Unit |
|---|---|
| 10 | Seconds |
| 13 | Milliseconds |
| 16 | Microseconds |
| 19 | Nanoseconds |
The year 2038 problem
Older systems store Unix time in a signed 32-bit integer, which tops out at 2,147,483,647. That is 03:14:07 UTC on 19 January 2038. One second later the counter overflows, so these systems need 64-bit time.
The same limit applies backwards: the earliest 32-bit time is 20:45:52 UTC on 13 December 1901.
Converting a meeting time instead? Use the time zone converter.