LiveChat 
Support 
FTP Client and FTP Server: How the Two Halves Work Together
If you have ever tried to upload files to a website and ended up staring at words like “host,” “port 21,” and “passive mode,” you are in the right place. The whole thing makes a lot more sense once you realize that FTP is not one program sitting on your computer. It is a partnership between two programs: an FTP client and an FTP server. They live in different places, do different jobs, and meet in the middle to move your files.
In this guide, I will walk you through what each half does, how they shake hands and connect, the difference between active and passive mode, and why in 2026 you should almost always reach for the secure version of this connection. By the end, “setting up FTP” will feel obvious rather than mysterious.
Key Takeaways
• FTP names a relationship, not a single program. An FTP client and an FTP server are two cooperating halves of one system.
• The FTP server runs on your web host, stores your files, and waits quietly for connections.
• The FTP client (like FileZilla) runs on your computer and reaches out to connect, upload, and download.
• You connect by giving the client four details: host, username, password, and port, then you drag files to transfer.
• You almost never “set up an FTP server” yourself; your host already did. You configure the client.
• In 2026, prefer SFTP or FTPS over plain FTP, because plain FTP sends your password in readable text.
What does the client-server model of FTP actually mean?
FTP stands for File Transfer Protocol, and a protocol is just an agreed-upon way for two computers to talk. In this case, the conversation is about moving files. But a conversation needs two participants, and that is exactly what FTP gives you.
On one side, you have the FTP server. This is software running on the machine that stores your files, usually your web host. It is always on, always listening, patiently waiting for someone to knock on the door and ask for access.
On the other side, you have the FTP client. This is software running on your own computer. When you want to upload a new homepage or download a backup, the client knocks on that door, proves who you are, and starts moving files back and forth.
Neither half is useful alone. A server with no client connecting to it just sits there. A client with no server to talk to has nowhere to send files. FTP only happens when both halves cooperate, which is why understanding the relationship is the key to understanding everything else. (If you want the plain-English definition of the protocol first, see .)
What is an FTP client?
An FTP client is the software you install on your own computer to connect to a server and transfer files. It is the half you actually touch and click.
A popular, free example is FileZilla, but there are many others, and most of them work in a similar way. The client gives you a visual window, usually with two panels: your local computer’s files on one side and the remote server’s files on the other. You drag a file from the left to the right to upload it, or from the right to the left to download it.
The client’s job is to:
- Open a connection to the server using the address and port you give it.
- Log you in with your username and password.
- Show you the folders and files on the server.
- Upload files from your machine to the server, or download them back.
Think of the client as your remote control. It does not store your website. It just gives you a friendly way to reach the place that does.
What is an FTP server?
An FTP server is the service running on your web host that accepts connections, checks logins, and manages the files and accounts stored on it. It is the always-on half of the partnership.
When you sign up for web hosting, your host sets up an FTP server for your account behind the scenes. That server is responsible for:
- Listening for incoming connections from FTP clients.
- Verifying usernames and passwords so only authorized people get in.
- Keeping track of which folders each account is allowed to see.
- Storing your files and serving them to the client when requested.
Here is the part that trips people up: you almost never run this half yourself. The server already exists on your host’s hardware, configured and running. Your job is simply to connect to it with the right details.
| Role | What it does | Where it runs |
|---|---|---|
| FTP client | Reaches out, logs in, uploads and downloads files; what you click | Your computer |
| FTP server | Listens for connections, checks logins, stores and serves files | Your web host |
How do the FTP client and server connect to each other?
The client opens a connection to the server’s address on port 21, logs in with your username and password, and then the two open a second channel to actually move file data. Let me unpack that, because it is the heart of how FTP works.
First, the client needs to find the server. It uses the host (an address like `ftp.yoursite.com` or a numeric IP) and a port (the door number, traditionally 21 for plain FTP). Port 21 is the “command channel,” where the two programs exchange instructions like “list this folder” or “send me this file.”
Next, the client sends your username and password. The server checks them. If they match an authorized account, the door opens. If not, you get rejected.
Once you are logged in, something interesting happens. The command channel handles instructions, but the actual file contents travel over a separate data channel. FTP uses two channels: one for the conversation and one for the cargo. How that second channel gets opened is where active and passive mode come in.
What is the difference between active and passive mode?
Active and passive mode describe who opens the data channel that carries your files, and passive mode is the one that plays nicely with modern firewalls.
In active mode, the server reaches back to your computer to open the data connection. That sounds reasonable, but home routers, firewalls, and NAT (the technology that lets many devices share one internet address) often block a server trying to initiate a connection inward. The result is a login that works but transfers that mysteriously stall.
In passive mode, your client opens both connections outward to the server. Since outgoing connections are what firewalls expect and allow, passive mode usually “just works.” This is why most FTP clients default to passive mode, and why it is the friendlier choice for almost everyone.
You rarely need to think about this. If transfers hang after a successful login, switching your client to passive mode is the classic fix. Otherwise, leave it on passive and move on.
The thing that finally clicks FTP into place is realizing that “FTP” names a relationship, not a program. It is two cooperating halves, and you are almost always operating only one of them. The FTP server already exists, running quietly on your web host, waiting. What you install and use is the FTP client, the half that reaches out and connects. So when people get confused about “setting up FTP,” it is usually because they are conflating the two. You rarely “set up an FTP server” because your host already did that. Instead, you configure an FTP client with the connection details your host gives you (hostname, username, password, port), and it talks to their server. Once you see that the server is the host’s always-on half and the client is your reach-out half, every FTP setup becomes obvious: you are not building both ends, you are plugging your client into a server that is already listening. And in 2026, make sure that connection is the secure kind: SFTP, not plain FTP.
How do you connect to an FTP server step by step?
Here is the actual process, the same one you will follow in nearly any client. You will need four pieces of information from your web host first: the host, username, password, and port.
- Gather your connection details. Find your FTP or SFTP host (often something like `ftp.yoursite.com`), your username, your password, and the port. Your host provides all of these, usually in your control panel or a welcome email.
- Open your FTP client. Launch FileZilla or whichever client you chose.
- Enter the host. Type the host address into the connection field.
- Enter your username and password. These prove you are allowed in.
- Enter the port. Use 21 for plain FTP, or 22 for SFTP. Your host will tell you which to use. When in doubt, ask for the SFTP settings.
- Connect. Click connect. The client opens the command channel, logs you in, and shows you the server’s folders.
- Navigate to the right folder. For website files, this is usually a folder named `public_html`, `www`, or `htdocs`. This is where your live site lives.
- Drag to transfer. Drag files from your computer into that folder to upload, or drag them out to download. That is it.
If a transfer stalls after step 6, revisit passive mode as described above. Prefer working through your control panel? An lets you upload without installing any client at all.
Why should you use SFTP or FTPS instead of plain FTP?
Plain FTP sends your username, password, and files as readable text, so anyone watching the connection could capture them. SFTP and FTPS encrypt the connection, which is why they are the standard in 2026.
This is the single most important security point in this whole guide. Classic FTP on port 21 was designed in an era before encryption was routine. When you log in over plain FTP, your password travels across the network in cleartext. On an untrusted network, that is a real risk.
The fix is simple. Use one of the secure versions:
- SFTP (SSH File Transfer Protocol) runs over a secure SSH connection, typically on port 22. It is the most common secure choice.
- FTPS (FTP Secure) adds TLS encryption on top of traditional FTP.
Both protect your login and your file contents from eavesdroppers. Most modern hosts and clients support them, and switching usually means changing the protocol and port in your client’s settings. If you would like a deeper comparison, see . The rule of thumb for 2026: if a secure option is available, use it, and most reputable hosts make it available by default.
Do you run an FTP server on your own machine or use your host’s?
For uploading and managing a website, you use your host’s FTP server. Running your own FTP server on your computer is a separate, advanced task that most people never need.
This is the last big point of confusion to clear up. Technically, you can install FTP server software on your own computer so that other people connect to *you*. But that is a different use case entirely, usually for sharing files from a home or office machine.
When your goal is to publish or update a website, the server you connect to is the one your web host already runs. You provide the client, your host provides the server, and you connect the two. You are not building an FTP server; you are plugging into one that already exists.
Upload your site the easy and secure way with DarazHost. DarazHost runs reliable FTP and SFTP servers on every account and supports any FTP client you like, including FileZilla. Prefer to skip the client entirely? Every plan includes an easy cPanel File Manager so you can upload and edit files right in your browser. You get secure transfers over SFTP and FTPS, free SSL, and 24/7 support ready to hand you the exact connection settings (host, username, port) for your account. Whether you love a desktop client or want a no-install option, your files are covered.
What are FTP clients and servers commonly used for?
Now that the two halves make sense, here is where the partnership shows up in everyday work:
- Uploading website files. The classic use: pushing your HTML, CSS, images, and theme files to the server so they go live. (For a beginner walkthrough, see .)
- Downloading and storing backups. Pulling a copy of your site files down to your computer for safekeeping.
- Bulk file management. Moving, renaming, or deleting many files at once, which is often faster than doing it one by one in a browser panel.
- Transferring large media. Uploading big files like videos or design assets that would be awkward through a web form.
In all of these, the pattern is identical: your client reaches out, the host’s server answers, and files move between them.
Frequently asked questions
Is FTP the same as an FTP client? No. FTP is the protocol, the agreed-upon method for transferring files. An FTP client is the software you install to use that protocol. The client is one half; the FTP server on your host is the other.
Do I need to install an FTP server? Almost certainly not. When you want to upload a website, your web host already runs the FTP or SFTP server for you. You only install and configure the client. Running your own server is a separate, advanced scenario.
What port does FTP use? Plain FTP uses port 21 for its command channel. SFTP typically uses port 22, and FTPS uses TLS over the standard FTP ports. Your host will tell you which port and protocol to enter in your client.
Why does my FTP connection log in but then freeze? This is usually an active-versus-passive mode issue. Firewalls and routers often block the server from opening a connection back to you. Switching your client to passive mode lets your client open both connections outward, which typically fixes the stall.
Is plain FTP safe to use? Plain FTP is not encrypted, so it sends your password and files as readable text. For security, prefer SFTP or FTPS, which encrypt the connection. In 2026, secure transfer should be your default.
This article is part of our hosting-basics cluster. For the bigger picture of how everything fits together, read our pillar guide: Web Hosting Basics: The Complete Guide to How Hosting Works and How to Choose.
