Set Up Your Phone, Computer, and Calendar for Multiple Time Zones

Most time-zone articles explain what a time zone is or how to think about scheduling. This is not one of those. This is a setup guide. When you finish, every device you own will show the correct time in two or three zones at a glance, your calendar will stop quietly shifting meetings when you travel, and you'll know exactly which setting causes the most common time-zone bug there is: the floating-time trap.

The goal is narrow and worth stating plainly. You want your phone, your laptop, and your calendar to agree with each other and with reality, no matter where you are or who you're coordinating with. The rest of this article configures each one, in order, with the exact menu paths.

Why a second clock beats mental math

If you regularly work with people in another zone, doing offset arithmetic in your head ("they're six hours ahead, so 3 p.m. there is 9 a.m. here?") is slow and error-prone, and it gets worse around **daylight saving time (DST)** changes, when the gap between two zones temporarily shifts because the regions don't switch on the same date. A persistent secondary clock removes the calculation. You glance, you know.

Pick the two or three zones that genuinely matter: your home zone plus a key client, your company headquarters, or family abroad. Don't add ten cities. A cluttered clock is one you stop reading, which defeats the purpose.

iPhone and iPad (iOS)

iOS gives you two solid options.

• World Clock in the Clock app. Open Clock → World Clock, tap +, and search for a city in the zone you want. Each row shows "Today" or "Tomorrow" plus the hour difference, so you can see at a glance when a colleague has already rolled into the next day.
• The Clock widget. Faster, because you never open the app. Long-press the Home Screen, tap + in the corner, search Clock, and add the multi-city widget. To change which cities show, long-press the widget and choose Edit Widget. On the Lock Screen you can add a small Clock complication for one alternate city.

Verify one setting: Settings → General → Date & Time → Set Automatically should be on. That lets the phone update its own zone from your location and carrier as you travel, which is what you want.

Android

Wording varies by manufacturer (Pixel and Samsung label menus differently), but the core feature is the same.

• Open the Clock app and go to the World clock tab.
• Tap the globe or + icon and add your target cities.
• Look for Automatic home clock in the Clock app's settings. When it's on and you travel to a new zone, the app automatically adds a clock for your *home* zone, so you can still see the time back home.

For an at-a-glance view, add a clock widget to your home screen. The stock Google Clock widget and Samsung's combined weather-and-clock widget both let you pick a city; place two side by side for a dual-zone readout.

As on iOS, keep Settings → System → Date & time → Set time automatically on, along with the network-provided time-zone option.

macOS

macOS hides its world clock where many people never look: Notification Center widgets.

• Open System Settings → Date & Time and confirm Set time and date automatically is on.
• Open Notification Center (click the date/time in the menu bar, or swipe in from the right edge of a trackpad), scroll to the bottom, and click Edit Widgets. Choose Clock, then pick the World Clock style. Add one widget per city; you can stack several.
• On recent macOS versions you can also drag these widgets straight onto the desktop.

If you live in the menu bar, a third-party menu-bar clock can show a second zone right beside the system clock. The built-in widget covers most needs without extra software.

Windows

Windows 11 and 10 let you run up to two additional clocks alongside the system clock.

• Open Settings → Time & language → Date & time and enable Set time automatically and **Set time zone automatically**.
• Find Additional clocks. In Windows 11 it sits on the same Date & time page; in older builds it's in Control Panel under Date and Time → Additional Clocks.
• Tick Show this clock, choose a time zone, and label it something readable like "London team" or "Mom (IST)." Repeat for the second clock.

Click the clock in the taskbar and the flyout shows all three times together. It's the quickest dual-zone setup on any desktop OS.

The part that actually breaks: calendar time zones

Device clocks are the easy half. Calendars are where people get burned, because a calendar event isn't just a time. It's a time *attached to a zone*, and that attachment can fail in two opposite ways.

Set your calendar's primary time zone

• Google Calendar: Open **Settings → Time zone. Set Primary time zone to your home zone, then enable Display secondary time zone and pick a second one. Google shows both as labeled columns down the left edge of the week view. Also turn on "Ask to update your primary time zone to your current location"** so the app prompts you when you travel instead of silently changing things.
• Outlook (desktop): Go to **File → Options → Calendar → Time zones. Label your primary zone, tick Show a second time zone (a third is available too), and label each. Both bars then appear in the day and week grids. On Outlook for the web, the equivalent lives under Settings → Calendar → View**.

Set the time zone *on the event*, not just on your app

This is the single most valuable habit in this article. When you create an event that spans zones — say a call with a partner in Berlin — open the event detail view and look for the **time zone selector** next to the start and end times.

• In Google Calendar, click the times while creating the event and choose **Time zone**. You can set a different zone for the start and the end, which is handy for flights.
• In Outlook, expand the event and use the **Time zones** button to attach a zone to the start and end.

When an event carries an explicit zone, it stays anchored to a real-world instant. Fly somewhere else and the event simply moves on your local grid, so a 10:00 Berlin call still rings at the correct moment wherever you are.

The floating-time trap

Here is the bug that wrecks meetings. Some events are stored as floating time: a wall-clock time with *no* zone attached. A floating event set for 9:00 a.m. means 9:00 on whatever clock the viewing device happens to be on. This commonly affects all-day events, items imported from apps that don't store a zone, and entries created by tools that drop the zone.

It sounds harmless until you travel. Set a floating 9:00 a.m. reminder in New York, fly to London, and it now fires at 9:00 a.m. London time — five hours earlier in real terms than you meant (New York 9:00 a.m. is 2:00 p.m. in London). The event "floated" to follow your device instead of staying pinned to the New York morning.

How to avoid it:

• For timed cross-zone meetings, always confirm the event shows an explicit time zone. If the field is blank or reads "device time zone," set it deliberately.
• Reserve floating behavior for things that genuinely *should* follow you. "Take medication at 8 a.m." or "lunch at noon" are correctly floating, because you want them at that local time wherever you are.
• Be wary of all-day events across zones. An all-day item can render a day early or late on someone else's calendar precisely because of zone handling. For a cross-zone deadline, a timed event with an explicit zone ("Submit by 5:00 p.m. New York time") is far safer than an all-day block.

The 7-point setup checklist

Run through this once and you're done.

1. Phone: auto-set date/time on; add a clock widget with your home zone plus one or two key zones. 2. Laptop: auto-set time on; add a World Clock widget (macOS) or Additional Clocks (Windows). 3. Calendar primary zone: set explicitly to your home zone. 4. Calendar secondary zone: enable the second column and label it. 5. Travel prompt: turn on "ask before changing my primary time zone." 6. Per-event zones: make attaching a zone to cross-zone meetings a reflex. 7. Floating check: confirm important cross-zone events show a real zone, not "device time."

A worked example

You're in Chicago (Central Time, America/Chicago) running a weekly sync with teammates in London (Europe/London) and Bengaluru (Asia/Kolkata, India Standard Time).

• Add three clocks: Chicago, London, Bengaluru. When it's 8:00 a.m. in Chicago, it's 2:00 p.m. in London and 6:30 p.m. in Bengaluru. India runs at UTC+5:30, a half-hour offset, and observes no DST.
• Create the recurring meeting with its time zone set to America/Chicago. Every attendee's calendar then translates it correctly, and it survives DST shifts, including the spring and autumn weeks when the US, UK, and India don't change clocks together. In 2026, for instance, US clocks spring forward on March 8 but UK clocks not until March 29, so for three weeks the Chicago–London gap is five hours instead of the usual six. An event anchored to America/Chicago handles that automatically; a floating one would drift.
• Before sending the invite, check the slot against everyone's working hours so nobody lands at 11 p.m. Timezio's [meeting planner](https://timezio.com) and [time zone converter](https://timezio.com) make that a few seconds' work, and the DST checker flags those transition weeks before they bite.

Configure once, then trust it

The point of secondary clocks and explicit event zones is to stop doing arithmetic and stop second-guessing whether a meeting will fire at the right moment. Your devices show the time everywhere you care about; your calendar anchors every event to a real instant instead of a floating number. Get those two things right and most of the cross-zone friction that derails remote teams quietly goes away.