qBittorrent Best Settings 2026: Defaults, What to Change and What to Skip

The best qBittorrent settings are mostly its defaults: DHT, PeX and local peer discovery on, 500 global connections, no speed limits. What actually changes your speed is a reachable listening port, an upload cap that is not too low, a few active downloads at a time, and disk settings that suit your drive.

The defaults and menu labels below were checked against qBittorrent 5.2.4 on October 3, 2026. Numbers such as 500 connections and DHT on are already the defaults, so the cheat sheet puts the real default next to every recommendation. Version note (rechecked November 9, 2026): qBittorrent 5.3.0 came out on October 19, 2026, and it changes which engine you get. Its default Windows installer now uses libtorrent 2.1, and a separate “lt12” installer keeps libtorrent 1.2. The project’s release note warns that 2.1 has worse read performance than 1.2, which can cut upload speed, so heavy seeders may want the lt12 build. On 5.2.4 the default was libtorrent 1.2 and “lt20” was the 2.0 option. The build you run changes some Advanced-tab options (see the Advanced tab section). The current downloads need Windows 10 or later, or macOS 13 or later. On macOS, the official download was still 5.2.3 on November 9, 2026, and the project describes the Mac version as barely supported.

In a hurry? Jump to: cheat sheet · open the port · slow speeds · Advanced tab · SSD, HDD or NAS · seeding · anonymous mode · VPN binding · export settings · Android

qBittorrent settings cheat sheet: default, recommended value and why

Open the settings with Tools > Options (Alt+O) on Windows, Tools > Preferences on Linux, or qBittorrent > Preferences on macOS. Where this guide says Options, read Preferences on Linux and macOS. In 5.2.4 the tabs are Behavior, Downloads, Connection, Speed, BitTorrent, Search, RSS, WebUI and Advanced. “Leave” below means the default is already the right choice for most people. Some tips in older guides no longer match 5.2.4, and they are flagged where they come up.

Setting (tab)	Default in 5.2.4	Set it to	Why
Listening port (Connection)	Random, 1024-65535	A forwarded port, or leave UPnP on	Reachability matters, not the number
UPnP / NAT-PMP (Connection)	On	Leave on	Off if you forward by hand or use a VPN port
Peer connection protocol (Connection)	TCP and µTP	Leave	One protocol means fewer peers
Connections, global / per torrent (Connection)	500 / 100	Leave	Already the defaults
Upload slots, global / per torrent (Connection)	20 / 4	Leave	Peers you upload to at once
Download limit (Speed)	Unlimited	Leave	Cap only to free bandwidth for other uses
Upload limit (Speed)	Unlimited	Unlimited, or just under your line speed	Very low caps can slow downloads
Alternative limits (Speed)	10 / 10 KiB/s, schedule off	Set real numbers first	Pinned near 10 KiB/s? Check this
DHT, PeX, LSD (BitTorrent)	All on	Leave on	Skipped automatically for private torrents
Encryption mode (BitTorrent)	Allow encryption	Leave	“Require” shrinks your peer pool
Anonymous mode (BitTorrent)	Off	Off, or on with a VPN	Limits client details, not your IP
Torrent Queueing (BitTorrent)	Off (3 / 3 / 5 once on)	On, 3 to 5 active downloads	Many torrents split your bandwidth
Seeding limits (BitTorrent)	None	Leave, or set a ratio or time	Default action: Stop torrent
Pre-allocate disk space (Downloads)	Off	HDD: optional. SSD: skip	Less fragmentation, slower start
Incomplete torrents path (Downloads)	Off	Optional: your fastest drive	Moved to the save path when done
Network interface (Advanced)	Any interface	VPN adapter, if you use a VPN	Transfers stop if the VPN drops

• Upload limit. The BitTorrent protocol specification (BEP 3) describes choking as tit-for-tat-ish: clients favor peers that upload to them. A very low upload cap can therefore cost download speed on an unfinished torrent. If uploads disrupt other devices, cap just under your real upload speed rather than far below it.
• Alternative limits. The speed-limit button in the status bar switches between the normal and alternative limits, so a transfer pinned near 10 KiB/s often means the alternative limits are on.
• DHT, PeX and LSD. qBittorrent disables all three for private torrents by itself (project FAQ), so there is no need to switch them off. The Trackers tab shows them as Disabled.
• Encryption. “Require encryption” connects only to peers that support it. There is no “Prefer encryption” option in 5.2.4, and protocol encryption is obfuscation, not anonymity.
• Pre-allocation. libtorrent says full allocation minimizes fragmentation but can be costly; sparse files are its default.

How do I open the port and fix the yellow “firewalled” icon?

The connection icon in the status bar has three states, and they come straight from qBittorrent’s own code. Green (Online) means at least one peer has connected to you. Yellow means no peer has made a direct connection to you yet. Red (Offline) usually means qBittorrent could not listen on the selected port. Yellow does not prove the port is closed: libtorrent sets the flag only when the first incoming connection arrives, so a new or idle client can stay yellow even with a working forward.

1. Open the Connection tab. Leave Use UPnP / NAT-PMP port forwarding from my router ticked, or untick it if you forward manually.
2. For a manual forward, pick any free port (the project’s options page just says to specify a port or choose a random one), enter it under Port used for incoming connections, and forward the same number for both TCP and UDP to the PC running qBittorrent. libtorrent listens for TCP on that port and uses a UDP socket on it for µTP and DHT.
3. Click Apply, allow qBittorrent through your PC’s firewall if prompted, and start a popular torrent so peers have something to connect to.
4. Check the icon. qBittorrent has no built-in port test (older tips mention a Test button, but 5.2.4 has only a Random button), so an online TCP port checker, run while qBittorrent is open, is how you confirm from outside.

Two cases UPnP cannot fix. If your ISP puts you behind carrier-grade NAT (your router’s WAN address differs from the public address you see online), no forward on your router will work. And on a VPN, UPnP only talks to your home router, so you need a provider that offers port forwarding and then enter the port it assigns you.

How to tell if you are behind carrier-grade NAT or double NAT. Open your router’s status page and note the WAN (Internet) IP address, then compare it with the address any “what is my IP” page shows. If they differ, or the WAN address starts with 100.64 through 100.127 (the range reserved for carrier-grade NAT) or sits in a private range (10.x, 172.16 to 172.31, 192.168.x), a forward on your own router cannot work. Your options are to ask your ISP for a public IP address, to put the ISP’s gateway into bridge mode if you run your own router behind it (double NAT), or to use a VPN that offers port forwarding. Without any of these, qBittorrent still downloads; it just reaches only peers that accept incoming connections, so speeds are often lower.

Why is qBittorrent so slow? Symptom-by-symptom fixes

No setting can speed up a torrent with few seeders, so check that first. Then match what you see to the table.

Check the units first. Internet plans are sold in megabits per second (Mbps), but qBittorrent shows bytes per second (KiB/s and MiB/s). One MiB/s is about 8.4 Mbps, so a 100 Mbps line tops out near 12 MiB/s and a 500 Mbps line near 60 MiB/s before protocol overhead. A reading of “only 11 MiB/s” on a 100 Mbps plan is the line running flat out, not a bad setting.

What you see	Likely cause	Fix
Speed stuck near 10 KiB/s	Alternative limits are on	Click the status-bar speed-limit button
“Stalled” at 0 B/s	No reachable peer has the data	Check trackers and seeds; try another torrent
Yellow status icon	Peers may not reach you	Open the port (steps above)
Red “Offline” icon	Cannot listen on the port	Change the port; check Network interface
Slow with many torrents	Bandwidth split too thin	Queue 3 to 5 active downloads
“Queued” and not seeding	Queue limits reached	Raise active uploads, or Force start
Disk at 100%, speed swings	The drive cannot keep up	Fewer active downloads; see storage below
Huge RAM figure (libtorrent 2.0)	Memory-mapped file I/O	Try POSIX or pread/pwrite disk IO
Calls or games lag	Upload fills your line	Cap upload just under line speed
Nothing moves after VPN reconnect	Bound adapter changed	Re-select it, restart qBittorrent

• Stalled means the torrent is active but nothing is arriving right now, usually because no reachable peer has the data. No setting revives a dead swarm.
• Queued torrents are held back by the queueing limits. Right-click a torrent and choose Force start to bypass them for that torrent.
• Disk at 100%. On Windows with poor throughput, the project FAQ also points at the drive’s MSI mode. That is a driver-level change, so read the FAQ before trying it.
• Large RAM figure. libtorrent 2.0’s memory-mapped file I/O can make the process’s memory look huge, and some users have reported out-of-memory crashes. Set Disk IO type to POSIX-compliant or Simple pread/pwrite and restart. On Windows, the RAM usage limit (default 512 MiB) also applies.
• VPN reconnects. If qBittorrent is bound to the VPN adapter, re-select the adapter under Advanced > Network interface after it changes, then restart qBittorrent.

The alternative limits sit under the global limits on the Speed tab. The numbers in this screenshot are example values, not recommendations.

qBittorrent Advanced tab: the settings worth knowing

libtorrent’s own tuning guide says its defaults suit an end-user client on a normal desktop computer, so change one Advanced setting at a time, and only to fix a specific problem. The rows you see depend on the libtorrent build you installed. Check it under Help > About qBittorrent > Software Used (on macOS, the qBittorrent menu > About):

• libtorrent 1.2.x (the default installer for 5.2.4 and the “lt12” installer for 5.3.0, version 1.2.20) keeps libtorrent’s own disk cache, so Advanced shows Disk cache (auto by default) and Disk cache expiry interval (60 s).
• libtorrent 2.0.x (the “lt20” installer for 5.2.x, version 2.0.15) hands caching to the operating system through memory-mapped files, per libtorrent’s 2.0 upgrade notes. The two disk-cache rows disappear (so tips to “set the disk cache” only apply to 1.2 builds), and Disk IO type, Hashing threads and, on Windows only, Physical memory (RAM) usage limit appear. Since 5.3.0 the default Windows build uses libtorrent 2.1.2. The project says 2.1 should have fewer I/O problems than 2.0, so if you upgraded from an lt20 build, check Help > About and your Advanced tab before copying any older tip.

Setting	Build	Default in 5.2.4	Suggestion
Network interface	All	Any interface	VPN adapter, if you use a VPN
Disk queue size	All	1,024 KiB	32,768-102,400 KiB on fast lines
Disk IO type (restart)	lt 2.0+	Default (memory-mapped)	POSIX or pread/pwrite for a NAS
RAM usage limit	lt 2.0+, Windows	512 MiB	Leave unless memory or stalls
Hashing threads	lt 2.0+	1	Leave; 1 suits hard drives
Disk cache / expiry	lt 1.2 only	Auto / 60 s	Leave
Asynchronous I/O threads	All	10	Leave
File pool size	All	100	Leave
µTP-TCP mixed mode	All	Prefer TCP	Leave
Upload choking algorithm	All	Fastest upload	Leave

• Disk queue size. libtorrent’s docs warn that a value set too low severely limits download rate, and libtorrent 2.1 raised its own default from 1 MiB to 100 MiB (the 5.3.0 release candidate’s libtorrent 2.1 builds follow). The 32,768 to 102,400 KiB range is a suggestion for fast connections. The cost is RAM, up to that amount.
• Disk IO type. Default means memory-mapped files where the system supports them. Leave it for local drives. For a NAS or network share, or if memory use is the problem, try POSIX-compliant or Simple pread/pwrite.
• RAM usage limit. This is a hard cap on the process’s working set, which includes memory-mapped file pages. Change it only to fix a memory or stall problem; there is no documented best value. It was removed on macOS in 4.6.1 and on Linux in 5.2.0.
• Hashing threads. Only used for full rechecks. libtorrent advises 1 on hard drives.
• File pool size. libtorrent keeps files open because antivirus hooks make opening and closing them costly. Raise it only if you seed thousands of files.
• µTP-TCP mixed mode. libtorrent’s tuning notes say Prefer TCP stops TCP being throttled, so on a home line TCP can crowd out µTP. If torrenting makes other traffic lag, cap upload first.
• Upload choking algorithm. Round-robin spreads upload evenly across peers, and Anti-leech favors peers that have just started or are nearly finished.

One trap: the project wiki’s page on options still lists some older defaults, such as a file pool size of 5000 and a resume-data interval of 3 minutes. The 5.2.4 source code uses 100 and 60 minutes, and this guide follows the code.

Best qBittorrent settings for an SSD, HDD or NAS

On a fast connection, disk speed rather than bandwidth is often the limit. Match the settings to where the files are written.

Local SSD or NVMe

• Leave Disk IO type on Default and skip pre-allocation.
• On a very fast line, raise Disk queue size.
• On a libtorrent 2.0+ build, try more Hashing threads if full rechecks are slow.
• Why: libtorrent’s docs say memory-mapped I/O likely performs best on a local SSD.

Internal hard drive

• Turn on Torrent Queueing with 2 to 3 active downloads, and leave Hashing threads at 1.
• Consider pre-allocating disk space. It reduces fragmentation but can be slow to start.
• If you also have an SSD, point “Use another path for incomplete torrents” at it so unfinished data lands there.
• Why: libtorrent describes hard drives as storage optimal for sequential access and advises a single hashing thread.

NAS or network share

• On a libtorrent 2.0+ build, choose POSIX-compliant or Simple pread/pwrite as the Disk IO type.
• Better still, run qBittorrent on the NAS itself and use the WebUI, or download to a local drive and move finished files.
• Why: libtorrent says memory-mapped writes to NAS, NFS or network shares are most likely inferior. The pull request that added Simple pread/pwrite in 5.0.1 cites memory-mapped problems, including slower performance on network drives.

Does qBittorrent seed automatically? Best settings for seeding and upload

Yes, by default. A fresh install has no ratio or seeding-time limit, so a finished torrent keeps uploading until you stop or remove it. The settings that matter for seeding:

• A reachable port and an open upload limit. More peers can connect to you, and nothing caps what you send. If uploads disrupt other devices, cap just under your real upload speed.
• Maximum active uploads. This only applies with Torrent Queueing on. The default is 3, and seeds beyond it wait in the queue, so raise it (and Maximum active torrents) if you seed a lot. Ticking “Do not count slow torrents” stops idle torrents from taking slots.
• Seeding Limits. Under Options > BitTorrent, set a ratio, total seeding time or inactive seeding time, then choose Stop torrent, Remove torrent, Remove torrent and its files, or Enable super seeding. Version 5.2 added limits per category. Private trackers set their own minimums.

What does qBittorrent anonymous mode do?

Anonymous mode (Options > BitTorrent > Privacy) is off by default. In 5.2.4 it tells libtorrent to try to hide your client’s identity in four ways, according to libtorrent’s documentation:

• it uses a generic user-agent with trackers, except for private torrents;
• it does not send your local IPv4 and IPv6 addresses to private trackers;
• it does not send a configured announce IP address to trackers; and
• it does not send your client version to peers in the extension handshake.

What it does not do: hide your IP address from the peers you exchange data with, make anything faster, or replace a VPN. qBittorrent’s own wiki warns that it gives no strong privacy guarantees on its own, and says that if you already use a VPN, proxy or I2P you probably want it on. Private trackers set their own rules about clients, so check yours before enabling it there. Very old builds (2.9 to 3.2.5 with libtorrent below 1.0) also switched off DHT, local peer discovery and UPnP in this mode; that is not the case in 5.x. To confirm it is active, open View > Log > Show and look for “Anonymous mode: ON” in the Execution Log.

How do I bind qBittorrent to a VPN?

A VPN changes which IP address peers see; it does not change what is legal to download. Binding makes qBittorrent use only the VPN’s network adapter, so transfers stop if the VPN drops. The qBittorrent wiki recommends this as an extra layer on top of a VPN’s own kill switch.

1. Connect your VPN first so its adapter appears (on Windows 11 the wiki suggests finding its name under “View network connections”).
2. Open the settings, go to Advanced, and set Network interface to the VPN adapter.
3. Click Apply and restart qBittorrent.
4. Optional check: tick Show external IP in status bar under Behavior (added in 5.1.0). With a working VPN it should show the VPN’s address, not your ISP’s. It is a sanity check, not a leak test.

If you still need a VPN, check the provider’s peer-to-peer policy and whether it offers port forwarding before you pay; our VPN app roundup covers the general picture.

Is qBittorrent legal and safe?

The software is legal, free and open source (GPLv2), and the project’s FAQ says it contains no malware, spyware or advertisements. What you download is a separate question: sharing copyrighted material without permission can be infringement in the US and most other countries, while Linux installers, public-domain works and files whose creators distribute them by torrent are fine. Download qBittorrent only from the official site, qbittorrent.org. Its news page warns that third parties upload rip-offs of the code wrapped in ads and monetization schemes, and says the project does not distribute qBittorrent through the Microsoft Store (warning dated June 15, 2026).

Where does qBittorrent store its settings, and can you export them?

qBittorrent keeps its settings in a plain config file, and the Options window has no export button. To back up or move your setup, close qBittorrent and copy both folders for your system: the settings folder and the data folder (torrent list, resume data and logs).

• Windows: settings in %APPDATA%\qBittorrent (qBittorrent.ini); data in %LOCALAPPDATA%\qBittorrent.
• Linux: settings in ~/.config/qBittorrent/ (qBittorrent.conf); data in ~/.local/share/qBittorrent/.
• macOS: settings in ~/.config/qBittorrent/ (qBittorrent.ini); data in ~/Library/Application Support/qBittorrent.
• Linux Flatpak: settings in ~/.var/app/org.qbittorrent.qBittorrent/config/qBittorrent/; data in ~/.var/app/org.qbittorrent.qBittorrent/data/qBittorrent/.

On the new machine, install the same or a newer version and paste both folders into the same places. Then check your save paths, because any path that does not exist on the new machine will not work. To reset qBittorrent to defaults, delete the files in the settings folder. For a portable setup on Windows, create a folder named profile next to qbittorrent.exe; on Linux, start it with --profile=<folder> (portable mode needs 4.2.1 or later). Keep a copy of both folders in whatever backup service you already use.

Is there a qBittorrent app for Android?

No. The official download page, checked on October 3, 2026, lists Windows, macOS and Linux builds, plus packages for FreeBSD, Haiku, OS/2 and many Linux distributions, and nothing for Android. There are two practical options.

• Control qBittorrent on a PC or NAS from your phone. Turn on Options > WebUI and open its address in your phone’s browser (default port 8080, username admin). Set a password first: since 4.6.1 there is no default one. Version 5.2.0 added several mobile fixes to the WebUI. Keep it on your home network, or reach it through a VPN, rather than exposing it to the internet. The Android remote app listed on the project’s wiki, qBittorrent Controller, is archived (last code update January 2022) and was no longer on Google Play when checked, so skip it.
• Torrent on the phone itself. Use a separate Android client. LibreTorrent (open source) and BiglyBT (ad-free, open source) were both live on Google Play on October 3, 2026. Their settings differ from qBittorrent’s, so nothing in this guide applies to them.

Where these recommendations come from

This guide is a research summary, not a lab report. No speed measurements were taken, so it makes no promise about how many MB/s any change adds. On October 3, 2026 we did the following:

• Read each default and menu label quoted here from the qBittorrent 5.2.4 source code (session defaults, Options dialog and Advanced-tab definitions), and compared the defaults with the 5.3.0 release-candidate code for changes. On November 9, 2026 we rechecked the download and news pages after the final 5.3.0 release.
• Took version, build and libtorrent details from the project’s download page, news page and changelog.
• Used the project wiki (options, anonymous mode, FAQ, VPN binding, portable mode) for behavior and file locations. Where the wiki lists older defaults than the code, the code won.
• Used libtorrent’s reference, tuning guide and 2.0 upgrade notes, and the BitTorrent protocol specification (BEP 3), for what the engine settings do.
• Checked the Android apps named here on Google Play and, for qBittorrent Controller, its code repository.

The screenshots come from a qBittorrent 5.0 beta on macOS; the labels they show match the 5.2.4 source. Anything that is a suggestion rather than a documented default or behavior is worded as one, and tips from older versions of this guide that these sources could not back up were removed.

The five settings that matter most

Leave the connection limits, DHT/PeX/LSD and encryption on their defaults. Make sure your port is reachable, keep upload limits off or just under your line speed, queue 3 to 5 active downloads, bind to your VPN adapter if you use one, and touch the Advanced disk settings only if your drive or NAS is the bottleneck. Check which libtorrent build you have under Help > About before following any Advanced-tab advice, because 5.3.0 made libtorrent 2.1 the default Windows build on October 19, 2026.