Usenet is a decentralised, worldwide network for posting and retrieving messages and files that predates the web itself. It sounds ancient — it is ancient, roughly as old as email — but in 2026 it’s still one of the fastest and most reliable distribution networks in existence. It just works differently to anything you grew up with on the modern internet.

This is the plain-English version. No marketing, no scare stories, just how the thing actually works — including the two concepts that make it genuinely different from the modern web: retention and PAR2 repair.

The 30-Second Version

Usenet is a network of servers that store and exchange articles (chunks of data) on newsgroups (named topic areas). When you use Usenet you’re downloading those articles from a provider’s server, then your newsreader reassembles them into the files you wanted. For binary files, a small pointer file called an NZB tells your reader exactly which articles to fetch.

That’s the whole system. Everything else — providers, retention, indexers — is detail on top of that.

The Core Concepts, One By One

Newsgroups

Newsgroups are named discussion/publication areas, organised hierarchically. Text groups look like alt.tv.serendipity or uk.rec.sheds. Binary groups are where people post files, and they’re organised by category. You subscribe to a group in your newsreader and it lists the articles available.

Articles

Every post on Usenet is broken into articles — discrete chunks, each with its own unique message ID. A large binary file becomes hundreds or thousands of articles, plus optional PAR2 repair files that let your reader reconstruct missing chunks. Your newsreader pulls the articles, checks the PAR2, and reassembles the original file.

Providers and retention

You don’t connect to “the internet” to get Usenet — you connect to a provider’s server over a specific port (usually SSL on port 563). The provider stores articles for a set period called retention. When articles fall outside the retention window, they’re deleted. See my Usenet retention explained guide for why big retention numbers can mislead you — and why completion (how complete a file is when you actually pull it) matters more than the headline number of days.

PAR2 repair — the part most explainers skip

This is the quiet engineering magic that keeps binaries usable. Posters add parity files (PAR2) alongside the main binaries — typically 5–10% redundant data. When a download is missing a few articles (from a takedown, a propagation gap, or ageing out of retention), your newsreader uses that parity to reconstruct the missing pieces, the way checksum clues in a crossword let you deduce a missing cell.

The catch, and the reason it ties directly into provider choice: PAR2 can only repair up to the parity a release ships with. If a file is missing more than ~10% of its articles, no repair can save it. That’s why a provider with high completion beats a provider with a giant retention number — the former keeps you inside working coverage so your finite PAR2 budget is spent on genuine stragglers, not systemic gaps. The full science is in the retention guide — and the hands-on repair walkthrough is in the hands-on repair walkthrough.

Indexers

Because Usenet has no central search, you need an indexer to find binaries — essentially a searchable directory of NZB files. Indexers come in free and paid forms, and they differ enormously in what they index and how fresh they are. I cover the setup dance in the getting-started guide, and the ‘how they work / how to choose’ detail in Usenet indexers explained.

Newsreaders and automation

A newsreader (like SABnzbd, NZBGet, NZB360, or a desktop client) fetches the articles your NZB references and assembles them into a file. The big improvement of the modern era is automation: tools like Sonarr and Radarr watch for new releases and hand the NZBs to SABnzbd automatically. That’s how a lot of people now use Usenet without ever opening a “reader” app — it just runs in the background on a NAS or a home server.

How Downloading Actually Flows

Let’s trace one download end to end:

  1. You find a binary in an indexer and grab its .nzb file — a small XML-style file listing every article and which newsgroups hold it.
  2. You open that NZB in SABnzbd (or your reader).
  3. SABnzbd connects to your provider’s server over SSL, opens many simultaneous connections, and pulls the listed articles.
  4. It verifies and repairs with PAR2, then extracts and renames to the final file.

That whole pipeline is why Usenet downloads at your line’s maximum speed — the provider isn’t throttling you the way a torrent swarm or a direct-download host does, and multiple connections saturate your bandwidth.

Why People Still Use It in 2026

Usenet’s advantages over modern alternatives are concrete:

  • Speed. Server-hosted, so download speed is limited by your connection, not by how many people are seeding.
  • Retention. Major providers keep binaries 15+ years. Old stuff stays findable.
  • Repair. PAR2 parity means a slightly-incomplete download usually still arrives complete.
  • No seeding. You download and leave. You’re never asked to give back upload bandwidth.
  • Automation. The whole pipe can run unattended.

The honest downsides: it’s not free (you pay a provider, and usually an indexer), there’s a learning curve, and — let’s be real — much of the popular binary traffic exists in a legal grey area. Use it on the right side of the law where you live. That’s why the first thing in my setup guide is staying private.

The UK Thing

Because you’re likely reading from the UK: Usenet works well here, but a few UK specifics shape the experience. UK ISPs have historically throttled plaintext Usenet traffic, so SSL on port 563 is effectively mandatory. And heavy sustained downloads can hit Fair Usage Policies on “unlimited” broadband plans. Neither is a dealbreaker — both are manageable with the right config. The Usenet vs torrents guide has the full UK ISP breakdown.

Usenet vs the Alternatives

The most common comparison is against torrents. Rather than duplicate it here, I’ve written the full breakdown: Usenet vs torrents: which is actually better?. Short version: Usenet wins on speed, reliability and automation; torrents win on being free and having no central cost.

Where to Go Next