Quick answer: In 2026, the United States and Canada spring forward on Sunday, March 8 and fall back on Sunday, November 1. The UK, Ireland, and the EU spring forward on Sunday, March 29 and fall back on Sunday, October 25. Australia's DST states run the opposite schedule - daylight saving ends on Sunday, April 5 and resumes on Sunday, October 4. Because these dates don't line up, there are two "danger windows" each year when the time difference between the US and Europe is off by an hour from its usual value.

Never do the math by hand: Open the BestSyncTime converter with your two cities - it applies every region's 2026 DST rules automatically, so the overlap you see is always correct, even during the changeover weeks.

The 2026 dates at a glance

Here are the confirmed clock-change dates for the major regions that observe Daylight Saving Time in 2026:

RegionSpring forward (DST begins)Fall back (DST ends)Standard offset
United States & CanadaSun, March 8, 2026 (2:00 AM local)Sun, November 1, 2026 (2:00 AM local)Varies (UTC−5 to −8)
UK & IrelandSun, March 29, 2026 (1:00 AM GMT)Sun, October 25, 2026 (2:00 AM BST)UTC+0 (GMT)
European UnionSun, March 29, 2026 (1:00 AM UTC)Sun, October 25, 2026 (1:00 AM UTC)Varies (UTC+0 to +2)
Australia (NSW, VIC, SA, TAS, ACT)Resumes Sun, October 4, 2026 (2:00 AM)Ends Sun, April 5, 2026 (3:00 AM)Varies (UTC+8 to +10)
New ZealandResumes Sun, September 27, 2026 (2:00 AM)Ends Sun, April 5, 2026 (3:00 AM)UTC+12

Keep two things in mind while reading that table. First, the Southern Hemisphere's seasons are reversed, so Australia and New Zealand "fall back" in April and "spring forward" in September-October - the opposite of the north. Second, not every part of a country changes: several Australian states and a couple of US states sit DST out entirely, which we'll cover below.

The rules behind the dates

The dates aren't arbitrary - each region follows a fixed rule, which is why you can predict them years in advance.

In the United States and Canada, the rule set by the Energy Policy Act of 2005 is: DST begins on the second Sunday in March and ends on the first Sunday in November. In 2026 that lands on March 8 and November 1.

In the United Kingdom, Ireland, and the European Union, the rule is the last Sunday in March to the last Sunday in October - March 29 and October 25 in 2026. All EU member states change at the same absolute moment (01:00 UTC), rather than at the same local clock time, so the transition ripples across the continent's zones simultaneously. Despite Brexit, the UK and Ireland still change on the same dates as the EU, because the underlying rules were inherited and never amended.

In Australia, DST is decided state by state. New South Wales, Victoria, South Australia, Tasmania, and the ACT observe it, running from the first Sunday in October to the first Sunday in April.

Who doesn't change their clocks

Roughly 180 countries never observe DST at all, including most of Asia, Africa, and South America - so India, China, Japan, and Russia keep the same offset year-round. But there are notable exceptions *inside* countries that otherwise do change:

  • - United States: Arizona (except the Navajo Nation) and Hawaii do not observe DST. US territories - Puerto Rico, Guam, the US Virgin Islands, American Samoa, and the Northern Mariana Islands - also stay on standard time year-round.
  • - Australia: Queensland, Western Australia, and the Northern Territory do not change their clocks, which creates real internal confusion each summer - during DST months, Sydney and Brisbane, normally on the same clock, drift an hour apart.

This is exactly why "just add X hours" rules break down: the offset between two cities can depend on the *date*, the *state*, and whether *either* side is currently observing DST.

The two danger windows (this is what trips everyone up)

The single most important consequence of these mismatched dates: the US and Europe do not change clocks on the same weekend. The US springs forward three weeks *before* Europe, and falls back one week *after* Europe. That creates two windows each year when the transatlantic time gap is temporarily wrong:

Spring window - March 8 to March 29, 2026: The US has moved to daylight time, but Europe hasn't yet. During these three weeks, the New York-London gap shrinks from its usual 5 hours to 4 hours. A call normally set for 2:00 PM New York / 7:00 PM London becomes 2:00 PM New York / 6:00 PM London. If nobody updates the invite, the London participant shows up an hour off.

Autumn window - October 25 to November 1, 2026: Europe has fallen back, but the US hasn't yet. Again the gap is 4 hours instead of 5 for that week, and the same mismatch strikes recurring meetings.

The reason this causes so much chaos is that most calendar invites store a fixed local time. When the offset between two cities shifts mid-year, a "recurring 3 PM meeting" silently lands at the wrong hour for one side until both regions have finished transitioning.

The fix takes five seconds: During a changeover week, drop both cities into BestSyncTime and read the live gap straight off the Overlap Dial. It already knows who has and hasn't switched - so you schedule against reality, not last month's offset.

Will these clock changes even continue?

There's ongoing debate about abolishing DST, though nothing is settled for 2026:

  • - In the United States, the Sunshine Protection Act - which would make DST permanent - has passed the Senate more than once but stalled in the House. Sleep researchers actually favor making *standard* time permanent instead, citing health benefits.
  • - In the European Union, a 2018 public consultation found 84% of respondents wanted to end clock changes, but implementation has been repeatedly delayed, and member states never agreed on whether to lock in summer or winter time.
  • - Mexico largely abolished DST in 2022, and Brazil suspended it in 2019 - a reminder that the map genuinely changes from year to year.

The practical takeaway: don't assume this year's rule is permanent. Verify the current dates each season rather than relying on memory.

How to protect your schedule around the changes

A few habits will keep the clock changes from catching you out:

  • - Mark the danger windows. Put March 8-29 and October 25-November 1 on your calendar as "US/EU offset mismatch" reminders if you work across the Atlantic.
  • - Store meetings in a specific time zone, not just a clock time. Good calendar apps let you attach a time zone to an event so it adjusts correctly for everyone.
  • - Re-confirm recurring cross-border meetings in the week before and after each transition.
  • - Ease the personal adjustment. For the sleep disruption, shift your bedtime by 15-20 minutes a night for a few nights before the change, and get bright morning light on the day of and after - it helps reset your body clock faster.
  • - Let a tool handle the arithmetic. The offset math is exactly the kind of thing that's easy to get wrong under deadline pressure and trivial for software to get right.

The short version

For 2026: the US changes on March 8 and November 1; the UK and EU change on March 29 and October 25; Australia's DST states change on April 5 and October 4. The dates are fixed by rule, so you can plan around them - but the mismatch between regions creates two windows a year when transatlantic times are off by an hour. Know the windows, store your meetings with a time zone attached, and let a converter do the offset math.

Get the exact overlap now: Open BestSyncTime, add your cities, and drag the Overlap Dial to see everyone's shared hours - DST already accounted for.