How to Completely Uninstall Google Chrome on Mac in 2026 (Remove Keystone Updater and Profile Data)

Dragging Google Chrome to the Trash is not enough. Chrome installs a background service called GoogleSoftwareUpdate (also known as Keystone) that keeps running after the app is gone, re-registers itself at login, and quietly phones home. If you want to completely remove Google Chrome from your Mac, including the updater, your profile data, cached pages, and every leftover file, this guide walks through every step on macOS Sonoma, Sequoia, and the current Tahoe release.

What Chrome Actually Installs on Your Mac

Before you delete anything, it helps to know what you are dealing with. A typical Chrome installation leaves files in at least six separate locations:

• The app itself: /Applications/Google Chrome.app
• Your profile data (history, bookmarks, saved passwords, extensions): ~/Library/Application Support/Google/Chrome/
• Caches (often 500 MB to several gigabytes): ~/Library/Caches/Google/Chrome/
• Preferences and settings: ~/Library/Preferences/com.google.Chrome.plist
• GoogleSoftwareUpdate (Keystone) agent: ~/Library/Google/GoogleSoftwareUpdate/
• Keystone launch agents (the part that survives a reboot): ~/Library/LaunchAgents/com.google.keystone.agent.plist and related plists

The Keystone updater is the stubborn piece. Google designed it to reinstall itself if you delete only its preference files, and it runs at every login through a LaunchAgent. Removing Chrome without addressing Keystone leaves a background process consuming CPU and making outbound network calls indefinitely.

Step 1: Quit Chrome and Stop the Keystone Agent

Make sure Chrome is fully closed. Right-click the Dock icon and choose Quit, or run this in Terminal:

osascript -e 'quit app "Google Chrome"'

Then stop the Keystone agent so it cannot interfere while you clean up:

launchctl remove com.google.keystone.agent 2>/dev/null
launchctl remove com.google.keystone.daemon 2>/dev/null

If either command returns an error saying the service was not found, that is fine. It just means that particular component was not loaded.

Step 2: Delete the Chrome Application

Open Finder, go to Applications, and drag Google Chrome.app to the Trash. Alternatively, from Terminal:

sudo rm -rf /Applications/Google\ Chrome.app

Empty the Trash before continuing so macOS releases any file handles.

Step 3: Remove the Keystone Updater Completely

This is the step most uninstall guides skip. Keystone lives in your home Library folder and registers itself as a LaunchAgent so it starts at login. Remove it in full:

# Remove the Keystone application bundle
rm -rf ~/Library/Google/GoogleSoftwareUpdate

# Remove LaunchAgent plists that restart it at login
rm -f ~/Library/LaunchAgents/com.google.keystone.agent.plist
rm -f ~/Library/LaunchAgents/com.google.keystone.xpcservice.plist

# Remove the Keystone framework if present
rm -rf ~/Library/Caches/com.google.Keystone

Some older Chrome versions also dropped a system-level Keystone in /Library/Google/ (outside your home folder, owned by root). Check with:

ls /Library/Google/

If you see a GoogleSoftwareUpdate folder there, remove it with:

sudo rm -rf /Library/Google/GoogleSoftwareUpdate
sudo rm -f /Library/LaunchDaemons/com.google.keystone.daemon.plist

Step 4: Delete Chrome Profile Data and Caches

Your browsing history, cookies, saved passwords, and downloaded extensions are stored in Application Support. Your cached website assets sit in Caches. If you do not need to keep your Chrome profile (for example, you are switching browsers permanently), delete both:

# Profile data: history, bookmarks, passwords, extensions
rm -rf ~/Library/Application\ Support/Google/Chrome

# Cached pages and resources (often the largest chunk)
rm -rf ~/Library/Caches/Google/Chrome

# Preferences file
rm -f ~/Library/Preferences/com.google.Chrome.plist
rm -f ~/Library/Preferences/com.google.Chrome.helper.plist

If you want to keep your bookmarks before deleting, open Chrome first and export them via the bookmark manager (Bookmarks menu → Bookmark Manager → three-dot menu → Export bookmarks). Saved passwords can be exported from chrome://password-manager/settings.

Step 5: Remove Remaining Google Library Files

A few more files may be scattered around your home Library. These cover crash reports, saved state, and any Chrome-related preferences stored by macOS itself:

# Crash reports
rm -rf ~/Library/Application\ Support/CrashReporter/Google\ Chrome*

# Saved application state (window positions etc.)
rm -rf ~/Library/Saved\ Application\ State/com.google.Chrome.savedState

# Any residual Google folder if now empty
rmdir ~/Library/Google 2>/dev/null

Step 6: Verify Keystone Is Not Still Running

After removing the files, confirm the updater is gone from your process list and login items:

ps aux | grep -i keystone

You should see only the grep line itself. If a Keystone process shows up, kill it with kill -9 <PID> and double-check that the LaunchAgent plist files from Step 3 were successfully removed.

Also open System Settings → General → Login Items and Extensions. Look under Allow in the Background for any Google or Keystone entry. If one persists, click the minus button to remove it.

How to Find Chrome Leftover Files with Crumb

If you would rather not run each Terminal command by hand, Crumb can surface these leftovers visually. Crumb scans your full disk and flags app remnants, including Google Keystone files and Chrome profile data, grouped by their origin app. You can review exactly what will be removed before anything is deleted. Crumb runs entirely on-device and requires no account, so your profile data never leaves your Mac during the scan. This is particularly useful if you manage several machines or uninstall apps frequently and want a reviewable list rather than a set of manual commands.

How Much Space Does Chrome Leave Behind?

The numbers vary widely depending on how long you have used the browser. A light Chrome install might leave 200 to 300 MB after the app is removed. Heavy users with years of cached data, offline content, and dozens of extensions can find 2 to 5 GB scattered across the paths above. The cache folder (~/Library/Caches/Google/Chrome/) is almost always the largest single piece.

Completely Removing Chrome vs. Just Resetting It

If your goal is to fix a broken Chrome rather than remove it entirely, you have two lighter options:

• Reset Chrome settings: Go to chrome://settings/reset and choose Restore settings to their original defaults. This clears extensions, cookies, and startup pages without removing the app.
• Delete only the profile: Close Chrome, remove ~/Library/Application Support/Google/Chrome/Default/ (just the Default subfolder), and relaunch. Chrome recreates a fresh profile while keeping your login.

Neither of these removes Keystone. If the background updater is what you are concerned about, the Terminal steps in Step 3 above are the only reliable fix.

After Uninstalling: Confirm Chrome Is Completely Gone

Run a quick Spotlight or Finder search for "Google Chrome" in your Library folders. If nothing appears except possibly an old crash log, you are done. You can also run:

find ~/Library -iname "*chrome*" -o -iname "*keystone*" 2>/dev/null

Any results that come back are worth reviewing. Most will be harmless log fragments, but anything inside LaunchAgents or Application Support should be deleted.

Completely uninstalling Chrome on a Mac takes more than a Trash drag. The Keystone updater is genuinely persistent, and the profile data can hold gigabytes of cached content that you probably did not know was accumulating. Following the steps above leaves your system clean. If you want to audit what other apps have left behind in the same way, Crumb shows a full map of app leftovers and lets you decide what to remove before anything is touched.