What the result means
A Unix timestamp counts the time since 1 January 1970 at 00:00:00 UTC (the Unix epoch). Many systems count in seconds, JavaScript and many APIs count in milliseconds, and some databases use microseconds. When the unit is on Auto-detect, the tool guesses it from the size of the number:
| Digits (today) | Unit |
|---|---|
| 10 | Seconds, for example 1700000000 |
| 13 | Milliseconds, for example 1700000000000 |
| 16 | Microseconds, for example 1700000000000000 |
Results are shown in UTC, in your own time zone, in ISO 8601 format, and relative to now.
Example
1700000000
UTC: Tue, 14 Nov 2023 22:13:20 GMT
ISO: 2023-11-14T22:13:20.000Z
Limits
- Auto-detect is a guess based on size. Pick the unit yourself if the result looks wrong.
- A timestamp has no time zone. The zone only matters when it is shown as a date, so check whether a date means UTC or local time.
- Leap seconds are ignored, as in standard Unix time.
- Dates are limited to the range JavaScript supports (about 270,000 years either side of 1970).
FAQ
Why is my timestamp off by exactly a few hours?
Usually the date was read in one time zone and written in another. Compare the UTC row with your local row.
What is the year 2038 problem?
Systems that store seconds in a signed 32-bit integer overflow on 19 January 2038. Modern 64-bit systems are not affected.
How do I get the current timestamp?
The box at the top shows it live in seconds and milliseconds. Press Use now to convert it.