How to uninstall Cyberduck on Mac

Cyberduck connects to servers and cloud storage. The bookmarks, history and connection profiles it saves live in a folder it shares with Mountain Duck and Cyberduck CLI, so copy that folder somewhere safe before you remove anything, and leave it in place if you still use either tool. These steps cover the official zip from cyberduck.io and the Homebrew cask cyberduck.

Quit and remove the app

1. Quit Cyberduck from its menu or Command + Q, then check Activity Monitor for Cyberduck and confirm the process has exited.
2. Move Cyberduck.app from Finder's Applications folder to the Trash.

Where Cyberduck keeps data

Cyberduck's own documentation puts your bookmarks, connection history and saved profiles in ~/Library/Group Containers/G69SCX94XU.duck/Library/Application Support/duck/, and says that folder is shared with Cyberduck CLI and Mountain Duck. Your preferences are separate, in ~/Library/Preferences/ch.sudo.cyberduck.plist. Cyberduck FAQ

The group container is named after Cyberduck's Apple Developer Team ID (G69SCX94XU) rather than Cyberduck's bundle ID, and Mountain Duck, from the same developer, uses the very same folder: its Homebrew cask names ~/Library/Group Containers/G69SCX94XU.duck in its zap list too. If you want to keep your saved server connections, copy that folder somewhere else before removing Cyberduck, especially before using Homebrew's zap step below.

Check the result

pgrep -il cyberduck
launchctl list | grep -i cyberduck
ls -d "$HOME/Library/Application Support/Cyberduck" "$HOME/Library/Group Containers/G69SCX94XU.duck"

• No output from pgrep means no Cyberduck process is running.
• No output from launchctl list means Cyberduck has no background job registered.
• ls -d prints each folder that still exists and reports "No such file or directory" for the rest. A surviving group container means your saved connections are still there, which is what you want if you use Mountain Duck or Cyberduck CLI.

If you installed it with Homebrew

The cyberduck cask's zap list reaches ~/Library/Application Support/Cyberduck, ~/Library/Caches/ch.sudo.cyberduck, ~/Library/HTTPStorages/ch.sudo.cyberduck, ~/Library/Logs/Cyberduck, your preferences file, saved window state, and ~/Library/Group Containers/G69SCX94XU.duck. Running brew uninstall --cask --zap cyberduck yourself moves all of them to the Trash, whatever you ticked in Mole, including the shared group container and the connections Mountain Duck and Cyberduck CLI read from it. Homebrew Cyberduck cask

When Mole removes a Homebrew install, it checks the zap list first. Mole does not treat the shared group container as Cyberduck's own, and ~/Library/Application Support/Cyberduck is unselected by default, so while that group container exists Mole leaves --zap out: Homebrew removes the app and its receipt, and only the rows you ticked go to the Trash.

To keep your saved connections, copy ~/Library/Group Containers/G69SCX94XU.duck/Library/Application Support/duck/ somewhere else first, or remove the app without the zap step:

brew uninstall --cask cyberduck

What Mole lists

For Cyberduck installed from cyberduck.io or the Homebrew cask:

• ~/Library/Caches/ch.sudo.cyberduck, ~/Library/HTTPStorages/ch.sudo.cyberduck, ~/Library/Logs/Cyberduck, your preferences file and saved window state are selected by default.
• ~/Library/Application Support/Cyberduck is listed but not selected, because it's named after the app rather than its bundle ID.
• Mole never lists ~/Library/Group Containers/G69SCX94XU.duck, where your saved connections live, even though Homebrew's zap list names it. Group containers are protected in Mole unless the folder name carries the app's own bundle ID, and this one is a Team ID group that Mountain Duck uses as well. If you're sure no Cyberduck-family app needs it, remove it yourself in Finder after copying what you want to keep.

What this test covered

Cyberduck was installed with the Homebrew cask cyberduck and uninstalled on September 17, 2026, with Mole Preview 272, alongside other apps in the same batch. That build still ran Homebrew's zap step, which removed the G69SCX94XU.duck group container along with the app. Server sign-in, Mountain Duck, Cyberduck CLI and the official zip from cyberduck.io were not tested.