FileZilla SFTP — Connecting and Transferring Files Securely

FileZilla supports SFTP (SSH File Transfer Protocol) natively — no plugins or extensions required. SFTP in FileZilla operates over SSH on port 22, encrypting all commands and file data end-to-end. This guide covers how to set up an SFTP connection in FileZilla using both password and SSH key authentication.

FTP vs SFTP vs FTPS in FileZilla

FileZilla supports three distinct protocols, and it is worth understanding the difference before connecting:

• FTP — standard File Transfer Protocol on port 21. Data is transmitted unencrypted. Suitable only for non-sensitive transfers on trusted networks.
• FTPS — FTP with TLS/SSL encryption. Adds encryption to standard FTP. Uses port 21 (explicit TLS) or port 990 (implicit TLS). Still FTP underneath.
• SFTP — SSH File Transfer Protocol on port 22. A completely separate protocol from FTP. All data and credentials are encrypted via SSH. The recommended choice for most servers.

When your hosting provider or system administrator says to use "secure FTP," they usually mean SFTP. Select it explicitly in FileZilla Site Manager to avoid accidentally connecting unencrypted.

How to Connect to a Server Using SFTP in FileZilla

Method 1: Quick Connect Bar (Password Authentication)

1. Open FileZilla. At the top, find the Quickconnect bar with Host, Username, Password, and Port fields.
2. In the Host field, type sftp:// followed by your server address — for example, sftp://example.com. The sftp:// prefix tells FileZilla to use SFTP.
3. Enter your Username and Password.
4. Set Port to 22 (or leave blank — FileZilla defaults to 22 for SFTP).
5. Click Quickconnect. FileZilla connects and shows your server's file system in the right panel.

Method 2: Site Manager (Recommended for Saved Connections)

1. Go to File → Site Manager (or press Ctrl+S / Cmd+S).
2. Click New Site and give it a name.
3. Set Protocol to SFTP — SSH File Transfer Protocol.
4. Enter your Host (server address) and Port (usually 22).
5. Set Logon Type to Normal for password authentication.
6. Enter your User and Password.
7. Click Connect. FileZilla saves the connection for future use.

SFTP with SSH Key Authentication in FileZilla

SSH key authentication is more secure than passwords and is preferred on servers that support it. Many cloud providers (AWS, DigitalOcean, Linode) use SSH keys by default.

Using an OpenSSH key (.pem or no extension)

1. Open File → Site Manager.
2. Create a new site, set Protocol to SFTP.
3. Set Logon Type to Key file.
4. In the Key file field, browse to your private key file (e.g., my-server.pem).
5. Click Connect. FileZilla uses the key for authentication — no password needed.

Using a PuTTY key (.ppk format)

FileZilla accepts .ppk keys directly. In Site Manager, set Logon Type to Key file and browse to your .ppk file. If you have an OpenSSH key and need to convert it, use PuTTYgen (free) to convert: Load the key, then Save private key as .ppk.

Adding keys to Pageant (Windows)

If you use Pageant (PuTTY's SSH authentication agent) on Windows, FileZilla automatically uses keys loaded into Pageant without requiring you to specify a key file manually. Set Logon Type to Interactive in Site Manager.

Common FileZilla SFTP Errors and Fixes

Error: Connection timed out after 20 seconds

This usually means the server is not accepting connections on port 22, or a firewall is blocking the connection. Check that your hosting provider has SFTP enabled and that port 22 is open. Some providers use a non-standard SFTP port — check your hosting dashboard or ask your provider for the correct port number.

Error: Host key verification failed

FileZilla checks the server's SSH host key on first connection and stores it. If the key changes (server reinstalled, IP reassigned), FileZilla warns you. If you are sure the server is legitimate, click OK to accept the new key. If unexpected, this could indicate a man-in-the-middle situation — verify with your server administrator before accepting.

Error: Authentication failed (password)

Double-check your username and password. Note that SFTP usernames are case-sensitive. If your account uses SSH key authentication only (password login disabled), you must use the Key file logon type in Site Manager rather than password.

Error: No supported authentication methods available

This means the server does not accept password authentication — only SSH keys. Set Logon Type to Key file in Site Manager and provide your private key file. If you do not have a key, generate one with PuTTYgen (Windows) or ssh-keygen (macOS/Linux) and add the public key to the server's ~/.ssh/authorized_keys.

FileZilla SFTP — FAQ

Does FileZilla support SFTP?

Yes. FileZilla has built-in SFTP support — no plugins needed. Select SFTP — SSH File Transfer Protocol as the protocol in Site Manager, or prefix your host with sftp:// in the Quickconnect bar.

What is the difference between FTP and SFTP in FileZilla?

FTP transfers data unencrypted over port 21. SFTP uses SSH encryption over port 22 and is a completely different protocol — not FTP over SSH, but an independent secure file transfer protocol. For any server handling real data, SFTP is the correct choice.

What port does FileZilla SFTP use?

SFTP in FileZilla uses port 22 by default — the standard SSH port. If your server uses a custom SFTP port, enter it in the Port field in Site Manager or in the Quickconnect bar.

How do I use SSH keys with FileZilla SFTP?

In Site Manager, set Protocol to SFTP and Logon Type to Key file. Browse to your private key (.pem, .ppk, or OpenSSH format). FileZilla uses the key for authentication. The corresponding public key must already be installed on the server in ~/.ssh/authorized_keys.

Is SFTP the same as FTPS?

No. SFTP (SSH File Transfer Protocol) operates over SSH on port 22. FTPS (FTP over TLS) is FTP with TLS encryption, usually on port 21 or 990. They are completely different protocols. Both are supported in FileZilla but are configured differently in Site Manager.