SFTP Performance: How to Make SFTP Transfers Faster

SFTP performance is rarely held back by your network. It is held back by the protocol's own defaults. SFTP — the Secure File Transfer Protocol, which moves files over an encrypted SSH connection — sends data in tiny 32 KB chunks, uses one connection per session, and waits for a reply before sending the next chunk. Picture mailing a big box one teaspoon at a time, and waiting for a thank-you note after each spoonful. That is why "SFTP is slow" is the universal complaint, and why the fix is almost always one of four settings, not a faster internet line.

The good news: most of the slowness is tunable. This guide walks through the four levers that actually move SFTP speed — buffer size, parallel connections, network latency, and where your data physically sits — and then the honest moment where the right answer is to stop tuning SFTP and use a transfer mode built for high volume. If you can pick your own protocol, a purpose-built transfer client delivers the same files over a faster path. If a partner requires SFTP, the four levers below are the ones to pull.

Increase the SFTP Buffer Size

The buffer is how much data SFTP sends in one go before it stops and waits for an acknowledgment. Most clients default to 32 KB, which was reasonable on a slow dial-up line and is far too small on a modern connection. Make the buffer bigger and you send more data per round-trip, so the transfer spends less time waiting and more time moving.

On the command line, the -B flag sets the buffer size in bytes. Bumping it from the default to 128 KB is a common first step:

sftp -B 128000 username@MYCOMPANY.files.com

In a graphical client, look for a setting named "buffer size" or "data chunk size" and raise it. Increasing it 4x to 32x over the default is usually safe and often the single biggest win.

Use Multiple Parallel Connections

A single SFTP session moves one file at a time over one connection. If you are transferring many files, that one lane is the bottleneck — the files line up and wait their turn. Opening several connections at once lets multiple files move in parallel, the way adding checkout lanes at a store clears the line faster.

In FileZilla, open Edit > Settings > Transfers and raise Maximum Simultaneous Transfers to somewhere between 10 and 25.

In Cyberduck, open Edit > Preferences > Transfers, set Transfer Files to "Open multiple connections," and then raise the connection count in the lower-right of the Window > Transfers panel.

A caution: more connections is not always better. Past a point you saturate the link or hit the server's connection limit, and throughput stops improving. Raise the number, watch your actual speed, and stop when it stops helping.

Reduce Network Latency

Latency is the round-trip delay between your computer and the server — the time it takes a packet to get there and a reply to come back. Because SFTP pauses for an acknowledgment on every chunk, high latency hurts it more than almost any other protocol: every chunk pays the full round-trip tax. Cutting latency is often the difference between a transfer that crawls and one that flies.

Three practical ways to lower it:

• Use a wired Ethernet connection instead of Wi-Fi. Wi-Fi adds delay and packet loss that SFTP feels on every chunk.
• Drop unnecessary VPNs and proxies. A VPN that routes your traffic through a distant city adds round-trip time to every packet. If you are in Europe transferring to a server in Europe, but your VPN exits in the United States, your data crosses the Atlantic twice for no reason.
• Connect to the closest server region. The shorter the physical distance, the lower the latency.

Pay Attention to Where Your Data Sits

When your storage spans multiple regions, where a given file physically lives changes how fast you can reach it. A file in a region near you transfers quickly; the same file in a region across the world is slow over SFTP no matter how you tune the client, because latency is set by distance.

Two things to watch:

• Reaching files across multiple regions? For cross-region work, a faster transfer client or API handles the optimization better than raw SFTP does.
• Using a custom domain? A custom domain is typically pinned to a single region. If you connect to it from another part of the world, every transfer pays that distance. As a quick test, try connecting to the standard app.files.com endpoint instead of your custom domain — if it is markedly faster, region distance was the culprit.

When to Stop Tuning and Switch Transfer Modes

There is a ceiling. SFTP's request-and-wait design means that past a certain file size or volume, no amount of buffer tuning closes the gap with a protocol built for bulk transfer. If you are routinely moving very large files or pushing high volume across regions, the four levers above will only take you so far.

At that point the move is to switch transfer modes for those workloads:

• A purpose-built desktop and CLI transfer client sends data over multiple parallel streams instead of SFTP's single lane, which is what makes it fast for large files.
• An API or SDK is the right tool for automated, high-volume transfers, because it can fan a job out across many connections without a human watching a progress bar.

Switching transfer modes does not mean abandoning SFTP. You keep the SFTP endpoint for the partners who require it and use the faster path for the workloads that need it.

Running SFTP on a Modern Platform

Most teams that keep fighting slow SFTP transfers eventually move off a single tuned server and onto one platform that does the whole job. Files.com is the cloud-native File Orchestration Platform: one platform that replaces the stack of legacy tools IT teams run to move files — SFTP and FTP servers, MFT suites, file-sharing apps, and the custom scripts holding them together. It speaks every protocol, connects to 50+ cloud and on-prem systems, automates every transfer, and keeps a complete audit trail. Speed is one half of secure file transfer; the other half is knowing every transfer arrived, and a platform gives you both without tuning a server by hand. When the job is large file transfer rather than many small files, the same platform resumes interrupted uploads and records the delivery.

For SFTP specifically, Files.com's managed SFTP service gives your partners the standard SFTP endpoint they already know, while you get a faster path for the workloads that need it — the Files.com Desktop App, CLI, and SDKs move data over multiple parallel streams, so a large transfer that would crawl over plain SFTP runs at full speed. The same endpoint can sit in front of storage you already own, every transfer is logged for audits, and a file arriving over SFTP can trigger an automated workflow on its own. If you want to understand the protocol itself first, our guide to how SFTP works covers the fundamentals. If you just want to mount an SFTP server as a drive on your Mac or Windows desktop, ExpanDrive does that.

To see the faster transfer path in practice, explore Files.com's managed FTP and SFTP or start a free trial — no credit card, live in minutes.