Apple Calendar with Multiple Time Zones (2026): Mac, iPhone, and iPad Setup That Actually Works

Apple Calendar handles multiple time zones better than most people think. The catch: the feature is switched off by default on the Mac, hides behind a confusingly named setting on iPhone, and even fully configured it still lacks the two things Google and Outlook users lean on. This post covers all of it.

Turn on time zone support on the Mac

Out of the box, Calendar on macOS pins everything to your system clock. To change that:

Open Calendar, then Calendar > Settings (Cmd + comma).
Go to the Advanced tab.
Tick Turn on time zone support.

Two things appear. A time zone menu shows up in the top-right corner of the Calendar window, and every event editor gains a Time zone field.

The menu in the corner changes your viewing zone. Pick "Sydney" and your whole week redraws in Sydney time, which is the fastest way to sanity-check what a proposed slot looks like on the other side before you send the invite. Your events don't move; you're just looking at them through a different clock.

The per-event field is the more important one. An event created for "9:00 AM, Auckland" stays at 9:00 AM Auckland time no matter where you travel or what DST does. Without time zone support, that event silently means "9:00 AM wherever my laptop happens to be," which is how people end up calling into meetings an hour late from a hotel.

There's also a floating option in the per-event time zone picker. A floating event stays at the same wall-clock time in whatever zone you're in. Right for "gym at 7 AM," wrong for anything with other humans in it.

iPhone and iPad: what Time Zone Override actually does

On iOS the equivalent setting is Time Zone Override. You'll find it under Settings > Apps > Calendar on iOS 18 and later, or Settings > Calendar on earlier versions.

The name trips everyone up, so here is the plain version:

Override off (the default): events display in whatever zone your phone is currently in. Fly from London to New York and your 3 PM London meeting correctly shows as 10 AM.
Override on: everything is pinned to the one zone you chose, regardless of where you are. Your calendar becomes a fixed reference clock.

Leave it off unless you have a specific reason. The main legitimate use is short trips where you want to keep living on home time: two days in another zone, all your commitments still anchored back home, no mental conversion. Turn it on, set your home zone, turn it off when you're back. People who leave override on permanently and then relocate get a calendar that quietly lies to them.

When creating an event on iPhone, the event editor has its own Time Zone row below the start and end times. Same rule as the Mac: set the zone the meeting is actually defined in, especially for recurring meetings organised by someone in another country.

What Apple Calendar won't do

Two honest gaps compared to Google Calendar and Outlook:

No second time column. Google can show two zones side by side down the left edge of day view. Apple gives you one zone at a time, switched from the corner menu.
No world clock sidebar. There's no built-in strip of "here's the current time for these five cities" inside Calendar.

Workarounds that mostly close the gap:

World Clock widgets. Both macOS and iOS ship a World Clock widget (from the Clock app) that holds multiple cities. On the Mac, park one in Notification Centre or on the desktop next to your calendar.
A pinned overlap board. A Timezoners board shows your actual teammates and their working hours rather than abstract city clocks, and a browser tab of it does more than a second time column would anyway. Paste the board link into the notes of your recurring cross-zone events so every attendee gets the same live view.

Recurring meetings and DST

Apple Calendar stores events against a time zone, not a UTC offset, so a weekly meeting set for 10:00 AM New York time correctly stays at 10:00 AM New York when clocks change. The people it drifts for are the attendees in countries that change on different dates, and no calendar app can fix that; it's a property of the planet.

What you can do is make the anchor explicit. Put one line in the description of every recurring cross-zone series: "This meeting is anchored to 10:00 New York. If DST just moved for you and it didn't for New York, your local time shifted." That sentence costs nothing and answers the twice-yearly confused Slack message before it gets sent.

For the specific 2026 dates when the US, UK, and Australia move their clocks, see our US-Australia overlap guide.

A sane traveller's checklist

Before a trip across zones:

Confirm Time Zone Override is off on the phone so the calendar follows you.
On the Mac, use the corner menu to preview your week in the destination zone. Look for anything that landed at 3 AM.
For meetings you organise, check the event's own time zone field says what you mean, not just a time.
Decline or move the conflicts before you fly, not from the airport.

Common questions

My event shows the wrong time on my iPad but the right time on my Mac. One device has Time Zone Override on. Check Settings on the iPad; nine times out of ten that's the culprit.

Can I see a colleague's time zone in Apple Calendar? Not directly. Invitees show their response status, not their local time. This is exactly the gap a shared board covers: their working hours sit next to yours and the overlap is visible before you propose a slot.

Do zone changes sync through iCloud? Event time zones sync, yes. The Mac's viewing zone and each device's override setting are per-device, which is why the previous question happens.

Should I just schedule everything in UTC? No. Set events in the zone the meeting is anchored to, usually the organiser's. UTC is for servers and logs. Humans reschedule around local mornings and school runs, and a UTC-labelled invite makes everyone do a conversion to find out if they can make it.