Overview
Computers often store time as a Unix timestamp: the number of seconds since 00:00:00 UTC on 1 January 1970. This converter turns a date and time into that number.
Enter the date and time in UTC.
Worked examples
| Inputs | Result |
|---|---|
| Date (UTC): year2,026Date (UTC): month (1-12)1Date (UTC): day (1-31)1Time (UTC): hour (0-23)0Time (UTC): minute (0-59)0Second (0-59)0 | Unix timestamp: 1767225600Milliseconds: 1767225600000ISO 8601: 2026-01-01T00:00:00Z |
Show 2 more examples
| Date (UTC): year2,000Date (UTC): month (1-12)1Date (UTC): day (1-31)1Time (UTC): hour (0-23)0Time (UTC): minute (0-59)0Second (0-59)0 | Unix timestamp: 946684800Milliseconds: 946684800000ISO 8601: 2000-01-01T00:00:00Z |
| Date (UTC): year2,038Date (UTC): month (1-12)1Date (UTC): day (1-31)19Time (UTC): hour (0-23)3Time (UTC): minute (0-59)14Second (0-59)7 | Unix timestamp: 2147483647Milliseconds: 2147483647000ISO 8601: 2038-01-19T03:14:07Z |
How it works
The timestamp counts every second since the Unix epoch, ignoring leap seconds. JavaScript and many APIs use milliseconds, which are 1,000 times larger.
The formula
Timestamp = seconds between 1970-01-01T00:00:00Z and the date
| UTC | Enter the time in UTC, not local time |
Practical tips
- 1 January 2026 00:00 UTC is 1767225600.
- Convert local time to UTC first, for example with the time zone converter.
- 32-bit signed timestamps overflow on 19 January 2038.
Frequently asked questions
Seconds or milliseconds?
Unix systems use seconds; JavaScript’s Date.now() uses milliseconds.
Can timestamps be negative?
Yes, for dates before 1970.