April 19, 2026

Google Calendar Time Zones: The Complete Guide

Everything you need to know about time zones in Google Calendar — settings, travel, cross-region meetings, and the edge cases that trip people up.

The thing nobody tells you about calendar time zones

Google Calendar does not store events in your time zone. It stores them in UTC and translates on display. Every event has a start instant and an end instant, anchored to a specific moment in the world, and your calendar shows them in whatever zone you are currently set to.

That single fact explains almost every time zone bug you have ever seen. An event that looks right at 3pm when you create it can look wrong at 9am the next morning if your phone and laptop disagree about which zone you are in, or if daylight saving time crossed in between.

Understanding how Google Calendar handles zones is the difference between confident cross-region scheduling and the recurring nightmare of missed or doubled meetings.

The two settings that control everything

In Google Calendar settings, under General → Time zone, you will find two fields.

Primary time zone. This is the zone your calendar displays in by default. Every event without an explicit zone is shown in this one.

Display secondary time zone. Adds a second column to the left of your calendar showing another zone side by side. This is the single most useful setting for anyone who works across regions.

Below these, a third option matters: Ask to update my primary time zone to current location. With this on, Google Calendar prompts you to switch zones when you land somewhere new. Leave it on unless you have a specific reason not to.

Setting time zones on iPhone

Open Settings on your iPhone → General → Date & Time. The system-level Automatically toggle controls what your iPhone thinks your current zone is. The Google Calendar app reads this. If your iPhone zone is wrong, your calendar app is wrong.

In the Google Calendar app itself, open the hamburger menu → Settings → General → Use device time zone. With it on, the app follows your iPhone. With it off, you can lock the app to a specific zone regardless of where the phone thinks it is.

Setting time zones on Mac

System Settings → General → Date & Time controls the Mac's zone. Google Calendar in the browser follows your Google account setting, not the Mac's — but Apple Calendar follows the Mac. If you use both, keep both in sync.

Events across time zones

Google Calendar has a feature most people miss: per-event time zones. When you create an event, click the start time, and you will see a Time zone option. You can set a different zone for the start and the end.

This is useful in two specific cases.

Flights. A flight from New York to London leaves in EST and arrives in GMT. Set the start time in EST and the end time in GMT, and the event displays correctly no matter which zone you view it from.

Events happening elsewhere that you do not want to shift. A conference session "at 2pm local time in Tokyo" should stay at 2pm Tokyo even when daylight saving changes in your home zone. Setting the event's zone to Asia/Tokyo locks it there.

For normal meetings with people in another zone, you do not need per-event zones. Just create the event in your own zone and Google will show it correctly to everyone based on their own settings.

Traveling with your calendar

The reliable workflow when traveling:

1. Before you leave, do not change your calendar zone. Create any travel-related events with explicit time zones (flights especially). 2. When you land, let Google Calendar prompt you to switch your primary zone. Accept it. 3. On arrival, verify one or two events in the new zone look correct. Time zone bugs show up most often right after a zone switch. 4. When you return home, repeat.

The common mistake is manually changing zones before leaving. Doing so shifts the display of events you already created, which can make them look wrong even though the underlying time is correct. Trust the automatic switch on arrival.

The "I set it in the wrong zone" problem

If you created an event while your calendar was set to the wrong zone, the event is stored at the wrong UTC instant. Fixing the display requires editing the event, not the zone. Open the event, change the start time to the correct one, save. Do not try to fix it by switching zones — that will break something else.

Scheduling across regions

A few habits that save hours.

Turn on the secondary time zone display. If you regularly work with one other region, putting their zone next to yours removes mental arithmetic. Settings → General → Time zone → Display secondary time zone.

Use the "Find a time" feature. In the event editor, the Find a time tab shows the calendars of invitees side by side with their zones translated. This is far more reliable than asking everyone to send their availability in text.

Write zones explicitly in event titles for shared calendars. "Strategy review (10am PT / 1pm ET / 6pm UTC)" in the title removes ambiguity for attendees who open the event from an app that is not showing their zone correctly.

Avoid 9am and 5pm. Daylight saving time changes in the US, Europe, and Australia do not align. Events scheduled near start-of-day or end-of-day in one region can fall outside working hours in another for a few weeks each year. Schedule in the middle of the day when possible.

Daylight saving time, the silent killer

DST shifts happen on different dates in different countries. The US shifts on the second Sunday in March and first Sunday in November. Europe shifts on the last Sunday in March and last Sunday in October. Australia shifts in October and April, in the opposite direction because of the southern hemisphere. Many countries do not observe DST at all.

For the two to three weeks between US and Europe DST transitions, the time difference between New York and London temporarily drops from five hours to four, or expands from five to six. Recurring meetings set up without this in mind will fire at the wrong local time for one side during those windows.

There is no clean fix — Google Calendar does its best to translate correctly, but recurring events created with a specific zone will sometimes land at an unexpected local time for attendees in a different zone. The practical workaround: during transition weeks, double-check any cross-region recurring meetings manually.

See the Google Calendar time zone help article for the reference behavior.

Working hours and time zones

If you have set working hours in Google Calendar (Settings → Working hours and location), they are defined in your primary zone. When colleagues in other regions use Find a time to schedule with you, their app translates your working hours to their zone.

If you move across zones frequently, keep working hours defined and update your primary zone on arrival. The combined behavior means people scheduling with you will see your actual availability wherever you are, not your old availability translated through a stale zone.

The edge cases worth knowing

All-day events do not have zones. An all-day event on April 19 is April 19 everywhere. This is usually correct for birthdays and holidays, occasionally wrong for things like conference days that technically span two zones.

Recurring events and zone changes. If you move zones permanently, existing recurring events continue to fire at their original zone's local time. To fix them, edit the series and save. Google will re-anchor the recurrence to your new primary zone if you explicitly change the time.

Zones vs offsets. "UTC+1" is an offset, not a zone. "Europe/Paris" is a zone that is UTC+1 in winter and UTC+2 in summer. Always pick a zone, never an offset, when creating events — otherwise DST handling breaks.

Shared calendars in organizations. Calendar zones are per-user, not per-calendar. Every attendee sees the same event translated to their own zone. This is the correct default, but it means you cannot force everyone to see a meeting "in Tokyo time."

How Daychat fits

Daychat reads your Google Calendar settings, including your current primary zone, and interprets natural-language input accordingly. When you say "schedule a call with the Tokyo team on Thursday at 9am their time," it sets the event in the Asia/Tokyo zone so it stays correct regardless of where you open the calendar next. When you travel, Daychat follows your device's zone for new events, so what you type matches what lands on your calendar.

Try Daychat for free

Chat with your Google Calendar today.

Download on the App Store