Calendar on Mac not syncing with iPhone: where to look first

An event exists on the Mac and not on the iPhone, or the other way round, and both devices insist they are signed in to the same account. Most of the advice available for this starts with restarting something, which occasionally works and teaches nothing about why the calendar broke.

The useful move is to stop treating this as one fault. "Calendar on Mac not syncing with iPhone" covers at least four different problems that produce the same symptom, and each one has a different fix. Sorting out which one is happening takes about three minutes and saves the afternoon that a blind sequence of restarts and account removals will otherwise consume.

The four things that look identical from the outside

An event that is missing on one device is caused by one of the following, in rough order of how often it turns out to be the answer.

The calendar the event was created in does not sync at all. Calendar on the Mac can hold local calendars, grouped under a heading named On My Mac, and those exist only on that Mac. Nothing is broken when their events fail to appear on the phone. They were never sent anywhere.

The two devices are not looking at the same account. Two Apple Accounts, or the same Apple Account with the Calendar service switched off on one device, produce a silence that looks exactly like a sync failure.

The event did sync but is filtered out of view. The calendar exists on both devices and is simply unticked in the sidebar or the calendar list on one of them. On the iPhone this is one tap away in the Calendars list at the bottom of the screen.

The transfer is genuinely delayed or stuck. This is the real sync failure, and it is the least common of the four. It behaves differently depending on whether the account is iCloud, Google, or Exchange, which is why the fix has to come after identifying the account type rather than before.

Read the server copy before touching either device

Neither the Mac nor the iPhone is a reliable witness about what is actually stored. The third copy is, and it is reachable in a browser.

For an iCloud account, open iCloud.com and look at Calendar there. For a Google account, open the calendar in a browser while signed in to that specific account. What shows up in the browser is what the server holds, and comparing that against both devices turns a vague complaint into a specific direction of failure.

Event is on	Event is missing from	What it means
Mac only	server and iPhone	The event is in a local calendar, or the Mac has not uploaded yet
Server and Mac	iPhone	The calendar is switched off or unticked on the iPhone
Server and iPhone	Mac	The calendar is unticked in the Mac sidebar, or that account is not enabled in Calendar settings
iPhone only	server and Mac	The event was saved to a local or subscribed calendar on the phone
Nowhere	everywhere	The event was deleted, by someone with access or by a failed edit

The two rows worth dwelling on are the first and the last. An event that lives on the Mac alone was almost certainly created in the wrong calendar rather than lost in transit, and repeatedly signing out of accounts will never fix that. An event that has vanished from all three places was deleted, and no amount of resyncing will bring it back from a device.

The account checks, in the order that pays

Once the direction is known, the account settings are where the answer usually sits.

Confirm the same Apple Account on both devices, using the address shown at the top of Settings on the iPhone and at the top of Apple Account in System Settings on the Mac. An address that differs by an alias still counts as the same account, but a second personal account created years ago does not.

Confirm that Calendar is switched on for iCloud separately on each device. This is a per-device toggle, not an account-wide one, and it is the single most common cause of a one-sided calendar. It sits under Apple Account, iCloud, then the full list of apps using iCloud.

Confirm the date and time are set automatically on both. A clock that is wrong by hours will put events in places nobody is looking, and a clock wrong by more than that can break the secure connection the sync relies on.

Check whether iCloud storage is full. When the account has no room, new data stops being accepted, and the failure is silent in Calendar rather than announced. Apple also publishes a live service status list, so a genuine outage can be ruled out in seconds on the Apple system status page rather than guessed at.

None of these four checks involve deleting an account, and all of them are reversible. That is the reason to do them before anything drastic.

Local calendars and the default calendar setting

The On My Mac group deserves its own treatment, because it creates a problem that keeps regenerating after every fix.

Calendar on the Mac lets a new event be saved into a local calendar, and it will do so silently whenever a local calendar is the default. Every event created without thinking about which calendar it belongs to then lands somewhere the iPhone cannot see. The account list in Calendar settings shows whether any local calendars exist, and moving their events is a matter of dragging each event onto an iCloud calendar, or selecting the events and changing the calendar in the inspector.

The setting that stops it recurring is the default calendar. On the Mac it is in Calendar settings under General, and on the iPhone it is in the Calendar settings for the system. Pointing both at the same iCloud calendar means an event created in a hurry, from a keyboard shortcut or by talking to a Mac calendar app, goes somewhere both devices can see it. Getting event entry down to one line of text is only an advantage when the line ends up in a calendar that syncs, which is why the entry method and the default calendar are worth setting in the same sitting. A guide to Entering events is only useful after that default is correct.

Google and Exchange accounts behave differently

If the calendar in question came from Google or from a work Exchange server, the iCloud advice does not apply and the timings are different.

Google calendars reach Apple's Calendar through a standard protocol that polls for changes rather than being pushed instantly. On the Mac, the polling interval is set per account in Calendar settings, and it can be set to refresh every minute if a delay of fifteen minutes is the actual complaint. On the iPhone, the same behaviour is governed by the fetch settings for that account.

Secondary and shared Google calendars carry a further trap. A calendar that appears in a browser under a heading for other calendars does not automatically arrive on an iPhone. Google keeps a separate per-device selection page that controls which of those calendars are sent to mobile devices, and until a calendar is ticked and saved there, the iPhone will not show it no matter how many times the account is removed and added.

Exchange and Microsoft 365 accounts add an administrator to the picture. Whether outside applications may connect at all is a domain policy, not a device setting, so a work calendar that works in a browser and fails on both Apple devices is usually a policy question rather than a repair job.

Duplicates and shifted times point somewhere else

Two symptoms get filed under sync failure and belong to a different cause entirely.

Events that appear twice are almost always arriving from two sources at once. The usual pair is an account connection plus an older subscription link to the same calendar, or the same Google account added twice under both an alias and the primary address. A third variant appears in work settings, where a calendar is both shared directly and subscribed to by URL. The accounts list on each device names every source, and removing the redundant one is safe because the events are stored on the server rather than in the connection.

Events that appear at the wrong hour are a time zone question. Calendar on the Mac can be set to show times in a fixed time zone rather than the current one, and an event created while that option is on carries the zone it was given. After travel, or after a work account has been set to a head office time zone, the same event can legitimately read 10:00 on one device and 18:00 on another. The fix is to make the time zone support setting consistent, then check the event itself, which stores its own zone.

Neither of these is repaired by resyncing. Removing accounts and forcing refreshes on a duplicate will produce two copies again as soon as the second source reconnects, which is why the source list is the place to look before anything is deleted.

Forcing a resync without losing anything

When the checks are clean and the delay is real, there is an order to the heavier steps that puts the reversible ones first.

Quit Calendar on both devices and reopen it. On the iPhone, opening the Calendar app and pulling down in the list view triggers a refresh. On the Mac, the same effect comes from the refresh command in the View menu, or from setting the account interval to one minute temporarily.

Toggle Calendar off and then on again for the account on the device that is behind. When switching iCloud Calendar off, the Mac offers to keep or delete the local copy, and keeping it is the safe answer. Only after the toggle has been switched back on and the events have reappeared is it worth deleting the leftover local copy, and only once it is clear those events also exist on the server.

Restart the device that is behind, not both. Restarting the device that already holds the correct data achieves nothing and makes it harder to tell what changed.

Remove and re-add the account last, and only for non-iCloud accounts. Events for a Google or Exchange account are stored on their server, so removing the account on a device removes a copy. Signing out of iCloud entirely is a much larger action and is not a troubleshooting step for a single missing event.

Anyone who reaches the end of that list with a calendar still misbehaving is looking at an account-level problem rather than a device one, and Apple's own support material is the right next stop before any more settings get changed.

What to change first

Start with the server copy in a browser, because it decides which device is wrong and saves every wasted step after that. Then check the Calendar toggle for the account on the device that is behind, and set both default calendars to the same syncing calendar so new events stop landing in a local one. If the day-to-day annoyance is that events keep being created in the wrong place rather than that sync is broken, that is a question of how events get entered, and Caltimate is one of the Mac calendar applications worth comparing on exactly that point.