Daylight Saving Time Calculator

What this countdown is counting to

This page counts down to the next daylight saving change in the region you pick, and shows the date it lands on, the local clock time at the moment of the change, and the UTC offset on each side of it. Your region is preselected from the time zone your device reports; change the dropdown and everything below it updates. All of the arithmetic runs in your browser, so there is no lookup to a server and nothing is stored.

Only two things can happen to a clock. When the clocks go forward, an hour is skipped and local time jumps ahead: in most regions the change is applied between 2:00 a.m. and 3:00 a.m. When the clocks go back, an hour is repeated and local time falls behind. In the northern hemisphere the forward change happens in spring and the back change in autumn. In the southern hemisphere the pair is the other way round, which is why Australia and New Zealand change in April and October.

The 2026 clock changes, region by region

A region's dates come from a rule rather than a fixed list. Most rules read "the second Sunday in March" or "the last Sunday in October", which is why the date moves from one year to the next while the pattern stays the same. The table gives the rule and both 2026 dates for every region the tool covers.

The northern and southern hemispheres swap the pair rather than using different arithmetic: Australia's forward change in October is the same "first Sunday" rule applied to its own spring. Mexico is the awkward row. Most of the country stopped changing its clocks, but the northern border strip keeps the United States dates, so Tijuana changes on 1 November 2026 with California while Mexico City does not change at all.

One consequence is worth knowing before you book a call. The United Kingdom and central Europe change on 25 October 2026, a week before the United States and Canada. For that week London is only four hours ahead of New York instead of the usual five, because New York is still on daylight time while London has already gone back to standard time.

Places that never change the clocks

Daylight saving is not a global custom, and quite a few large places have never used it or have stopped. Near the equator the length of the day barely moves through the year, so shifting an hour of it from morning to evening buys nothing. Countries that are very wide but keep one clock, such as China and India, have a harder problem: their eastern and western edges already live hours apart on the same clock, so a national shift helps one end and hurts the other. Elsewhere it is simply a local decision, which is why a single country can disagree with itself.

How the dates are worked out

The countdown is not a lookup table of published dates. The page holds the rule for each region and derives the date every time it renders, which is why it can show 2027 without anyone editing it. Two steps are involved.

First, find the day. The second Sunday in March 2026 is 8 March, because 1 March 2026 is itself a Sunday and the second one is a week later. The first Sunday in November 2026 is 1 November, because 1 November 2026 is a Sunday. The last Sunday in October 2026 is 25 October: the last day of that month is a Saturday, so the Sunday before it is the last Sunday.

Second, convert that local moment into a UTC instant, by subtracting the offset the zone was on just before the change. New York goes back at 2:00 a.m. on 1 November 2026 while still on UTC-04:00, which is 06:00 UTC. London goes back exactly a week earlier at 2:00 a.m. on 25 October while on UTC+01:00, which is 01:00 UTC. The tool shows that instant as well, because a stored timestamp is always in UTC and the local clock time is the part that moves.

The dates in the tables above and the countdown itself were checked against the IANA time zone database, which is the same source operating systems use to decide what time it is. If a region changes its rule, the database changes with it.

What the extra hour does to your day

The hour is real, but it is not extra daylight. The sun is not affected by the clock; daylight saving moves an hour of light from one end of the day to the other. Going forward in spring trades a darker morning for a brighter evening. Going back in autumn does the reverse, and the hour you gain is the hour that comes back to the morning.

The arithmetic is worth stating plainly. If sunset came at 5:50 p.m. on the Saturday before the change, then on the Sunday, with the clock set back an hour, sunset arrives at about 4:50 p.m. The sun set at the same moment; the clock reading moved. Sunrise moves the same way, which is why late October and early November mornings are suddenly lighter than the evenings.

The famous "extra hour of sleep" is optional. It exists only if you are asleep when the change happens and you wake on your usual schedule. Anyone working a night shift, or awake at that hour, simply watches the same hour arrive twice, which is why payroll and timesheet systems for that night usually count hours worked rather than reading a clock.

Schedules, devices and the hour that happens twice

Phones and computers with automatic time zones handle the change without help, and they use the same rule data this page does. Watches, ovens, car clocks and wall clocks do not, and the ones that read the wrong time for a week are usually those.

Going back is the harder of the two directions, because the local hour before the change happens twice. In New York the clock reads 1:00 a.m. to 2:00 a.m. twice on the night of 1 November 2026, and anything stamped with a local wall-clock time in that window is ambiguous. In London the repeated window is 1:00 a.m. to 2:00 a.m. on 25 October; in Berlin it is 2:00 a.m. to 3:00 a.m. Going forward is the opposite problem: the local hour between 2:00 a.m. and 3:00 a.m. does not exist in New York on 8 March 2026, so a wall-clock time inside it cannot be resolved at all.

That is the practical reason to store timestamps in UTC and convert only for display, which is what the Unix timestamp converter is for. It also matters for scheduled jobs: a task set for 2:30 a.m. local time runs twice, once, or not at all on a changeover night, depending on how the scheduler treats the missing or repeated hour. The cron expression generator builds the expression and shows the next run times, and the safest habit for that one night is to schedule the job in UTC. More seasonal calculators, including the holiday ones this page sits beside, are collected on the holiday and seasonal tools page.

Why the change lands in the small hours of a Sunday

A Sunday morning is when the fewest people are commuting, trading or travelling, so an hour that disappears or arrives twice disturbs the smallest number of schedules. The hour matters too: the change is made in the middle of the night rather than at midnight so that the date does not become ambiguous along with the time. A midnight change would make 2 November start twice in the same region, which is a much harder problem for anything that records dates than a repeated hour is.

Regions do not agree on the exact hour, and the tool prints the one that applies. The United States and Canada change at 2:00 a.m. local time, the United Kingdom changes when 1:00 a.m. UTC arrives, which is 1:00 a.m. in March and 2:00 a.m. in October on a London clock, and central Europe changes at the same UTC instant, which its own clock reads as 2:00 a.m. in March and 3:00 a.m. in October. Australia and New Zealand change at 2:00 a.m. local time in their spring and at 3:00 a.m. in their autumn.

FAQ

When do the clocks go back in 2026?

In the United States and most of Canada, on Sunday 1 November 2026. In the United Kingdom and central Europe, on Sunday 25 October 2026. Australia and New Zealand are in the southern hemisphere, so their clocks went back on 5 April 2026 and go forward again in October.

Do the clocks go forward or back in November?

Back, in every northern hemisphere region on this page. Going back means an hour is repeated rather than skipped, so the evening gets darker an hour earlier and the morning gets lighter an hour earlier. In the United States and Canada that happens on 1 November 2026; in the United Kingdom and central Europe it happens a week earlier, on 25 October 2026.

Does every country change its clocks?

No. Most of Asia, Africa and the tropics do not, because the length of the day barely varies there through the year. Within countries that do change, individual states and territories can opt out: Arizona and Hawaii do not change, while the rest of the United States does, and Queensland in Australia does not change while New South Wales does.

Why does the change happen in the middle of the night?

Because almost nobody is awake, commuting or trading at that hour, so a missing or repeated hour disturbs the fewest schedules. It also avoids midnight, where a change would make the date itself ambiguous rather than just the time. Exact hours differ by region and are listed in the table above.

Is the extra hour in autumn an extra hour of daylight?

No. The sun is not affected by the clock. Daylight saving moves an existing hour of light from the morning into the evening, and moving the clock back returns that hour to the morning. The total daylight on a given date is the same either way, so what changes is when it falls.

Are the dates the same every year?

No, because most rules are written as the first, second or last Sunday of a month, so the date moves. In the United States the clocks go back on 1 November in 2026 and on 7 November in 2027. In the United Kingdom the dates are 25 October 2026 and 31 October 2027.