Syncing Google Calendar with your Mac

Most people searching for how to sync Google Calendar with a Mac are not at the setup stage. The account is already added. Something about it is just wrong: an event created on the phone takes an hour to appear, a calendar a colleague shared is nowhere in the sidebar, a deleted meeting is still sitting there. The symptoms look like software failure, and they almost never are.

One fact makes the troubleshooting much faster. Syncing does not move the calendar to the Mac. The events stay on Google's servers, and the Mac holds a copy that it refreshes. Nothing is being converted, and nothing is at risk of being lost. Almost every problem below is a setting that does not match the expectation, which means each one has a specific place to look rather than a general fix.

Three different things get called syncing

The word covers three arrangements on macOS, and they behave differently enough that naming the current one is the first step.

The first is using the web version, either in a browser tab or installed as a standalone window through Chrome or Edge. Nothing syncs here. The screen is Google's, rendered live. Delays and duplicates do not occur, but the calendar sits outside macOS notifications, Focus modes, and Notification Center widgets.

The second is adding the Google account to the Calendar app included with macOS. This connects over CalDAV, the open protocol for calendar clients, and pulls events into a local database. Nearly every symptom described below belongs to this arrangement.

The third is a third party calendar app for Mac connected to the same account. Most of them use the same protocol, so the symptoms and the fixes match the second case. Some use Google's own API instead, which changes how quickly updates arrive. Compared with other calendars lays out where those paths differ.

Naming the current arrangement matters because the complaint changes meaning. Someone using the web version who reports slow syncing is describing a page that needs reloading, not a sync interval.

Setting up the account, and the three checks right after

Adding the account takes about a minute, and it should not involve typing a CalDAV server address by hand.

• Open System Settings and select Internet Accounts.
• Choose Google. A real Google sign in window appears, so two factor prompts and Workspace policies behave normally.
• Tick Calendars. Untick Mail and Contacts if only the calendar is wanted.
• Open the Calendar app and look at the sidebar.

That last step is where the actual work starts, because three settings decide whether the result feels correct.

Which calendars came across

A Google account usually holds more than one calendar: a primary one, any secondary ones created later, and any shared by other people. They do not all arrive automatically. A calendar missing from the sidebar is almost always switched off for sync on the Google side rather than hidden locally. Comparing the sidebar against the list visible in the web version identifies exactly which ones are absent.

How often it refreshes

CalDAV polls. The Mac asks the server for changes at a set interval instead of being pushed them the moment they happen. The Calendar app exposes this per account, and the default can be as long as an hour. Setting it to the shortest available value resolves the majority of complaints about slow syncing, because the sync was never broken, only waiting.

Which app is allowed to notify

Opening the same account in several places means alerts arrive from all of them: the web version, the Calendar app, a third party app, and the phone. Four copies of the same reminder trains a person to dismiss all four. Decide which one notifies and turn the others off during setup, not after the habit forms.

Events arriving late, or only travelling one way

Work through this in order.

First, establish the direction. Events created on the Mac usually reach the phone quickly, because the Mac writes to the server immediately. Events created on the phone reach the Mac slowly, because the Mac only learns about them on its next poll. That asymmetry is the design working as intended, not a fault.

Second, shorten the refresh interval. If the delay disappears, the problem was the wait.

Third, if a specific event never arrives at all, check whether the calendar it belongs to is enabled for sync. Late and absent look identical for the first hour, and they have different causes. Deleting the account and adding it again does not help with the second one, and returns the setup to the same state.

Fourth, if events refuse to save in one direction, look at permissions. Calendars shared by other people are often shared read only. Adding an event to one of those either fails silently or appears briefly and then vanishes. The app is not malfunctioning. The sharing setting does not allow writes.

Fifth, check which calendar new events are being saved to. Every calendar app has a default calendar for new entries, and after adding a Google account that default may still point at a local or iCloud calendar. Events created that way are saved correctly and never reach Google at all, which looks exactly like a one way sync failure. The setting sits in the Calendar app preferences, and changing it applies only to events created afterwards. Anything already saved to the wrong calendar has to be moved, which is a matter of editing the event and changing its calendar rather than recreating it.

Duplicates, and events that will not delete

Duplicates come from one of two places.

The same meeting genuinely exists on two calendars. A work account and a personal account both hold it, or accepting an invitation created a copy on a personal calendar. Turning off the display of one calendar in the sidebar removes the duplicate without deleting anything.

Or the same account was added twice. Adding Google through Internet Accounts and then adding the same address again as a manual CalDAV account produces two connections reading the same data, which produces two of every event. Opening the account list and looking for the same address on two rows settles it in a few seconds.

Events that will not delete are usually about ownership rather than caching. Deleting an invitation removes it from the personal calendar but not from the organiser's, so it can reappear as still scheduled elsewhere. A delete made on the Mac also needs one poll cycle to be visible on the phone, so a minute of overlap is normal.

Before deleting the account and adding it again

Removing the account and setting it up from scratch is the usual first reaction, and it splits cleanly into cases where it helps and cases where it cannot.

It helps when the sign in itself has expired. Changing a Google password or replacing the device used for two factor authentication can leave a stale connection that never prompts for reauthentication. Adding the account again restores it.

It cannot help when the calendar is not enabled for sync on the Google side, because the new connection reads exactly the same settings and arrives at exactly the same result. Repeating the process a third time changes nothing except the time spent. Checking the sidebar list and the refresh interval before removing anything takes under a minute and prevents most of these loops.

Why the phone and the Mac look different

Reports that the same account looks different on an iPhone and a Mac are common, and the cause is almost never sync. Several settings are stored per device.

Calendar colours are one. A colour chosen in the web version does not always travel, and a client can assign its own based on the order calendars were added. The events are identical, so a colour mismatch is not evidence of anything being wrong.

Which calendars are displayed is another. Hiding a calendar on a phone hides it on that phone only. Seeing it on the Mac means the Mac still has it ticked. Anything described as appearing on one device only is usually this, and the fix is in the sidebar rather than in the account settings.

Notification behaviour is a third. The reminders attached to an event are stored with the event and are shared, but how each device chooses to present them is governed by macOS and iOS separately. A Focus mode active on one machine silences alerts there while the other one rings, which reads as broken sync even though the event is present in both places.

When a work account will not connect

Google Workspace administrators can block third party apps from connecting to an account. When that is set, sign in often succeeds while the calendar never populates, or the sign in stops at a screen requesting administrator approval.

The test is simple. Add a personal Google account to the same Mac. If that one syncs correctly, the Mac is configured properly and the block is on the work account. No local setting will change that, and the next step is asking the administrator whether external calendar clients are permitted.

The web version usually still works in this situation, including the Google Workspace features that exist nowhere else: appointment schedules, working hours, and out of office blocks. Installing it as a standalone window is often the practical answer for a locked down work account.

What sync cannot fix

Once the setup is correct, the remaining problems fall into two shapes, and neither is solved by syncing faster.

The first is events that never get entered. Something is agreed verbally, the form feels like too much work in the moment, and it is forgotten by evening. A perfectly synced calendar that is missing a third of the week is still wrong. The fix is a shorter path from decision to saved event, which is what Entering events covers.

The second is a day that is accurate and still impossible. Two meetings, both correctly entered, both with alerts that fired, with no way to travel between them in the gap. Nothing in the sync layer addresses that, because the calendar was never asked to represent the movement between events. Travel time explains treating that gap as part of the schedule instead of something held in memory.

Distinguishing the two takes about a week of noting one line on every day that went badly. The notes cluster quickly, and they point at different tools. Missing events point at the entry path. Impossible days point at how the schedule handles the space between commitments. Reading those notes is faster than reading comparison articles, because they describe the actual week rather than a feature list.

What to change first

Shorten the refresh interval, confirm every expected calendar is actually listed in the sidebar, and pick one app to handle notifications. Once the setup is no longer the problem, keep a week of notes on what actually broke each day, and if the answer is travel between correct events rather than missing ones, look at what a native option like Caltimate does with that gap.