A calendar that lives next to the clock

The want is specific and reasonable: glance up, see what is next, carry on. Not a window, not a tab, not a switch to another app. A small thing next to the clock that answers one question in half a second.

Several apps do exactly this, and most of them are cheap or free. The part that trips people up is not choosing between them. It is that a menu bar calendar and a Google account do not talk to each other directly, and installing the app before understanding that produces an empty calendar and a wasted evening.

Where a menu bar calendar gets its events

Almost every menu bar calendar on the Mac reads from the system calendar database rather than connecting to Google itself. Itsycal states this openly in its own feature list, under integration with the Mac Calendar app. The apps are small precisely because they do not implement account handling, sync, or credentials. They display what macOS already knows.

The consequence is a single prerequisite. A Google account has to be added to the Mac's Calendar app first, and only then will its events appear in the menu bar. Skipping that step is why the app shows an empty month after installation, which reads as a broken app and is a missing account.

A few apps take a different approach and open Google Calendar in a browser when a date is clicked, keeping the menu bar purely as a viewer. Menu Bar Calendar works this way, offering either the Calendar app or Google Calendar as the destination for a click. That is a reasonable design for anyone who wants the glance without moving anything off the web.

The distinction is worth holding on to when comparing options. An app that reads the system database can show event titles, times, and locations in the bar. An app that only links out can show a month grid and nothing else, because it has no access to the events.

There is a third arrangement, used by the full calendar applications. Fantastical and BusyCal handle the Google account themselves rather than borrowing from the system, which means their menu bar view works whether or not the account was ever added to Apple's Calendar app. That independence is the main practical reason to choose one of them for this purpose, and it comes attached to a much larger application than the want usually justifies.

Set up the source before installing anything

Two steps, done once, and every menu bar app afterwards works on the first launch.

First, add the Google account to Calendar on the Mac. Apple documents the route through the app itself rather than through System Settings, choosing Calendar, then Add Account, then the provider, then following the sign in prompts. The account then appears as its own section in the sidebar with its calendars beneath it.

Second, decide which calendars travel. This is the step that is skipped almost every time, and the reason a shared team calendar never appears in the bar.

Which calendars are automatically synced: Any calendars that you find under "My Calendars" in Google Calendar on your computer. Birthdays. Source: support.google.com

Anything under Other Calendars, which is where shared, subscribed, and holiday calendars collect, has to be ticked on Google's Calendar sync page and then refreshed. Until that is done the calendar is not late or hidden, it is simply not being requested.

While in Calendar settings, set the account to push rather than a timed fetch, under Calendar, Settings, Accounts. A menu bar calendar updating on a one hour delay defeats the purpose of having it there at all.

The options and what each puts in the bar

All figures below were checked on 2026-09-21 and are worth confirming before buying, since prices and requirements move.

App	Price	macOS minimum	In the bar	Reads events
Itsycal	Free, donations optional	macOS 11	Date, optional clock replacement	Yes, via Calendar app
Menu Bar Calendar	Free	macOS 26.0	Month grid on click	No, links out
Dato	18.00 USD once	macOS 26.0	Clock, world clocks, events	Yes, via Calendar app
Fantastical	Free tier, paid subscription	macOS 12.4	Full calendar window	Yes, own account handling
BusyCal	49.99 USD once, direct	macOS 12.0	Menu bar panel	Yes, own account handling

Itsycal is the narrowest and the most widely recommended, and it is distributed directly rather than through the App Store. It shows a month, lists events from the Calendar app, creates events, joins virtual meetings, and can replace the system clock. Its macOS 11 requirement makes it the only option here that runs on an older Mac.

Menu Bar Calendar is deliberately minimal and free, from a developer who also publishes Dato for anyone who outgrows it. Dato is a one time purchase at 18.00 USD on the App Store with updates included for the life of the app, and adds world clocks and fullscreen meeting notifications. Both require macOS 26.0, which rules out machines that have not been updated.

Fantastical and BusyCal are full calendar applications that also offer menu bar access, so they are a different proposition: the menu bar is a feature rather than the product. BusyCal is sold once at 49.99 USD directly from the developer with a fourteen day trial, and Fantastical is a subscription with a free tier. Either is overkill if the only requirement is a glance, and either is the right answer if the menu bar want came alongside dissatisfaction with the calendar itself. The wider differences are set out in Compared with other calendars.

What the menu bar cannot fix

A menu bar calendar answers one question well and is not a substitute for a calendar. Three things reliably disappoint people who expected more from it.

Entry is the first. Most of these apps can create an event, and the creation form is small by necessity, so anything with guests, a location, a video link, or a repeat rule sends the user back to a full window. The menu bar improves reading, not writing, and if writing is the slow part then this is the wrong tool for it. That distinction is worth being honest about before installing four of them looking for the one that fixes it.

Notifications are the second. A menu bar calendar generally does not replace system alerts, and the alerts continue to come from the Calendar app or from whichever client owns the account. If reminders are not arriving now, adding a menu bar app will not change that, because the alert settings, notification permissions, and any active Focus are what control it.

Conflicts are the third. A month grid with dots and a list of the next few events gives no view of whether the afternoon actually fits, and the overlap that matters is usually between a meeting and the travel or preparation around it rather than between two meetings. Putting that time into the day as real events is what makes the glance meaningful, which is covered in Travel time.

Five checks worth running in the first hour

Menu bar apps are cheap enough that people install three and keep none, usually because the thing that made each one unsuitable only showed up on day four. These five checks surface most of it immediately.

Check how much width it takes. Menu bar space is finite, and on a MacBook with a notch it is more finite than it looks, because items that do not fit to the left of the notch are hidden with no warning. An app showing a full date and a clock can be the item that pushes something else out of view. Most of these apps allow the bar format to be shortened, and it is worth setting that before deciding the app is too greedy.

Check whether several accounts are distinguishable. A personal account and a work account rendered in identical text is worse than useless during a glance, since the whole point is deciding without thinking. Calendar colours usually carry through from the Calendar app, but not always into the compact bar view.

Check how all day events are handled. Holidays, deadlines, and out of office markers are all day events, and an app that lists them alongside timed events at the top of the day can bury the actual next meeting under three banners.

Check what happens at a month boundary. On the twenty ninth, the useful view is the next seven days rather than the remainder of the month, and apps that show a strict month grid become least useful exactly when the week ahead matters most.

Check that it still runs after a system update. Two of the options here require macOS 26.0, which is a signal that the developer moves with the system, and it also means an unupdated Mac cannot run them at all. An app that has not been updated across two macOS releases will usually have visible problems with appearance or notifications regardless of how well it worked before.

Menu bar, Dock, or widget

The same underlying want gets expressed three different ways, and the three have different answers.

A Dock icon is what people usually ask for when they want the calendar to be one click away rather than always visible. Any calendar app provides that, and so does a web app saved from Safari, which puts Google Calendar's own interface in the Dock with its own icon and its own notification permission. That route costs nothing and keeps the familiar interface.

A widget is the option most often forgotten. Notification Centre and the desktop both hold calendar widgets in several sizes, showing the next event or the month, and they come from the system with no installation. For anyone who checks the schedule a few times a day rather than constantly, a widget does the job without adding another icon to a crowded bar.

The menu bar earns its place when the glance needs to happen without any deliberate action at all, many times an hour. That is a real pattern, and it is worth being clear that it is the pattern being solved for, because menu bar space is finite and every app there competes with the rest.

What to change first

Add the Google account to the Mac's Calendar app and tick the calendars that matter on Google's sync page, before installing anything. That step alone makes events visible to every option on this page, and it is the difference between an app that works on first launch and one that looks broken. Then start with Itsycal, since it is free and runs on older systems, and only move to a paid option if something specific is missing. If the real frustration turned out to be how long it takes to put an event in rather than how quickly it can be read, that is a different problem, and Caltimate is built around it.