Making a Mac calendar carry a real schedule

The search for a Google Calendar desktop app on a Mac ends the same way every time. The App Store has the iPhone and iPad app. The download pages have Chrome, Drive, and Google Earth. There is no Mac build of Calendar, and Google says so plainly in its own help: the Get started with Google Calendar page states that Calendar cannot be downloaded and installed on a computer, and points to the browser instead.

That closes one door and opens four others. A browser tab, a web app in the Dock, the Calendar app that came with the Mac, or a third party calendar that talks to the same Google account. All four work. All four drop something, and the thing each one drops is what decides the answer.

What Google actually ships, and what it does not

Google Calendar exists as a web application and as mobile apps. On a computer, the supported browsers are Chrome, Firefox, Safari, and Microsoft Edge, with JavaScript and cookies turned on. On an unsupported or outdated browser, Google's help warns that some features stop working and the application might not open at all, with the specific example that calendars can be read but not updated.

Offline support is narrower than most people assume. Google's offline page limits it to Chrome, and states directly that offline access is not supported in Firefox, Safari, or Microsoft Edge. Once it is switched on under Settings, then General, then Offline, the calendar syncs events from the last four weeks and everything in the future. While offline, the calendar is readable but not writable. Events cannot be created or edited, guests cannot be emailed, and tasks are unreachable. Clearing the browser's cached images and files also clears offline support, so it has to be switched back on afterwards.

That is the honest shape of the browser route. It is complete when the network is up, and it is a read-only archive of four weeks when the network is down. For someone who takes a laptop onto a train or into a building with no signal and expects to move a meeting, this is the constraint that matters, and it is the one the download-a-desktop-app articles skip.

Route one: keep it in the browser, but give it a window

The browser route does not have to mean a tab lost among thirty others. macOS has a supported way to turn a webpage into something that behaves like an application.

In Safari, opening calendar.google.com and choosing File, then Add to Dock, creates a web app. Apple documents this as available starting with macOS Sonoma 14. The result is saved into the Applications folder inside the home folder, appears in the Dock and in Spotlight, and runs with a stripped toolbar instead of the full browser chrome.

There is one detail in Apple's documentation that quietly decides whether this route succeeds. A web app shares no cookies, website data, or settings with Safari. Signing into Google in Safari does not sign into the web app. The account has to be added again inside the web app itself, and the same separation applies to notifications: Apple's page specifies that the site's notification request must be answered inside the web app, not in Safari, for the web app to appear in System Settings under Notifications and for the unread badge to show on the Dock icon.

Chrome has an equivalent through its own install-as-app behaviour, which produces a separate window with its own icon. Either way, the calendar is still the web application. Nothing has been made native, and nothing about the offline limits above has changed.

The separation between a web app and the browser cuts both ways, and it is genuinely useful for anyone holding more than one Google account. Because the web app keeps its own cookies, a second web app pointed at the same address can be signed into a different account, and the two sit in the Dock as two icons instead of one tab with an account switcher inside it. The trade is that each one has to be set up separately, including its notification permission, and neither of them shows both accounts in a single grid.

What the browser route costs on a working day

The web application is the most complete version of Google Calendar that exists, so the cost is not missing features. It is friction, and the friction concentrates in three places.

Account switching is the first. Google Calendar displays one signed-in account's calendars at a time, so two work identities means either switching accounts or sharing one account's calendars into the other so they render together. Neither is difficult once, and both are irritating daily.

Window behaviour is the second. A calendar in a tab competes with every other tab for the same window, and the keyboard shortcuts that make Google Calendar fast are only in effect while the page has focus. Command-Tab reaches applications, not tabs, so the calendar is always one extra step away. The Dock web app removes precisely this problem and nothing else.

Startup state is the third. A browser opened fresh shows the calendar only after the page loads, and on a slow connection that load is visible. Applications that keep a local store draw the schedule immediately and reconcile afterwards, which is a difference measured in seconds but noticed every single morning.

Route two: connect the Google account to the Mac's Calendar app

The Calendar app that ships with macOS speaks to Google directly. Google's help gives the steps: open Calendar, go to Calendar, then Preferences, then the Accounts tab, click Add, choose Google, and sign in. On the same Accounts tab, Refresh Calendars sets how often the two sides check each other.

What crosses over is narrower than the account as a whole. Google's page states that the calendars listed under My Calendars sync automatically, along with Birthdays. Anything else, meaning the calendars other people have shared and the subscriptions sitting under Other calendars, does not appear until it has been ticked on Google's Calendar sync page and saved. A missing shared calendar in the Mac's Calendar app is almost always this and not a sync failure. If the older Delegation tool was ever used in Calendar, Google's help says it has to be unchecked under Accounts, then Delegation, before sync will work.

Three Google features do not survive the crossing, named in Google's own list: email notifications for events, creating new Google calendars, and Room Scheduler. Alarms still fire through macOS notifications, but a reminder configured as an email on the Google side will not produce an email once the event is being managed from the Mac. For anyone whose team books rooms through Google, the third item is the one that sends them back to the browser.

Route three: a Mac calendar built by someone else

Several Mac calendar applications connect to the same Google account and put the schedule in a real window. Prices and requirements below were taken from each vendor's own pages on 2026-09-21.

Application	Price	macOS requirement	Notes
Fantastical	Free to download, Flexibits Premium is 6.99 USD per month or 56.99 USD per year on the US App Store	macOS 12.4 or later	Free tier covers accounts, events, tasks, and notifications
BusyCal	49.99 USD one time from BusyMac, 14 day trial, also on Setapp	macOS 12.0 or later	Includes travel time and a menu bar extension
Itsycal	Free, MIT licensed, downloaded from mowglii.com	macOS 11 or later	Menu bar only, reads the accounts the Calendar app already has
Notion Calendar	Free	Published as a macOS download	Built around Google Calendar and Notion workspaces
Morgen	15 USD per month billed yearly, or 30 USD per month billed monthly, 14 day trial	Ships for macOS, Windows, and Linux	Planning and time blocking rather than a plain calendar

Before any of them is paid for, one check is worth more than a feature comparison: connect the Google account, then look for the calendars that were shared by other people. An application that holds its own Google connection will list them without the extra step described above, while an application that reads through the Calendar app will show exactly what the Calendar app is already showing, missing calendars included. That single test tells you which architecture is in front of you, and it takes two minutes on a trial.

Two structural points are worth more than any feature list. First, Itsycal does not hold accounts of its own. It reads whatever the Calendar app is already syncing, which means the Google connection in route two has to be working first. Second, the applications that do hold their own accounts, such as Fantastical and Morgen, talk to Google directly and are therefore not bound by the three features Apple's Calendar app drops.

Which route the problem points to

The routes are not ranked. They answer different complaints.

Working offline on a plane or a train points at route two or three, because the browser gives four weeks of read-only history and nothing writable. Wanting the schedule out of the browser without changing anything else points at route one, the Dock web app, which takes about a minute. Room booking and Google-side email reminders point back at the browser, because those are the features that do not cross into other applications.

A schedule that is genuinely spread across accounts, such as a work Google account, a personal one, and an iCloud calendar shared with family, points at route three. That is the case the built-in Calendar app handles adequately and specialised applications handle well, since colour rules, calendar sets, and per-account filtering are where they spend their design effort. A comparison of how different Mac calendars handle that case is collected in Compared with other calendars.

Making the choice stick

Whichever route is taken, two settings decide whether the calendar is trustworthy a month later. Refresh frequency, because a calendar that checks every hour will show a meeting that was moved forty minutes ago as still happening. And notification permission, granted to the specific application or web app that is supposed to alert, which is where the Dock web app catches people out.

Travel time is the third setting worth attention, and it is the one that separates a calendar that lists events from a calendar that protects a day. Setting it means the alert fires when it is time to leave rather than when the meeting starts, and the mechanics of that are covered in Travel time.

What to change first

Start with route two, since it costs nothing and reveals the real problem. Add the Google account in the Calendar app, tick the missing calendars on Google's sync page, and use the schedule for a week. If what is missing after that week is room booking or Google-side email reminders, the browser is the answer and a web app in the Dock makes it bearable. If what is missing is speed, offline editing, or control over several accounts at once, the next step is a native calendar, and Caltimate is built for that case.