How to uninstall Loopback on Mac
Keep a record of wanted virtual-device routing before uninstalling Loopback. Its current manual says the built-in uninstall removes virtual audio devices and backend components. This guide covers the official Mac app and Homebrew cask loopback; older ACE-based variants can have different backend controls.
Run Loopback's own uninstall first
Stop apps using Loopback devices and select another input/output device where needed. Keep screenshots or notes of routes you want to recreate, and copy wanted ~/Library/Application Support/Loopback configuration outside that folder. While Loopback is still installed, choose Help › Uninstall Loopback… and complete its backend-removal steps, including administrator authorization when requested.
After that finishes, quit Loopback and move Loopback.app from Applications to Trash. Keep other Rogue Amoeba apps' working audio components; do not delete a shared engine directory by hand.
Review settings and local state
After backing up wanted configuration, completing the official backend removal and quitting the app, press Shift + Command + G in Finder to open the support, cache and preferences locations below, then move the Loopback items you no longer need to Trash. Remove the background agent through the vendor or package flow; keep shared audio-engine and activation files.
| Location | Keep or remove |
|---|---|
| ~/Library/Application Support/Loopback | Local support data. Back up wanted configuration before resetting. |
| ~/Library/Caches/com.rogueamoeba.Loopback | App cache. |
| ~/Library/Preferences/com.rogueamoeba.Loopback.plist | App preferences. |
| ~/Library/LaunchAgents/com.rogueamoeba.loopbackd.plist | Background-agent file named by the cask's ordinary uninstall. Use the vendor or package removal path. |
The cask also names Loopback HTTP storage, WebKit and saved state. Preserve shared Rogue Amoeba activation/engine settings, including com.rogueamoeba.audiounit.plist. Uninstalling does not cancel a subscription or delete an account.
Check the remaining app and agent
pgrep -il 'Loopback|loopbackd'
ls -d /Applications/Loopback.app "$HOME/Library/Application Support/Loopback" "$HOME/Library/LaunchAgents/com.rogueamoeba.loopbackd.plist"
launchctl list | grep -F com.rogueamoeba.loopbackd
No process or agent match means none was shown in that query. A match needs a check, and a failed query is unknown. Printed paths remain, missing-path errors mean absence, and permission errors leave them unknown. Check that Loopback virtual devices have disappeared from your audio-app device menus after the official uninstall.
If you installed it with Homebrew
brew uninstall --cask loopback
The ordinary cask uninstall requests quit for Loopback and loopbackd and removes its specified user launch-agent file. It does not replace the vendor's virtual-device/backend uninstall. Direct brew uninstall --cask --zap loopback also removes support data, cache, HTTP storage, preference patterns, saved state and WebKit in the cask, without consulting Mole's checkboxes.
Mole checks Homebrew's full removal list and skips --zap when it reaches unchecked data, shared files or anything it cannot verify. It still removes the leftovers you selected.
What Mole lists
Exact app preferences, caches, HTTP storage and WebKit state are selected by default when present. Display-name support data is listed but not selected with Remove data and settings with apps off; enabling it can preselect eligible reviewed data. Shared audio-engine settings stay outside this app-data selection.
What this test covered
Loopback 2.5.0 was copied from the official package to Applications and uninstalled on September 21, 2026, without installing the audio backend or a Homebrew receipt. The app and local preference/cache/HTTP/WebKit data went to Trash, while three temporary WebKit leaves returned permission errors. Virtual devices, ARK or ACE removal and an installed background agent were not verified.