An FTP site is a server that accepts file transfers over the File Transfer Protocol. You connect to it with a username and password, see a directory listing, and move files in either direction — historically the standard way to publish a website.
One thing to know upfront: FTP is legacy technology. Chrome and Firefox removed support for it in 2021, and the protocol sends your password in plain text. FTP sites still exist and still work, but almost every case that used to call for FTP now calls for SFTP.
This guide covers what an FTP site is, how to connect to one, how to map it as a network location on Windows or macOS, and what to use instead.
Table of Contents
What is an FTP site?
An FTP site — also called an FTP server — is a machine connected to the internet running FTP server software, listening on port 21. It exists to receive and serve files.
The name is misleading in one way: an FTP site isn’t a website. There’s no page to render, no HTML, no browser experience. It’s a filesystem exposed over the network, and what you get when you connect is a directory listing, much like a folder on your own computer.
The protocol behind it is FTP — File Transfer Protocol, defined in 1971. Our guide on what FTP means covers the protocol itself: its history, how the commands work, and where it sits among the internet’s original protocols. This article is about the practical side — the server, how to reach it, and what to use instead.
Every FTP site has four things you need to connect:
| What you need | Example |
|---|---|
| Host | ftp.example.com or an IP address |
| Port | 21 for FTP, 22 for SFTP |
| Username | Assigned by whoever runs the server |
| Password | Same |
Your hosting provider gives you all four when you sign up, usually in the welcome email or the control panel.
How an FTP site works
The exchange is straightforward, and it’s older than the web — FTP was defined in 1971, two decades before HTTP.
1. The client opens a connection to the server on port 21.
2. The client authenticates with a username and password. Some servers allow anonymous FTP, where the username is literally anonymous — historically how public software archives were distributed.
3. The server sends a directory listing, and the client displays it as a browsable folder tree.
4. Files move in either direction. Upload puts a local file on the server; download does the reverse.
5. The session closes when the client disconnects or times out.
One quirk worth knowing: FTP uses two connections, not one. The control connection on port 21 carries commands, and a separate data connection carries the actual file contents. That split is why FTP has active and passive modes — and why it interacts badly with firewalls and NAT. Passive mode is the default now precisely because it works through firewalls; if a connection authenticates but then hangs on the directory listing, switching to passive almost always fixes it.
⚠️ The state of FTP today
This is the part most articles about FTP leave out, and it changes the answer to “should I use an FTP site?”
Browsers no longer support FTP. Chrome removed it in version 88 (January 2021) and Firefox in version 90 (July 2021). Typing ftp:// into a modern browser does nothing useful. If you remember browsing FTP archives in a browser window, that era ended.
FTP sends everything in plain text — username, password, and file contents. Anyone able to observe the connection can read all of it. In 1971 that was acceptable; on today’s internet it isn’t.
Most hosting providers still offer FTP for compatibility, and it still works with a dedicated client. But they also offer SFTP, and there’s no reason to choose the unencrypted one.
The practical rule: if you’re setting something up today, use SFTP. If you’re connecting to an existing FTP site you don’t control, use a proper client and assume the connection is readable.
Which one should you use?
Three protocols, similar names, and only one of them is worth choosing for a new setup.
| Encrypted | Port | Use it? | |
|---|---|---|---|
| FTP | No — plain text | 21 | Only if forced |
| SFTP | Yes, over SSH | 22 | Yes |
| FTPS | Yes, over TLS | 990 or 21 | If SFTP isn’t available |
SFTP is the answer for almost every case. It encrypts everything, uses a single connection — which makes firewalls far less trouble — and if your host gives you SSH access, you already have it. Just change the protocol in your client and use port 22.
FTPS is genuinely FTP with a TLS layer. Secure, but it inherits FTP’s two-connection design and the firewall problems that come with it. It exists mostly where a specific compliance requirement names it.
And despite the names, SFTP and FTPS are unrelated protocols — SFTP is a subsystem of SSH and shares no code with FTP. For the full technical comparison, including authentication methods and how each handles the connection, see our guide on what FTP means.
How to connect to an FTP site
Since browsers dropped support, you need a client.
FileZilla — free, open source, Windows, macOS and Linux. The default recommendation.
WinSCP — Windows only, free, with a two-pane interface many people prefer.
Cyberduck — macOS and Windows, free, clean interface.
Your host’s web-based file manager — no installation, works from any browser, and usually the fastest route for a single file.
The connection, step by step:
- Open the client and enter the host (
ftp.example.com). - Enter the username and password from your host.
- Set the port — 21 for FTP, 22 for SFTP.
- Choose the protocol. Pick SFTP if it’s offered.
- Connect. The remote directory appears alongside your local files.
- Drag files across to transfer them.
Where your website files go: almost always public_html, or sometimes www or htdocs. Files placed anywhere else won’t appear on your site.
How to map an FTP site as a network location
A common request, and worth its own section: you can add an FTP site to your file manager so it behaves like a normal folder.
On Windows:
- Open File Explorer and right-click This PC.
- Choose Add a network location, then Next twice.
- Enter the address as
ftp://ftp.example.com. - Untick Log on anonymously and enter your username.
- Give the location a name and finish. It appears under This PC.
On macOS:
- In Finder, choose Go → Connect to Server (
Cmd+K). - Enter
ftp://ftp.example.comand click Connect. - Enter your credentials.
⚠️ Two limitations to know. Windows FTP network locations are read-only in practice for many servers — you can browse and copy out, but uploading often fails. And macOS mounts FTP volumes read-only by design. For actual file management, a dedicated client is more reliable than a mapped location.
For SFTP, neither system supports it natively as a network location — you need a client, or a tool like WinFsp with SSHFS on Windows or Mountain Duck on macOS.
What FTP sites are used for
Publishing a website. The original use case, and still common on shared hosting: upload your files to public_html and they’re live.
Transferring large files. FTP handles multi-gigabyte transfers and resumes interrupted ones, which is why it survived in media and print workflows.
Bulk transfers. Moving thousands of files at once is where FTP still outperforms a browser upload form.
Backups. Some backup tools push archives to an FTP destination, and many NAS devices support FTP as a target.
Public archives. Historically, anonymous FTP distributed software and documents. Most of these have moved to HTTPS, but some university and government archives still run FTP servers.
Common FTP problems
Connection times out or hangs after login. Almost always active vs passive mode. Switch your client to passive, which is what works through firewalls and NAT.
“530 Login incorrect.” The credentials are wrong, or the account is FTP-disabled. Note that hosting FTP usernames often include the domain — the format is typically user followed by @ and your domain name, rather than just user.
Files upload but the site doesn’t change. They went to the wrong directory. Check you’re in public_html and not one level above it.
Permission denied on upload. The directory permissions don’t allow writing. Our guide on Linux file permissions covers what the numbers mean.
Transfer corrupts the file. FTP has ASCII and binary transfer modes, and sending an image or archive in ASCII mode corrupts it. Set the client to binary or auto.
Frequently asked questions
What is an FTP site?
A server connected to the internet running FTP software on port 21, which accepts file transfers. You connect with a username and password, see a directory listing, and move files in either direction. It isn’t a website — there’s no page to view, just a filesystem exposed over the network.
Can I open an FTP site in a browser?
No, not in a modern one. Chrome removed FTP support in version 88 (January 2021) and Firefox in version 90 (July 2021). You need a dedicated client like FileZilla, WinSCP or Cyberduck, or your host’s web-based file manager.
Is FTP still used in 2026?
Yes, but mostly for legacy reasons. Hosting providers still offer it for compatibility, and it persists in workflows built around it. New setups should use SFTP, which encrypts the connection and works better through firewalls.
Is FTP secure?
No. FTP sends the username, password and file contents in plain text, so anyone able to observe the connection can read all of it. Use SFTP (port 22) or FTPS instead — both encrypt the session.
What’s the difference between FTP and SFTP?
FTP is unencrypted and uses two connections on port 21. SFTP runs over SSH on port 22, uses a single encrypted connection, and passes through firewalls far more easily. Despite the names, they’re unrelated protocols — SFTP is part of SSH and shares no code with FTP.
What is an FTP location?
Usually it means one of two things: the address of an FTP site (ftp.example.com), or an FTP site added to your file manager as a network location so it behaves like a folder. Windows supports the second through “Add a network location”, though uploads through it often fail — a dedicated client is more reliable.
What port does an FTP site use?
Port 21 for the control connection, with a separate data connection on a port negotiated during the session. SFTP uses port 22, and FTPS typically 990. Our guide on common TCP ports covers where each sits.
Why does my FTP connection hang after logging in?
Active versus passive mode. In active mode the server opens a connection back to your machine, which firewalls and NAT block. Switch your client to passive mode — it’s the default in modern clients precisely because it works through firewalls.
Where do I upload my website files?
Into public_html in most cases, or www or htdocs depending on the server. Files placed in the parent directory won’t be served. If your uploads succeed but the site doesn’t change, wrong directory is the first thing to check.
What is anonymous FTP?
An FTP site configured to accept the username anonymous with any password, historically how public software archives were distributed. It’s rare now — most public files moved to HTTPS — but some university and government archives still run it.
Copahost hosting includes SFTP and SSH access on every plan, plus a web-based file manager for when you just need to move one file. Free SSL, LiteSpeed servers with NVMe storage, and free migration from your current host.
See hosting plansConclusion
An FTP site is a server that accepts file transfers — a filesystem you reach over the network with a username and password. For thirty years it was how websites got published, and on shared hosting it still works exactly as it always did.
But the honest summary in 2026 is that FTP is legacy. Browsers dropped support in 2021, and the protocol sends your password in plain text. Everything FTP does, SFTP does encrypted, over a single connection, on port 22 — and if your host gives you SSH access, you already have it.
So the practical advice is short. Connecting to someone else’s FTP site: use FileZilla or WinSCP, and switch to passive mode if it hangs. Setting up your own file transfers: use SFTP and don’t look back. And for a single file, your host’s web file manager is faster than either.
