When does daylight saving time end? 2026 dates, explained

Twice a year, roughly a quarter of the world's population changes its clocks. The rest do not. That mismatch — not the hour itself — is what makes daylight saving time such a persistent source of missed calls, wrong bookings, and calendar invitations that land sixty minutes off.

This guide covers what actually happens when the clocks change, why the dates differ from country to country, and the specific traps that catch people scheduling across borders.

What is daylight saving time?

Daylight saving time (DST) is the practice of moving clocks one hour ahead for the warmer part of the year, so that sunset comes an hour later by the clock. Clocks "spring forward" one hour when it starts and "fall back" one hour when it ends. In the United States it runs from the second Sunday in March to the first Sunday in November.

Daylight saving time dates: 2026, 2027 and 2028

Every date below is a Sunday. In the US and Canada the change happens at 2:00 a.m. local time in each time zone, so it sweeps across the country over several hours rather than happening everywhere at once.

In the southern hemisphere the seasons are reversed. Australia's participating states (New South Wales, Victoria, South Australia, Tasmania and the ACT) start daylight saving on October 4, 2026 and end it on April 4, 2027. New Zealand starts on September 27, 2026 and ends on April 4, 2027.

What actually happens when the clocks go back

In the US, at 2:00 a.m. on Sunday, November 1, 2026, the clock goes back to 1:00 a.m., and the hour from 1:00 to 2:00 a.m. happens a second time. Phones, computers and most smart devices change automatically; ovens, car dashboards and wall clocks usually need to be set back by hand. From that day, mornings are lighter and sunset comes about an hour earlier by the clock. It is a good moment to check anything scheduled with people in Europe: for the week between October 25 and November 1, New York is only four hours behind London instead of the usual five.

What daylight saving time actually does

Daylight saving time shifts a region's clocks forward by one hour during the warmer months, so sunset falls later in the evening by the clock. Nothing about the sun changes. What changes is the label attached to each moment: the instant that would have been called 6:00 a.m. is now called 7:00 a.m., and everyone's schedule moves with it.

Technically, the region changes its UTC offset. New York sits at UTC−5 in winter and UTC−4 in summer. London sits at UTC+0 in winter and UTC+1 in summer. This is why time zone abbreviations come in pairs — EST and EDT, GMT and BST, CET and CEST — and why writing "EST" in June is usually wrong.

The spring transition: an hour that doesn't exist

When clocks spring forward, one hour is deleted from the calendar. In the United States, at 2:00 a.m. local time on the second Sunday of March, the clock jumps directly to 3:00 a.m. The times between 2:00 and 2:59 a.m. simply never occur on that date.

This has practical consequences. A recurring 2:30 a.m. alarm will not fire that morning. A meeting scheduled for a nonexistent local time gets silently reinterpreted by most calendar software, usually by shifting it forward. And that day is 23 hours long, which quietly breaks any calculation assuming a day is always 86,400 seconds.

The autumn transition: an hour that happens twice

The reverse is stranger. When clocks fall back, the hour between 1:00 and 2:00 a.m. runs twice. Written as a local time, "1:30 a.m." on that date is ambiguous — it refers to two distinct moments an hour apart, and there is no way to tell them apart without also recording the UTC offset.

That day is 25 hours long. A shift worker who clocks in at 11 p.m. and out at 7 a.m. has worked nine hours, not eight. Systems that store only a local timestamp genuinely cannot resolve which of the two 1:30 a.m.s an event belongs to, which is why timestamps meant for the record are stored in UTC and converted only for display.

Why the dates don't line up

Every country picks its own transition dates, and the choices were never coordinated.

The gap between the American and European start dates creates two or three weeks each March when the usual New York–London difference is four hours instead of five. A recurring transatlantic call set for 9:00 a.m. New York, 2:00 p.m. London will be an hour out of alignment for those weeks unless the invitation was created with proper time zone information rather than a fixed offset.

A second, larger trap: the southern hemisphere runs the opposite schedule. Sydney observes daylight saving from October to April, while London observes it from March to October. The two are almost never on daylight time simultaneously, so the London–Sydney difference swings between nine, ten and eleven hours across the year. There is no single correct answer to "how many hours ahead is Sydney?"

Where it isn't observed at all

Roughly 70 countries change their clocks; most of the world's countries do not. Within countries that do, there are exceptions worth knowing:

• Arizona stays on Mountain Standard Time year round — except the Navajo Nation, which does observe daylight saving.
• Hawaii does not observe it.
• Queensland, the Northern Territory and Western Australia do not, while New South Wales, Victoria, South Australia, Tasmania and the ACT do. Brisbane and Sydney therefore share a clock for half the year and not the other half.
• Saskatchewan stays on Central Standard Time all year.
• Japan, China, India, Singapore and most of Africa and South America either abandoned it decades ago or never adopted it.

Countries near the equator gain almost nothing from it: day length barely varies there across the year, so there is no seasonal daylight to shift.

A short history, and why the rules keep changing

The idea is usually traced to a 1907 pamphlet by the British builder William Willett, though the New Zealand entomologist George Hudson proposed a similar scheme in 1895. Germany was the first country to adopt it nationally, in 1916, as a wartime coal-conservation measure; Britain and the United States followed within months.

What matters practically is that the rules have never been stable. The United States moved its start date from April to March in 2007. The European Union voted in 2019 to abolish seasonal clock changes, but the decision has not been implemented and member states have not agreed on which time to settle on. Mexico dropped it in 2022. Several US states have passed legislation for permanent daylight time, which currently requires an act of Congress to take effect.

This is precisely why software should never hardcode an offset for a city. The world clock and zone converter here read the current rules from your browser's copy of the IANA time zone database, the reference dataset that tracks every zone's schedule and its historical changes. When a country changes its rules, that database is updated and the tools follow — no code change needed.

Practical rules for scheduling across a change

• Schedule in a named zone, not an offset. "9:00 a.m. America/New_York" survives a transition; "9:00 a.m. UTC−5" does not.
• Check recurring meetings in mid-March and late October. These are the weeks when the US and EU are out of step.
• Avoid scheduling anything between 1:00 and 3:00 a.m. local on a transition date. The hour may not exist, or may exist twice.
• Store timestamps in UTC and convert only when showing them to a person.
• Don't assume a day is 24 hours when computing a duration across a transition. Subtract absolute instants, not local wall-clock times.