Understanding the result
For a timestamp, the result shows the moment in UTC (as an ISO 8601 string and in words), in your device's time zone and as milliseconds. The unit you selected is stated above the results, so a value is never silently read as the wrong unit.
For a date and time, the result shows the Unix timestamp in seconds and milliseconds and the equivalent UTC time. The current Unix timestamp is shown at the top and can be copied.
What is a Unix timestamp?
A Unix timestamp counts the seconds that have passed since 00:00:00 UTC on 1 January 1970, the Unix epoch. It identifies a single moment in time regardless of time zone, which makes it popular in databases, APIs and log files.
Many systems and languages, including JavaScript, use milliseconds instead of seconds, which produces a 13-digit number today rather than a 10-digit one.
How it works
A seconds timestamp is multiplied by 1,000 to give milliseconds. The moment is then displayed in UTC and in your time zone using your browser's time zone data, so daylight saving is handled correctly.
Negative timestamps are moments before 1970. Timestamps up to about 275,760 years either side of 1970 can be represented.
Converting a date and time to a timestamp uses the time zone you select. For a local time that does not exist (skipped by a clock change) or that happens twice, the tool tells you how it was interpreted.
Examples
1700000000
As seconds this is 14 November 2023, 22:13:20 UTC. As milliseconds, 1700000000000 is the same moment.
0 and -1
0 is 1 January 1970, 00:00:00 UTC. -1 is one second earlier, 31 December 1969 at 23:59:59 UTC.
2147483648
This is 19 January 2038, 03:14:08 UTC, one second past the largest value a signed 32-bit counter can hold. JavaScript dates and 64-bit systems continue past it without a problem.
Things to keep in mind
- Check the unit. A 13-digit number is almost certainly milliseconds; the tool suggests the switch if you enter one as seconds.
- A Unix timestamp has no time zone. Time zones only matter when you display it or when you convert a local date and time into one.
- Leap seconds are not counted in Unix time: each day is treated as exactly 86,400 seconds.
- The "2038 problem" affects software that stores time in a signed 32-bit integer. It does not apply to JavaScript dates, which use a 64-bit floating-point number of milliseconds.