What is GoogleUpdater on Mac, and can you remove it?

What GoogleUpdater does

Google’s Chrome Help describes GoogleUpdater as a service that regularly checks for updates and installs them when available. Its technology is open source, and the Chromium documentation describes an updater that can manage registered applications outside the browser process.

Closing a Chrome window does not therefore mean every related update task should stop immediately. Nor does a background-item notification prove that a new browser tab was opened. The updater has its own schedule and registered-app checks.

Older instructions may mention GoogleSoftwareUpdate or Keystone. Current Chromium documentation discusses migration from that older updater. Match the installed executable and edition rather than deleting every folder with Google in its name.

Identify its path and launch agent

On our read-only macOS 27.0.1 check on 23 October 2026, a user-scoped GoogleUpdater app was installed under ~/Library/Application Support/Google/GoogleUpdater/. A Current entry pointed to a versioned app. No GoogleUpdater process was running in that particular process snapshot.

The user launch agent was ~/Library/LaunchAgents/com.google.GoogleUpdater.wake.plist. Reading its property list showed a GoogleUpdater executable with a wake-all task and a 3,600-second interval. That is an observation on this Mac, not a claim that all versions always run on exactly the same schedule.

Chromium’s design documents distinguish user LaunchAgents from system LaunchDaemons. A system-scoped installation can therefore have different ownership and locations. A folder’s absence in your account does not prove that no updater is installed for the whole Mac.

Use Activity Monitor to inspect a running copy and macOS’s background-item information to identify its publisher and path. A similar process name is insufficient to verify a different executable. Do not grant an unfamiliar item permissions solely because it contains “Google.”

Why it appears in Login Items and background notices

macOS exposes background activity separately from apps that open a window at login. An updater can be permitted to run without being an ordinary visible startup app. System settings and organizational policy may manage that permission.

Review System Settings › General › Login Items & Extensions and the relevant item. The startup items guide explains the difference between a login window and a background helper. If a prompt repeats, record its wording and the actual executable before changing anything.

Turning off an updater while keeping the browser can interrupt automatic security updates. Do not use that as a permanent performance shortcut. A managed Chrome installation belongs with your administrator’s update policy.

If GoogleUpdater is busy or reports an error

1. Check the browser’s update status. Open Chrome’s About page and note the installed version and any update error. Let an intended download complete on a suitable network.
2. Watch sustained activity. A short installation task is different from repeated failed checks. Note whether CPU or network work settles.
3. Use the available updater details. Google’s enterprise help documents chrome://updater for updater information. Availability can depend on the installed version and policy.
4. Restart normally after saving work. Recheck the same error rather than repeatedly killing background copies.
5. Ask the right support owner. For a work or school Mac, provide the update error to IT. For a personal Mac, follow Google’s current update troubleshooting.

Do not manually delete a versioned updater directory during an update. A temporary file, old version and active version have different purposes. This guide did not run an update, wake command or uninstall command to test the service.

Can you remove GoogleUpdater?

If you still use Chrome or another registered app, keep a reliable update mechanism. If you no longer need those apps, uninstall them through their documented route. The Chrome removal guide covers exports, sync, profiles and managed installations.

Chromium’s updater manual says it notices removal of Mac app bundles on its own, potentially after a few hours. When it has no applications left to manage, it uninstalls itself. Other registered software can keep it necessary, so removing Chrome alone is not a universal guarantee that every updater component disappears immediately.

The developer manual also documents explicit wake and uninstall operations. Those are not needed as a generic cleanup command here. We do not give wildcard deletion commands for shared Library folders or advise bypassing administrator policy.

What the update check communicates

Google documents update-related information such as release channel, basic hardware information, installed Chrome version and recent use. Read its linked explanation if that affects your decision. A background network request is not automatically evidence that the updater is uploading browsing history.

Choosing a different browser is a separate product decision. If you remove Chrome, preserve the bookmarks and credentials you need first. Keeping an old browser while blocking its updater trades an update problem for a security-maintenance problem.

Where Tend fits

Tend’s free Startup Items view can identify traditional launch agents and their paths. Use it to understand an item before changing its state; a security updater is not a good candidate to disable just because it runs in the background.

If a user-owned GoogleUpdater runs, Tend can list it under its own updater app bundle. It is not automatically grouped into Chrome because one app updates the other. A root-owned copy is outside Tend’s named current-user process list and can contribute to the macOS share.

Tend’s update checks do not replace GoogleUpdater’s own Chrome update delivery. Keep the vendor’s supported mechanism while its software remains installed.

Questions

Related guides

Sources

• Google, Chrome install and update data and maintain Chrome updates.
• Chromium, Updater design and Updater user manual.
• macOS 27.0.1, read-only updater-directory, launch-agent property-list and process checks; no update or removal operation executed.

Sources checked 23 October 2026. Spotted something out of date? Tell us and we'll fix it.