NZBGET

Complete and fast: watched folders, URL fetching, API submission, per-category routing, duplicate detection and a queue that reorders without complaint. Functionally it matches SABnzbd on this axis, and the differences that remain are taste rather than capability. Nothing we fed it in normal use caused a stumble.

Built-in automatic verification, repair and unpack, with a quick-check mode that skips full verification when blocks are intact, which saves real time on weak hardware. Repair quality matched SABnzbd in our use. The scripting hooks around post-processing are powerful, with a smaller library of community scripts than the SABnzbd world offers.

The fastest raw pipeline in the table on constrained hardware, and the equal of anything on a proper machine: C++ efficiency means the CPU spends its time on repair and unpack rather than on the runtime. It saturated the same line as everything else on a desktop; the difference appears on a NAS, where NZBGet keeps up and heavier clients start to throttle the line themselves.

Everywhere, including places nothing else in this table will go: Windows, macOS, Linux, BSD, every NAS ecosystem, Docker, Raspberry Pi and genuinely low-power ARM hardware, with the web UI controlling it from anywhere. If the machine has a network stack, NZBGet probably has a build for it.

Full API with native support across the *arr stack, watched folders, and an extension system for post-processing. In practice it is a drop-in alternative to SABnzbd in automated setups, and the choice between them usually comes down to hardware and habit. The community and script library are smaller, which occasionally shows when you want an off-the-shelf recipe.

The reason this entry exists, and the best score on the axis anywhere in this table. NZBGet idles in a few tens of megabytes and runs comfortably on hardware SABnzbd would strain: routers, first-generation NAS boxes, the weakest Pis. If your download machine is chosen for silence or power draw rather than horsepower, this axis decides the whole comparison.

None, identical to SABnzbd and for the identical reason: it is a pipeline, not a portal. Discovery comes from your indexer, Global Search, or automation. Score the axis low and the design honest.

A dense, functional web UI that shows its engineering heritage: every number you could want is on screen, arranged with more regard for information than for looks. Perfectly usable, less polished than SABnzbd’s, and irrelevant in the automated setups where nobody looks at either UI from one month to the next.

Free and open source. The original project’s trademark-era paid tier is gone; the maintained fork is entirely free. Checked August 2026.