What time will it be in your city after the next DST change?
Twice a year, your local time shifts by an hour. If you want to know in advance what time it'll be next Tuesday — after this weekend's DST change — the math is straightforward.
For the simple answer in any city, the time converter handles it directly. The rest of this post explains how to do it yourself if you want to.
The basic mechanic
If you're in a DST-observing region:
Spring forward (US: second Sunday of March; EU: last Sunday of March):
- Your local clock skips from 1:59:59 AM directly to 3:00:00 AM
- After the shift, "12 noon" is what used to be "11 AM"
- A meeting scheduled for "10 AM next Tuesday" stays at 10 AM on the new clock
Fall back (US: first Sunday of November; EU: last Sunday of October):
- Your local clock falls from 1:59:59 AM back to 1:00:00 AM
- After the shift, "12 noon" is what used to be "1 PM"
- A meeting scheduled for "10 AM next Tuesday" stays at 10 AM on the new clock
What this means for the same calendar moment
If a meeting is at "10 AM Eastern Time on Tuesday March 10, 2026," and DST has just kicked in (March 8 was the spring shift), then:
- In UTC: the meeting is at 14:00 UTC (because EDT is UTC-4)
- In Eastern Standard Time (the time zone the meeting was created in if anyone created it before the shift): wait — there's no such thing as "10 AM EST on March 10" anymore, because EST is now over for the year. EDT is in effect.
This is why anchoring recurring meetings to UTC matters. Or anchoring to "Eastern Time" (the generic name) which automatically follows DST.
Calculating the new wall-clock time
If you know:
- Your previous offset (e.g., UTC-5 in winter)
- The DST shift direction (forward or back)
- The shift amount (1 hour)
Then your new offset is:
- Spring forward: previous offset + 1 hour (e.g., UTC-5 → UTC-4)
- Fall back: previous offset - 1 hour (e.g., UTC-4 → UTC-5)
Your wall clock for any UTC moment becomes:
- New local time = UTC + new offset
So at UTC 14:00, after spring forward to EDT (UTC-4):
- Local time = 14:00 + (-4) = 10:00 AM EDT
Real examples for the next US DST shift
Say it's right before March 8, 2026 (US spring forward). Your colleague in California asks: "What time will it be in New York at 9 AM Pacific time on Monday March 9?"
Without DST shift in effect: 9 AM PT (UTC-8) = 12 PM ET (UTC-5).
After spring forward (which happened Sunday March 8): 9 AM PT (UTC-7) = 12 PM ET (UTC-4).
So 12 PM in both cases. But the underlying UTC moment shifted by an hour.
This is the kind of thing that makes recurring meetings shift unexpectedly. The time converter handles it automatically.
What gets affected by the shift
Things that observe DST automatically:
- Your phone, computer, smart watch
- Calendar apps (Google, Outlook, Apple)
- Smart home devices (Nest, Hue, etc., usually)
- Most modern operating systems
Things that may not auto-adjust:
- Old analog clocks
- Some kitchen appliances (microwave, oven)
- Some car clocks (depends on year/make)
- Some smart-home devices that haven't received tzdata updates
- Some industrial equipment
Things that need explicit coordination:
- Recurring meetings scheduled in local time
- Cross-region team schedules
- Live broadcasting (TV, radio)
- Stock market opening hours (timed to local exchange)
After the next shift in your country
Specific dates for the next shifts depend on your country. The DST calendar lists them all. Common 2026/2027 examples:
- US spring 2026: March 8 (already passed if you're reading this in summer)
- US fall 2026: November 1
- US spring 2027: March 14
- EU spring 2026: March 29
- EU fall 2026: October 25
- EU spring 2027: March 28
- Australia (NSW etc.) spring 2026: October 4
- Australia (NSW etc.) fall 2027: April 4
Practical "what to do this weekend" checklist
The weekend before a DST shift:
- Check your phone's automatic time setting (Settings → General → Date & Time → Set Automatically should be ON)
- Check upcoming calendar entries for the next 2-3 weeks. Confirm meeting times are correct
- Check shared calendars with cross-region colleagues for the gap period
- Check smart-home devices for clock-related rules (your morning lighting schedule, for instance)
- Reset analog clocks that don't auto-adjust
- Check car clock if it's an older model that doesn't auto-adjust
The morning of the shift:
- Sleep schedule may feel off for a few days
- Be cautious driving on Monday
- Confirm your phone shows the new time
What if my country doesn't observe DST?
You don't have a shift to worry about. Your offset stays constant. But colleagues in DST-observing countries will shift relative to you, so cross-zone meetings still need attention.
For example: India (UTC+5:30, no DST) is 9.5 hours ahead of New York in winter and 9.5 hours ahead in fall, but only 9.5 hours ahead in spring/summer when New York shifts to EDT. Wait — that's the same offset. Why?
Because Indian time doesn't change, and New York shifts. From Mumbai, the shift is invisible — Mumbai stays UTC+5:30. But New York moves from UTC-5 to UTC-4, so the difference between Mumbai and New York changes from 10:30 hours to 9:30 hours.
The meeting planner tracks all of this automatically.
FAQ
When is the next US DST shift?
The next forward shift is the second Sunday of March. The next backward shift is the first Sunday of November. Specific dates depend on the year. The DST calendar lists them.
Do I need to manually change my phone clock?
No. iOS and Android both handle DST automatically using the IANA tz database, as long as you have automatic time enabled.
What if I forget DST is happening this weekend?
Most modern devices handle it for you. You'll wake up Sunday morning and your phone will show the new time. The biggest risk is showing up an hour early or late for a meeting on Monday — confirm your calendar before showing up.
Why does my microwave still show the old time after DST?
Most microwaves don't have DST awareness. You need to manually set the new time. Some newer connected microwaves do auto-adjust.
What time will my flight depart after the DST shift?
Flight schedules display in local time. After the shift, the same numbered flight will depart at the same local clock time, just with a different underlying UTC time. Airlines handle this in their booking systems.
My calendar showed two different times for the same meeting. Why?
Probably the meeting was created without an explicit time zone. Different devices applied different default zones. Fix: re-create the meeting with explicit time zone, or use UTC anchoring.
Bottom line
After the next DST shift, your local clock has shifted by one hour but the underlying UTC moments are the same. Most devices handle this automatically. Recurring meetings shift on local clocks (which is usually what you want, but sometimes creates cross-region confusion).
For looking up exact times for any future date in any city, the time converter handles it including DST.