Why qBittorrent Not Downloading? | Fix Stuck Torrents

qBittorrent can fail in a few different ways. A magnet may sit on “Downloading metadata.” A torrent may show “Stalled” forever. The speed meter may stay at 0 B/s even though the torrent looks active. Those clues matter. They point to different fixes, and guessing usually burns time.

Most download failures come from one of five places: the torrent has no live seeders, your app cannot accept incoming connections, a VPN or firewall is blocking traffic, your save path is broken, or qBittorrent is waiting in queue. Once you sort the symptom into the right bucket, the fix gets plain.

qBittorrent Not Downloading After You Add A Torrent

Start with the status line, not the speed graph. qBittorrent tells you where the process stopped. “Downloading metadata” points to peer discovery. “Stalled” can mean no active peers, a blocked port, or a hard speed cap. “Queued” means the torrent is waiting its turn. “Missing files” points to a folder or drive problem. “Errored” means qBittorrent tried to write data and failed.

One dead torrent can make a healthy app look broken. Public torrents rise and fall with the swarm. If seeders disappeared, no setting inside qBittorrent can create data out of thin air. Before you start changing settings, try one fresh torrent that you know has many seeders. If that one runs, your app is fine and the first torrent is the weak link.

Read The Clue You Already Have

• Downloading metadata: the magnet has not found enough live peers yet.
• Stalled: the torrent has no usable peers right now, or your app cannot reach them well.
• Queued: queue rules are holding it back.
• Missing files: the save folder moved, the drive is asleep, or the path is gone.
• Errored: disk space, permissions, antivirus, or a bad destination folder stopped writing.

Rule Out A Dead Swarm First

If your torrent shows zero or near-zero seeders, the problem may end right there. Magnets also need working trackers, DHT, PeX, or live peers to fetch the metadata. The qBittorrent FAQ explains how the client handles peer discovery and private torrents. If you have a private torrent, leave its own rules alone and read the tracker message column before changing anything.

A good test is simple: add one torrent from a busy Linux distribution or another lawful file with a large swarm. If that one starts, your network path works. If it also stalls, move to the next section.

Five Fixes To Try Before You Change Half The App

You can clear a lot of false alarms in five minutes.

1. Pause the torrent, wait a few seconds, then resume it.
2. Right-click the torrent and reannounce to the tracker.
3. Fully close qBittorrent, reopen it, and try again.
4. Test one known-healthy torrent so you can separate app trouble from swarm trouble.
5. Update the client from qBittorrent’s official download page if you are on an old build.

Do not change ten settings at once. One change, one test. That keeps you from fixing one issue and creating two more.

If none of those moves the needle, use the table below to match the symptom to the usual cause.

What You See	What It Usually Means	What To Do Next
Downloading metadata forever	Magnet cannot find enough live peers	Try a different torrent, reannounce, and check that DHT and trackers are not dead
Stalled with 0 seeds	The swarm is dead	Find a healthier torrent or wait for a seeder to return
Stalled on every torrent	Port, firewall, VPN, or queue issue	Test firewall access, VPN binding, and queue rules
Queued	Active download limits are reached	Raise the queue limit or force resume the torrent
Missing files	Save path changed or drive is offline	Reconnect the drive and set the correct location
Errored	Disk full or app cannot write to the folder	Free space, pick a writable folder, and retry
Works only when VPN is off	VPN blocks forwarding or the bound adapter is wrong	Check the network interface and the port your VPN gives you
Peers appear but speed stays at 0 B/s	Hard speed cap, bad port, or weak peers	Clear limits, test another swarm, and verify the listening port

When Healthy Torrents Still Sit At 0 B/s

This is the point where network rules usually step in. BitTorrent works best when other peers can reach your client. If Windows blocked qBittorrent the first time it asked for network access, inbound traffic can stay shut. Microsoft says non-Microsoft apps may need an inbound exception rule so the traffic can get through. If qBittorrent is missing from the allowed apps list, add it back instead of switching the firewall off.

Check The Listening Port

Open qBittorrent’s connection settings and note the listening port. If you use a router with manual port forwarding, the same port must be forwarded there too. If your VPN offers port forwarding, the port in qBittorrent must match the one the VPN opened. When those two numbers drift apart, peers can see you badly or not at all.

Some VPN setups add one more trap: qBittorrent may still be pointing at the wrong network adapter. If you bound the client to a VPN adapter and later changed servers or apps, qBittorrent can end up tied to an adapter that no longer carries traffic. In that state, torrents often look alive but never move.

Look For Artificial Limits

qBittorrent can throttle itself. Alt speed mode, low global rate limits, or strict queue rules can make a broken-looking client that is only following your settings. Check the bottom bar for the turtle icon, open the speed limits, and make sure the torrent is not waiting in queue behind older jobs. Also glance at the scheduler if you ever set one up.

Setting Area	Healthy Sign	Bad Clue
Listening Port	One fixed port that matches your router or VPN mapping	A random port on each launch with no matching forward
Network Interface	Correct adapter for your normal connection or VPN	Bound to an old or idle adapter
Windows Firewall	qBittorrent is allowed on the network profile you use	App missing from allowed rules or blocked on first run
Queueing	Torrent is active, not waiting	Shows queued or starts only after another torrent ends
Rate Limits	Upload and download caps fit your line	Near-zero caps or alt speed mode left on
VPN Binding	Bound only when the chosen VPN adapter is live	Binding left on after the adapter changed

Disk And Folder Problems That Masquerade As Network Trouble

Not every dead download is a network issue. qBittorrent may be ready to pull data and still fail because it has nowhere safe to put the file. External drives are a common culprit. If the drive letter changed, the disk went to sleep, or the cable dropped, qBittorrent can flip to missing files or errored states. The same thing happens when the default save path points to a folder you no longer have permission to write to.

Open the save path for the affected torrent and make sure it still exists. Then check free space. A nearly full drive can stall writes long before it hits zero in a neat, clean way. If you use Windows folder protection or third-party antivirus, try a normal local folder such as Downloads for one test torrent. If that works, your old destination is the problem, not the client.

Watch For Recheck Loops

If qBittorrent keeps rechecking and never settles, the files on disk may not match the torrent state. Force a recheck once. If the same torrent falls back into an error right after that, move it to a simple local path and test again.

A Clean Order Of Attack That Saves Time

When qBittorrent won’t download, the smartest move is to narrow the field fast:

• Test one busy torrent.
• Read the status line.
• Update qBittorrent if your build is old.
• Check firewall access and the listening port.
• Check queue rules and speed caps.
• Check the save folder, free space, and drive health.
• Then test with and without your VPN binding setup.

Most people fix the issue by step three or four. That is why random tweaking hurts. The torrent itself may be dead. Or the app may be blocked by one neat setting. Once you test in order, the fault stops hiding.

If you want the shortest version, start by proving whether the torrent is alive. After that, the big three are firewall access, a working listening port, and a writable save folder. Get those right, and qBittorrent usually springs back to life.