Google Calendar Settings Not Syncing? What Actually Syncs

When Google Calendar looks different on your Mac, phone, and in the browser, it is tempting to call the whole thing a sync problem. Usually it is not one problem. Google Calendar has account data, calendar visibility, and app-level preferences—and those move through different paths.

This guide gives you a practical way to separate them. Start with Google’s source of truth, then check the calendar and device that are actually out of step. It also explains what a desktop client such as hora can refresh from Google, and what stays deliberately local to your Mac.

The short answer: events and calendar membership live with the Google account. A calendar app’s layout, notification choices, cached data, and many device settings often do not. The symptom matters more than the word “sync.”

1. First, identify what is missing

Before changing any setting, open calendar.google.com in a browser while signed into the same Google account. If the event is missing there too, the issue is upstream: it may have been created in a different account or calendar, or not saved as expected. Google’s own troubleshooting starts with the same basic checks: confirm the account and calendar, then make sure the calendar is visible.

If the event exists on the web but not on your Mac, you have narrowed the issue to the local client, its account connection, its visible calendars, or the time it last refreshed. Google also notes that a calendar can be hidden from the current view, which can look exactly like a missing event. See Google’s sync troubleshooting guidance for the account-and-calendar checks.

2. What Google Calendar normally syncs

Think of Google Calendar as the shared record for a Google account. Events, their times, guests, recurrence rules, calendars you own or subscribe to, and changes made by collaborators are account data. Once a client authenticates to that account and is allowed to see a calendar, it can read those changes from Google.

That does not mean every screen will look identical. A browser, an iPhone, Apple Calendar, and a dedicated Mac app can choose different default views, show different sidebars, or expose different controls. The important diagnostic question is: is the underlying event present in the account?

3. What often stays on one device

Many “settings not syncing” reports are actually about app preferences. Things like window position, week versus month view, color appearance, keyboard shortcuts, notification style, menu-bar behavior, cached data, and which calendars are currently collapsed can be specific to one app or device.

Notification behaviour is especially easy to misread. Google-level event reminders may travel with an event or calendar, while macOS notification permissions and an app’s own alert presentation are controlled locally. If an event appears correctly but no alert arrives, investigate notifications separately from calendar data.

4. A reliable troubleshooting order

Use this order to avoid disconnecting an account before you know what failed:

1. Check calendar.google.com in the same Google account. 2. Check that the correct calendar is visible, not merely the event. 3. Confirm the Mac app is signed into that same account and has permission to read calendars. 4. Refresh or reopen the client, then give it a moment to complete a sync. 5. Only then investigate the app’s local settings, network connection, or a reconnect.

The distinction between live data and cached data matters here. A desktop client may keep a local copy so it opens quickly and remains useful during a short network interruption. That cache is not a second source of truth; it must be refreshed from Google before it can reflect a new remote change.

5. What this means in hora

hora is a native Mac client that connects directly to Google Calendar. It keeps calendar data cached locally for speed and offline resilience, then refreshes it from Google. The app supports the calendar data you expect to be shared—timed and all-day events, recurring events, focus time, working location, out-of-office events, and appointment schedules. For a deeper explanation of the mechanism, read our real-time Google Calendar sync on macOS build note.

With the relevant optional permission enabled, hora can use Google Calendar watch channels, a small Hora service, and Apple Push Notifications to trigger a refresh soon after Google reports a change. It is important not to call that “instant” synchronization: background delivery can be delayed, coalesced, or unavailable, so the app also has a fallback refresh path. The result is a design that is fast in normal use without promising something the platform cannot guarantee.

Your event titles, descriptions, attendees, and meeting links are not sent to the Hora notification service for that push-assistance flow. The service receives the minimum identifiers needed to trigger a local refresh; the Mac app then retrieves calendar data from Google. You can read the product-level privacy explanation in hora’s support documentation.

If an event is present at calendar.google.com but not in hora, start by checking the signed-in Google account and visible calendars, then allow a refresh to finish. If it is absent from Google’s web calendar too, fix it at the source first. That order avoids treating a local display symptom as a data-loss problem.

6. Do not confuse a sync issue with an integration choice

Some calendar applications read Google Calendar through a purpose-built API; others rely on CalDAV or system-level accounts. The transport affects which fields and event types an app can represent, but it does not change the basic diagnostic rule: verify the Google account’s record first. Our Google Calendar API vs. CalDAV guide explains why that decision matters for a Mac calendar app.

When the event is correct online and the local app has had time and permission to refresh, the next step is specific to that app. When the event is wrong online, changing a Mac preference will not fix it.

A calmer way to debug Google Calendar

“Not syncing” is a useful description of a symptom, not a diagnosis. Check the shared record first, then the selected calendar, then the client’s connection and local presentation settings. That sequence is quicker, safer, and makes it much easier to tell whether you need to edit an event, unhide a calendar, refresh an app, or change a notification preference.

If you are choosing a dedicated Mac client in the first place, our guide to a Google Calendar app for Mac compares the browser, Apple Calendar, multi-provider apps, and a focused native client.

Frequently asked questions

Do Google Calendar settings sync across devices?

Account data such as events and calendars sync through Google. Many settings that control a particular app’s appearance, cache, notifications, or window behaviour remain local to that device or app.

Why does an event show in Google Calendar on the web but not on my Mac?

Check that the Mac app uses the same Google account, that the event’s calendar is visible, and that the client has completed a refresh. If the event is absent on the web too, the issue is in the account data rather than the Mac app.

Does a local cache mean my Google Calendar changes are lost?

No. A cache is a local copy used for speed and resilience. After the client connects and refreshes, it should reconcile with the current data in Google Calendar.

Does Google Calendar sync instantly?

No client can honestly guarantee that. A change can be detected quickly, especially with push-assisted refresh, but network conditions and background-delivery policies can introduce a delay.