What qBittorrent’s “Allow outgoing connections when seeding” setting does
Learn what qBittorrent’s seeding outgoing connections setting controls, where to find it in 5.3, and why most seeders should leave it enabled.
Leave “Allow outgoing connections when seeding” enabled for ordinary BitTorrent sharing. Disabling it stops seeding and finished torrents from attempting outgoing peer connections; it does not mean “stop uploading.” The distinction is who starts the connection, not which direction the file data travels.
qBittorrent exposed this libtorrent setting in version 5.3.0, released October 19, 2026, with controls in both the desktop GUI and WebUI. The feature appears in the official release notes, and the merged implementation confirms both interfaces.
What “outgoing” means while seeding
An outgoing peer connection is one your client initiates. An incoming connection is one another peer initiates toward your client. Neither term determines whether you upload or download: the BitTorrent protocol specification describes peer connections as symmetrical, with data able to flow in either direction.
For example, after you finish downloading a Linux distribution you are permitted to share:
- Your seed can initiate a connection to a downloader and then upload pieces to it.
- A downloader can initiate a connection to your seed and receive those same pieces.
The checkbox controls the first route. According to libtorrent’s settings reference, seeding_outgoing_connections applies to seeding and finished torrents and defaults to true.
| Setting | Effect |
|---|---|
| Enabled | Seeding and finished torrents may attempt outgoing peer connections. |
| Disabled | Those torrents do not attempt outgoing peer connections. Incoming connections are not disabled by this switch. |
It is a session-wide preference, not a per-torrent upload rule. qBittorrent’s implementation also sets its own default to enabled.
Where to change it
In qBittorrent 5.3:
- Open Options/Preferences and select Advanced.
- Find Allow outgoing connections when seeding in the libtorrent settings, near Outgoing connections per second.
- Leave it checked for normal use, or uncheck it to prevent seeding torrents from initiating new peer connections.
- Apply or save your change.
The exact English label is present in the 5.3 desktop source and the built-in WebUI preferences. If it is absent, check the version of the client actually running—especially the server when using WebUI.
When disabling it makes sense
Libtorrent describes disabling this setting as useful in very specific applications where outgoing connection attempts are costly and offer little benefit. Its example is a network where no nodes are behind a firewall or NAT, so seeds need not initiate connections themselves. That is a specialized deployment, not a general speed recommendation.
For an ordinary home seed, disabling outgoing attempts removes one way to reach downloaders. If your listening port is also unreachable from outside, you cannot rely on new incoming connections to replace that route. This checkbox does not open a port or change your firewall; libtorrent documents listening interfaces and port mapping separately.
Before testing it disabled, verify inbound reachability. Then compare connected peers and uploaded bytes over equal-length periods on lawful torrents with actual downloader demand, keeping your other settings unchanged. Swarm demand can change between comparisons, and zero upload on an idle swarm proves little. Restore the checkbox if useful connections or uploads decline.
For a separate discussion of disk-read limitations and backend choice, see our qBittorrent 5.3 heavy-seeder build guide.
What this setting will not solve
It is not an upload-speed limit. Use upload rate limits if your aim is to reduce bandwidth use. The neighboring Outgoing connections per second instead controls the rate of connection attempts; libtorrent documents that setting separately as connection_speed.
It is not a privacy switch. It does not disable trackers, DHT or PEX, and peers that connect to you still communicate with your network endpoint. The protocol specification describes tracker peer lists containing addresses and ports, and peer handshakes identifying the torrent. Waiting for incoming connections does not make public-swarm participation anonymous.
It is not a stop-seeding control. To end sharing, stop the torrent rather than merely preventing it from initiating new peer connections. Download and seed only material you have the right to use and distribute.