Switching to SFTP for secure file transfers

Traditional FTP (port 21) transmits data, including your account credentials, in plain text, making it vulnerable to interception. SFTP (SSH File Transfer Protocol) on port 22 encrypts both your password and your data in transit, protecting your website files and sensitive information from unauthorised access. 

While connection via port 21 remains possible, switching to SFTP is strongly recommended to ensure your file transfers are secure.

What you should know:

1. Update your FTP software to SFTP (Recommended)

We recommend updating your FTP software (such as FileZilla) to connect using SFTP on port 22 instead of FTP on port 21. Port 22 ensures your credentials and files are fully encrypted during transfer.

Follow these steps to connect using Filezilla: How to use FileZilla FTP

2. Update automated deployments, if applicable

If you use an automated deployment workflow, update it to use SSH keys on port 2222. 

3. Connecting via port 21 (FTP with TLS)

If you choose to continue using FTP on port 21, you will be prompted to accept an ‘unknown’ certificate upon connecting. This occurs because our server wildcard certificate provides TLS encryption for port 21, and your FTP client may not automatically recognise or trust it yet. You can safely proceed by accepting the certificate, though switching to SFTP on port 22 avoids this step altogether.

It is good practice to change your passwords regularly to prevent unauthorised access to your information.

Additional FTP information is available in our FTP Quick Guide.