Taking FileZilla off a Mac for good
To uninstall FileZilla from a Mac completely, quit it, drag FileZilla from the Applications folder to the Trash, and then delete the hidden settings folder at ~/.config/filezilla. That last folder is the part most guides skip, and it is the part that matters: it holds the Site Manager entries, recent servers, the transfer queue and, unless a master password was set, the saved server passwords in a form that is easy to read back. If the app was FileZilla Pro, there is one more step that has to come first: deregister the licence, because uninstalling does not free the registration slot.
This guide covers the full removal, why each step exists, how to keep the server list for later, and what to install instead if FileZilla is being replaced rather than just removed. Details were checked against FileZilla's own pages and source code on October 8, 2026.
Why the official uninstall guide does not help on a Mac
The FileZilla Pro knowledge base has a page titled "How to Uninstall FileZilla/FileZilla Pro". On October 8, 2026, every step on that page is for Windows: open Control Panel, choose Programs and Features, right click and uninstall. It ends by suggesting a manual check for leftover folders, without saying where they are.
On macOS there is no uninstaller and no Control Panel. Apps are bundles, and removing the bundle removes the program. Settings live elsewhere, in the user's home folder, and stay behind after the app is deleted. That design is deliberate: reinstalling an app brings its settings back. For a transfer client that stores server credentials, it also means that "deleted" is not the same as "gone".
The current FileZilla Client release is 3.71.1, and the download page lists macOS 10.13.2 or newer as the requirement. The steps below apply to any 3.x version.
Step 1: if it is FileZilla Pro, deregister before anything else
FileZilla Pro limits how many devices a licence can be registered on at once. The knowledge base article "Deregister FileZilla Pro Before You Reinstall or Switch Computers" states plainly that uninstalling the application does not free the slot. A user who deletes the app and later activates on a new Mac can hit a "registration limit exceeded" message.
The official macOS steps are:
- In Finder, open Applications and find FileZilla Pro.
- Control-click it and choose Show Package Contents.
- Open Contents, then MacOS.
- Open Terminal and drag the
filezillafile from that folder into the Terminal window, which fills in its full path. - Type a space, then
--deregister --regkey=followed by the registration key. - Press Return.
If FileZilla Pro has already been deleted, the same article says it can be reinstalled and then deregistered. If the Mac has already been wiped, FileZilla Pro support at [email protected] can reset the registration after verifying the licence. FileZilla Pro CLI has its own separate registration and needs its own deregistration.
The free FileZilla Client has no registration, so this step does not apply to it.
Step 2: decide whether to keep the server list
Before deleting settings, decide whether the saved sites will be needed again, either in FileZilla on another Mac or in a different app.
FileZilla has an export function under File > Export. The export dialog offers separate categories: Site Manager entries, the transfer queue, settings, and filters. Exporting the Site Manager entries writes an XML file that can be imported later on another machine.
Two cautions apply.
Passwords travel with the file. FileZilla's settings offer three choices for passwords: save them, do not save them, or save them protected by a master password. If no master password was set, saved passwords are stored in a reversible encoding, not encrypted. Treat the exported file as a credentials file. Keep it in an encrypted location or delete it once the servers are set up elsewhere.
Other apps do not read it directly. Cyberduck, Transmit and ForkLift do not open FileZilla's XML as a bookmark list. The export is useful as a reference: host names, ports, user names and paths can be copied from it. For SFTP servers, defining each one as a Host alias in ~/.ssh/config is the most portable format, because every SFTP client and the terminal can use it.
Step 3: delete the app and the settings folder
Quit FileZilla first, including any transfer still in the queue. Then:
- Drag FileZilla (or FileZilla Pro) from Applications to the Trash.
- In Finder, press Shift+Command+G to open Go to Folder, type
~/.config/filezilla, and press Return. - If the folder opens, go up one level, select the
filezillafolder, and move it to the Trash. - Empty the Trash.
Why that exact folder: FileZilla's source code looks for its settings directory in a fixed order on macOS and Linux. It first checks $XDG_CONFIG_HOME/filezilla, then ~/.config/filezilla, then the older ~/.filezilla. On a standard Mac, the environment variable is not set, so the second location is the one in use. Very old installations may still have ~/.filezilla as well, so check for both.
The folder contains files such as filezilla.xml (general settings), sitemanager.xml (saved sites), recentservers.xml (the quick connect history), filters.xml, and queue.sqlite3 (the transfer queue). Deleting the folder removes all of them in one move.
The Mac App Store build of FileZilla Pro runs in the App Sandbox, so its settings sit inside a container folder under ~/Library/Containers rather than directly in the home folder. Whether that container is removed along with the app is worth checking with the command in the next section.
Step 4: check that nothing is left
A single Terminal command lists anything with FileZilla in its name in the usual places, without deleting anything:
find ~/Library ~/.config ~/.filezilla -iname '*filezilla*' 2>/dev/null
After a clean removal the list is usually empty. If something is listed, open it in Finder with Go to Folder and the path shown, check what it is, and move it to the Trash.
If an entry appears under ~/Library/Containers and FileZilla Pro from the App Store is no longer installed, that container can also be removed. If it is still installed, leave it alone.
Avoid running a recursive delete command copied from a forum. A typo in a path with rm -rf cannot be undone. Moving items to the Trash through Finder gives a chance to restore anything removed by mistake.
When the goal is a clean reinstall, not a removal
Some searches for a FileZilla uninstall are really about a broken install: the Site Manager will not open, the window layout is off screen, or transfers stall after an update. Deleting the app alone does not fix these, because the cause usually sits in the settings folder, and a fresh copy of the app reads the same folder on its first launch.
A safer approach than deleting everything:
- Quit FileZilla.
- In Finder, use Go to Folder with
~/.configand rename thefilezillafolder tofilezilla-old. - Download the current release from the official FileZilla site and replace the app in Applications.
- Launch it. FileZilla creates a new, empty settings folder.
- If the problem is gone, import only the sites from the old folder using File > Import and the old
sitemanager.xml. If the problem returns after importing, the saved sites were not the cause, and the other files in the old folder can be left out.
Renaming instead of deleting keeps a way back. Once the new setup has worked for a few days, filezilla-old can be moved to the Trash.
This also answers a common question in support threads: whether a reinstall "resets" FileZilla. It does not. Only removing or renaming the settings folder does.
Before selling or handing over the Mac
If FileZilla is being removed as part of preparing a Mac for a new owner, the steps above are not enough on their own, and they are also not necessary. Apple's guidance for macOS Monterey and later is to use Erase All Content and Settings, which removes every user's data, including the FileZilla settings folder, in one operation. Apple's support article on erasing an Intel Mac with Disk Utility points Monterey and later users to that function instead.
What still needs doing by hand before the erase:
- Deregister FileZilla Pro, since the licence server cannot see that the Mac was erased.
- Export the Site Manager if the servers will be used on the next Mac, and store the export somewhere encrypted.
- Copy any private keys from
~/.sshthat are still needed. Those are erased along with everything else.
The order matters. Once the Mac is erased, deregistration has to go through FileZilla Pro support, and keys that were not copied are gone.
Why people remove it, and what replaces it
Common reasons include a security review that flags stored passwords, a switch to a client with cloud storage built in, a cleanup before selling a Mac, or simply not needing FTP any more. The right replacement depends on which of those applies. Prices below are from each vendor's official page, checked October 8, 2026.
| Option | Price | Requires | Fits when |
|---|---|---|---|
| Cyberduck 9.5.4 | Free (donation optional) | macOS 10.13 or later | A free client with many cloud services included is needed |
| Transmit 5 | $45 one time, 7 day trial | macOS 13.0 or later | A dual pane transfer app with sync is wanted |
| ForkLift 4 | From $19.95 with 1 year of updates | macOS 14.6 | Transfers plus a full local file manager are wanted |
Built in sftp, scp, rsync |
Free, already on the Mac | Any current macOS | Servers are SFTP only and the terminal is familiar |
Whichever option is chosen, set it up and confirm one real upload before deleting FileZilla's settings. Having the old Site Manager available as a reference during setup avoids guessing at ports, user names and remote paths that were saved years ago and never written down anywhere else. If a server uses a non standard port or a specific remote start folder, both are recorded in the export.
The terminal route needs no install and leaves no settings folder beyond ~/.ssh. rsync -avz --dry-run ./site/ user@host:/var/www/ shows what would be uploaded before anything moves.
The weakness of the terminal route is that the local folder is out of sight while commands run. A file manager with a built-in terminal keeps the folder list on screen and opens the shell already inside the selected folder, which removes the cd step and makes it easier to see what is being uploaded. The features page shows how that pairing works, and the comparison page lists what different types of file manager can and cannot do, including the ones that handle FTP themselves.
What to change first
Deregister FileZilla Pro if it applies, export the Site Manager only if the servers are still needed, then delete both the app and ~/.config/filezilla. If the replacement is SFTP from the command line, Atriens is free on the Mac and keeps the project folder and its terminal in one window.
Frequently asked questions
Does dragging FileZilla to the Trash remove it completely?
No. It removes the program, but the settings folder at ~/.config/filezilla stays behind, including saved sites and, without a master password, readable passwords. Delete that folder as well for a complete removal.
Where does FileZilla store saved passwords on a Mac?
In sitemanager.xml and recentservers.xml inside ~/.config/filezilla. Unless a master password is set in FileZilla's settings, they are stored in a reversible encoding rather than encrypted, so the folder should be deleted or protected.
Does FileZilla Pro need to be deregistered before uninstalling?
Yes, if the licence will be used again. FileZilla Pro's knowledge base says uninstalling does not free the registration slot. Deregister with the --deregister --regkey= option on the binary inside the app bundle, or contact [email protected] if the Mac has already been wiped.
Can FileZilla sites be imported into Cyberduck or Transmit?
Not directly. FileZilla's export produces its own XML format. Use it as a reference to re-enter each server, or define SFTP servers as Host aliases in ~/.ssh/config so any client can use them.
Will reinstalling FileZilla bring the old sites back?
Only if ~/.config/filezilla was left in place. FileZilla reads that folder on launch, so a reinstall without deleting it restores the previous sites, queue and settings.