How to Use FileZilla: A Step-by-Step Guide for Beginners

How to use FileZilla comes down to four actions: connect to your server, open the right folder, drag files across and check the transfer queue. Most people do all four in under five minutes once they have their login details.

I built this guide in October 2026 from FileZilla’s own wiki, the Site Manager documentation and WordPress’s file transfer guidance. I also tried an older FileZilla build on an Apple Silicon Mac, and that test shows why the right download matters.

This FileZilla tutorial covers the download, the connection fields and the two ways to connect. You also get the upload steps for WordPress files and the permission settings. Then come the common errors and the safety rules.

What Is FileZilla?

FileZilla is a free open-source program that moves files between your computer and a web server. It speaks FTP, FTPS and SFTP. You can upload WordPress themes, plugins and images without a hosting file manager. The FileZilla Client is the part you install on your computer.

FileZilla also makes a separate FileZilla Server, which you install on a machine you want to turn into a file server. Website owners almost always want the Client.

People search for “FileZilla how to use” and “how to run FileZilla”, and both questions start with the Client. The FileZilla download page says the latest stable Client is 3.71.1 as of October 2026.

The page also lists three editions: FileZilla (Free), FileZilla with a manual and FileZilla Pro. The free edition covers FTP, FTPS and SFTP, which is all most WordPress sites need. This FileZilla user guide uses the free Client throughout.

How to Download and Install FileZilla

Download FileZilla from the official project site and pick the build that matches your computer. The download page lists Windows 64-bit and 32-bit, Linux 64-bit and 32-bit, and two macOS builds: Apple Silicon and Intel. Choosing the wrong one is the most common install problem on a Mac.

I saw that problem first hand. A FileZilla 3.55.1 build on my Apple Silicon Mac refused to start, and the terminal printed “bad CPU type in executable”. That older build was Intel-only, and the Mac had no translation layer installed.

Follow these steps:

1. Open the official page: Go to filezilla-project.org and choose Download FileZilla Client.
2. Pick your system: Select Windows, Linux, macOS Apple Silicon or macOS Intel. Check Apple menu, About This Mac, if you are unsure of your chip.
3. Run the installer: Open the downloaded file and follow the prompts. On a Mac, drag FileZilla into Applications.
4. Open FileZilla: Launch it. You should see an empty main window with a connection bar at the top.

Download only from the official site. Third-party mirrors can bundle other software with the installer.

What You Need to Connect With FileZilla

You need four details to connect: a host, a username, a password and a port. Your hosting company gives you these, usually in a welcome email or in the hosting panel under FTP accounts. You also need to know whether the server uses plain FTP or the encrypted SFTP.

The host is a server name such as ftp.example.com or your server’s IP address. The username and password belong to an FTP or SSH account, which is often not the same as your WordPress login. Leave the port blank unless your host names one.

Use this table to match the protocol to the standard port:

Protocol	What it does	Standard port
FTP	Sends files and your password as plain text	21
FTPS (FTP over TLS)	FTP with encryption added	21 for explicit mode
SFTP	File transfer over an SSH connection	22

The port numbers are the registered ones in the IANA service name and port registry. WordPress’s guide on FTP clients is blunt about the risk. Plain FTP sends data in clear text. Use SFTP or FTPS whenever your host supports it.

How to Connect to a Server With Quickconnect

Quickconnect is the fastest way to connect, and it needs no setup. You type the host, username and password into the bar at the top of FileZilla and press the Quickconnect button. Use it for a one-time job, and use the Site Manager for sites you visit often.

Follow these steps:

1. Enter the host: Type your host in the Host field. For SFTP, write sftp:// before the name, and for FTPS write ftps://.
2. Enter your login: Fill in the Username and Password fields.
3. Leave the port blank: FileZilla’s tutorial says to leave Port empty unless your login information names a port.
4. Click Quickconnect: The message log underneath shows each step of the connection.

The tutorial on the FileZilla wiki describes the same steps. When it works, the log ends with a line saying the directory listing succeeded, and the right-hand panel fills with your server’s folders.

FileZilla Tutorial: How to Connect With the Site Manager

The Site Manager saves a server so you can reconnect in one click. Open it from the File menu, or press Ctrl+S on Windows or Command+S on a Mac. You add a New site, fill in the General tab and press Connect.

Follow these steps:

1. Open the Site Manager: Choose File > Site Manager.
2. Create a site: Click New Site and type a name you will recognize, such as your domain.
3. Choose the protocol: In the Protocol list, pick SFTP if your host supports it. Pick FTP only when it does not.
4. Fill in the General tab: Enter the Host and then the User and Password. Set the Logon Type to Normal.
5. Click Connect: FileZilla saves the entry and connects.

The Site Manager page on the FileZilla wiki lists the General tab fields: Host, Port, Protocol, Encryption, Logon Type, User and Password. It also lists the Logon Type choices, which matter for security.

The Advanced tab holds a Default remote directory. FileZilla’s wiki gives /public_html as an example. FileZilla then opens in your website folder every time. Set it once and you will never land in the wrong folder.

Understanding the FileZilla Window

The FileZilla window has four areas that you use in every session. The message log sits at the top and the local files are on the left. The remote server files are on the right, and the transfer queue runs along the bottom.

The FileZilla tutorial describes three of them. The local pane shows files on the computer you are using, and the server pane shows files on the server you connected to. The transfer queue lists files waiting to move and files already moved.

The log at the top is the part beginners skip, and it is the most useful when something fails. It prints every command and reply. When a connection stops, the last red line tells you why.

The queue at the bottom has three tabs: Queued files, Failed transfers and Successful transfers. Keep them in view during big uploads. You then spot a failed file before you leave the screen.

How to Use FileZilla to Upload and Download Files

How to use FileZilla for transfers is simple. You upload by dragging files from the left pane to the right pane, and you download by dragging the other way. You can also right-click a file and choose Upload, or double-click it.

Follow these steps:

1. Find your local files: In the left pane, browse to the folder that holds the files you want to send.
2. Open the server folder: In the right pane, open the folder where they belong, such as your site’s root.
3. Transfer the files: Drag them across, or right-click and choose Upload.
4. Watch the queue: The Queued files, Failed transfers and Successful transfers tabs at the bottom show progress.

To download, find the file on the server pane and drag it to a folder on the left. Always check the Successful transfers tab afterward. A file that sits in the Failed transfers tab did not arrive.

How to Upload a WordPress Plugin or Theme With FileZilla

Upload a plugin by extracting its zip file on your computer and then copying the extracted folder into the wp-content/plugins folder on the server. WordPress’s Manage Plugins guide says to transfer the extracted folder to that directory with SFTP or a remote file manager. Themes work the same way in wp-content/themes.

Follow these steps:

1. Extract the zip: Unzip the plugin or theme on your computer. Upload the extracted folder and leave the zip file behind.
2. Connect: Open your saved site and go to the WordPress folder on the server.
3. Open the right folder: Browse to wp-content/plugins for a plugin, or wp-content/themes for a theme.
4. Upload the folder: Drag the extracted folder from the left pane into that folder on the right.
5. Activate it: Log in to WordPress and activate the plugin or theme from the dashboard.

This manual route helps when the dashboard upload fails on a size limit. It also helps when a bad plugin has locked you out. Then you must remove its folder, as our guide on fixing a plugin fatal error explains.

Back up before you replace or delete anything. Renaming a plugin folder through FileZilla turns the plugin off, which is a quick way to find a plugin that broke your site.

Plugins bought on CodeCanyon can use the same route, and you can install CodeCanyon plugins over SFTP after unzipping the right file.

Moving a whole site works the same way. Our guide on how to move a WordPress site to a new domain shows which files and database steps go with the transfer.

How to Change File Permissions in FileZilla

File permissions control who can read, write and run a file on the server. Right-click a file or folder in the server pane and choose File permissions to see a numeric value. WordPress recommends 755 for directories and 644 for files. Set those unless your host says otherwise.

Follow these steps:

1. Select the item: Right-click the file or folder in the server pane.
2. Open File permissions: Choose File permissions from the menu.
3. Enter the value: Type 755 for a folder or 644 for a file.
4. Apply to subfolders if needed: Tick the option to apply the change to folders inside it, and pick the right type of item.

The WordPress hardening guide gives the same numbers: directories at 755 and files at 644. It also notes that wp-config.php should be readable only by you and the web server, which usually means 400 or 440.

Do not set 777 to make an error go away. A file anyone can write to is a security hole, and the real fix is usually the file’s owner.

Active and Passive Mode in FileZilla

FileZilla can transfer data in active or passive mode, and passive is the safer choice behind a home router. In passive mode, the client asks the server for an address and connects to it. In active mode, the server connects back to your computer, which firewalls often block.

The FileZilla wiki explains the difference in its Network Configuration page. It says that in passive mode, which it recommends, the client sends the PASV command and the server replies with an address.

A sign of the wrong mode is a connection that succeeds and then fails on the directory listing. If you see that, check your firewall and try the other mode in the Site Manager’s Transfer Settings tab.

Most home setups work with passive mode and nothing else. Change it only when the log shows a stalled listing, because switching modes without a reason adds one more thing to debug.

Common FileZilla Errors and How to Fix Them

Most FileZilla errors point to one of four causes: a wrong login, a blocked port, a permission problem or the wrong protocol. The message log at the top of the window tells you which one. Read its last lines first, because they hold the server’s reply.

Check these in order:

• 530 Login incorrect: The username or password is wrong. The code is a standard reply defined in RFC 959, where 530 means not logged in. Check your FTP account details.
• Connection timed out: The host or port is wrong, or a firewall blocks it. Check the host, the port and your network.
• Connection refused: Nothing is listening on that port. You may be using FTP on a server that only offers SFTP. Change the protocol.
• 550 Permission denied: The account cannot write to that folder. Open the folder permissions or upload to a folder you own.
• Failed to retrieve directory listing: Try passive mode, and check your firewall.

If a transfer stops halfway, requeue it from the Failed transfers tab. A large upload may time out on a slow link, and a smaller batch usually finishes.

FileZilla Security Best Practices

Use SFTP, protect your saved logins and keep FileZilla updated. WordPress’s own docs say to prefer SFTP, because with SFTP your password is never sent in the clear and cannot be intercepted by an attacker. Plain FTP is acceptable only when your host offers nothing else.

Follow these rules:

• Choose SFTP or FTPS: Plain FTP sends your password as readable text.
• Use Ask for password on shared computers: FileZilla’s Logon Type list includes Ask for password, which remembers the password only for the session.
• Use key files where you can: The Key file logon type is for SFTP and needs your private key and a public key on the server.
• Update the Client: Install new versions from the official site, since the current release is 3.71.1.
• Remove old sites: Delete Site Manager entries for servers you no longer use.

If you manage client sites, give each person their own FTP account. Then you can remove one account without changing everyone else’s password.

File transfer is one part of site security. Our WordPress security checklist covers the rest, from strong logins to update habits, and our WordPress security services can audit a site you inherit.

Conclusion

Now you know how to use FileZilla to connect, upload and fix common errors. Download the right build, connect with SFTP through Quickconnect or the Site Manager, and drag files from the left pane to the right.

Check the transfer queue after every job, set permissions to 755 and 644, and keep your logins safe. A short checklist beats a long guess when something breaks.

Frequently Asked Questions (FAQs)