The File Transfer Protocol, often shortened to FTP, is a network protocol in the application layer of the TCP/IP model. Its main job is to let files move between two computers on a network, typically a client and a server. It started in the early 1970s within US research networks and was standardized over time by the Internet Engineering Task Force. It is still one of the best-known ways to exchange documents on the Internet.
Technically, FTP uses a client-server architecture and relies on two separate connections: one for commands and one for data. This sets it apart from many other protocols and explains both its flexibility and some configuration headaches, especially when traffic passes through firewalls and address translation devices. In everyday use FTP has largely been joined or replaced by safer options, but it remains a conceptual reference for understanding how files move across a network.
From ARPANET origins to IETF standards
The first FTP specifications date back to work on ARPANET, when the need to transfer files between different computers became a practical requirement. Over the years the protocol was revised and refined several times, leading to a widely used version documented in the requests for comments published by the Internet Engineering Task Force. These publications, known as RFCs, are the reference source for anyone who wants to understand how the protocol works in detail.
Over time, extensions were added that broadened its capabilities, adding features such as resuming an interrupted transfer or negotiating additional parameters. Despite its age, FTP is still supported by operating systems, applications and network devices of all kinds, which shows its solid design and ease of use.
The two channels a session runs on
FTP works through two separate channels. The first, called the control channel, is opened by the client to a well-known port on the server and is used to exchange commands and their replies. The second, called the data channel, is only activated when a file or directory listing actually needs to be transferred. This separation keeps a stable command session while data travels over a dedicated connection.
There are two main ways the data channel can work. In active mode the server establishes the connection to the client, while in passive mode the client connects to the server. The choice between the two depends on the network configuration and on firewalls, which often make passive mode preferable.
When passive mode is needed
Active mode reflects the original design of the protocol, but it can be problematic when the client sits behind a firewall or a device that blocks incoming connections. Passive mode was introduced precisely to overcome these obstacles, having the client open all the necessary connections. Understanding the difference between the two is essential for diagnosing the most common transfer problems.
Binary or text: which to choose
FTP supports several data representation modes. Binary mode transfers bytes without any interpretation and is suitable for images, compressed archives and executables. Text mode, on the other hand, performs conversions related to the different end-of-line formats of operating systems. Choosing the right mode prevents corruption of the transferred files.
Why FTP isn’t encrypted and what changes with FTPS and SFTP
The main limitation of FTP is the lack of encryption: credentials and content travel in clear text over the network and can be intercepted by anyone with access to the traffic. To address this, variants were developed that add a layer of protection via TLS, known as FTPS, or alternative protocols such as SFTP, which rely on SSH. These solutions provide confidentiality and data integrity at the cost of more complex configuration.
Another aspect to consider is the management of credentials and permissions. Many FTP servers allow anonymous access, which is useful for public file distribution but potentially risky if not configured carefully. Setting up directories, permissions and space quotas correctly is therefore part of responsible service management.
Anonymous access and the risks of abuse
Anonymous access lets unregistered users download files from a limited portion of the server. It is a historically common mode for distributing software and documentation, but it requires careful controls to prevent abuse.
FTPS and SFTP: what they add
The secure variants of the protocol add encryption to the control channel, the data channel or both. They keep the basic structure of FTP but require that client and server support the relevant security extensions.
FTP, SFTP and cloud compared
To understand FTP’s role, it helps to compare it with the most common alternatives. The table below summarizes the main differences in terms of security, connection type and typical use.
| Method | Encryption | Connection type | Typical use |
|---|---|---|---|
| FTP | None | Two separate channels | File exchange on controlled networks |
| FTPS | Via TLS | Two separate channels | Transfers that require protection |
| SFTP | Via SSH | Single channel | Secure server administration |
| HTTP | Varies | Single channel | Publishing and viewing content |
| Varies | Single channel | Sending small attachments |
The sequence of a session, step by step
An FTP session usually follows an ordered sequence of steps. Knowing this sequence helps you interpret error messages and configure client and server correctly.
- Opening the control connection to the server on the dedicated port.
- Sending credentials or logging in anonymously.
- Choosing the transfer mode, binary or text.
- Setting active or passive mode for the data channel.
- Navigating the directory structure using the dedicated commands.
- Starting the transfer of a file, either upload or download.
- Checking the result and repeating the operation for other files.
- Closing the session and releasing resources on the server.
Frequently asked questions
What does FTP stand for?
FTP stands for File Transfer Protocol. It refers both to the network protocol and to the service that uses it to exchange documents between computers.
Is FTP still used today?
Yes, FTP is still common in controlled environments, such as internal corporate networks or device updates. However, for transfers over the Internet, secure variants or other protocols are often preferred.
What is the difference between FTP and SFTP?
SFTP is not a simple extension of FTP but a distinct protocol that relies on SSH. Unlike FTP, SFTP encrypts the entire communication and uses a single channel.
Why is FTP considered insecure?
Because it doesn’t provide encryption: username, password and content travel in clear text. Anyone intercepting the traffic can read or modify them without much difficulty.
What are active and passive mode?
They are two ways of handling the data channel. In active mode the connection is opened by the server, in passive mode by the client. The choice depends on the network configuration.
Can I use FTP without installing additional programs?
Many operating systems and browsers include basic FTP functions, but for full use dedicated clients are recommended. These offer session management, transfer resumption and support for secure variants.
From the glossary to the projectIs your site built to be fast, secure and optimized for search?Website and e-commerce development takes speed, security and SEO into account from the start, with custom WordPress builds.Discover website development
Related entries:
Client-server Client Server Web server Model Context Protocol