How to Remove Browser Extensions on Mac (Chrome, Safari, Firefox, Edge) in 2026

If you've been accumulating browser add-ons for years, knowing how to remove browser extensions on Mac properly — not just disabling them — is worth a few minutes of your time. Extensions live in browser profiles, but uninstallers can leave preference files, support caches, and even launch agents scattered across your home folder. This guide covers every major browser in macOS Sequoia and macOS Tahoe, explains where leftover data hides, and shows you how to confirm nothing lingers after the extension is gone.

Why You Should Remove Extensions You No Longer Use

Disabled extensions still occupy profile storage and, in some browsers, run background processes at login. A handful of poorly maintained extensions can add up to tens of megabytes of cache in ~/Library/Application Support/ and slow down browser startup times. Beyond storage, stale extensions that no longer receive security updates are a meaningful attack surface on Apple Silicon and Intel Macs alike.

• Background service workers can keep running even when the extension is toggled off in some Chromium builds.
• Extension-specific caches inside ~/Library/Caches/ are not always cleared when you disable but not remove an extension.
• Some extensions install a native messaging host — a small binary under ~/Library/Application Support/Google/Chrome/NativeMessagingHosts/ — that persists after the extension UI entry is removed unless you also delete the host manifest.

How to Remove Extensions in Google Chrome on Mac

1. Open Chrome and click the puzzle-piece icon in the toolbar (or go to Window > Extensions).
2. Click Manage Extensions to open chrome://extensions.
3. Find the extension you want to remove and click Remove, then confirm.
4. Restart Chrome to ensure the background service worker is terminated.

Leftover Chrome Extension Files to Check

After removing an extension from the UI, inspect these locations for residual data:

• ~/Library/Application Support/Google/Chrome/Default/Extensions/ — the extension's unpacked folder; Chrome should delete it, but verify the subfolder (named after the extension ID) is gone.
• ~/Library/Caches/Google/Chrome/Default/Cache/ — shared cache; older entries from the removed extension age out normally but can linger for days.
• ~/Library/Application Support/Google/Chrome/NativeMessagingHosts/ — delete any .json manifest whose path key points to the removed extension's binary.

How to Remove Extensions in Safari on Mac

1. Open Safari and go to Safari > Settings (or Preferences on older macOS) > Extensions.
2. Select the extension in the left sidebar and click Uninstall.
3. Safari will prompt you to move the companion app to the Trash — do so, then empty the Trash.

Where Safari Extension Data Lives

Safari extensions on macOS are distributed as app extensions bundled inside a full Mac app. Uninstalling means removing that host app. Leftover support files may remain at:

• ~/Library/Safari/Extensions/ — legacy .safariextz bundles (pre-macOS Mojave); delete any file whose name matches the removed extension.
• ~/Library/Containers/ — sandboxed container for the companion app, named after the app's bundle identifier (e.g., com.example.MyExtension); safe to delete once the app is trashed.
• ~/Library/Application Support/com.apple.Safari/Extensions/ — extension state; entries self-clean after the next Safari launch but can be deleted manually.

How to Remove Extensions in Mozilla Firefox on Mac

1. Click the menu button (three horizontal lines) and choose Add-ons and Themes, or press Command+Shift+A.
2. Switch to the Extensions tab, find the extension, click the three-dot menu beside it, and select Remove.
3. Restart Firefox when prompted.

Firefox stores extension files in your profile folder at ~/Library/Application Support/Firefox/Profiles/<profile-id>/extensions/. Each extension is either a .xpi file or an unpacked subfolder named after the extension's ID. After removal, these should vanish automatically, but confirm by listing the directory in Terminal:

ls ~/Library/Application\ Support/Firefox/Profiles/

Then navigate into your profile folder and check the extensions/ subdirectory. If a stale folder remains, it is safe to delete.

How to Remove Extensions in Microsoft Edge on Mac

1. Go to edge://extensions in the address bar.
2. Click Remove under the extension tile and confirm.
3. Restart Edge.

Edge is Chromium-based, so its extension storage mirrors Chrome's layout, with paths rooted under ~/Library/Application Support/Microsoft Edge/ rather than Google/Chrome/. Check the same three locations — Default/Extensions/, Default/Cache/, and NativeMessagingHosts/ — substituting the Edge path.

Browser Extension Storage Locations at a Glance

How to Find and Delete Leftover Extension Data in Terminal

If you want to confirm nothing is left behind after removing a Chrome or Edge extension, you can use the extension's ID (visible in chrome://extensions with Developer Mode on) to target the exact folder:

rm -rf "~/Library/Application Support/Google/Chrome/Default/Extensions/<extension-id>"

For native messaging host manifests, list the directory and look for any .json file referencing a binary path that no longer exists:

ls ~/Library/Application\ Support/Google/Chrome/NativeMessagingHosts/

Open suspicious manifests with cat and check the path value. If the binary is gone, delete the manifest. Leaving orphaned manifests causes Chrome to log errors on startup but is otherwise harmless — still, cleaning them up is good hygiene.

If you have extensions across multiple browsers and want a single view of what's accumulating in ~/Library/Application Support/ and ~/Library/Caches/, a tool like Crumb can audit all of these at once and show what's safe before you delete. For a broader look at how much space browser data is consuming alongside other app data, see our guide on what is taking up space on your Mac.

Extensions vs. Installed Apps: Know the Difference

Some browser extensions ship alongside a companion Mac app — password managers and screen-capture tools are common examples. Removing the extension from the browser's Extensions page does not uninstall the companion app. You must separately drag the app to Trash or use the app's own uninstaller. Conversely, uninstalling the Mac app may leave the browser-side extension entry orphaned, showing an error icon. Remove that entry too.

If you are doing a full cleanup of an app that bundled a browser extension, the process is the same as completely uninstalling apps on Mac — app binary, support files, containers, and any browser-side remnants.

After Removing Extensions: Quick Sanity Checks

• Restart each browser after removal so that background scripts and service workers actually terminate.
• Check Login Items — open System Settings > General > Login Items & Extensions. Some extension companion apps install a login item that persists after uninstall. Remove any entry whose source app is now gone.
• Review Launch Agents — scan ~/Library/LaunchAgents/ for any .plist whose Program path points to a removed extension's binary. If the file it references no longer exists, delete the plist and run launchctl remove <label> to unload it from the current session.
• Clear browser caches — browser caches do not auto-shrink until they hit an internal size cap. To reclaim space immediately, clear cached data from each browser's settings after removing extensions.