SABnzbd Setup Guide: Usenet Downloads on Your Seedbox
On this page ▾
What Is SABnzbd?
SABnzbd is a web-based Usenet downloader — the alternative to NZBGet. It’s easier to set up and has a more user-friendly interface, though slightly less resource-efficient than NZBGet.
What You Need Before Starting
Usenet works differently from torrents — the seedbox hosts the downloader, but access to Usenet itself is a separate subscription you bring:
- A Usenet provider (news server) — this is where the data comes from. Typically $3–10/month. You’ll get a hostname, username and password.
- An indexer — the search engine that produces
.nzbfiles, Usenet’s equivalent of torrent files. Most are free with optional paid tiers. - SABnzbd on your seedbox — one click, below.
Installing SABnzbd
- Dashboard → Apps → SABnzbd → Install
- Open SABnzbd (default port: 8080 or 9090)
Configuration
Add News Server
- Config → Servers → Add Server
- Enter your Usenet provider details: host, port (563 SSL), username, password
- Set connections to 20-30
- Enable SSL
Categories
Create categories matching your *arr apps: sonarr, radarr, readarr. Each category can have a different download path — this keeps TV, movies and books separated so the right app imports the right files.
Connect to Sonarr/Radarr
In Sonarr/Radarr: Settings → Download Clients → Add → SABnzbd. Enter localhost, port, and API key (from SABnzbd → Config → General → API Key). Set the category to match what you created above. From then on the *arr apps send NZBs to SABnzbd automatically and import the finished downloads.
Performance Tuning
Defaults work, but two settings make a visible difference on a fast seedbox connection:
- Article cache (Config → General) — raising the cache lets SABnzbd assemble downloads in memory instead of hammering the disk. A few hundred MB is plenty.
- Direct Unpack (Config → Switches) — starts extracting archives while the download is still running, shaving minutes off large grabs.
If downloads run slower than expected, add connections in steps of 10 up to your provider’s limit, and confirm SSL port 563 — some providers throttle the plain-text ports.
Common Failure Modes
- “Missing articles” / failed downloads — the post has aged off your provider’s retention or was taken down. Not a configuration problem; your *arr app will automatically try the next release.
- Everything queues but nothing starts — almost always wrong server credentials or the connection limit set to 0. Test the server entry in Config → Servers.
- Downloads finish but never import — category path mismatch between SABnzbd and the *arr app. The category folder SABnzbd writes to must be the path Sonarr/Radarr watches.
SABnzbd vs NZBGet
| Feature | SABnzbd | NZBGet |
|---|---|---|
| Interface | More user-friendly | Functional |
| Resource usage | Higher (Python) | Lower (C++) |
| Speed | Fast | Slightly faster |
| Best for | Beginners | Performance-focused |
Both are one-click installs here — see the NZBGet guide if you lean the other way.
Frequently Asked Questions
Do I need my own Usenet provider subscription?
Yes. EvoSeedbox hosts SABnzbd for you, but Usenet access itself comes from a news-server provider you subscribe to separately (typically $3–10/month). We host the downloader — you bring the provider account.
Is Usenet faster than torrents on a seedbox?
Usenet downloads pull from a single fast server, so they typically saturate whatever your plan and provider allow, regardless of seeders. Torrents depend on swarm health. Many users run both: torrents for ratio and rare content, Usenet for automation-friendly grabs.
Does Usenet affect my torrent ratio?
No — Usenet has no ratio concept and no uploading. Downloads via SABnzbd don’t touch your tracker stats either way.
Can Prowlarr manage my Usenet indexers too?
Yes — Prowlarr handles both torrent indexers and Usenet indexers, and syncs them to Sonarr/Radarr in one place. See the Prowlarr guide.
Related Pages
Related articles
Put this into practice
EvoSeedbox ships with one-click app installs and up to 10 Gbps per box.
