Usenet predates the web. It began as a distributed discussion network in 1980 and, along the way, became a way of storing and retrieving binary files. For downloading, it works nothing like BitTorrent — and the differences are worth understanding before you decide whether to bother.
How it differs from torrents
| Torrents | Usenet | |
|---|---|---|
| Where files come from | Other users (peers) | A provider's servers |
| Speed | Depends on seeders | Consistently your full line speed |
| Do you upload? | Yes — that is the point | No, ever |
| Ratio obligations | Yes on private trackers | None |
| Who can see you | Every peer in the swarm | Only your provider, over SSL |
| Availability of old content | Dies when seeders leave | Held for the provider's retention period |
| Cost | Free (tracker accounts aside) | Provider subscription, plus usually an indexer |
The headline difference: Usenet is a download service, not a sharing network. There is no seeding, no ratio to protect and no swarm to be visible in. You pay a provider, you download at full speed, and you are done.
What you need
Three pieces, and people are often surprised the first two are separate:
- A provider — the company actually storing the articles. The things that matter are retention (how far back their archive goes, now commonly 5,000+ days), connection count and whether they offer SSL. Most sell unlimited plans for a few euros a month.
- An indexer — a search engine for Usenet. Providers store; indexers help you find. Some are free, the better ones charge a modest annual fee.
- A downloader — SABnzbd or NZBGet, running on your box. Both deploy in one click from the Cresdock panel.
You feed the downloader an .nzb file (the rough equivalent of a .torrent), and it fetches the pieces from your provider, repairs anything corrupt, and unpacks the result.
SABnzbd or NZBGet?
Both work well and both integrate with the *arr apps. In short:
- SABnzbd — friendlier interface, larger community, more guides written about it. The default recommendation for most people.
- NZBGet — written in C++ and noticeably lighter on CPU and memory. Worth choosing on a smaller box, or if you like a leaner setup.
You will not go wrong either way. Pick one, and switch later if it annoys you — the *arr apps treat them interchangeably.
Par2 repair: the part that looks like magic
Usenet articles expire, get corrupted, or go missing from a provider's retention. Downloads therefore ship with par2 recovery files — parity data that can rebuild missing pieces, in the same spirit as RAID.
Your downloader handles this automatically: it grabs the archive, notices what is missing, downloads only as much parity as it needs, reconstructs the file and then unpacks it. You just see a completed download.
The relevance to a seedbox is that par2 repair and unpacking are CPU-heavy. On a shared box with a couple of cores, a large repair can take a while. If you plan to lean on Usenet hard, a Rootserver with more dedicated cores makes a real difference.
Running it alongside torrents
This is where a seedbox genuinely shines, and it is the setup we would recommend to most people: run both.
Prowlarr → manages torrent indexers AND usenet indexers
↓
Sonarr/Radarr → looks for a release
↓
├─ SABnzbd → if a good usenet result exists
└─ qBittorrent → otherwise, grab the torrent
↓
same library folder → your media serverSonarr and Radarr will happily use both and prefer whichever finds a suitable release first. In practice Usenet wins for anything recent and popular — instant full-speed download, no waiting on seeders — while torrents cover older or niche material that has aged out of retention, plus anything only your private trackers carry.
Because our bandwidth is unmetered either way, running both costs you nothing extra. See the *arr stack guide for how to wire it together.
Practical notes
- Always enable SSL in your downloader. Providers offer it as standard, and without it your connection to them is unencrypted.
- Set connections sensibly. Providers cap simultaneous connections per account; using more than your plan allows just causes errors. 20–30 is plenty to saturate most lines.
- Retention is not a promise about any one file. A 5,000-day retention figure describes the archive generally; individual posts can still be incomplete or removed.
- Usenet does not help your ratio. If you are on private trackers, Usenet downloads contribute nothing to upload. Use it to take pressure off your torrent client, not to replace it.
Common questions
Is Usenet more private than torrenting?
In one specific sense: there is no swarm, so no peer sees your address — only your provider does, over an SSL connection. On a seedbox that distinction matters less, since the box is already the thing in the swarm, not you.
Do I need Usenet if I already have a seedbox?
No, but they complement each other well. Usenet gives instant full-speed downloads with no seeding obligation; torrents give you private-tracker content and long-tail availability. Running both is common and costs no extra bandwidth here.
Is it legal?
Usenet itself is a legitimate, decades-old protocol, and paying a provider for access is entirely legal. As with torrents, what you choose to download is your responsibility.