Disable Chrome Auto Updates on Mac: Step-by-Step

Chrome’s automatic updates keep your browser secure, but they can also interrupt your workflow, change extensions, or cause compatibility issues with enterprise tools. This guide shows you how to turn off auto-updates on macOS, using either the built-in preferences or a terminal command for more control. You’ll need admin access to your Mac and, if you want to revert later, the ability to re-enable updates.

What You’ll Need

An administrator account on your Mac
Access to the Terminal app (in /Applications/Utilities/)
Chrome closed before making changes

Step-by-Step

Back up your Chrome profile (optional but recommended). Go to ~/Library/Application Support/Google/Chrome and copy the entire folder to an external drive or cloud storage. This protects your bookmarks, passwords, and extensions if something goes wrong.
Quit Chrome completely. Press Cmd+Q or choose Quit Google Chrome from the Chrome menu. Make sure no Chrome processes remain (check Activity Monitor if needed).
Open Terminal. Go to Applications > Utilities > Terminal, or search for it with Spotlight (Cmd+Space).
Disable updates via the defaults command. Type the following command and press Enter:
defaults write com.google.Keystone.Agent checkInterval 0
This sets the update check interval to zero, effectively turning off automatic checks. To fully stop the updater, also run:
sudo chmod 000 /Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Contents/Resources/GoogleSoftwareUpdateAgent.app/Contents/MacOS/GoogleSoftwareUpdateAgent
Enter your admin password when prompted.
Verify the change. Run defaults read com.google.Keystone.Agent checkInterval to confirm it outputs 0. If you see an error, the key may not exist; that’s fine—the chmod step is the main blocker.
Restart Chrome. Open Chrome and check chrome://settings/help. It should show “Chrome is up to date” but won’t auto-download new versions. Note that the “Relaunch” button may still appear if an update was already downloaded—just ignore it.

Common Mistakes

Not quitting Chrome before changing permissions. If Chrome is running, it may re-create or re-permission the updater files, undoing your changes.
Using the wrong path. The GoogleSoftwareUpdateAgent path can vary slightly between Chrome versions. Double-check the path in Finder before running the chmod command.
Only setting checkInterval. Some users find that Chrome still updates because the Keystone agent runs independently. The chmod step is essential to fully block it.
Forgetting that updates are also triggered by Chrome’s own updater. Even with Keystone disabled, Chrome may check for updates when it launches. The chmod blocks the actual update process, so this is fine.

Tips

Use a managed policy (for work Macs). If your Mac is managed by an organization, you can set the AutoUpdateEnabled policy to false via a configuration profile. This is more reliable than manual tweaks and survives Chrome updates.
Re-enable updates easily. To undo the chmod, run sudo chmod 755 /Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Contents/Resources/GoogleSoftwareUpdateAgent.app/Contents/MacOS/GoogleSoftwareUpdateAgent and delete the defaults key with defaults delete com.google.Keystone.Agent checkInterval.
Consider a manual update schedule. Instead of fully disabling updates, you can set the check interval to a large number (e.g., 86400 for daily) to reduce interruptions while still getting security patches.

Troubleshooting

Chrome still updates after following steps. This can happen if your Mac has a managed profile or if Chrome was running during the chmod. Re-check that Chrome is closed, then re-run the chmod command. Also verify the file path exists—if not, use find /Library/Google -name "GoogleSoftwareUpdateAgent" to locate it.
You get “Operation not permitted” when running chmod. This is often due to macOS System Integrity Protection (SIP) or Full Disk Access restrictions. Go to System Settings > Privacy & Security > Full Disk Access and add Terminal, then retry. If SIP is enabled, you may need to disable it temporarily (not recommended for security).
The defaults command returns an error. The key might not exist. That’s okay—the chmod is the main blocker. You can also try defaults write com.google.Keystone.Agent checkInterval -int 0 to force an integer.
After disabling, Chrome shows a “Failed to update” error. This is expected. It means updates are blocked. You can ignore it or set the checkInterval back to a positive number to stop the error while still blocking actual updates.

Frequently Asked Questions

Will disabling updates make my browser unsafe?

Yes, you’ll miss security patches and bug fixes. Only disable updates if you have a strong reason (e.g., testing or enterprise compatibility) and consider manually updating periodically.

Can I still update Chrome manually after disabling?

Yes. You can re-enable updates by reversing the steps, or download the latest installer from Google’s site and run it—it will replace the current version without needing the updater.

Does this affect other Google apps like Drive or Earth?

The chmod command only targets Chrome’s updater. Other Google apps that use Keystone may still update. To disable all Google software updates, you’d need to repeat the process for each app’s updater.

Will this break Chrome extensions?

No, extensions are stored separately and are not affected by disabling updates. However, some extensions may require a newer Chrome version to work, so you might run into compatibility issues over time.

How do I know if my Mac is managed by an organization?

Check System Settings > General > Device Management. If there’s a profile listed, your Mac is managed. In that case, the organization’s policies may override your manual settings.

Is there a way to disable updates without using Terminal?

You can use a third-party app like “Chrome Update Blocker” (not officially supported) or create a launchd plist to prevent the updater from running. However, the Terminal method is the most direct and reliable.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →