FTP
ProtocolsFTP is a standard network protocol used to transfer files between a client and a server over TCP/IP. In web hosting, it is commonly used to upload website files, download backups, and manage directories on a hosting account. FTP typically relies on a username and password and can operate in active or passive mode, with optional encryption provided by related secure variants.
How It Works
FTP uses a client-server model: an FTP client (such as a desktop app or command-line tool) connects to an FTP server running on the hosting machine. After authentication, the client can list directories, upload and download files, rename items, and change permissions depending on the account rights. FTP separates control commands from file data transfers, which is why it may use multiple connections during a session.
FTP can run in active or passive mode, which affects how the data connection is established through firewalls and NAT. In active mode, the server initiates the data connection back to the client; in passive mode, the client initiates both control and data connections to the server, which is often more compatible with modern networks. Classic FTP is unencrypted, so credentials and file contents can be exposed unless a secure alternative is used.
Why It Matters for Web Hosting
FTP access is a practical capability to compare across hosting plans because it determines how you can deploy and maintain site files outside a control panel or CMS. When evaluating providers, look for support for secure file transfer, the ability to create multiple FTP accounts, clear directory restrictions (such as access limited to a specific site root), and compatibility with passive mode to avoid connection issues from corporate or home networks.
Common Use Cases
- Uploading website files (HTML, CSS, JavaScript, images) to the document root
- Deploying themes, plugins, or custom assets for CMS-based sites when the admin UI is unavailable
- Downloading logs or backups for troubleshooting and disaster recovery
- Editing configuration files (for example, .htaccess) when SSH access is not provided
- Managing multiple sites by using separate FTP accounts with restricted directories
FTP vs SFTP
FTP is the traditional file transfer protocol and is often available for compatibility, but it does not encrypt credentials or data by default. SFTP is a different protocol that runs over SSH and provides encryption and stronger security controls. For hosting decisions, prefer SFTP when possible, especially on public Wi-Fi or when transferring sensitive files, and use FTP only if it is wrapped in an encrypted option or limited to low-risk scenarios.