How Daylight Saving Time Works Around the World

Understand skipped hours, repeated hours and different clock-change dates before your next international meeting.

Zone & Hour editorial · Published September 30, 2026 · Examples are explicitly dated

The date is part of the time

“Nine in New York” does not identify a moment until you add a date. New York’s offset from UTC changes during the year. A participant in Seoul, whose clock currently stays on the same offset, sees a recurring New York meeting move even though nothing changes on the Seoul clock.

Daylight saving time changes the relationship between a civil clock and UTC. It does not add an hour to the day’s sunlight. The local clock labels are moved so that a different part of the daylight period falls within ordinary social schedules. Different governments make different choices about whether, when and by how much to change their clocks.

For meetings, the useful question is not “Does this country use DST?” It is “What are the rules for this location on this date?” A country can contain several time zones and exceptions. Choose a city, then keep the date attached to your conversion.

A missing hour is not a valid appointment

In New York on March 8, 2026, the clock moves from 1:59:59 AM to 3:00 AM. A requested local time of 2:30 AM has no corresponding instant. Silently treating it as 3:30 AM may look convenient, but it changes what the organizer entered.

This converter rejects nonexistent local times and asks for another time. For an appointment, choose a valid time after the change or confirm a different date. For software, keep the original input and report why it cannot be resolved; an apparently successful conversion should never hide that decision.

The NIST daylight-saving guide gives the current US schedule and its 2026 dates.

A repeated hour needs a choice

When the clock moves backward, an hour can happen twice. New York’s 1:30 AM on November 1, 2026 identifies two instants: 05:30 UTC and 06:30 UTC. The local label is identical, but the UTC offsets differ.

The converter presents a first-or-second-occurrence choice instead of guessing. Shared links use an ISO timestamp ending in Z, so once you choose an occurrence, the link preserves the actual instant. A friend opening the link does not need to repeat the ambiguity decision.

For overnight support shifts, transport or maintenance work, record an explicit offset or UTC timestamp as well as the local display. A list of local labels alone can make events appear duplicated or out of order when the clock goes back.

Two cities can change on different weekends

The US and UK do not use the same transition dates. In 2026, the UK moves forward on March 29 and back on October 25. The UK government’s clock-change page publishes that schedule.

That creates intervals when the familiar New York–London gap is different. These noon-based examples make the effect visible:

Use the New York to London converter for the precise day and time. The difference can change partway through a transition day, so a date-only rule is not always precise enough.

Southern seasons reverse the pattern

Sydney’s daylight-saving season includes parts of the northern hemisphere’s winter. When one city gains an hour and the other loses one, their relative difference can change by two hours across the year, with intermediate periods around the separate transition dates.

Do not label every city as simply “summer time” without stating whose summer you mean. For cross-hemisphere teams, use month names and explicit dates. Our southern hemisphere guide works through a Sydney–New York example.

Keep the calendar anchored to a city

For a recurring meeting, decide which participant’s local time is the anchor. “Every Tuesday at 9 AM in America/New_York” expresses a different intention from “Every Tuesday at 14:00 UTC.” Both are valid, but they behave differently through clock changes.

Before the transition season, inspect at least one occurrence after each affected city’s next change. If the result becomes unreasonable, change the series with participants’ agreement rather than expecting a fixed UTC link to preserve everyone’s local hour.

Questions that come up often

Does every daylight-saving change last an hour?

No universal rule says it must. Time-zone history includes non-hour changes. Software should use the installed time-zone rules instead of adding a hardcoded sixty minutes.

Why does my colleague’s computer disagree?

Their device may have old time-zone data or an incorrect system clock. Update the operating system and browser. For newly announced changes, verify the local authority’s notice before a critical appointment.

Can the website predict future laws?

No. It follows the rules available to its browser or build runtime. The IANA Time Zone Database is updated as political decisions change those rules. The meeting planner recalculates using your selected date and current device data.