How to uninstall FileZilla on Mac
This guide covers the Mac client downloaded from the FileZilla website. Save wanted site settings and connection records first. The default ~/.config/filezilla directory can hold connection details; it is not disposable cache. Keep remote files and local transfer files separately.
Quit and remove the client
Finish transfers or stop the queue, then press Command + Q to quit FileZilla. Move FileZilla.app from Applications to Trash. This does not delete files on your server or cancel server services.
Review configuration
Use Shift + Command + G in Finder to inspect these locations. Copy wanted configuration elsewhere before deciding whether to trash it. These paths were present in the tested official build; older versions and custom configuration locations need separate checks.
| Path | Decision |
|---|---|
~/.config/filezilla |
User configuration that may contain sites and connection details. Keep it if needed. |
~/Library/Preferences/org.filezilla-project.filezilla.plist |
Preferences. Back them up if wanted. |
Do not delete the whole ~/.config directory; other apps may store data there.
Check the result
if [ -e "/Applications/FileZilla.app" ]; then
printf '%s\n' 'App bundle still exists'
else
printf '%s\n' 'App bundle not found at this path'
fi
ls -ld "$HOME/.config/filezilla"
ls -ld "$HOME/Library/Preferences/org.filezilla-project.filezilla.plist"
The first check inspects the original app location. An ls listing means data remains, No such file means it is absent, and Permission denied leaves the result unknown. Other app copies, custom configuration locations and remote files are outside these checks.
What Mole lists
Preferences and the observed system temporary cache are selected by default. ~/.config/filezilla is app data: with app-data selection off, it is listed but not selected. Ordinary cleanup does not treat it as cache. Keep it if you need the configuration.
What this test covered
On October 8, 2026, the official Apple Silicon build of FileZilla 3.71.1 was installed and launched. Mole then removed the app, preferences, system temporary cache and explicitly selected test configuration directory. Status displayed one app row; the update scan did not identify a channel. No real FTP server was connected, and site-backup restoration and custom configuration locations were not tested.