Google Agenda on a Mac, outside the browser
There is no Google Agenda app for Mac to download. Google Agenda is the name Google Calendar carries in French, Dutch and Portuguese, and Google lists only four places where it runs: the web, the Android and iOS apps, and Wear OS or Apple Watch. The Google Calendar product page says so in one sentence, and the Google Calendar listing on the App Store shows compatibility lines for iPhone, iPad and Apple Watch, with no line for Mac (both checked on October 18, 2026). Every "download" button that promises a desktop build is a third party client, a browser feature, or an installer around the web address.
So the real question is not where to download it. It is which of five working arrangements fits the way the calendar is used: inside Apple Calendar, as a Safari web app, as a Chrome web app, as a separate app built by a site to app tool, or through a paid client. Each one is set up in a few minutes. They differ in what they keep from Google's own screen and what they give up.
The short answer by situation
Most people searching for this want one of three things, and each has a clear first choice.
- One grid for every calendar. If a work Google calendar has to sit next to an iCloud family calendar, Apple Calendar with a Google account added is the first choice. The data merges, and nothing else does that for free.
- Google's own screen, but out of the tab pile. If the complaint is only that the calendar gets lost among browser tabs, a web app is the first choice. The interface stays identical, so every keyboard shortcut and every Google view still works.
- A purpose-built Mac client. If the goal is a menu bar view, natural language entry or a different design, a paid client is the route, and it costs money every month or once.
The rest of this guide covers each route with the exact menu names, the limits that matter, and the settings to change before relying on it for meetings.
Route one: add the Google account to Apple Calendar
Every Mac ships with Calendar, and it accepts a Google account directly. Apple's Calendar User Guide gives the path:
- Open the Calendar app.
- Choose Calendar, then Add Account.
- Select Google, click Continue, and sign in when the browser window opens.
Each account appears as its own group in the sidebar. If the sidebar is hidden, choose View, then Show Calendar List.
The detail most guides leave out is which calendars actually arrive. Google's help article on adding Google Calendar events to Apple Calendar says that only the calendars listed under "My Calendars" and the Birthdays calendar sync automatically. Calendars that someone else shared, team calendars and room calendars stay missing until they are ticked on Google's Calendar sync page, saved, and then refreshed in Apple Calendar. If a colleague's calendar is visible in the browser but not on the Mac, that page is the reason.
The same article points to two other settings. On the Accounts tab, Refresh Calendars sets how often Apple Calendar pulls changes. And if the old Delegation tool was ever used for this account, its calendars have to be unchecked, or sync does not work.
What this route gives is a genuine native app. It shows events without a connection, appears in Command-Tab, sends notifications through macOS and merges every account into one view.
What it gives up is everything that belongs to Google's interface rather than to the events themselves. Working hours, appointment schedules, sharing settings and the newer Google features are managed in the browser. Shortcuts are different too. For someone whose only problem was finding the tab, a week of relearning is a real cost.
Route two: a Safari web app
Since macOS Sonoma 14, Safari can save any page as a separate app. Apple's article on Safari web apps describes the steps:
- Open calendar.google.com in Safari and sign in.
- Choose File, then Add to Dock. The Share button has the same command.
- Type a name and click Add.
The app is saved to the Applications folder inside the home folder and can be opened from the Dock or Spotlight. Apple states that it shares no history, cookies or website data with Safari, which means the Google sign-in has to be done once more inside the new window.
Two settings matter for a calendar. First, notifications: Apple notes that the red badge on the Dock icon only works when the notification prompt is answered inside the web app, not in Safari. Accept the prompt when Google Calendar asks from within the new window. Second, the app can be added as a login item, so it is open before the first meeting of the day.
The limits are equally clear. It needs Sonoma or later. It is one website per app, with no tabs, so Calendar, Gmail and Drive become three separate windows. Extensions are limited to Safari's own, which can be turned on or off per web app in its Settings. And if two Google accounts are needed, each one needs its own web app.
Route three: a Chrome web app
Chrome has a similar feature that also runs on older systems. Google's Chrome help page on web apps gives the current menu path:
- Open Google Calendar in Chrome.
- Click More, then Cast, save, and share, then Install page as app.
- Follow the prompt.
The installed app opens in its own window and can be kept in the Dock. Settings live under More, then App info, then Settings, inside the app window.
The trade-off is that the app is still part of Chrome. It uses the same Chrome profile, so it shares that profile's sign-in, cookies and extensions. That is convenient when there is one Google account. It is less convenient when a personal and a work account both need a calendar window, because switching accounts in one window affects the other. It also means closing Chrome can close the calendar, depending on how Chrome is set to run in the background.
Route four: a separate app built by a site to app tool
A site to app tool takes a web address and builds a real .app bundle around it, usually with its own browser profile. The calendar looks exactly as it does in the browser, but the app is independent: its own Dock icon, its own sign-in, and no connection to the main browser window.
This route earns its place in three situations. The first is two Google accounts at once. With a separate profile per app, a work calendar and a personal calendar can both stay signed in without either one logging the other out. The second is Chrome extensions. A Chromium-based tool can load extensions such as a password manager inside the calendar window, which Safari web apps cannot do with Chrome Web Store extensions. The third is bundling. Some tools can open several addresses as tabs in one app, so Calendar, Gmail and Drive live in one window instead of three.
As a concrete example, the free tier of one such tool allows up to three apps with every feature, and the paid tier is a one-time purchase listed on its pricing section. The user guide shows the details that matter for a calendar: notifications are off by default and have to be switched on per app, after which alerts arrive through macOS Notification Center. A Quick Setup option opens several URLs as tabs at launch, and its own example is Gmail plus Google Calendar plus Google Drive in one app.
The cost is one more piece of software to install and the need for a Chromium browser already on the Mac, since these apps run on the installed browser rather than bundling their own.
Route five: a dedicated calendar client
Several companies sell Mac clients that talk to Google Calendar through its API. Prices below were checked on the vendors' own pages on October 18, 2026.
- hora Calendar is built only for Google Calendar. It costs $2.99 a month, $29.99 a year or $59.99 once, after a 7-day free trial, and its site lists macOS 15 or later.
- BusyCal sells for $49.99 with a 14-day free trial, requires macOS 12.0 or later, and is also offered through Setapp.
- Fantastical has a Free tier and paid Premium plans with a 14-day trial. The free tier limits some features, such as the weather forecast range and how far ahead calendar mirroring reaches.
These clients add things Google's web screen does not have, such as menu bar views and typed event entry. They also replace Google's interface, so Google-only features may need the browser now and then, as with Apple Calendar.
The five routes compared
| Route | Cost | Looks like Google's screen | Two Google accounts at once | Minimum macOS |
|---|---|---|---|---|
| Apple Calendar | Free | No | Yes, merged in one grid | Any current |
| Safari web app | Free | Yes | One web app per account | Sonoma 14 |
| Chrome web app | Free | Yes | Awkward, shares a Chrome profile | Whatever Chrome supports |
| Site to app tool | Free tier, then a one-time fee | Yes | Yes, one profile per app | Depends on the tool |
| Calendar client | Subscription or one-time | No | Yes | Depends on the client |
The table hides one point. Apple Calendar and the clients copy events to the Mac. The three web routes keep using Google's screen, so they need a connection, but they never fall behind Google's own features.
Settings to change on whichever route is chosen
A calendar window that does not alert anyone is not much better than a tab. Whatever route is chosen, three checks take two minutes.
Notifications first. In Google Calendar's Settings, open the notification settings and allow notifications on the computer. Then open System Settings, then Notifications, find the app by its name, and allow alerts. Web apps appear in that list under the name given to them, not under the website address.
Open at login. In System Settings, then General, then Login Items, add the calendar app so it is running before the day starts.
Keep it in the Dock. Right-click the running app's Dock icon and choose Options, then Keep in Dock.
Then test it once. Create an event five minutes ahead with a reminder set to one minute before, switch to another app, and wait. If no alert appears, the permission is missing in one of two places: inside Google Calendar's own settings, or in the macOS Notifications list. Checking both now is far cheaper than finding out during a missed call. While the test event is open, also confirm the time zone shown in Google Calendar matches the Mac's own, since Google Calendar keeps its own time zone setting separate from the system one. Delete the test event afterwards, and the setup is ready for real meetings.
What to change first
If the only complaint is a lost tab, give the calendar its own window today with Safari's Add to Dock or Chrome's Install page as app, and turn on notifications inside that window. If two Google accounts or Chrome extensions are part of the day, Kagemusha builds a separate calendar app with its own profile, free for up to three apps.
Frequently asked questions
Is there an official Google Calendar app for macOS?
No. Google offers Calendar on the web, on Android and iOS, and on Wear OS and Apple Watch. On a Mac, Google's answer is the web version at calendar.google.com, which can be given its own window with a browser's web app feature.
Why do shared calendars not show up in Apple Calendar?
Google only syncs the calendars under "My Calendars" and the Birthdays calendar automatically. Shared and team calendars have to be ticked on Google's Calendar sync page and saved. After that, refresh Apple Calendar and they appear.
Can two Google accounts each have their own calendar window?
Yes. Safari needs one web app per account, since each web app keeps its own cookies. A site to app tool that gives every app its own browser profile does the same with Chromium. Chrome's built-in web apps share the Chrome profile, so they are less suited to this.
Do Google Calendar reminders work when the browser is closed?
With a Safari web app or a separate app built by a site to app tool, reminders come from that app, so the main browser can be closed. The app itself has to be running, which is why adding it to Login Items helps. With Apple Calendar, macOS sends alerts from the synced events.
Does a calendar web app work offline?
Mostly not. The web routes load Google's screen, so a connection is needed to see and change events. Apple Calendar and paid clients keep a copy of events on the Mac and can show them without a connection.