What is ZoomUpdater on Mac, and can I disable it?

Last updated: 2026-08-05

What it is

ZoomUpdater is an update helper bundled inside Zoom Workplace. Its bundle identifier is us.zoom.updater, and the executable sits inside the installed Zoom application at /Applications/zoom.us.app/Contents/Library/LaunchAgents/ZoomUpdater.app/Contents/MacOS/ZoomUpdater. It is third-party software installed with Zoom, not an Apple component or a core macOS service.

In the installation that was inspected, launchd starts ZoomUpdater when the user logs in and then starts it periodically. The configured interval was once per hour. KeepAlive was disabled, so launchd was not instructed to keep ZoomUpdater running continuously. Other Zoom releases and administrator-managed installations may use different configurations.

ZoomUpdater checks whether the installed Zoom client is eligible for an update. When an update is available, it can download the installer package and stage it for installation. ZoomAutoUpdater, whose bundle identifier is us.zoom.ZoomAutoUpdater, is another helper bundled with Zoom; it should not be confused with ZoomUpdater.

Why it talks to the network

ZoomUpdater contacts Zoom-controlled version and update services when its login check or scheduled job runs. The response tells it whether the device is eligible for a newer Zoom client under the applicable update policy. That policy may use Zoom’s Slow or Fast channel, a custom channel, or settings managed by an administrator.

A routine run may only need to check update eligibility. If the device qualifies for a newer release, ZoomUpdater can then retrieve an installer package from delivery infrastructure controlled by Zoom. This creates two very different traffic patterns: small, intermittent checks when nothing needs to be installed, and a much larger download when an update is ready.

The exact hostnames used by these services have not been independently verified and may change. A hostname list presented as permanent or exhaustive would therefore be misleading. The confirmed point is narrower: ZoomUpdater communicates with Zoom-controlled version and update infrastructure for client updating.

How much traffic is normal

Normal ZoomUpdater traffic is usually low and intermittent because its job runs at login and on a schedule rather than remaining active as a continuous network service. An update check does not have the same traffic profile as an installer download.

When a new release is available, a much larger burst can be normal. Its size is comparable to downloading the relevant Zoom installer package. There is no independently verified byte range that applies across installations, so a specific MB figure would create false precision. The total varies with the release, the Mac’s architecture, and the organization’s deployment policy.

A sustained stream of heavy traffic would not match the verified pattern of occasional checks and update-package downloads. That observation alone does not identify the cause, however; the useful next step is to measure ZoomUpdater itself over the relevant time window.

Can you turn it off

Temporary throttling or pausing is reasonable, but permanent blocking needs another update plan. macOS exposes the relevant background control at:

System Settings > General > Login Items & Extensions > App Background Activity > Zoom

The row may instead appear as Zoom Video Communications, Inc., and an administrator-managed Mac may present or lock it differently. Zoom also provides an update preference at Zoom Workplace > Settings > General > Zoom Updates > Automatically keep Zoom up to date; administrators may hide or enforce that setting.

Turning off background activity may stop or disrupt ZoomUpdater’s scheduled checks and downloads. The installed Zoom client can continue working at first, so disabling the helper does not immediately disable meetings. The longer-term consequence is different: the client may miss security and compatibility fixes and can eventually fall below Zoom’s enforced minimum version. If that happens, Zoom may require an update before the user can join meetings or use its services.

A manual update routine or an IT-managed deployment can replace background updating. Without either one, permanent blocking trades a small amount of scheduled network activity for an increasingly outdated client.

What people get wrong

• ZoomUpdater is not part of macOS. Its system-like name does not make it an Apple daemon. It is a third-party helper installed inside Zoom Workplace.

• ZoomUpdater is not designed to run continuously. In the inspected launchd configuration, KeepAlive was disabled. The job started at login and on an hourly schedule, then performed update work when invoked. Configurations can differ between releases or managed deployments, but permanent execution was not the verified design.

• ZoomUpdater does not carry normal Zoom meeting audio or video. Its confirmed role is checking for client updates and downloading or staging installer packages. Meeting media traffic should not be attributed to ZoomUpdater merely because Zoom created the process.

• “Zoom installs updates whenever the app is idle” is too broad. Zoom’s documented ordinary automatic-update behavior installs an update when the Zoom client restarts. Installing after a period of inactivity, or automatically restarting an inactive client, is a separate policy that an administrator can configure. Those managed behaviors should not be presented as the universal default.

• Disabling ZoomUpdater does not immediately disable Zoom meetings. The existing client can keep working initially. The risk accumulates later: missed security and compatibility fixes can leave the client below Zoom’s minimum supported version, after which updating may become a condition for joining or using Zoom services.

• Deleting the executable or its launchd property lists is not a reliable optimization. A Zoom installation or repair may recreate those files, while automatic updating remains damaged in the meantime. The Zoom update preference and macOS background-activity control provide the available settings-based controls; a permanently disabled configuration still needs manual or centrally managed updates.

Seeing what it actually used

Before changing the update settings, open Bytetally’s per-process statistics and inspect ZoomUpdater over a window that includes its scheduled checks. This shows whether you are seeing small periodic activity or a larger installer download instead of relying on a generic estimate. If background updating is paused, compare the same process view afterward and make sure another update method remains in place.

Related processes

Common questions