How to Uninstall Mountain Duck on Mac
Let pending transfers finish or safely cancel them first. While the drive is still mounted, COPY wanted files to an independent location outside the mount, sync and removal folders and open the copies, then unmount the drive before quitting Mountain Duck; a move or deletion within the mount can propagate to the server. The recorded test used a direct download, not a Homebrew installation.
Remove the app and inspect its data
Quit Mountain Duck, then use Finder › File › Move to Trash on Mountain Duck.app, as the vendor instructs. Review its login item and any File Provider extension in System Settings. The vendor warns that bookmarks and credentials are shared with Cyberduck. The support folder can hold bookmarks. The group container and Keychain credentials may be shared with Cyberduck, so do not remove them solely because Mountain Duck left. Vendor guidance.
After quitting, copy wanted state to an independent private backup outside all removal folders and verify it. In Finder, press Shift + Command + G to open each location or its parent, then move only existing unwanted items confirmed to belong exclusively to this installation to the Trash. Keep shared parents and retained versions' data:
~/Library/Application Scripts/io.mountainduck.fileprovider~/Library/Application Scripts/io.mountainduck.findersync~/Library/Application Scripts/io.mountainduck.loginitem~/Library/Application Support/Mountain Duck~/Library/Caches/io.mountainduck~/Library/Containers/io.mountainduck.fileprovider~/Library/Containers/io.mountainduck.findersync~/Library/Containers/io.mountainduck.loginitem~/Library/HTTPStorages/io.mountainduck~/Library/Logs/Mountain Duck~/Library/Preferences/io.mountainduck.plist
Keep ~/Library/Group Containers/G69SCX94XU.duck and ~/Library/Preferences/G69SCX94XU.duck.plist while Cyberduck or another installed copy uses them. If all owners are gone, back up and verify wanted shared state before individually deciding whether to trash those exact items. The vendor also offers defaults delete io.mountainduck to erase only Mountain Duck’s preferences after backup; it does not clear the shared group or Cyberduck’s credentials. Inspect any custom cache folder you previously configured and remove it only after ownership and backup are confirmed.
Check the result
ls -ld ~/Library/'Application Support'/'Mountain Duck' ~/Library/'Group Containers'/G69SCX94XU.duck
Run this read-only check after quitting the app. A printed path still exists; “No such file or directory” means that path is absent, while a permission error needs its own investigation.
If you installed it with Homebrew
Ordinary cask uninstall unloads io.mountainduck.loginitem independently of zap selections. The Homebrew cask has a zap list that includes Application Support/Mountain Duck, File Provider/login containers, cache and the G69SCX94XU.duck group shared with Cyberduck; manual zap does not check Mole selections. Run the command below without --zap if you want to keep those files and inspect them separately. A manual --zap follows the whole cask list regardless of Mole’s checkboxes. Mole skips --zap when its list reaches unchecked or shared data, or a removal scope it cannot verify; selected remnants still follow Mole's own removal flow.
brew uninstall --cask mountain-duck
What Mole lists
With Remove data and settings with apps off, the display-name support review row starts unchecked; with it on, an eligible existing own unshared row may start checked. Back up wanted state and uncheck it to retain it. Exact bundle-ID cache and preferences are normally selected; shared Cyberduck material and protected group data need separate ownership checks.
What this test covered
Mountain Duck 5.3.2 from the official archive was removed on September 20, 2026. Cyberduck was an installed sibling; File Provider was not installed. No server mount, transfer or bookmark restoration was tested.