FileZilla Site Manager: Choosing FTPS or SFTP for a Remote Host

Many FileZilla users connect to a remote server by entering a hostname and picking the first secure option in the Site Manager. The connection then hangs, returns a timeout, or fails authentication even though the credentials are correct. The usual cause is a protocol mismatch: FTPS and SFTP both encrypt file transfers, but they are different protocols running on different services. Choosing the wrong one means FileZilla speaks FTP to an SSH daemon, or TLS to an FTP server that only accepts plain commands.

This post explains how to decide between FTPS and SFTP in FileZilla's Site Manager, configure each one, and verify the connection using the client log.

FTPS and SFTP are not the same service

FTPS is FTP over SSL/TLS. It typically uses port 21 for the control channel and separate ports for data transfers. SFTP is the SSH File Transfer Protocol. It runs commands and data inside a single SSH tunnel, usually on port 22. Because the protocols are unrelated, a server that offers SFTP on port 22 will not understand an FTPS request on port 21, and vice versa.

FileZilla's Site Manager lets you store both configurations for the same host, but you must select the protocol that matches the service actually listening on the remote server.

Configure FTPS with explicit TLS

1. Open File > Site Manager and click New site.
2. Enter the remote host and set Port to 21.
3. Set Protocol to FTP - File Transfer Protocol.
4. Set Encryption to Require explicit FTP over TLS (FTPS).
5. Set Logon type to Ask for password or Normal.
6. Click Connect and watch the log pane at the top of the window.

If the server supports explicit FTPS, the log should show TLS negotiation after the initial greeting. If the server only offers plain FTP, the TLS request will be rejected and the connection will fail.

Configure SFTP over SSH

1. Open File > Site Manager and click New site.
2. Enter the remote host and set Port to 22.
3. Set Protocol to SFTP - SSH File Transfer Protocol.
4. Set Logon type to Ask for password, Key file, or Interactive.
5. If you choose Key file, browse to your private SSH key, for example id_ed25519. FileZilla may offer to convert keys that are not in OpenSSH format.
6. Click Connect and watch the log pane.

A working SFTP connection begins with an SSH server banner and key exchange. If you see Connection refused on port 22, the remote host is probably not running an SSH service.

Verify the connection in the log pane

FileZilla writes connection events to the top log pane. Use it to confirm which protocol succeeded:

• FTPS: look for TLS negotiation following the FTP greeting.
• SFTP: look for the SSH banner and key-exchange lines.
• Failure: Connection refused, 530 login errors, or authentication failures usually mean the protocol, port, or credentials do not match the server.

Test with one small file before transferring a larger batch. This confirms the channel is open without risking a long partial transfer.

Trade-offs and credential storage

FTPS requires the firewall to allow the control port and a passive data port range. SFTP needs only one port, usually 22, which is often simpler behind network restrictions. FTPS may present a server certificate for you to trust; SFTP presents an SSH host key.

FileZilla can save passwords in the Site Manager. Without a master password, those credentials are stored locally in a recoverable form. Set a master password under File > Settings > Interface if you save logon details.

Increasing the number of simultaneous transfers under Settings > Transfers can improve bulk throughput, but too many connections may trigger rate limiting or temporary blocks on the remote server.

Actionable closing

Ask your administrator or hosting panel whether the server offers FTPS, SFTP, or both. Create one Site Manager entry for the correct protocol, test it with a small file, check the log pane for the expected handshake, and set a master password before saving any password.