FileZilla Multiple Connections: How to Set It, the 10-Transfer Limit, and What It Can’t Do

FileZilla multiple connections are set in two places: Edit → Settings… → Transfers → Maximum simultaneous transfers (1 to 10) for the whole program, and Site Manager → Transfer Settings → Limit number of simultaneous connections for one server. Ten is a hard ceiling, and each connection carries one file — FileZilla never splits a single file across connections. If you are pulling one 40 GB file from a seedbox, this setting changes nothing; a segmented client such as evoftp or lftp pget is what actually helps.

Where the setting lives

Global limit (all servers)

1. Open Edit → Settings… (macOS: FileZilla → Settings…).
2. Select Transfers in the left-hand list.
3. Set Maximum simultaneous transfers. The spinner accepts 1 to 10.
4. Optionally set Limit for concurrent downloads / uploads. These are sub-limits: with the maximum at 2 and the upload limit at 10, you still get 2.
5. Click OK. New queue items use the new limit.

Per-server limit (one site)

1. Open the Site Manager (File → Site Manager…, Ctrl+S / ⌘+S) and select or create the site.
2. Open the Transfer Settings tab.
3. Tick Limit number of simultaneous connections and enter a value in Maximum number of connections.
4. Connect through this Site Manager entry; Quickconnect ignores the per-site limit.

The global setting counts transfers, the per-site one counts connections; FileZilla keeps one connection purely for browsing, so a per-site limit of 3 means two transfers.

Why 1 stops you browsing

FileZilla runs several sessions: one lists directories, the rest move files. Set the limit to 1 and, in the wiki’s own words, “You cannot browse the server anymore while a transfer is in progress.”

The 421 “Too many connections” case

An FTP server that replies 421 Too many connections from this IP enforces a per-user cap smaller than what FileZilla opened. Set the per-site Maximum number of connections to the server’s cap (often 2 or 4) and reconnect through the Site Manager entry. 421 is an FTP code; an SFTP server refuses extra sessions by dropping the login instead, but the same per-site limit is the remedy.

Why 10 is the hard cap

You cannot go above 10 in the interface, and the project has declined to raise it for over fifteen years:

• FileZilla Pro knowledge base: “FileZilla/FileZilla Pro can run up to 10 file transfers – uploads or downloads – at a time.”
• Forum thread 51699 (2019), moderator boco: “No, 10 transfers per running FileZilla is max.” Lead developer Tim Kosse: “Not enough thought went into the limit. In hindsight I should have put a much lower limit.”
• Tracker ticket #5062, asking for 200, was opened in 2009 and rejected (“This limit is intentional. FTP has a high protocol overhead, using too many parallel connections can easily overwhelm servers.”), reopened, and rejected again in 2017.

The part that matters for a seedbox: files, not segments

“Maximum simultaneous transfers” is per-file parallelism. Ten connections means ten different files at once; one file always travels over exactly one connection, start to finish. The developers have said so for a decade:

• 2012, thread 24720 (“Segmented Downloads – Any Plans?”): “Never. There’s no need for it.”
• 2015, thread 35292: “FileZilla doesn’t use segmented transfers.”

So for the classic seedbox job — one 40 GB remux — the setting is nearly irrelevant. The file sits on a single TCP stream, and one stream from a distant server is capped by your round-trip time, not your line. The 24720 poster described it: a few MB/s with 10 threads in FileZilla, while a segmented client on the same route filled the connection. Ten small files fly; the one file you want does not. See why FileZilla downloads are slow for the full diagnosis.

What does help: a segmented client

A segmented client splits one file into ranges and pulls each range over its own SSH connection at the same time, writing them straight into place. Two options that work with any SFTP server:

evoftp (free, Windows / macOS / Linux)

1. Download it from neo.myseedbox.site/share/evoftp/. Portable build, no installer.
2. In the EvoSeedbox client area, open the Desktop app row, click Connection file, and double-click the .evoftp file. It connects with your SFTP details filled in.
3. Select the file in the right pane and press Download (Ctrl/⌘+D). The Balanced profile uses 4 segments per file, 3 files at once, 8 connections; on a long-distance route pick Long distance (8 segments, 16 MB in flight) or use Download ▾ to force 8 segments for one file.

Resume works through a .evoftp-part sidecar. It has no WebDAV or cloud storage, uploads are single-stream, and the macOS build is unsigned — the guide lists what it lacks.

lftp (command line; on every EvoSeedbox server and most Linux/macOS machines)

lftp -u USERNAME sftp://SERVER.myseedbox.site
pget -n 8 "Some.Large.File.mkv"
mirror --parallel=3 --use-pget-n=8 "Season 01"

pget -n 8 is eight segments on one file; mirror --use-pget-n does it for every file in a folder; -c continues an interrupted transfer. On Windows, run it under WSL. For FileZilla’s other tuning options see maximum transfer speed in FileZilla; for the technique itself, segmented download over SFTP.

Goal → setting → does it help?

FAQ

Does 10 connections get me banned from my seedbox?

No. Ten SFTP sessions from one client is normal; evoftp’s own profiles go up to 12. Bans on EvoSeedbox servers come from repeated failed logins, not from connection count. If FileZilla retries a wrong password across ten connections, that is what trips the ban — fix the credentials first.

Why is my seedbox limiting connections?

Most SSH servers cap how many sessions one login may open at once. If transfers fail above a certain count, drop the per-site limit to 4 to 6. If a single large file is still slow at any count, the limit is not the problem — the single stream is.

Does this apply to SFTP too?

Yes. Both settings apply to FTP, FTPS and SFTP alike, and the 10 ceiling is the same. Over SFTP each simultaneous transfer is a separate SSH login, so the per-file rule holds: ten files at once, never ten pieces of one file.

If your seedbox traffic is a few big files rather than thousands of small ones, leave FileZilla at its defaults and use evoftp for the downloads that matter. It is free, and it needs no setting at all.