Daylight Saving Time 2026 — When Clocks Change and How It Affects You

United States and Canada: Spring forward on Sunday, March 8, 2026, at 2:00 AM local time (clocks move to 3:00 AM). Fall back on Sunday, November 1, 2026, at 2:00 AM local time (clocks move to 1:00 AM). This applies to most states except Arizona (excluding the Navajo Nation), Hawaii, and the US territories of Puerto Rico, Guam, American Samoa, and the US Virgin Islands.

European Union and UK: Spring forward on Sunday, March 29, 2026, at 1:00 AM UTC (clocks move forward one hour). Fall back on Sunday, October 25, 2026, at 1:00 AM UTC (clocks move back one hour). Note the three-week gap between the US and EU spring transitions — from March 8 to March 29, the time difference between New York and London is four hours instead of the usual five. This is the period that trips up international schedulers every year.

Australia: Daylight saving in Australia ends on Sunday, April 5, 2026, at 3:00 AM local time (clocks move to 2:00 AM). It resumes on Sunday, October 4, 2026, at 2:00 AM local time (clocks move to 3:00 AM). Only New South Wales, Victoria, South Australia, Tasmania, and the ACT observe DST. Queensland, Western Australia, and the Northern Territory do not.

Most of the world does not observe daylight saving time. The entire continents of Africa and Asia (with rare exceptions) stay on standard time year-round. India does not observe DST. China does not observe DST. Japan stopped observing DST in 1952. Russia permanently abandoned DST in 2014 after years of public complaints. Most of South America doesn't observe it, though a few countries have gone back and forth. Countries near the equator see minimal variation in daylight hours between seasons, so DST provides little benefit.

Even within countries that observe DST, there are exceptions. In the US, Arizona and Hawaii skip DST entirely. In Australia, Queensland and Western Australia don't participate. In Canada, most of Saskatchewan stays on standard time. These internal exceptions add another layer of complexity for anyone scheduling across those regions — you can't assume an entire country is on the same clock adjustment.

Daylight saving time was widely adopted during World War I to save energy by aligning waking hours with daylight. The idea was that if people were awake during more daylight hours, they would use less artificial lighting and save fuel. In the modern era, with air conditioning, LED lighting, and 24/7 screen usage, the energy savings are negligible — studies show DST saves less than 1% of total energy consumption, and some analyses suggest it actually increases energy use because of additional air conditioning in the longer, warmer evenings.

The movement to end DST has gained significant momentum. The European Parliament voted to abolish the clock change, though implementation has been delayed repeatedly due to member states disagreeing on whether to stay on permanent summer time or permanent winter time. In the US, the Sunshine Protection Act — which would make daylight saving time permanent — has been introduced multiple times in Congress. Several US states have passed legislation to adopt permanent DST, pending federal approval. The debate essentially boils down to: do you prefer lighter mornings (standard time) or lighter evenings (daylight saving time)?

The biggest headache with DST isn't the clock change itself — it's that different countries change on different dates. Between March 8 and March 29, 2026, the US has already sprung forward but Europe hasn't. That means the New York-to-London time difference temporarily drops from five hours to four. A meeting that's normally at 2 PM New York / 7 PM London is suddenly at 2 PM New York / 6 PM London. If nobody updates the invite, the London participant shows up an hour late — or an hour early, depending on who set the original time.

The same problem occurs in reverse in the autumn. The US falls back in early November, but Europe falls back in late October. For about a week, the difference shifts again. And Australia's DST runs on the opposite schedule (their summer is the Northern Hemisphere's winter), creating yet another set of transition mismatches. For teams with members in the US, Europe, and Australia, there are potentially six to eight weeks per year when normal time offsets are temporarily wrong.

Let your calendar handle it. If you schedule meetings using Google Calendar or Outlook and select the correct timezone for each participant, the calendar app will automatically adjust for DST. The problem only arises when people schedule by memory or mental math. Double-check during transition weeks. In the weeks around March and November, verify meeting times using the Timezone Converter rather than assuming your usual offset is correct.

Communicate proactively. If you manage a global team, send a brief heads-up before each DST transition: "Reminder: US clocks spring forward this Sunday. Our Monday standup will be one hour earlier for non-US participants until Europe changes on March 29." That one sentence prevents a week of confused calendar checks. Check the World Clock during transition periods to quickly verify what time it is in your colleagues' cities. It accounts for all DST changes automatically, so you always see the accurate current time.

Whether DST eventually gets abolished or not, it's the reality we work with today. The clock changes are predictable — they happen on the same schedule every year. With a little preparation and the right tools, the transition doesn't have to disrupt your work or your sleep. Set your clocks, update your mental models, and move on. And if you're in one of the countries that doesn't observe DST, enjoy the simplicity — and be patient with your colleagues who are adjusting their clocks twice a year.