Getting started with Usenet is fiddlier than it needs to be, mostly because nobody writes down the whole pipeline in one place. This is that one place. Follow it top to bottom and you’ll go from knowing nothing to having a fully automated Usenet setup that runs itself — and stays stable when you start pulling hundreds of gigabytes a week.

A quick honesty note up front: two of the four pieces of this pipeline cost money (a provider and, usually, an indexer). I’ve written the cheapest providers guide separately because “cheapest” and “how to set it up” are different questions. Here, we’re setting things up the right way first — including the UK-specific decisions that trip people up.

What You’ll Need

The modern Usenet stack has four parts:

  1. Provider — the server that stores articles. (Paid, ~£5–9/mo or blocks.)
  2. Indexer — the searchable catalogue of NZB files. (Often paid for good ones.)
  3. Newsreader / downloader — grabs the articles and assembles files. (SABnzbd is the standard.)
  4. .nzb file — the pointer that says “these specific articles = this file.”

Optionally, automation on top (Sonarr/Radarr) makes it fully hands-off.

Step 1: Pick a Provider (and the Backbone Behind It)

Choose a provider based on backbone, retention, and completion — I’ve costed this out in the UK provider comparison. The single most important starting insight: almost every provider resells someone else’s backbone. Pick the storage network first, then shop the front-ends on price.

There are three backbones that matter in 2026:

  • Omicron — the biggest, deepest spool (Eweka, Newshosting and dozens of resellers). Best for very old content; some front-ends have low connection caps.
  • UsenetExpress — fast, modern, excellent completion on a single coherent spool (UsenetExpress, NewsgroupDirect, ViperNews).
  • Abavia — the classic independent European backbone (Usenet.Farm and a few resellers), strong European peering.

For a first account, the sensible default is a provider with SSL, at least 50 connections, and strong completion on new releases — you don’t need maximum retention to start. A multi-backbone unlimited makes for the most forgiving first setup, because completion on one spool covers gaps on another. If anyone ever tells you “just buy the spool with the most days,” remember the PAR2 repair science angle: completion beats a big retention headline every time.

If you’d rather not commit to a subscription while learning, grab a block (fixed data, never expires) from a reputable backbone — see the cheapest options. Cheap, and you can’t waste money while you learn.

Recommended starting account: a multi-backbone unlimited (or block) from NewsgroupDirect covers the most bases per pound and its Grand Slam plan bundles four backbones in one account, which is unusually forgiving while you learn. See current deals.

UK ISP selection note

Your broadband also determines how fast Usenet actually runs. Key points for UK readers:

  • SSL on port 563 is non-negotiable against UK ISP throttling — configure it the moment you add your server (Step 3).
  • Fair Usage Policies: unlimited UK plans often have an unadvertised cap. Usenet saturates a line very efficiently, so heavy users can trip a FUP faster than they’d expect. Pick a genuinely unlimited fibre plan or schedule big pulls off-peak.
  • Routing/peering: a spool with good European peering (Abavia/Usenet.Farm) can out-download a “deeper” spool that’s routed poorly to the UK. See the retention guide’s ISP section and the best UK providers for why backbone peering matters as much as headline days.

Step 2: Get an Indexer

You can’t browse Usenet like a website — you need an indexer to find binaries. Indexers differ wildly in coverage, freshness, and quality of the NZBs they produce.

  • Free/public indexers exist but are hit-or-miss, often slow-indexed and full of dead NZBs.
  • Paid/private indexers are usually a small annual fee and offer far better coverage, faster indexing, and working NZBs. They’re worth the money for the automation step to work properly.
  • Newznab indexers expose an API that tools like Sonarr/Radarr hook into — you’ll want one that supports this for automation.

Sign up for one good indexer first. You can add a second later to improve completion — no single indexer covers everything, and a backup is a common trick. For new users, get comfortable with free options first, then pay once you’re sure the pipeline works. The full decision framework is in Usenet indexers explained.

Step 3: Set Up SABnzbd

SABnzbd is the industry-standard downloader. It accepts NZBs, connects to your provider, downloads the articles, verifies with PAR2, extracts, and renames — all unattended. (If you’re on constrained low-RAM hardware, see the SABnzbd vs NZBGet comparison before you commit.)

Install

  • Windows/macOS: download the installer from sabnzbd.org and run it; it launches a browser-based UI.
  • Linux / NAS / Docker: the classic approach is a Docker container. A minimal docker run -p 8080:8080 -v /your/downloads:/downloads ghcr.io/sabnzbd/sabnzbd gets you up in seconds.

Configuration

  1. Add your server. In Config → Servers, add your provider’s host, username, password, port 563 with SSL enabled (TLS). Set connections to the maximum your plan allows (often 100). Enable TLS on both server (479) and client (478) for header encryption — this is your UK ISP-throttle defence.
  2. Set paths. Point Config → General at your complete and incomplete download folders. Keep them on fast storage (SSD or RAID), not the same slow spinning disk as your OS — Usenet saturates drives, and disk speed is a silent bottleneck on big transfers.
  3. Enable repairs. SABnzbd handles PAR2 automatically when you open an NZB that includes .par2 files. Number of repair threads: start at 1–2.
  4. Test. Download a small NZB from your indexer and watch it land.

Large-transfer stability (worth doing now)

So you don’t learn this the hard way after a hundred gigabytes:

  • Cap connections to your provider’s allowance — more than allowed fragments and slows you down, not speed you up.
  • Queue cleanly. Let one download finish and repair before stacking ten at once; that avoids CPU/RAM meltdown during simultaneous PAR2 repairs.
  • Watch the repair phase. On a big release, PAR2 verification is the CPU-hungry part. If a multi-hundred-GB download slows at the finish line, your disk or CPU is the culprit — not the downloader.

SABnzbd fixes a lot for you automatically — missing articles, bad filenames — which is exactly why it beats a bare newsreader for binaries. It also means you get the PAR2 repair budget working for you without thinking about it — and when a repair does stall, the settings that fix it are in repair troubleshooting.

Step 4: Automation (Sonarr/Radarr) — Optional But Life-Changing

This is where Usenet gets properly good. Instead of hunting for NZBs, you install:

  • Sonarr — watches TV series, grabs NZBs automatically as episodes release.
  • Radarr — does the same for films.

Since both feed SABnzbd when you connect an indexer, once it’s set up you basically never touch Usenet directly again: a new episode appears, Sonarr finds the NZB on your indexer, hands it to SABnzbd, SABnzbd downloads and renames it into your media folder.

Both run great in the same Docker setup as SABnzbd. Expect a half-day to get the integration right the first time — the payoff is years of hands-off downloads.

Two things, and I won’t sugar-coat either:

  • Encryption: your provider-to-you connection should be SSL/TLS (port 563) — mandatory. Some providers (NewsgroupDirect among them) bundle a VPN; a VPN adds protection for your general traffic. Without SSL you’re sending plaintext that UK ISPs have previously throttled and can inspect. The Usenet vs torrents guide digs into why SSL beats VPN roulette for Usenet specifically.
  • The legal reality: much of the popular binary traffic on Usenet is copyrighted material. Downloading it in the UK can put you on the wrong side of copyright law regardless of file protection or encryption. Use Usenet legally. Don’t treat encryption as a licence to ignore the law where you live. This guide covers the technical setup — you own the legal side.

Full Pipeline Recap

Indexer ──NZB──> Sonarr/Radarr ──> SABnzbd ──SSL(563)──> Provider
                                          │
                                          └──> VERIFY (PAR2) → EXTRACT → RENAME → media folder

Automation makes it elegant; without it, it’s still a two-click download.

Next Steps