How to Configure FileZilla on Windows: Client and Server
Set up FileZilla Client to connect to a server, and FileZilla Server to make a Windows machine an FTP server: users, folders, passive ports, encryption.
4 min readBy Smita
Reviewed by the AmazingRDP technical team

Running FileZilla Server needs administrator rights and a public IP address. A Windows VPS has both. See Windows VPS from $8.99
FileZilla is two separate programs with one name. FileZilla Client connects to a server to move files. FileZilla Server turns a Windows machine into a server that others connect to. Most people need only the client. This page covers both, client first.
Download either from the project's own site, filezilla-project.org, and read each page of the installer; decline any optional extras it offers.
Part 1: FileZilla Client
A quick connection
Fill in the bar at the top: Host, Username, Password, Port, and click Quickconnect. For SFTP, write the host as sftp://203.0.113.10 and leave the port empty or enter 22.
A saved connection
- Open File, Site Manager, and click New site.
- Protocol: choose SFTP for a Linux server or any server with SSH. Choose FTP with Require explicit FTP over TLS for web hosting that offers FTP.
- Host and Port: the server's address; 22 for SFTP, 21 for FTP.
- Logon Type: Ask for password is the safe choice on a shared PC. For key login choose Key file and select your key: see generating an SSH key.
- Click Connect. Accept the server's fingerprint the first time.
Working with it
Your computer is on the left, the server on the right. Drag files across, or double-click. The pane at the bottom shows the queue and failed transfers. View, Directory comparison colours the differences between the two sides.
Settings worth changing
- Edit, Settings, Transfers: simultaneous transfers. Two to four is a good value; more can trip a server's connection limit.
- Edit, Settings, Interface, Passwords: set a master password, or choose not to save passwords. Without one, saved passwords lie readable in a file in your profile.
- File editing: choose your editor, so that "View/Edit" on a remote file opens it and uploads it when you save.
Other clients and how they compare: six FTP and SFTP clients.
Part 2: FileZilla Server
Use this when other people or devices must send files to a Windows machine by FTP. It needs administrator rights, so it runs on a VPS or dedicated server, not on a shared remote desktop. If the other side can use SFTP, consider Windows' own SSH server instead: see OpenSSH on a Windows server.
Install and connect the administration window
- Run the installer. It asks for an administration password; choose one and keep the administration port at its default.
- Start Administer FileZilla Server, connect to
127.0.0.1with that password. - Open Server, Configure.
Create a user and give it a folder
- Go to Rights management, Users, and click Add. Enter a name.
- Tick Require a password to log in and set one.
- Under Mount points, click Add. Virtual path is what the user sees, for example
/. Native path is the real folder, for exampleC:\ftp\client1. - Choose the access: Read only or Read + Write. Give each user the least that works.
- Click Apply.
Passive ports
FTP uses one connection for commands and opens another for every file. For clients behind routers, which is nearly all of them, the server must offer a fixed range of ports for those:
- Under Protocols settings, FTP and FTP over TLS, open Passive mode.
- Tick Use custom port range and enter a range, for example 50000 to 50100.
- If the server is behind a router, enter its public IP address in the field for the public address.
Encryption
In the same section, the Connection Security tab holds the certificate. The installer creates a self-signed one, which encrypts but makes clients show a warning the first time. Keep the minimum at explicit FTP over TLS, so that passwords are never sent unencrypted.
Open the firewall
New-NetFirewallRule -DisplayName "FTP control" -Direction Inbound -Protocol TCP -LocalPort 21 -Action Allow
New-NetFirewallRule -DisplayName "FTP passive" -Direction Inbound -Protocol TCP -LocalPort 50000-50100 -Action Allow
Do not open the administration port to the internet. More in opening ports on Windows Server.
Problems
| Message in the client | Cause |
|---|---|
| Connection timed out | Wrong address or port, or port 21 or 22 closed in a firewall |
| Login works, then "Failed to retrieve directory listing" | The passive port range is not set or not open on the server |
| 530 Login incorrect | Wrong user name or password; both are case-sensitive |
| 550 Permission denied | The user's mount point is read-only, or Windows permissions on the folder do not allow the server's service account to write |
| Certificate warning | A self-signed certificate. Compare the fingerprint with the one shown in the server's settings, then trust it |
| "Insecure FTP connection" warning | The server offers no encryption. Use SFTP or FTP over TLS if the server has them |
The Linux side of the same job: FTP or SFTP on Ubuntu. For a Windows machine with a public IP address and administrator rights, see our Windows VPS plans.
Questions
How do I connect to a server with FileZilla?
Open File, Site Manager, add a new site with the protocol (SFTP or FTP), the host, the port and your login, and click Connect.
What is the difference between FileZilla Client and FileZilla Server?
The client connects to servers to transfer files. The server makes a Windows machine accept FTP connections from others.
Why does FileZilla fail to retrieve the directory listing?
The data connection is blocked. On the server, set a passive port range and open it in the firewall.
Is FileZilla safe?
Yes, when downloaded from the project's own site. Use SFTP or FTP over TLS, and set a master password if you save logins.