SFTP
SFTP (SSH File Transfer Protocol) is a protocol for securely transferring and managing files within an encrypted SSH connection. It lets you not only upload and download files but also browse, rename, delete and set permissions on them — all over a single encrypted channel on port 22. Despite the similar name, it is not an extension of classic FTP but a separate protocol built on top of SSH.
How SFTP works
SFTP relies on SSH mechanisms to establish and protect the session:
- the client connects to the SSH server and authenticates — by password or, more securely, with an SSH key,
- once the encrypted tunnel is up, the SFTP subsystem is started,
- commands and data (transfers, directory listings, permission changes) all flow through that single encrypted channel.
Because the entire exchange is encrypted, neither the login, nor the password, nor the transferred files are exposed to interception in transit — unlike plaintext FTP.
SFTP in practice
SFTP is the standard for securely uploading files to a server: deploying websites, publishing application files, moving backups, or exchanging data between systems. It is used through clients such as FileZilla and WinSCP — the latter often paired with PuTTY — as well as from the command line (sftp user@host). On modern hosting and VPS servers, SFTP is the default, recommended way to access files, replacing outdated, unencrypted FTP wherever transmission security matters.
Powiązane pojęcia
Najczęstsze pytania
How does SFTP differ from FTP?
SFTP encrypts the whole session and moves data inside an SSH connection on port 22, whereas plain FTP sends the login, password and files in cleartext. That means SFTP is secure by default, while FTP exposes data to interception.
Are SFTP and FTPS the same thing?
No. SFTP is a protocol built on SSH, while FTPS is classic FTP with an added TLS encryption layer. They differ in architecture, ports and authentication, even though both provide transmission confidentiality.
