What Is Daylight Saving Time and How Does It Work?

Every spring, millions of people lose an hour of sleep on the same weekend for a reason most of them couldn't fully explain if asked. Every autumn, that hour comes back, and for one specific night the clock plays the same hour twice. Both are daylight saving time — a deliberate, government-mandated shift of the clock that has nothing to do with how much sunlight a day actually gets, and everything to do with when that sunlight lands relative to when people are awake.

This guide covers the mechanism itself: what actually moves, when it moves in different parts of the world, and the specific edge case — a repeated hour — that trips up schedules and software every autumn. For how this interacts with UTC and GMT specifically, see UTC vs GMT: what's the difference; for converting a DST-affected time into another zone, see the guide to converting between time zones.

Daylight saving time is a seasonal adjustment to civil clocks: for part of the year, a region sets its clocks one hour ahead of its normal ("standard") time, then sets them back again later. The stated purpose is to make better use of natural daylight — by moving the clock forward, sunrise and sunset both happen an hour later by the clock, which shifts daylight out of the early morning, when most people are asleep, and into the evening, when they're awake and active.

The total number of daylight hours in a given day is fixed by the planet's tilt and the calendar date — DST changes nothing about that. What it changes is purely the label: the same moment of sunset gets a different clock reading depending on whether DST is in effect.

The mechanism is a single one-hour jump, applied twice a year in opposite directions, almost always in the middle of the night to minimize disruption:

• Spring forward: at the designated moment — 2:00 AM local time in the US — clocks jump directly to 3:00 AM. The hour from 2:00 to 2:59 AM is skipped entirely; it does not occur that night.
• Fall back: at the designated moment — again 2:00 AM in the US — clocks are set back to 1:00 AM. The hour from 1:00 to 1:59 AM then plays out a second time.

The exact dates are set by law and differ by region. The two changes are never on the same weekend across the Atlantic — Europe's clocks move about one to five weeks apart from the US's, depending on the year.

In 2026, that puts the US change on March 8 and November 1, and the EU change on March 29 and October 25. Both regions set the exact clock reading of the switch — 2:00 AM local time in the US, 01:00 UTC in the EU — as part of the law itself, not left to local interpretation.

The spring change is easy to picture: an hour is simply skipped. The autumn change is the more interesting one, because it produces something a normal clock can't otherwise do — the same local time reading occurring twice in a row, hours apart in real elapsed time but identical on the clock face.

DST is far from universal, and the pattern isn't random: it clusters in the mid-to-high latitudes, where the difference between summer and winter day length is large enough to be worth chasing. The United States, Canada, most of Europe, and parts of Australia and New Zealand observe it. Iceland is a notable exception even at high latitude — it stays on Greenwich Mean Time year-round, one of the reasons GMT and UTC line up there all twelve months (see UTC vs GMT for more on that specific case).

Most countries near the equator skip it entirely, including nearly all of Africa, South Asia, and Southeast Asia, because a day there is close to twelve hours of daylight regardless of season — there's no seasonal daylight surplus to shift around. Even within countries that do observe DST, exceptions exist: Hawaii and most of Arizona sit it out in the US, along with several US territories, while the rest of their respective countries change clocks twice a year.

Benjamin Franklin is often credited as the originator of daylight saving, based on a satirical 1784 essay poking fun at Parisians for sleeping through daylight hours — but it was a joke about candle costs, not a serious proposal to move clocks, and no clock-shifting scheme followed from it. The actual mechanism dates to the First World War: Germany adopted clock-shifting in 1916 to conserve coal, and the UK and US followed within the following two years, both dropping it again after the war ended.

DST became a fixture rather than a wartime measure much later. In the US, the Uniform Time Act of 1966 standardized the dates nationwide for the first time — before that, states and even individual cities picked their own DST schedules — and the Energy Policy Act of 2005 extended it to its current length. The EU harmonized its member states' schedules starting in 1980, with the current directive dating to 2001. Both regions have since debated ending the twice-yearly change on energy and health grounds — the European Parliament voted in 2019 to stop it — but as of today neither has finalized a repeal, and clocks still move on the schedule described above.

The practical effect of DST is that a place's offset from UTC isn't fixed — it changes twice a year. London sits at UTC+0 in winter and UTC+1 in summer; New York sits at UTC−5 in winter and UTC−4 in summer. Anyone converting a time or booking a meeting across that boundary needs to know not just the zone, but whether DST applies on that particular date — the method for doing that correctly is covered in the guide to converting between time zones, and the specific case of scheduling a call across several zones at once is covered in scheduling a meeting across time zones.

This is also why aviation, shipping, and computing default to UTC rather than any local zone: UTC never observes DST, so a UTC timestamp means the same thing in March and in August without any seasonal caveat attached.