Uninstall Ungoogled Chromium on Mac

Export bookmarks and check which Chromium profile this build uses before removing Ungoogled Chromium. The September 19, 2026 record covers the app copied from the official DMG.

Locate and back up the actual profile

  1. Open chrome://version in this Chromium app and record Profile Path. The parent folder is the user-data directory; a custom --user-data-dir can change it, so do not assume the default path below (Chromium user-data documentation).
  2. Open chrome://bookmarks, open its three-dot menu and choose Export bookmarks. Save the HTML file outside the recorded user-data directory and confirm it exists (bookmark export). Repeat for other profiles you need.
  3. Quit with Command + Q and check that its background processes have stopped. In Finder, use Shift + Command + G to open the recorded user-data location, then copy the whole folder outside that location. Before removing the original, open other installed Chromium builds and compare their Profile Path; keep any directory they share.

Quit and remove the app

Quit its windows and background processes, then move the app to Trash. Another Chromium build may use the same bundle ID and profile location, so identify the actual app and profile before changing either. The official page has more product information.

Review the app’s data

The cask names ~/Library/Application Support/Chromium, ~/Library/Caches/Chromium and ~/Library/Preferences/org.chromium.Chromium.plist. The first contains browser data; cache and preferences are separate. The cask also lists ~/Library/Saved Application State/org.chromium.Chromium.savedState. After confirming no other Chromium build uses these entries, inspect them in Finder with Shift + Command + G and move unwanted app data to the Trash, keeping any profile you chose to retain.

If you installed it with Homebrew

The Homebrew cask has its own --zap list. brew uninstall --cask ungoogled-chromium removes the cask without that list; brew uninstall --cask --zap ungoogled-chromium also acts on its listed data without consulting Mole’s checkboxes. Zap includes the profile root and can erase data used by another Chromium build. Mole skips Homebrew zap for browser casks and uses its own selected-remnant path.

brew uninstall --cask ungoogled-chromium

Check the result

These commands inspect the running process and one relevant location. They do not remove anything:

pgrep -il "Chromium"
ls -ld "$HOME/Library/Application Support/Chromium"

No pgrep match means no process with that name is running; a match needs identification before quitting anything. A listed path still exists, while an ls “No such file” error means only that exact path is absent. A permission error is inconclusive.

What Mole lists

Mole leaves the Chromium profile unselected and selects its cache and exact preference rows by default. The shared org.chromium.Chromium identity does not distinguish this distribution from another Chromium build.

What this test covered

The test used the app copied from the official DMG. On September 19, 2026, the 12 MB Chromium profile stayed under the browser-data policy while cache and preferences were selected. This does not test a second Chromium installation or profile sharing.