Transfer files with SFTP or encrypted FTP
Use SFTP where your plan provides SSH file transfer, or supported FTPS with TLS. SFTP and FTPS are different protocols, and an FTP account is not automatically an SSH/SFTP account.
Before you begin
Get the protocol, hostname, port and permitted username from your hosting details or support. Use a client that supports the required encryption. Keep a verified backup before replacing live files.
Steps
- For FTP/FTPS, open FTP Management in the panel and create a separate account if needed. Limit its directory to the files it needs and choose a unique password.
- For SFTP, confirm which SSH account and directory restrictions your plan supports. Do not assume an FTP password or folder restriction also applies to SSH.
- Configure the client with the exact protocol, server, port and account details. For FTPS require TLS; do not accept a downgrade to plain FTP.
- Verify the server certificate or SSH host-key fingerprint through a trusted source before accepting it. Stop on an unexpected change.
- Upload a harmless test file into the intended directory, verify its contents and permissions, then remove the test file.
- Deploy only the website’s public files to the document root. Keep private environment files, backups and source-control directories outside it.
SFTP command example
sftp -P 22 username@server-addressThe sample uses SSH port 22. Replace the port, username and address with the confirmed SFTP details. If your plan has no supported encrypted file-transfer service, use the panel’s HTTPS File Manager or ask support for a secure transfer method.
If something goes wrong
Authentication failures need a username/protocol check, not disabled encryption. An FTPS directory-listing timeout can involve passive data ports; ask support for the correct server-side configuration instead of opening arbitrary client or server ports.
Related articles
Last reviewed
2026-10-28