SABNZBD

The reference implementation. NZBs arrive by drag-and-drop, watched folder, URL, API or indexer integration, and the queue handles priorities, categories, per-category folders and post-processing scripts without breaking stride. Malformed and partially duplicated NZBs that confused lesser tools were handled gracefully in our use. This axis is what SABnzbd is for, and it shows.

Automatic verification, repair and extraction with years of edge cases baked in, including multi-set posts, nested archives and obfuscated filenames. Repair is tunable but never needs tuning. In our use, sets that could be saved were saved without intervention, and sets that could not be were failed quickly and clearly, which matters just as much.

Downloads run as fast as the account behind them allows: SABnzbd saturated the same gigabit line the provider bench used, with connection handling that scales to whatever your plan permits. Post-processing is where machines differ, since repair and unpack are CPU and disk work; on anything modern the pipeline keeps up with the line. Article-level tuning exists for people who enjoy that sort of thing and is unnecessary for everyone else.

Windows, macOS, Linux, FreeBSD, every NAS brand with a package system, Docker, and a Raspberry Pi if that is what you have. The web interface means the machine doing the downloading and the screen controlling it need not be the same device, which is the shape most serious setups take. Nothing else in this table comes close on deployment breadth.

The centre of the ecosystem. A full API, watched folders, category routing, pre- and post-processing scripts, and native support in Sonarr, Radarr, Lidarr and the rest of the automation stack. If your ambition is downloads that happen entirely without you, this axis is the reason SABnzbd is the default recommendation and has been for years.

Modest for what it does: comfortable on a NAS or a Pi, though its Python runtime makes it heavier than NZBGet, which exists largely to win this one axis. On any vaguely modern hardware the difference is academic. On a router or the weakest single-board machines, it is the one reason the entry above this one takes the top slot.

None, on purpose. SABnzbd downloads what you bring it, full stop; discovery belongs to an indexer or a tool like Global Search, and automation belongs to the *arr stack it plugs into. The low score here is the honest price of a deliberate design decision that is also the main thing a newcomer needs to understand before choosing it.

A clean web UI reachable from anything with a browser, plus themes and a mobile-friendly layout. It is a download manager’s interface, built for glancing at a queue rather than living in, and it is entirely adequate for that. First-run setup is a short wizard: server details in, working client out.

Free, open source, GPL-licensed, no tiers, no trial, no upsell. Two decades of development at the price of a donation link. This axis does not get more decisive than that. Checked August 2026.