Combining multiple calendars: what it does and where it breaks down

Most people who search for "multiple calendars" already have them. A work Google account, a personal Gmail, an iCloud calendar shared with family, maybe a team calendar someone added months ago. The question is no longer how to create another one. It is how to see them together without missing a clash, and how to stop the wrong person from booking over a dentist appointment that lives in the wrong account.

The short answer: keep the calendars separate where they are stored, and combine them only where they are read. A combined view on one screen solves the "cannot see everything at once" problem. A conflict check across accounts solves the problem of someone booking over taken time. These are two different jobs, done by two different kinds of tools, and most frustration comes from expecting one to do the other.

This guide walks through how Google Calendar, the Calendar app on the Mac, and booking tools each handle multiple calendars, the specific limits each one publishes, and the points where a combined setup quietly stops working. Limits and prices below were checked on the vendors' own pages on 18 October 2026.

Why people end up with multiple calendars

There are two different reasons, and they lead to different setups.

Several calendars inside one account. This is deliberate. Google's help page on creating a new calendar gives the example of a "Football" calendar for practices and games. The point is to colour, hide, and share one area of life on its own. The same account holds all of them, so one login sees everything.

Several accounts. This is usually not deliberate. An employer issues a Google Workspace or Microsoft account. A personal Gmail predates it. An iPhone created an iCloud calendar on day one. Each account has its own login, its own sharing rules, and its own idea of when someone is free.

The first case is easy. Every major calendar service lets one account hold many calendars, show or hide each one, and give each its own colour. The second case is where combining starts to matter, because no single service owns all the data.

What people usually want from combining

Looking at the help pages from Microsoft, Google, Calendly and others that rank for this query, the requests fall into three groups:

• See everything on one grid, so overlaps are obvious.
• Make busy time in one account block time in another, so colleagues and booking pages do not double book.
• Add a single event to more than one calendar at once, for example a public version on a team calendar and a private one on a personal calendar.

Each of these needs a different mechanism, covered below.

Several calendars inside one Google account

Google Calendar is the most common starting point, so its rules are worth knowing exactly.

Creating and organising

New calendars can only be created from a browser. Google's help page states this directly: after creation, the calendar appears in the browser and in the mobile app, but the mobile app cannot create it. The steps are short: next to "Other calendars", click Add other calendars, then Create new calendar, then give it a name.

The person who creates a calendar becomes its owner. Only the owner can permanently delete it or transfer ownership. That matters later, when someone leaves a team and the team calendar turns out to belong to their account.

Hiding is a per-calendar option ("Hide from list"), and colours are set per calendar. These two controls are the whole of what "managing multiple calendars" means in Google for most people.

Published limits

Google publishes a few numbers that set the outer edge:

Situation	Published limit	Source
Subscribing to other people's calendars	Performance issues above 400 subscribed calendars	Google Calendar Help
Creating calendars quickly	Do not create more than 60 calendars in a short period	Google Workspace Help
Sharing calendars quickly	Do not share with many users in a short period (750 shares)	Google Workspace Help
Subscribing to non-Google calendars by request	Not possible; only public calendars can be added by URL	Google Calendar Help

Few individuals reach these numbers. The last row matters more than the others: a request to subscribe only works for calendars hosted by Google. An iCloud or Outlook calendar can only come in through a published address, which makes it a read-only copy refreshed on Google's schedule, not a live connection.

How sharing level decides what a combined view shows

Before combining anything, check what each calendar is actually allowed to show. Google's sharing settings have five levels:

Permission	What the other person gets
See only free/busy (hide details)	Only when the owner is busy, no names or details
See event details	Names, times, places and descriptions
Make changes (see private events as free/busy)	Can edit non-private events
Make changes and see event details	Can edit and see who else has access
Make changes and manage sharing	Full control, including re-sharing

This table explains a common complaint: "My combined calendar shows blank blocks." If a calendar was shared at the free/busy level, any app that reads it receives only the busy times. The details were never sent, so no app can show them.

It also explains the opposite problem. Sharing a personal calendar with a colleague at "See event details" so that they can avoid clashes also hands them the names of every appointment. For conflict avoidance, free/busy is enough.

Work accounts add another layer

Google's page also notes that for work or school calendars, the administrator decides whether sharing is allowed at all. If sharing a work calendar outward is blocked, the only way to see it next to personal calendars is to sign in to both accounts in the same app. No amount of sharing settings will help.

Combining several accounts on a Mac

The Calendar app built into macOS can hold several accounts at once. Apple's guide to adding calendar accounts lists iCloud, Google, and any other CalDAV account. The path is Calendar > Add Account, then pick the provider and sign in. Each account appears separately in the sidebar.

This is a view-level merge. Events stay in the account that owns them. Removing an account from the app deletes nothing at the source. Deleting an event inside the app, however, is a real deletion on the server, and if the event is a meeting, attendees may hear about it.

Where the Mac Calendar app draws lines

Apple's own guide documents two limits that are easy to miss:

• Calendar groups only work in the On My Mac section. A group that bundles, say, a Google calendar and an iCloud calendar together cannot be made with the built-in feature. Groups are for local calendars.
• Extra calendars in an Exchange account are second class. Apple states that in calendars added to an Exchange account other than the main one, updated invitations and attendee responses are not visible, events are not seen by delegates, and they do not appear when others check availability. Full features are only available in the main Exchange calendar.

The second point is a real trap for anyone at a Microsoft-based employer. Creating a separate "Projects" calendar inside the work account looks tidy, but colleagues checking availability will not see those events as busy.

Third-party Mac calendars

Third-party calendar apps for Mac usually work the same way: sign in to each account, read events through the provider's interface, and draw them on one grid. The differences are in what they add on top. Some let the user save named sets of calendars (Work, Personal, Family) and switch between them in one step, which solves the problem that Apple's groups are limited to local calendars. Some can write the same event into two calendars at once. The features and comparison pages show what one desktop calendar covers, and the same questions apply to any app being considered.

Booking pages and conflict checks across calendars

Seeing calendars together does not stop other people from booking over busy time. That is a separate job: a booking tool reads several calendars and only offers slots that are free in all of them.

Calendly is a widely used example, and its pricing page is specific about the limit. As checked on 18 October 2026:

Plan	Connected calendars	Price shown
Free	1	Free
Standard	6	$10 per seat per month, billed yearly
Teams	6	$16 per seat per month, billed yearly

The Free plan checks one calendar for conflicts. Anyone whose real commitments are spread over a work account and a personal account needs the paid plan for the booking page to see both.

The underlying mechanism is the free/busy level described earlier. A booking tool only needs to know when time is taken, not what the event is. That is why connecting a private calendar to a booking tool does not expose the event names to the person booking. They see only that the slot is gone.

Copying events instead of reading them

Some tools go further and copy events between accounts, either as full copies or as placeholder "busy" blocks. This makes the busy time visible to anyone who looks at the destination calendar, including colleagues who use only the work account. The cost is that copies have to be kept in step. When the original moves, the copy has to move too, and when the original is deleted, the copy has to go. If the copying tool stops running, the destination calendar is left with stale blocks that look real.

Where a combined setup breaks down

Most problems reported in forums and help threads come from a short list of causes.

Different refresh speeds. A calendar connected by signing in updates through that provider's own sync. A calendar added by URL is fetched on a timer chosen by the app that subscribes. Two calendars side by side can be hours apart in freshness with no visible sign.

The default calendar for new events. With several calendars on screen, a new event goes to whichever calendar is set as the default. A personal appointment created in a hurry lands in the work account, and colleagues can see it. Check this setting first after adding a new account.

Sharing level, not the app. Blank blocks in a combined view are almost always a free/busy sharing level, as covered above.

Ownership. A team calendar created inside one person's account belongs to that person. When their account is removed, the calendar goes with it.

Exchange secondary calendars. As Apple documents, extra calendars inside an Exchange account do not show as busy to people checking availability.

Too many layers. A setup that combines a Mac app view, a copying service and a booking tool can produce three versions of the same event. When something looks duplicated, remove one layer at a time to find which one wrote it.

A quick diagnostic order

1. Confirm which account owns the event that looks wrong.
2. Check that account's sharing level for the calendar in question.
3. Check how the calendar is connected: signed in, or subscribed by URL.
4. Check the default calendar for new events in every app that writes.
5. Only then consider changing tools.

What to change first

Start by setting the default calendar for new events in every app, and by sharing personal calendars at the free/busy level only. If a combined view on the Mac is the goal, a desktop calendar that signs in to each Google account and saves named calendar sets, such as Caltimate, covers that without copying anything between accounts.