gizmobench

Unix Timestamp Converter

Convert a Unix timestamp to a date and a date back to a Unix timestamp, with the unit set to seconds and 1735689600 already in the box, so the answer is on screen before you type anything. The tool page reads whichever unit your number looks like; this page has been told it is seconds, which is what a ten-digit timestamp almost always is. The table underneath gives the timestamp at the start of every year from 2020 to 2035.

Current Unix time            · your local time
Convert a timestamp or date
Unit
Zone

The Unix timestamp at the start of each year

Midnight UTC on 1 January, in seconds and in milliseconds. Every row is the converter's own reading of that date, so the table and the tool above cannot disagree. A year is 31,536,000 seconds, or 31,622,400 when a 29 February falls in it.

Start of year (UTC)Unix secondsMilliseconds
1 January 202015778368001577836800000
1 January 202116094592001609459200000
1 January 202216409952001640995200000
1 January 202316725312001672531200000
1 January 202417040672001704067200000
1 January 202517356896001735689600000
1 January 202617672256001767225600000
1 January 202717987616001798761600000
1 January 202818302976001830297600000
1 January 202918619200001861920000000
1 January 203018934560001893456000000
1 January 203119249920001924992000000
1 January 203219565280001956528000000
1 January 203319881504001988150400000
1 January 203420196864002019686400000
1 January 203520512224002051222400000

Common questions

What is a Unix timestamp?
The number of seconds since midnight UTC on 1 January 1970, counted without leap seconds. It names an instant and carries no time zone, which is why 1735689600 is the start of 2025 in London and the evening of 31 December 2024 in New York: one number, two clock readings.
How do I convert a date to a Unix timestamp?
Type the date into the box instead of a number. 2025-01-01, 1 Jan 2025 14:30 and 2025-01-01T00:00:00Z are all read, and the Seconds row of the answer is the timestamp. A written date carries its own scale, so the unit control above is left out of it, and the line under the answer says the input was read as a date.
Is my number in seconds or milliseconds?
Count the digits: ten is seconds until the year 2286, thirteen is milliseconds. Reading one as the other is the mistake that silently lands you in 1970 or in the year 56000: 1735689600 is 2025-01-01T00:00:00.000Z as seconds and 1970-01-21T02:08:09.600Z as milliseconds. The unit control settles it when the digits lie, and it also covers microseconds and nanoseconds.
Does the timestamp change with my time zone?
No. The number is the same everywhere; only the way it is written out changes. The Local and UTC control switches which zone the readable rows are printed in, and the Seconds and Milliseconds rows do not move when you use it.
What happens to Unix time in 2038?
A signed 32-bit integer runs out at 2147483647 seconds, which is 2038-01-19T03:14:07.000Z. Systems that still store timestamps that way will wrap; this converter holds the value as a double, so dates well beyond 2038 and before 1970 both convert here. The table below stops at 2035 because that is as far as the question usually goes, not because the tool does.
Do leap seconds count?
No, and that is by definition rather than by omission. Unix time treats every day as exactly 86,400 seconds, so a leap second is not given a number of its own. That is why a timestamp converts to a date with plain arithmetic and no table of leap seconds is involved.

Exact to the second, and to the millisecond where your input carries them. Conversions use UTC internally and display your local zone alongside, so the two are never confused. Dates before 1970 and beyond 2038 are handled.