How to uninstall Rambox on Mac
Rambox's local profile holds sessions and cookies for the services you use. Save needed files and access details before removing it. The official uninstall instructions make profile deletion optional and distinguish it from configuration kept on Rambox's servers. This guide covers the official Mac app and Homebrew cask rambox.
Quit the app before removing it
Quit Rambox from its Dock menu or with Command + Q. After it closes, copy ~/Library/Application Support/Rambox to a backup outside that folder if it exists. The recorded Mac used the lowercase spelling rambox; inspect the actual folder on your disk rather than treating the two spellings as two independent backups.
Move Rambox.app to Trash. For a full local reset, the vendor's Mac instructions then call for restarting before optional profile removal. Keep the profile if you plan to reinstall or have not checked your backup.
Separate the profile from old preferences
| Location | Keep or remove |
|---|---|
| ~/Library/Application Support/Rambox | Sessions, cookies and local service data. Delete only after backup and an explicit decision to reset. |
| ~/Library/Logs/Rambox | App logs named by the cask. Inspect after quitting. |
| ~/Library/Caches/com.grupovrs.ramboxce | An older cask cache location, not proof that the current version created it. |
| ~/Library/WebKit/com.saenzramiro.rambox | An older WebKit location in the cask. Treat website data as personal data. |
The current cask also names these older paths. After quitting and checking your backup, open each parent folder with Shift + Command + G in Finder. A * is a filename pattern, not a folder to paste; match actual filenames and move only confirmed Rambox items you no longer need to the Trash.
~/Library/Application Support/CrashReporter/Rambox Helper_*.plist~/Library/Application Support/CrashReporter/Rambox_*.plist~/Library/Caches/com.grupovrs.ramboxce.ShipIt~/Library/Caches/com.saenzramiro.rambox~/Library/Preferences/ByHost/com.grupovrs.ramboxce.ShipIt.*.plist~/Library/Preferences/com.grupovrs.ramboxce.helper.plist~/Library/Preferences/com.grupovrs.ramboxce.plist~/Library/Preferences/com.saenzramiro.rambox.helper.plist~/Library/Preferences/com.saenzramiro.rambox.plist~/Library/Saved Application State/com.grupovrs.ramboxce.savedState~/Library/Saved Application State/com.saenzramiro.rambox.savedState
Match actual files to your installation; do not remove other services' data merely because Rambox displayed them. Uninstalling the client does not cancel a Rambox subscription or delete accounts in the connected services.
Check the remaining local state
pgrep -il Rambox
ls -d /Applications/Rambox.app "$HOME/Library/Application Support/Rambox" "$HOME/Library/Application Support/rambox" "$HOME/Library/Logs/Rambox"
No process output means no matching name is running. Check any match in Activity Monitor. A printed path remains, a missing-path error means it is absent, and a permission error leaves it unknown. On a case-insensitive disk the two support-folder spellings can refer to the same directory.
If you installed it with Homebrew
brew uninstall --cask rambox
This removes the cask app without zap. Direct brew uninstall --cask --zap rambox also removes the support profile and the older cache, preference, WebKit, saved-state and crash-report paths in the cask; it does not consult Mole's checkboxes.
Mole uninstalls Rambox without --zap and removes the leftovers you select.
What Mole lists
The Rambox support profile is listed but not selected. It is outside bulk selection and the Remove data and settings with apps opt-in. Personal or sensitive profiles need an individual choice; shared or unverified ownership is locked. Exact app preferences and ordinary caches are selected by default when present. The cask's older identifiers do not establish that Mole will list those older locations for the current app.
What this test covered
Rambox 2.7.1 was copied from the official package to Applications and uninstalled on September 21, 2026, without sign-in, a Homebrew receipt or a full installer run. In that historical run, the missing browser catalog entry caused the 44.8 MB support folder to be treated as ordinary app support and removed with the app and preferences. The current source classifies it as a protected profile; that change was not verified by repeating the official-package uninstall. Signed-in workspaces and recovery were not tested.