Great question! Even though SFTP feels clunkier with more intermediate steps compared to HTTPS, it still packs several practical advantages for single-file transfers—whether you're sending from client to server or pulling from server to client:

• Native, standardized file system controls
  Unlike HTTPS, which requires extra layers (like WebDAV or custom backend APIs) to handle file system tasks, SFTP comes built-in with commands to manage files post-transfer. For example, after uploading a single file, you can instantly adjust its permissions with chmod 755 myfile.txt, rename it, or delete old versions—all within the same session. HTTPS would need dedicated endpoints or additional tooling to do the same, adding unnecessary complexity for simple file workflows.

• Simpler, more secure authentication options
  SFTP natively supports SSH key pairs, which are far more convenient and secure than password-only auth for repeated transfers. If you're scripting single-file transfers (say, automated backups), SSH keys let you skip password prompts entirely without relying on short-lived tokens or OAuth setups (which are common in HTTPS-based transfers). Most servers already have SSH enabled, so you don't need to configure extra authentication layers just for file transfers.

• Consistent bidirectional transfer workflow
  With HTTPS, client-to-server transfers use PUT/POST requests, while server-to-client pulls use GET—these are separate operations that might require different endpoints or configurations. SFTP uses a single persistent connection for both directions: you can upload a file to the server, then immediately trigger a download of another file in the same session without re-authenticating or establishing a new connection. For server-initiated transfers (sending a file from server to client on demand), SFTP is more straightforward too—no need for webhooks or reverse proxies like you might with HTTPS.

• Out-of-the-box resumable transfers for large files
  While HTTPS can support resumable transfers with Range headers, this often requires backend server configuration and client-side support. SFTP has resumable transfers baked into the protocol. If your single large file transfer gets interrupted (e.g., network drop), most SFTP clients will automatically pick up where they left off without you having to re-upload or re-download the entire file. This is a huge time-saver for big single-file transfers like backups or media files.

• Minimal server setup for existing environments
  If your server already runs SSH (which is standard for most Linux/Unix servers), SFTP is ready to use with zero extra setup—just grant a user SSH access, and they can connect via SFTP. HTTPS, on the other hand, requires configuring a web server (Nginx, Apache), setting up SSL certificates, and often building or deploying an upload/download interface. For quick, one-off single-file transfers, SFTP is often the faster option to get up and running.

内容的提问来源于stack exchange，提问作者ahab