SABnzbd review: the Usenet downloader that finishes the job for you
What SABnzbd is
SABnzbd is a Usenet client written in Python and released under the GNU General Public License version 2 or later (https://github.com/sabnzbd/sabnzbd/blob/develop/LICENSE.txt). You give it an NZB file, it downloads the articles from your Usenet provider, verifies them against the PAR2 recovery data, repairs what is broken, unpacks the archives and moves the result into a folder named after the release. That whole chain is the product: unlike a generic download manager, SABnzbd expects the messy realities of Usenet and deals with them automatically. The Windows package bundles everything it needs, including Python, so installation does not require any separate runtime.
The workflow it creates
The application runs as a background service with a browser interface on localhost. You add NZB files by dragging them onto the window, by watching a folder, or by letting the built-in RSS reader pick up releases matching a filter. Downloads are split into server connections you configure with host, port, TLS setting and connection count, and multiple providers can be combined with a priority order so a block account is only used as overflow. Categories route completed downloads to different folders and can trigger a script, which is how people wire SABnzbd into tools that rename media or notify a phone. A queue view shows remaining time, speed per server and any failed articles, and the history view keeps a log of what was downloaded, unpacked or repaired.
Settings and limits worth knowing
You need a Usenet provider account, and usually a separate indexer, before the software can do anything at all; SABnzbd is the client, not the service. Give it enough disk space, because it needs room for the downloaded articles, the repair files and the unpacked result at the same time. The unpack step relies on bundled binaries, so a password-protected archive that the tools cannot read will sit in the queue with a clear error rather than being guessed at. Speed is governed by your provider, your connection count and your hardware: the unpack and repair phases are CPU and disk heavy, and running them on a slow drive is the usual cause of a system that feels sluggish during large downloads. The web interface can be reached from other machines, but exposing it beyond your local network without HTTPS and a password is a bad idea.
Who should choose something else
If you do not already have a Usenet subscription, this software has nothing to download from, and a BitTorrent client would be a more sensible starting point. For plain HTTP downloads from file hosts, use Motrix or another download manager. Choose SABnzbd when you do have a provider and want the verification, repair and unpack steps automated instead of running them by hand after every download.
- Best for
- Usenet subscribers who want NZB downloads verified, repaired and unpacked automatically, with categories and RSS rules driving the queue.
- Good to know
- A Usenet provider account is required. Large downloads temporarily need disk space for the articles, repair data and unpacked output at once.
How to get started
- Download the Windows setup executable from sabnzbd.org and install it.
- The installer offers to start SABnzbd; the interface then opens in your browser at localhost:8080.
- Enter your Usenet provider host, port, user name and password, then test the connection.
- Set the number of connections to what your provider allows, and enable TLS if offered.
- Choose download and complete folders, then create a category for each type of content.
- Add an NZB by drag and drop, or point the RSS reader at an indexer feed for automatic pickup.
Questions & answers
Do I need a Usenet subscription?
Yes. SABnzbd is only the client; it needs a provider account to download articles, and usually an indexer to find NZB files.
Where do completed downloads go?
Into the complete folder you configure, inside a subfolder named after the release. Categories can send different content to different folders and run a script afterwards.
Why is my queue so slow to finish?
Download speed depends on your provider and connection count, while repair and unpacking depend on CPU and disk. A slow disk during the post-processing phase is the common culprit.
