Google Calendar: set Zoom as the default for every new meeting

Adding a guest to a Google Calendar event and watching a Meet link appear on its own is convenient right up to the moment the organisation runs on Zoom. Then it becomes a small tax charged on every invitation: remove the Meet link, open the add-on, generate the Zoom link, check that only one conference is attached. Most articles on this search answer it with three clicks in a personal settings panel. That works for one person on a personal account, and it does not hold for a company, because the control that actually decides the default sits in the Admin console and it is not the setting most people are shown.

Two different controls, easily confused

There are two independent layers here, and knowing which one is in play saves an afternoon.

The first layer is what happens inside a single event. In Google Calendar, Meet is attached through a control labelled "Add Google Meet video conferencing", and a third-party provider appears in the "Add conferencing" dropdown once its add-on is installed from the Google Workspace Marketplace. A reader on a personal Gmail account can install the Zoom add-on and pick it from that dropdown per event, and that is the whole story for them.

The second layer is what gets attached automatically, and that layer belongs to the administrator on a work or school account. Google states the position directly:

If you have a work or school account, your administrator controls the add-ons that you can use or install in Calendar. Source: support.google.com

That single sentence explains why so many people follow a personal-settings guide, see the Zoom option appear, and still watch Meet links get generated automatically the next morning. The per-event dropdown and the automatic default are not the same switch.

There is also a hard limit worth knowing before any of this is configured. Google's documentation for administrators states that only a single conference can be attached to the conferencing field of a Calendar event, and warns that pasting extra conference details into the location field or the description causes confusion when people try to join. A Zoom default does not coexist with a Meet default. One of them has to lose.

The per-user setting, and what it actually covers

For an individual, the automatic behaviour lives under Settings, then Event settings, in the option named Automatically add Google Meet video conferences to events I create. Turning that off is the step most guides mean when they say to disable Meet as the default.

Note what that switch does and does not do. It stops Meet links from being created without being asked. It does not make Zoom take Meet's place. After turning it off, a new event arrives with no conference attached at all, and the Zoom link still has to be chosen from the "Add conferencing" dropdown. For a personal account, that is the honest ceiling: Meet can be switched off by the account holder, and Zoom can be made convenient, but not truly automatic.

Google's documentation describes the fallback behaviour that fills the gap. When Meet is not the default for an organisation, the add-on set as default, or the conferencing solution the person last used to create an event, is added to new events. That last clause is the useful one in practice. Once a Zoom meeting has been created through the add-on, the same choice tends to follow subsequent events, which is why some readers report that Zoom "became" the default without changing a setting, and why others see it silently revert after one Meet meeting is created for an outside guest.

One more behaviour catches people out. According to the administrator documentation, duplicating or copying an event does not carry video conferencing across. A copied event starts with no conference regardless of any default, which matters for anyone who builds a weekly meeting by duplicating last week's.

Making Zoom the organisation-wide default

On a Google Workspace domain the change is two separate jobs in the Admin console, and they live under different products.

Turn off the Meet default

The Meet default is a Calendar setting. In the Admin console the path is Menu, then Apps, then Google Workspace, then Calendar, then Sharing settings, then Video conferencing. Two checkboxes matter there. One is named "Make Google Meet the default video conferencing provider when available" and the other is "Automatically add video conferencing to events users create". Changing them requires the Calendar administrator privilege.

The second checkbox is the one that decides whether anything is attached automatically at all. Google's documentation describes the trigger precisely: with Meet as the default and conferencing switched on for events, Meet links are added when a user adds the first guest to an event. That is why the link appears at the moment a name is typed rather than when the event is saved.

Point the default at the add-on

Making a third-party add-on the default is documented as a Google Meet setting, not a Calendar one, which is where most attempts stall. The path is Menu, then Apps, then Google Workspace, then Google Meet, then Service status, where the option is set to "Off for everyone" and saved. The conferencing add-on is then installed for the organisation. This step requires the Google Meet administrator privilege, which is a different privilege from the Calendar one, so in many companies two people are involved.

Read that step carefully before scheduling it, because turning the Meet service off for everyone is a wider action than setting a preference. It is the documented route to handing the conferencing field to an add-on, and it also removes Meet from the people who occasionally needed it for an external guest. That trade-off is a decision for whoever owns the meeting stack, not a configuration detail.

One operational note from the same documentation: if a super administrator has enabled multi-party approval for general Calendar settings, a change to these individual settings triggers an approval process before it takes effect. A change that appears to have failed may simply be waiting for a second administrator.

Confirming the change actually took

Conferencing defaults fail quietly, so the change is worth proving rather than assuming. Four checks cover nearly every case, and they take about two minutes together.

Start with an event created from scratch, with one guest added, on the account that will actually be sending invitations. The guest matters: Google documents that the automatic link is attached at the moment the first guest is added, so an event with no attendees proves nothing. If a Meet link appears after that first name is typed, the automatic setting is still in force somewhere above the account.

Next, check an event created by a different person on the same domain. Domain settings apply to everyone, and one account carrying a stale browser session can make a working change look broken. If a colleague's new event behaves correctly and yours does not, the problem is local rather than policy.

Third, check the dropdown itself rather than the result. If Zoom does not appear in the "Add conferencing" list at all, the add-on is not installed for that account, and no default setting will conjure it. On a managed domain this is the administrator's install step, not a user action.

Finally, check a copy. Duplicate an existing meeting and look at the conferencing field, which should be empty, because Google documents that copied events carry no conferencing regardless of the default. Seeing that emptiness confirms the documentation is describing the same system in front of you, and it is a useful reminder for the recurring meeting that people build by duplication.

If an administrator change appears to have done nothing, the multi-party approval process noted above is worth ruling out before troubleshooting further. A pending approval looks identical to a failed save.

Which route fits which account

Situation	Can Meet be switched off	Can Zoom be attached automatically	Where the change is made
Personal Gmail account	Yes, in Event settings	No, chosen per event from the dropdown	Calendar settings
Workspace user without admin rights	Only for events they create	No	Calendar settings, within admin policy
Workspace administrator, Calendar privilege	Yes, domain wide	Not by itself	Admin console, Calendar, Sharing settings
Workspace administrator, Meet privilege	Yes, by turning the service off	Yes, once the add-on is installed	Admin console, Google Meet, Service status

The table makes the common dead end visible. A reader with a Workspace account and no admin rights cannot reach the setting that most search results describe, and no amount of clicking in personal settings will change that. The realistic move in that case is a request to whoever holds the Calendar privilege, phrased against the exact checkbox names above, which turns a vague complaint into a two-minute change.

Reducing the cost without changing any policy

Not every reader can change a domain policy, and for many the real goal is narrower than a default: never send an invitation with the wrong conference on it, and never hunt for a join link thirty seconds before a call.

Both of those are client-side problems, and this is where the calendar app on the Mac earns or loses its place. Three behaviours are worth testing in whichever app is used.

The first is whether the app can create a Zoom meeting at the moment the event is created rather than after it is saved. A calendar that generates the link as part of writing the event removes the two-step dance entirely, and how that works is described under Entering events.

The second is whether the app recognises join links it did not create. Meeting invitations arrive from other companies with links buried in the description, in a location field, or in a forwarded email, and an app that detects Zoom, Meet, Teams and Webex links and surfaces a single join button makes the origin of the link irrelevant. The Features page sets out which services are recognised.

The third is quieter and matters more over a week. The reason people are late to calls is usually not the link. It is the previous event, which ran into the one before it, or a meeting in a different building with no travel allowance in front of it. An app that measures the door-to-door trip and inserts the travel block before the event is solving that, and it is described under Travel time.

What to change first

Open Settings, then Event settings, and turn off the automatic Meet option so that nothing is attached without being asked, then create one Zoom meeting through the add-on so that the last-used provider works in your favour. If the account is on a Workspace domain, send the two Admin console paths above to whoever holds those privileges rather than retrying personal settings. On the Mac side, an app that creates the Zoom link while the event is being typed removes the step altogether, which is how Caltimate handles it.