Getting Google Calendar and Mac Calendar to agree

The events live in Google Calendar. The Mac has Calendar sitting in the Dock, and Calendar either shows nothing, or shows half of what the browser shows. Most instructions stop at "add the account and you are done", which is true for about ten minutes, until a shared calendar fails to appear or an invitation refuses to send an email.

The connection between Google Calendar and Calendar on macOS is real and supported, and it has a specific shape. Some things cross over, some things do not, and a few settings decide which. Knowing that shape up front saves an hour of clicking around later.

Two different things get called syncing

Google documents two ways to see a Google calendar inside another calendar application, and they behave nothing alike.

The first is an account connection. The Mac signs in to the Google account, and the calendars come across as editable calendars. Create an event on the Mac and it appears in the browser. Change a time in the browser and the Mac catches up. This is what most people mean by adding Google Calendar to Calendar.

The second is a subscription to a link. Google can hand out an address for a calendar in iCal format, and Calendar can subscribe to that address. The result is read only. Events show up, and nothing typed on the Mac goes back to Google. Google's own page on syncing with computer programs separates these two as "view and edit" versus "view only".

There is a third thing people sometimes mean, and it does not come free with either method: pushing iCloud events into Google Calendar. Connecting a Google account to Calendar on a Mac sends nothing in that direction. iCloud events stay in iCloud. Getting them into the Google web interface means publishing the iCloud calendar as a public address and subscribing to it on the Google side, which again lands read only. Anyone who wants one editable pool of events on both sides is going to have to pick one account as the home for new events.

Connecting the account on a Mac

Two doors lead to the same place.

From Calendar: open Calendar, then Calendar in the menu bar, then Settings. On older versions of macOS that menu item reads Preferences. Go to the Accounts tab, click the plus button under the list of accounts, pick Google, and continue. A sign in sheet opens, the Google password and second factor go in there, and Google asks for permission to let the Mac see and change calendars.

From System Settings: open System Settings, go to Internet Accounts, add a Google account, and tick Calendars in the list of things that account should handle. Mail and Contacts can stay off if only the calendar is wanted.

Both routes end with the account listed in Calendar's Accounts tab. The setting worth touching immediately is Refresh Calendars, in that same Accounts tab. It controls how often the Mac asks Google for changes, and the interval chosen there is the floor for how stale the Mac's view can be. A manual refresh is available any time from the View menu.

Sign in failing on a work address is usually not a password problem. A Google Workspace administrator can control which outside applications are allowed to connect to accounts in the domain, and the sign in then stops at the approval screen rather than at the password. That is a question for whoever runs the domain, not something a setting on the Mac can override.

Deciding which Google calendars actually appear

This is where most of the complaints start. The account connects, and then one calendar is missing.

Google's rule is narrow. Calendars listed under My calendars in the browser sync automatically, along with Birthdays. Everything else, which includes calendars other people have shared and calendars subscribed to from outside, sits under Other calendars and does not come across until it is selected on Google's calendar sync page. That page lives inside the Google account settings, shows a checkbox per calendar, and needs a save before it takes effect. Google's instructions for adding Google Calendar events to Apple Calendar walk through the same screen.

After saving there, force a refresh on the Mac rather than waiting. A calendar that was just enabled often appears on the next manual refresh and not before.

Two further switches hide in plain sight. Each calendar in Calendar's sidebar has a checkbox, and unchecking it hides the calendar without disconnecting it, which looks identical to a sync failure. And Calendar has a Delegation tab per account, used in the past to reach other people's calendars. Google states that delegation has to be turned off for the normal sync to work, so any leftover ticks in that tab are worth clearing.

What does not cross the border

Google publishes a short list of features that do not work once a Google calendar is being used through Calendar on a Mac, and the list is more consequential than its length suggests.

Email notifications for events do not work. An event created on the Mac can carry an alert that the Mac shows, but the email reminder Google would have sent is not part of the deal. Anyone relying on a reminder landing in an inbox needs to create or edit that event in the browser.

New Google calendars cannot be created from the Mac. Calendar will happily make a new local or iCloud calendar, which is not the same thing and will not appear in the browser. Creating a Google calendar is a browser job, after which it has to be enabled on the sync page described above.

Room Scheduler does not work. Booking a meeting room in an organisation that manages rooms through Google stays a browser task.

Guest handling deserves a separate note. Invitations sent from the Mac do go out, and replies from guests do come back, but the Mac is not the place to debug an invitation that never arrived. Open the event in the browser and look at the guest list there, because that is the copy Google acted on. The same applies to an event that arrived from someone else and shows the wrong response: change the response in one place and give the refresh interval time to settle before changing it again.

Beyond that list, treat anything Google has built on top of plain events as browser territory. The safe assumption is that a plain event with a time, a place, a note and a guest list travels intact, and that anything cleverer probably does not.

When events arrive late, or stop arriving

Run this in order, because the cheap checks catch most cases.

Confirm the event exists on the server by opening the same account in a browser. If it is not there either, the problem is on the device that created it, not on the Mac.

Check the refresh interval in the Accounts tab, then force a refresh from the View menu. A long interval looks exactly like a broken connection for as long as the interval lasts.

Check the checkbox next to the calendar in the sidebar, and check that the calendar is enabled on Google's sync page. A calendar someone shared last week is the classic case.

Check Internet Accounts to confirm Calendars is still switched on for that Google account. A password change or a revoked session can leave the account listed but inert.

Clear the Delegation tab for the account.

If all of that is clean, remove the account from Internet Accounts and add it again. Nothing stored only on the Mac is lost, because the events belong to Google. Before doing that, note which calendars were ticked, since the selection has to be redone.

Duplicate events are the reverse of this problem and have a narrow set of causes. The usual one is the same calendar arriving twice, once through the account connection and once through an older subscription link that nobody removed. The second is the same Google account added twice under slightly different addresses, such as an alias and the primary address. Both show up clearly in the Accounts tab, and deleting the redundant entry is safe because the events belong to Google either way.

When even a fresh connection lags, the next thing to look at is not Calendar. It is the Mac's network and power behaviour: a machine that sleeps aggressively will not poll, and a captive network at a hotel or an office guest network can leave the connection half open. Testing the same account on a phone on cellular data separates a Google problem from a Mac problem in about a minute.

The read only route, and when it beats the account

Subscribing to a link is the right answer more often than its reputation suggests.

In Google Calendar's settings for a specific calendar, there is an address in iCal format. The private version of that address works without signing in, which is exactly why it deserves care: anyone holding that address can read the calendar until the address is reset. On the Mac, File then New Calendar Subscription takes the address, and the subscription gets its own refresh interval.

This route suits three situations. A calendar that is only ever read, such as a team schedule or a season fixture list. A second Google account that should not be fully connected to the machine. And a shared calendar that keeps failing to appear through the account connection, where a subscription gets the events on screen today while the sharing question is sorted out later.

The cost is that the calendar is frozen from the Mac's side. No editing, no accepting invitations, no new events. That is a reasonable trade for a reference calendar and a bad one for a working calendar.

If Calendar itself is the weak link

Sometimes the connection is fine and the application is the problem. Calendar on macOS is deliberately plain, and that plainness shows up as slow event entry and thin views. A dedicated calendar app for Mac connects to the same Google account through the same mechanism, so nothing above changes, and adds its own entry and display layer on top. Typing a whole event as one sentence rather than filling a form is the difference people notice first, and it is worth seeing how entering events works before assuming the built in flow is the only option.

App	Listed price	Runs on	Connects to Google
Calendar	Included with macOS	macOS	Yes, account connection
Fantastical	Free tier, Flexibits Premium listed at 6.99 USD per month or 56.99 USD per year on the US App Store	macOS 12 or later, iOS, iPadOS, watchOS	Yes
BusyCal	49.99 USD, 14 day trial, also on Setapp	macOS 12.0 or later, iOS	Yes
Notion Calendar	Free	macOS, Windows, iOS, Android	Yes, plus Outlook and iCloud synced calendars
Morgen	14 day trial, Pro listed at 15 USD per month billed yearly or 30 USD per month billed monthly	macOS, Windows, Linux, mobile	Yes
Itsycal	Free	macOS 11 and later	Reads calendars already set up on the Mac

Prices and requirements above are the ones published on each maker's own pages at the time of writing, and they move. A side by side view of what these apps do differently sits on the comparison page.

What to change first

Connect the account, then open Google's calendar sync page and tick every calendar that matters, because that single screen explains most missing calendars. Set Refresh Calendars to the shortest interval offered, and only then judge whether the built in app is fast enough for daily use. If event entry is the part that grates, try a dedicated Mac calendar such as Caltimate against the same Google account before rebuilding any workflow.