NZBGet built its reputation as the quiet downloader on underpowered NAS units while SABnzbd became the default star in *arr tutorials. Learning how to use NZBGet in 2026 is still worthwhile when your hardware budget is measured in watts and megabytes of RAM, not when you chase the flashiest UI. The NNTP side mirrors SABnzbd: primary at priority zero, optional fill at priority one on a non-overlapping backbone, SSL on port 563, connection limits copied from the provider status page.
This walkthrough covers when NZBGet fits, how to wire servers and paths, and where Sonarr integration differs from the SABnzbd screenshots you see everywhere.
When NZBGet is the right tool
Choose NZBGet on ARM NAS, Raspberry Pi, old Synology models, and any host where idle RAM below a few hundred megabytes matters. It downloads, repairs PAR2, unpacks, and scripts post-steps with less overhead than heavier Python stacks on the same silicon.
If you run a modern x86 NAS with plenty of memory, SABnzbd's ecosystem advantage usually wins. Switching to NZBGet solely because a forum post said it is faster rarely pays the integration tax. See Usenet on Raspberry Pi for Pi-specific path and disk notes.
Initial install and web UI
Install from maintained packages or Docker images your platform trusts. Open the web UI, set a strong admin password, and define download directories: one incomplete scratch area and one complete folder Sonarr will read. Enable direct unpack when you trust extensions, but keep disk headroom for par expand.
On Docker, align PUID/PGID with mount ownership the same way you would for SABnzbd. Permission failures after unpack look like missing files in Sonarr even when NNTP succeeded.
Configuring NNTP servers and priorities
Add your primary unlimited account first: host, username, password, SSL on, port 563 unless the provider documents otherwise, active yes, priority 0. Cap connections at the retailer limit, not at your router's fantasy number. More connections than allowed can trigger throttling or bans.
Add fill only after logged misses prove you need a second backbone. Fill server priority 1 must sit on different retention ownership, not on a twin brand reselling the same Highwinds pool. Overlapping accounts waste money without raising completion.
Categories, scripts, and Sonarr/Radarr hooks
NZBGet uses categories to route jobs and fire post-processing scripts. Sonarr connects via NZBGet's API with a category name you configure on both sides. Radarr follows the same pattern. Documentation examples often show SABnzbd category strings; translate them literally and test one manual grab before automating season packs.
Enable par check and unpack in sane order: download, verify, repair if needed, unpack, then let Sonarr detect the final folder. Watch logs when a job stalls at 99 percent; often par is still working on slow CPUs.
Paths, duplicates, and disk hygiene
Keep incomplete and complete on volumes with known free space. NZBGet can pause when disk drops below thresholds; configure them instead of discovering corrupted half-unpacks. Duplicate detection interacts with Sonarr's own rules: avoid sending the same release twice from indexers during testing.
Backup NZBGet's config directory before major upgrades. It holds server passwords and category definitions you do not want to retype.
NZBGet vs SABnzbd in daily ops
SABnzbd wins for beginners because Sonarr defaults, Docker templates, and forum answers assume it. NZBGet wins when the box is small and you accept manual translation of those answers. Both respect the same provider economics: one good primary, evidence-based fill, no twin stacking.
Read SABnzbd vs NZBGet before running both side by side on the same complete directory.
FAQ
- Is NZBGet still maintained?
- Check your distribution or Docker maintainer. Prefer images with recent commits over abandoned forks.
- Which Docker image should I use?
- Pick a maintained LinuxServer or hotio style image with documented PUID/PGID and volume paths.
- Do Sonarr and Radarr support NZBGet?
- Yes via API and categories. Setup differs slightly from SABnzbd screenshots.
- Does NZBGet change which provider I should buy?
- No. Retention and backbone choice are independent of client.
- Can NZBGet use the same SSL settings as SABnzbd?
- Yes. Host, port, username, password, and connection cap copy directly.
Related
- SABnzbd vs NZBGet
- Docker Usenet stack
- Providers for downloaders
- NNTP pipelining explained
- SABnzbd setup guide