Guide

How Usenet works

Providers, retention, connections, NZBs, and plan types explained plainly.

Updated 2026-10-01

What Usenet actually is

Usenet is a distributed network of NNTP servers that exchange articles across newsgroups. Providers give you authenticated access to their spool. You do not "join a swarm" the way BitTorrent does - you download articles your provider still retains.

Providers, articles, and retention

A provider stores articles for a retention window. Binary retention on flagship Highwinds and Eweka brands now markets past 6,600 days. When retention expires - or a takedown removes a Message-ID - that article is gone on that spool. Retention class is why backbone choice beats logo choice. See the backbone map.

NZBs in plain language

An NZB is a small pointer file listing Message-IDs for a release. Indexers search and generate NZBs. Your newsreader (SABnzbd, NZBGet, or a web UI) reads the NZB and fetches those articles from your provider over NNTP, usually with SSL on port 563.

The three-piece stack

  1. Provider - ships the bits (reviews, matrix).
  2. Indexer - finds NZBs (not a Usenet host).
  3. Newsreader - downloads and repairs (SABnzbd or a beginner web UI).

Beginners can postpone the indexer by using Easynews web search - see best for beginners.

What Usenet is not

Usenet is not a single website, not a VPN, and not an illegal-content service. It is infrastructure. Completion depends on retention, takedown regime (DMCA vs NTD), NZB quality, and whether you added an independent fill (blocks).

What to do next

Pick one unlimited primary from the provider matrix, enable SSL, and run a week of downloads before you buy fill. Read DMCA vs NTD so jurisdiction is a deliberate choice, then configure the client with SABnzbd setup.

FAQ

What does Usenet retention mean?
How long articles stay on a provider spool. Longer retention helps older NZBs complete.
Do I need multiple providers?
Start with one unlimited primary. Add a different-backbone block when Priority 0 misses articles regularly.
Is an indexer the same as a provider?
No. Indexers point; providers store and serve articles.