Stop retyping FileZilla connections: Site Manager profiles, FTPS versus SFTP, and password safety

The problem: retyping connection details and picking the wrong protocol

You transfer files to the same server every day, but FileZilla opens with an empty quick-connect bar. You retype the host, port, username, and protocol. Eventually you choose port 21 for an SSH-based server or port 22 for an FTP server, and the connection fails. The hostname and port look right, but the underlying protocol does not match what the server expects.

FileZilla Site Manager, reached through Edit > Site Manager, stores named connection profiles so you do not have to rebuild them by hand. A profile can remember the host, port, logon type, default remote directory, transfer mode, and encryption settings. This post shows how to build one, how FTPS and SFTP differ, and what to know before saving a password.

FTPS and SFTP are not interchangeable

FileZilla supports FTP, FTPS, and SFTP in the Protocol dropdown, but they are different wire protocols:

Profile setting	FTPS explicit	SFTP
Protocol in FileZilla	FTP over TLS (FTPS)	SFTP over SSH-2
Default port	21	22
What happens on connect	FTP control channel starts plain, then upgrades with TLS	SSH-2 session; not FTP wrapped in SSL
Typical failure if mismatched	Server rejects SSH handshake on FTP port	Server expects FTP commands, receives SSH packet

Explicit FTPS usually begins on port 21 and upgrades the control channel, while SFTP runs on port 22 as a separate SSH-based protocol. If you save an SFTP server as an FTPS profile, the connection will fail even when the hostname and port appear correct. Verify the server administrator's required protocol before creating the profile.

Worked example: create a repeatable FTPS profile

Where: FileZilla desktop client, Edit > Site Manager. Required permissions: none to open Site Manager; writing a profile modifies your local FileZilla configuration.

1. Open FileZilla and choose Edit > Site Manager.
2. Click New site and name it, for example web-server-ftps.
3. Set Protocol to FTP over TLS (FTPS).
4. Enter Host, for example example.com, and Port 21.
5. Set Logon type to Ask for password if you do not want to store the password, or Normal to store username and password.
6. Enter User, for example deploy. Leave Password blank if you chose Ask for password.
7. Under Encryption, select Require explicit FTP over TLS if the server requires it.
8. Click OK.

To connect, open Site Manager, select web-server-ftps, and click Connect. If you chose Ask for password, enter the password when prompted. Check the status log after connecting. Look for lines indicating TLS negotiation on the control channel; the exact wording depends on your FileZilla version, so confirm the messages in your installed client rather than memorizing a specific line.

Saved passwords and the master password setting

If you set Logon type to Normal, FileZilla stores the password in its local configuration file. On Windows this is typically %APPDATA%\FileZilla\sitemanager.xml; on Linux, often ~/.config/filezilla/sitemanager.xml. Anyone with access to your user account or that file can potentially recover the stored credentials.

FileZilla offers a local master password under Edit > Settings > Security. When enabled, it protects stored Site Manager passwords. This is not a replacement for a dedicated credential vault, and it does not protect the connection itself—only the saved password on your computer. If your organization prohibits stored credentials, use Ask for password and do not enable Normal logon.

Verification and rollback

Practical check: open Edit > Settings > Security and confirm whether a master password can be set in your version. Then connect to the saved profile and review the status log for the expected protocol negotiation. If the server requires explicit FTPS and you see a protocol mismatch, delete the profile and recreate it with the correct Protocol and port.

Rollback: creating or editing a Site Manager entry writes to your local configuration. To remove a test profile, open Site Manager, select the entry, and click Delete. If you edited the configuration file by hand—which is not recommended—remove the corresponding server block, save, and restart FileZilla. Hand-editing risks malformed XML and can prevent Site Manager from opening.

Closing

Use Site Manager when you connect to the same host repeatedly. Match the protocol to the server, not the port alone, and treat saved passwords as local-only secrets protected at best by a master password. Verify menu paths and default ports in your installed FileZilla version before documenting a team procedure.