Daylight Saving Time 2027: US, UK and International Clock Changes

Daylight Saving Time 2027: US, UK and International Clock Changes

SEO title: Daylight Saving Time 2027: When US & UK Clocks Change

Meta description: See the 2027 clock-change dates: US March 14 and November 7; UK March 28 and October 31. Compare local transitions, exceptions and time-zone gaps.

Quick Answer: Under the rules in force as of October 15, 2026, U.S. places observing daylight saving time move clocks forward on Sunday, March 14, 2027 at 2:00 AM local standard time and back on Sunday, November 7 at 2:00 AM local daylight time. The UK moves forward March 28 at 1:00 AM GMT and back October 31 at 2:00 AM BST. The U.S. and UK do not change on the same dates, so the New York-London time difference temporarily drops from five hours to four hours in March and again around early November.

Daylight saving time 2027 at a glance

These dates come from the U.S. National Institute of Standards and Technology's federal-rule explanation, the U.S. Department of Transportation's jurisdiction guidance, GOV.UK's 2027 table and the European Commission's 2027-2031 published summer-time schedule. The city offsets below were computed with IANA time-zone data and should be checked again near publication if a government changes the law.

United States: clocks go forward on March 14, 2027

In a U.S. location observing DST, the transition occurs early Sunday, March 14, 2027. When the local standard clock is about to reach 2:00 AM, the next displayed time is 3:00 AM daylight time. The interval from 2:00 through 2:59 AM is skipped in that local calendar day.

In New York the reading changes from 1:59 AM EST to 3:00 AM EDT. That transition happens at 07:00 UTC. In Los Angeles the change is from 1:59 AM PST to 3:00 AM PDT at 10:00 UTC. The same federal rule applies at local 2 AM, but East and West Coast clocks do not change at the same worldwide instant.

If you schedule an event for 2:30 AM New York local time on March 14 without specifying how your system handles nonexistent times, the entry is ambiguous or invalid. Some applications reject it and some move it automatically; do not assume all scheduling systems use the same correction. Use a valid time or ask the organizer to specify a UTC instant.

The March transition also changes sunrise and sunset clock readings compared with the standard-time schedule. It does not mean the Sun abruptly behaves differently at the moment the time display changes. A city sunrise calculation for March 14 must use the post-change offset to give the correct local clock time.

The existing Spring Forward 2027 guide covers the March transition in greater depth. This annual page keeps the spring and autumn changes together for people planning across the whole year.

United States: clocks go back on November 7, 2027

DST ends on Sunday, November 7, 2027 in observing areas. At 2:00 AM daylight time, the clocks return to 1:00 AM standard time. That means the 1 AM hour happens twice, with the first occurrence using the daylight abbreviation and the second using the standard abbreviation.

In New York, 1:30 AM EDT and 1:30 AM EST are different instants one real hour apart. The first corresponds to 05:30 UTC and the second to 06:30 UTC. A train pickup, work shift or event ending at "1:30 AM" needs a first-or-second-hour label if it falls inside this interval.

The local calendar day contains 25 elapsed hours in observing locations, but that does not automatically extend a store's hours, a parking rule or a reservation. A business may operate by its own posted policy. Verify the event rule rather than reading the federal clock-change instruction as a promise of extra admission or service time.

A time-zone-aware system should be able to distinguish repeated local clock labels internally by UTC instant or offset. You should still check how its interface shows them to users. An email that contains only "Nov 7, 1:30 AM" does not resolve the ambiguity.

UK: March 28 forward and October 31 back

GOV.UK gives Sunday, March 28 and Sunday, October 31 as the UK clock-change dates in 2027. These are the last Sundays of March and October. The UK does not use the U.S. March 14 or November 7 dates.

The spring transition happens at 1:00 AM GMT. The minute before is 12:59 AM GMT; the next minute displayed is 2:00 AM BST. That skips the local 1:00-1:59 AM hour. The autumn transition occurs when the clock reaches 2:00 AM BST and returns to 1:00 AM GMT, so the 1 AM hour repeats.

London, Manchester, Edinburgh and Belfast use these UK mainland time rules. The same date is not a safe assumption for every British overseas territory, and UK rules should never be copied wholesale to other countries that happen to speak English.

A common misunderstanding is that the UK fall transition happens "at 2 AM GMT." That is the wrong pre-change label. It happens at 2:00 AM BST, corresponding to 01:00 UTC. Once the clocks roll back, they show 1:00 AM GMT. In spring, 1:00 AM GMT becomes 2:00 AM BST, also at 01:00 UTC.

The official GOV.UK clock-change page is the source for the UK dates and local clock rule. The annual dates can also be added to a calendar from the government site's ICS link.

Europe changes together in UTC, but not at the same clock reading

The European Commission's published schedule for 2027-2031 states that the EU summer-time periods begin and end at 01:00 UTC on March 28 and October 31, 2027. This is a common worldwide instant for the EU's summer-time transition, but the local clock display changes according to the country's time zone.

In Paris and Berlin, the March 28 change is from 1:59 AM CET to 3:00 AM CEST. In autumn, 2:59 AM CEST is followed by 2:00 AM CET. In London the corresponding readings are 12:59 AM GMT to 2:00 AM BST in spring and 1:59 AM BST to 1:00 AM GMT in autumn.

The United Kingdom is no longer an EU member, but its 2027 dates coincide with the EU dates. That produces simultaneous UK and continental changes when the UTC instant is compared. It does not remove the separate UK and EU legal sources.

The year-round difference between London and Paris is normally one hour for these mainland cities under the current rules, since the two regions change on the same UTC instant. That does not mean all European cities share one time zone. Iceland, for example, does not follow the same seasonal clock practice, and countries outside the EU set their own policies.

Exact 2027 transitions by representative city

The table contains real timezone transitions calculated with IANA zoneinfo, not an animation of a fake clock. "Before" is the local minute immediately preceding the UTC transition; "after" is the local minute at the transition. A jump of more than one displayed minute is what creates the missing or repeated hour.

Phoenix and Honolulu are omitted from this transition table because there is no 2027 change for them. The absence of a row is deliberate, not a failed calculation. The downloaded DST data file includes the city and source zone identifier, so the results can be inspected and regenerated.

If your city is not listed, use its exact IANA zone in a time-zone converter. A state name may be insufficient when a state includes more than one offset or when some communities follow different DST practice.

When New York and London are four hours apart in 2027

Most of the winter New York is five hours behind London. During the middle of the summer it is also five hours behind because both places have advanced their clocks by an hour. The exceptional periods occur when the U.S. and UK have changed on different Sundays.

The first mismatch starts when New York springs forward on March 14 but London remains on GMT until March 28. During that interval, New York is on UTC-4 and London is on UTC+0, giving a four-hour difference. After London changes, the gap returns to five hours.

The second mismatch begins October 31, when London returns to GMT but New York stays on EDT until November 7. Again the difference is four hours. When the U.S. changes on November 7, New York returns to EST and London is five hours ahead.

A 9 AM New York meeting at different dates

The table uses 9:00 AM at the New York office and computes London's time for that same instant. The meeting never changes its New York wall-clock starting hour, yet London's invitation shifts between 1 PM and 2 PM because the regional offsets diverge for two short periods.

This is the practical scheduling problem people often miss. A meeting planned as "9 AM EST" will not remain 9 AM New York local time all year, because EST and EDT are distinct offsets. Use "9 AM America/New_York" for a recurring New York-wall-time meeting, or use a fixed UTC time if the meeting is meant to occur at one global instant.

For the closely related workplace scenarios, see the site's guide to avoiding DST mistakes in global meetings, after confirming the page is live. A time zone is not simply a permanent offset; it includes a calendar of historical and future rule changes.

What changes for U.S. and UK business travel

A flight ticket's local departure and arrival clocks are normally displayed for the respective airports. Those two time readings should not be subtracted without accounting for the time zones and DST on the flight date. A New York-to-London trip in the March mismatch period crosses a four-hour offset difference; most other periods use five hours under current rules.

If your office schedules calls by local wall time, the invitation needs a named time zone and a date. A plain label such as "ET" may be useful but still relies on the software applying the correct historical rules. Avoid writing "EST" throughout the summer when New York is actually on EDT.

The autumn repeated hour creates a separate booking issue. An airport pickup in New York booked for November 7 at 1:15 AM could fall in the first or second instance of 1:15. Ask the service which occurrence its system uses. If it can provide a UTC timestamp or offset, the ambiguity disappears.

An international deadline stored as 23:59 on a local date must specify the jurisdiction. "End of October 31" in London and "end of October 31" in New York are different moments, especially in the interval after the UK has rolled back and before the U.S. has done so.

Which places do not observe U.S. daylight saving time?

The U.S. Department of Transportation lists Hawaii, most of Arizona, American Samoa, Guam, the Northern Mariana Islands, Puerto Rico and the U.S. Virgin Islands among jurisdictions that do not observe DST. Their clocks do not jump forward on March 14 or back on November 7 under the federal seasonal change.

Arizona needs one more detail. Arizona state law elects to remain on Mountain Standard Time, but the Navajo Nation observes daylight saving time. If you are travelling through northern Arizona or scheduling with a community there, check the exact location rather than assuming that every place within the state's geographic boundary has the same rule.

Phoenix stays at UTC-7 year-round. Denver changes between MST (UTC-7) and MDT (UTC-6). That means the two cities share the same offset in winter but differ by one hour while Denver is on daylight time. A label such as "Mountain Time" is not enough for precise year-round conversions without the place.

Hawaii also stays on its standard offset. But Hawaii is not a template for the whole Pacific region; other islands and territories set their own clock rules. Use the city or territory's published time-zone identifier, and do not infer DST merely from proximity to the continental United States.

Australia changes on different dates and in the opposite season

Sydney, New South Wales uses daylight saving time during the southern summer. The New South Wales Government lists the end of that summer-time period as Sunday, April 4, 2027, when the clocks move from 3 AM AEDT back to 2 AM AEST. The next start is Sunday, October 3, when 2 AM AEST moves forward to 3 AM AEDT.

This does not align with either the U.S. or UK schedule. A meeting involving Sydney and New York can change its relative offset multiple times across the year as each city changes on its own dates. If an automated schedule assumes a fixed "Sydney is X hours ahead" number, it will be wrong for part of the year.

The official NSW government page should be the source for the state's legal clock dates. The IANA Australia/Sydney record supplies the date-aware conversion for the worked examples and city selector. Do not claim all of Australia changes: states and territories differ in whether they observe daylight saving time.

A working date-aware city selector

The companion HTML file supplied with this batch includes a city selector that displays the 2027 transitions for New York, Chicago, Denver, Los Angeles, Anchorage, London, Paris and Sydney, plus clear nonchanging examples such as Phoenix, Honolulu and New Delhi. The component uses precomputed IANA transition instants rather than pretending to know live device time.

It shows the exact local readings immediately before and after a transition and the UTC instant. The supplied CSV is the source data for the component. If the site integrates this as a page component, its timezone database should be updated along with the site's existing time converter.

For an arbitrary meeting instant, use a functioning time converter or the existing meeting planner after verifying the published route. Do not attach a "Calculate" button to this article unless the corresponding live calculation actually works.

Elapsed time across a skipped or repeated hour

Subtracting two wall-clock labels can produce the wrong duration when a trip or shift crosses a transition. Consider New York's spring change on March 14, 2027. A session from 1:30 AM EST to 3:30 AM EDT is one real hour long. The clock faces appear two hours apart because the intervening local 2 AM hour did not exist.

The reverse problem happens in autumn. On November 7, a session from 1:30 AM EDT, the first occurrence, to 1:30 AM EST, the second occurrence, lasts one real hour even though both clock displays read 1:30. If the start and end are stored as plain local strings without offsets, a duration calculator may report zero or an error.

These are elapsed durations of explicit instants, computed by converting both endpoints to UTC before subtraction. They are not rules for pay or overtime. A contract, employer policy and local law govern how a work shift is recorded or paid, and this article does not assume one outcome for all workers.

This is why a meeting invitation or transport booking should preserve an offset-aware timestamp internally. The human-readable local display can still show the preferred zone, but an ambiguous repeated hour requires enough data to identify which actual instant was intended.

What if a government changes its DST law before 2027?

The dates in this guide follow laws and official schedules available as of October 15, 2026. A proposed bill is not a change in force. Do not update a reference page because a politician has announced support for ending seasonal clock changes; confirm that legislation or a legally effective regulation has been adopted and identify its effective date.

NIST explains the current U.S. federal transition rule, but the U.S. Department of Transportation regulates time zones and DST. For Britain, GOV.UK publishes the annual dates. For the EU, the European Commission's published 2027-2031 schedule establishes the UTC transition dates currently in effect.

If rules change, review the dates, the IANA database and every converted table together. Changing only the headline would leave inconsistent UTC instants, city examples and event labels elsewhere in the article. A change of law is an editorial update trigger, not a reason to present speculative dates as fact.

Use time zones instead of abbreviations when booking meetings

An abbreviation can mean an offset rather than a location with rules. EST means UTC-5, whereas America/New_York changes between UTC-5 and UTC-4 according to the applicable New York rules. BST means UK summer time, not a permanent London offset.

For a recurring meeting, specify whether it follows one office's local wall time or stays fixed in UTC. Those are different policies. A weekly call at 9 AM New York moves by one hour in UTC when New York changes clocks; a weekly call fixed at 14:00 UTC instead appears at a different New York local hour across the year.

For a one-time appointment inside an autumn repeated hour, include the full local date, zone and first/second occurrence or an explicit UTC offset. November 7, 2027, 1:30 AM EST and 1:30 AM EDT are unambiguous and one real hour apart. For nonexistent spring hours, choose a valid post-transition time instead of assuming an application will repair it as you expect.

A reliable global scheduling workflow starts with one exact instant and then displays it in each participant's time zone. That is more dependable than manually adding an assumed number of hours, particularly during March and late October or early November.