What Is Usenet and How Do You Get Started?
Usenet has been around for a long time, but it can still be confusing when you are new because there are several different ways to use it.
This page is a beginner-friendly starting point. It explains what Usenet is, the basic pieces you need, the different setup paths people usually take, and where to go next in the /r/usenet wiki.
Before posting, please read the subreddit rules:
Do not ask for specific content titles, invites, accounts, backdoor access, or anything that violates subreddit rules. Keep posts focused on Usenet services, setup, software, troubleshooting, providers, indexers, clients, and general concepts.
Quick Overview
Most Usenet setups involve some combination of these pieces:
| Piece | What it does |
|---|---|
| Usenet provider | Gives you access to Usenet servers |
| Search tool or indexer | Helps you find Usenet posts |
| Newsreader / NZB client | Connects to your provider and retrieves articles |
| Automation tools | Coordinate searching, grabbing, sorting, renaming, importing, and other user-defined workflows |
Some beginner-friendly services bundle provider access and search together.
More advanced setups usually separate each piece so you can choose your own provider, indexers, clients, and automation tools.
What Is Usenet?
Usenet is a distributed network made up of newsgroups. Newsgroups contain posts called articles.
To use Usenet today, most users connect through a Usenet provider. Depending on the setup, they may also use a search tool, an indexer, a newsreader, an NZB client, or automation apps.
The most important thing to understand is that Usenet is not usually one single app or website. It is a system made of several parts.
The common parts are:
A provider for server access
A search tool or indexer to help find posts
A newsreader or NZB client to retrieve articles
Optional automation tools for more advanced workflows
For more general background, see:
The Three Common Beginner Paths
There is not one correct way to get started. Most users follow one of these paths.
Path 1: Simple Usenet Search
This is usually the easiest beginner path.
Some services combine Usenet provider access with a built-in search interface. This lets you start with fewer moving parts because you do not immediately need to configure separate indexers, API keys, NZB clients, categories, automation apps, Docker paths, or import settings.
This path is good if you want to:
Start with the fewest moving parts
Use one account instead of several
Search manually
Learn basic Usenet concepts first
Avoid building a full automation stack on day one
The tradeoff is flexibility. A built-in search experience may be easier, but it usually gives you less control than a modular setup.
You may eventually want:
Better indexer coverage
A dedicated NZB client
Multiple indexers
Automation
Better troubleshooting visibility
More control over providers, categories, paths, and post-processing
Best for:
Brand-new users
Users who want the lowest-friction starting point
Users who want to understand the basics before building a more advanced setup
Path 2: Provider + Indexer + Newsreader
This is the standard modular Usenet setup.
You use:
A Usenet provider for server access
An indexer to find posts
A newsreader / NZB client to connect to the provider and retrieve articles
This setup gives you more control than an all-in-one search experience.
You can choose:
Your provider
Your indexers
Your NZB client
Your server settings
Your categories
Your connection count
Your folder paths
Your retention/backbone strategy
The tradeoff is that there are more things to configure and more places where problems can happen.
Best for:
Users who want more control
Users who want to understand how Usenet works
Users who are comfortable configuring software
Users who may want to build toward automation later
Useful wiki pages:
Path 3: Automation Stack
This is where many experienced users eventually end up.
A typical automation setup may include:
| Tool type | Examples | Main role |
|---|---|---|
| Usenet provider | See /r/usenet provider resources | Server access |
| Indexers | See /r/usenet indexer resources | Search results / NZBs |
| Indexer manager | Prowlarr, NZBHydra2 | Manage indexers across apps |
| NZB client | SABnzbd, NZBGet | Retrieve articles from Usenet |
| Automation apps | Sonarr, Radarr, Lidarr, Readarr | Apply user-defined rules and send jobs to the NZB client |
| Companion tools | Bazarr and others | Optional supporting tools for advanced setups |
In this setup, each tool has a job.
A simplified flow looks like this:
An automation app checks configured feeds or indexers based on user-defined rules.
Prowlarr or NZBHydra2 searches configured indexers.
The automation app sends a selected NZB to SABnzbd or NZBGet.
SABnzbd or NZBGet connects to your provider.
The client retrieves, verifies, repairs, and unpacks.
The automation app handles the completed result according to its settings.
Automation is powerful, but it adds complexity.
Common automation problems include:
Wrong API key
Wrong category
Wrong client setting
Wrong root folder
Wrong remote path mapping
Docker path mismatch
Permissions problems
Import failures
Indexer API limits
Failed retrievals
Repair/unpack failures
Provider authentication errors
App-to-client communication errors
Best for:
Users who already understand the basics
Users who have a working provider/client/indexer setup
Users who are comfortable reading logs
Users who want a more automated workflow
Useful external communities and docs are listed later on this page.
Recommended Learning Path
If you are new, do not start by installing every tool at once.
A better progression is:
Learn what Usenet is.
Learn the difference between a provider, indexer, and newsreader.
Choose either a simple search path or a basic modular setup.
Get provider access working.
Get one client working.
Get one indexer/search method working.
Learn how to read client logs.
Learn why retrievals fail.
Add better indexers if needed.
Add automation only after the manual workflow works.
Add backup providers or blocks only when you understand what problem they solve.
Tune paths, permissions, performance, categories, and automation rules.
A simple setup that works is better than an advanced setup you cannot troubleshoot.
Core Concept: Usenet Provider
A Usenet provider gives you access to Usenet servers.
Before choosing a provider, review:
The Provider Deals page is usually the best place to compare current offers. It lists available deals and includes details such as provider, backbone, price, retention, crypto support, and server/policy.
Do not treat the deals page as a ranked recommendation list. A provider appearing there does not mean it is officially endorsed by Reddit, the moderators, or the community. It is a comparison resource.
For your first provider, do not choose based only on the lowest price. Compare:
Price and renewal terms
Retention
Completion reputation
SSL support
Server location
Connection limits
Block vs unlimited plan type
Backbone
Takedown policy
Support reputation
Most beginners should start with one reliable unlimited provider. Add backup blocks or additional providers later only after you understand what problem you are trying to solve.
Retention
Retention is how far back a provider claims to store Usenet articles.
For example, a provider advertising thousands of days of retention is saying it may have articles available from that far back.
Higher retention can help with older posts, but it does not guarantee that every article from that time period will be available.
A retrieval can still fail because of:
Missing articles
Takedowns
Completion issues
Bad or stale NZBs
Indexer problems
Provider/backbone differences
Client repair or unpack failures
Think of retention as “how far back the provider may be able to go,” not a promise that everything from that date range will always work.
Completion
Completion means whether the provider has all the articles needed for a retrieval to finish successfully.
Retention and completion are related, but they are not the same thing.
A provider can have high retention and still be missing some articles.
If a retrieval fails because articles are missing, the cause may be completion, takedown, stale NZB data, provider/backbone differences, or result age.
Unlimited Plans
An unlimited plan is usually the simplest first provider plan.
With an unlimited plan, you pay for access over a period of time, such as monthly or yearly, rather than buying a fixed amount of data.
Unlimited plans are usually best for:
First-time users
Main provider access
Regular usage
Learning the basic setup
Automation setups later
Before buying, check whether the listed price is the renewal price or only a first-term promotion.
Block Accounts
A block account is prepaid access sold as a fixed amount of data.
For example, a block may be sold as 500 GB, 1 TB, or another fixed amount.
Blocks are often used as backup access. A common setup is one main unlimited provider plus a backup block from a different backbone.
Most beginners do not need to buy blocks immediately.
Consider a block later if:
Your basic setup already works
You understand how backup providers work in your client
You are trying to improve missing-article coverage
You know your issue is not caused by your indexer, client, paths, permissions, or automation settings
Backbone
A backbone is the underlying Usenet infrastructure a provider uses.
Two providers can have different names, prices, and websites while still using the same backbone.
Backbone matters most when you are adding a second provider or backup block. If two providers use the same backbone, they may not add much additional coverage as a backup pair.
For a first provider, do not overthink backbone. For backup access, it matters more.
Use the Providers Map to understand provider relationships and backbone information.
Server Location
Server location refers to where the provider offers access, such as US servers, EU servers, or both.
A closer server may perform better, but this depends on routing, your ISP, your client settings, and provider performance.
If a provider offers multiple server locations, test the one closest to you first unless the provider recommends otherwise.
DMCA vs NTD
Provider pages often mention takedown policy, such as DMCA or NTD.
In simple terms:
DMCA usually refers to a US-style copyright takedown process.
NTD usually means Notice and Takedown, commonly associated with EU-style takedown processes.
This matters because takedown policy can affect article availability.
However, do not assume that DMCA vs NTD alone determines whether a provider is better. Availability can also depend on:
Retention
Completion
Backbone
Provider infrastructure
Indexer quality
Result age
Whether the NZB is stale
Whether articles were removed
Your client configuration
Treat takedown policy as one comparison point, not the only deciding factor.
SSL
SSL encrypts the connection between your newsreader and your Usenet provider.
Use SSL if your provider supports it.
Your provider will usually list SSL server addresses and ports. Make sure your client settings match the provider’s instructions.
Connections
Connections are the number of simultaneous connections your client makes to the provider.
More connections do not always mean better speed.
Start with the provider’s recommended connection count. Increase or decrease only if you are troubleshooting speed or stability.
Beginner Provider Advice
For your first provider:
Check the Provider Deals page.
Pick one reliable unlimited plan.
Make sure SSL is supported.
Use the provider’s recommended server and connection settings.
Get your client working before buying extra providers or blocks.
Add backup access later only if you understand what problem it solves.
Core Concept: Search Tool or Indexer
An indexer helps you find Usenet posts.
An indexer is not the same thing as a provider.
| Thing | Role |
|---|---|
| Provider | Gives server access |
| Indexer | Helps find posts |
| Newsreader / NZB client | Retrieves articles from the provider |
| Automation app | Coordinates the workflow |
Some beginner-friendly services include search and provider access together. More advanced setups usually use separate indexers.
Indexer features may include:
Search quality
API access
API limits
Categories
Open or private registration
Free vs paid tiers
Retention visibility
Community reputation
Support and account rules
Useful wiki page:
Do not ask for invites if the subreddit rules prohibit it.
Core Concept: Newsreader / NZB Client
A newsreader or NZB client connects to your Usenet provider and retrieves articles.
Common clients include:
SABnzbd
NZBGet
Newsbin
Other Usenet clients listed in the software wiki
Your provider usually gives you:
Server address
Port
Username
Password
SSL setting
Connection limit
You enter those details into your client.
Useful wiki page:
Tool-specific support:
Official docs:
Ask /r/usenet when the question is about Usenet providers, indexers, retention, completion, backbones, blocks, or general Usenet concepts.
Ask the client-specific subreddit when the question is about client settings, UI behavior, repair/unpack settings, queue behavior, categories, scripts, or client errors.
Core Concept: Automation Tools
Automation tools are optional. They are useful after you understand the basics.
The most common automation ecosystem is the Servarr / *arr stack. These tools are often used to connect indexers, NZB clients, and user-defined automation rules.
Automation tools are powerful, but they add complexity. They are best used after you already understand the basic provider + indexer + client workflow.
Common Automation Tools
| Tool | Typical role | Support |
|---|---|---|
| Sonarr | Automation app that can monitor configured feeds, send jobs to a download client, and manage imports based on user-defined rules | /r/sonarr |
| Radarr | Automation app that can monitor configured feeds, send jobs to a download client, and manage imports based on user-defined rules | /r/radarr |
| Lidarr | Automation app that can monitor configured feeds, send jobs to a download client, and manage imports based on user-defined rules | /r/lidarr |
| Readarr | Automation app that can monitor configured feeds, send jobs to a download client, and manage imports based on user-defined rules; check current project status before setup | /r/readarr |
| Prowlarr | Indexer manager that integrates with automation apps and helps manage indexer settings in one place | /r/prowlarr |
| NZBHydra2 | Metasearch and indexer aggregation tool | /r/nzbhydra |
| Bazarr | Companion automation tool used alongside other automation apps | /r/bazarr |
| Servarr | General support community and documentation hub for the broader automation ecosystem | /r/Servarr |
Official docs:
When to Ask /r/usenet vs Tool-Specific Subs
Use /r/usenet for:
Choosing a Usenet provider
Understanding retention
Understanding completion
Understanding blocks vs unlimited plans
Understanding provider backbones
Comparing indexer concepts
Understanding missing articles
Understanding SSL and Usenet provider settings
General Usenet terminology
Provider or indexer availability questions, if allowed by rules
Use tool-specific subs for:
| Topic | Better place to ask |
|---|---|
| SABnzbd categories, queue, repair, unpack, scripts | /r/SABnzbd |
| NZBGet configuration, performance, scripts, queue behavior | /r/nzbget |
| Sonarr monitoring, imports, quality profiles, matching | /r/sonarr |
| Radarr monitoring, imports, quality profiles, matching | /r/radarr |
| Lidarr matching, imports, and organization settings | /r/lidarr |
| Prowlarr indexer sync, app integration, API issues | /r/prowlarr |
| General *arr stack issues | /r/Servarr |
| Docker pathing and permissions for *arr apps | /r/Servarr, tool-specific subs, or official docs |
| NZBHydra2 metasearch issues | /r/nzbhydra |
| Bazarr automation | /r/bazarr |
Many problems look like “Usenet problems” at first but are actually client, path, permission, category, or automation configuration problems.
Choosing Your First Setup
If You Want the Easiest Start
Use a simple Usenet search experience or an all-in-one provider/search service.
This is the least complex path.
You can learn:
Basic search
Basic provider concepts
Basic retention concepts
What results look like
What failures look like
Move to a modular setup later if you want more control.
If You Want More Control
Use:
One provider
One indexer
One client, usually SABnzbd or NZBGet
This teaches you the core pieces without going straight into automation.
Recommended order:
Choose provider.
Install client.
Add provider server settings.
Test connection.
Add indexer/search method.
Test a manual workflow.
Learn logs and errors.
Add more only when needed.
If You Want Automation
Start only after the basics work.
A beginner automation stack usually looks like:
Provider
Indexer
SABnzbd or NZBGet
Prowlarr or NZBHydra2
Sonarr/Radarr/Lidarr/Readarr depending on use case
Before adding automation, confirm:
Your provider works in your client.
Your indexer returns useful results.
Your client can retrieve articles.
Your client can repair/unpack.
Your folder paths are correct.
Your permissions are correct.
You understand where logs are.
If manual usage does not work, automation will not fix it.
Troubleshooting: What Is Actually Broken?
A lot of beginner troubleshooting comes down to identifying which piece failed.
Search Problem
Likely causes:
Indexer issue
Bad search terms
Indexer account limits
API limit reached
Wrong category
Indexer outage
Prowlarr/NZBHydra2 sync issue
Check:
Indexer account
Indexer status
Prowlarr/NZBHydra2 logs
API key
Categories
App-indexer connection
Better places to ask:
/r/usenet for general indexer concepts
/r/prowlarr for Prowlarr issues
/r/nzbhydra for NZBHydra2 issues
Indexer support forum/Discord if available
Provider Connection Problem
Likely causes:
Wrong server address
Wrong port
SSL mismatch
Wrong username/password
Expired account
Too many connections
VPN/routing issue
Provider outage
Check:
Provider dashboard
Client server settings
SSL port
Account status
Connection count
Client logs
Better places to ask:
Provider support
/r/SABnzbd or /r/nzbget if the client error is unclear
Retrieval Fails or Articles Are Missing
Likely causes:
Missing articles
Retention issue
Completion issue
Takedown
Bad NZB
Stale indexer result
Provider/backbone limitation
Check:
Age of result
Whether other results work
Whether another indexer has a different result
Whether another provider/block fills missing articles
Client logs
Better place to ask:
Do not include specific content titles.
Repair or Unpack Problem
Likely causes:
Not enough repair data
Corrupt result
Passworded archive
Disk full
Bad folder permissions
Path issue
Client setting issue
Check:
SABnzbd/NZBGet logs
Disk space
Permissions
Complete/incomplete folders
Repair/unpack settings
Better places to ask:
Automation Import Problem
Likely causes:
Wrong category
Wrong root folder
Wrong path mapping
Docker volume mismatch
Permissions issue
Completed item not visible to automation app
Remote path mapping missing
Quality/profile mismatch
Naming/matching issue
Check:
Sonarr/Radarr/Lidarr logs
SABnzbd/NZBGet category
Completed folder
Root folder
Docker compose paths
File ownership and permissions
Remote path mappings
Better places to ask:
Official Servarr Wiki
TRaSH Guides
Common Beginner Mistakes
Starting with automation too early
Automation is useful, but it creates more failure points.
Get the basic provider + client + indexer workflow working first.
Confusing providers and indexers
A provider gives access.
An indexer helps search.
A client retrieves articles.
Automation coordinates the workflow.
These are separate jobs.
Buying too much too early
Do not buy several providers, several blocks, and several indexers before you understand the setup.
Start with one provider, one indexer/search method, and one client.
Add more only when you know what problem you are solving.
Choosing only by price
The cheapest plan is not always the best plan.
Pay attention to:
Retention
Completion
Backbone
Support
Renewal price
Server locations
SSL support
Block vs unlimited options
Using too many connections
More connections do not always mean better speed.
Start with the provider’s recommended connection count and adjust only if needed.
Ignoring logs
Logs matter.
Before asking for help, check the logs in:
SABnzbd
NZBGet
Prowlarr
NZBHydra2
Sonarr
Radarr
Lidarr
Readarr
Your provider dashboard, if relevant
Mixing Docker paths
Many automation problems are really path problems.
For Docker setups, make sure your download client and automation apps see the same folders in compatible ways.
If your client saves something to one path but Sonarr/Radarr sees a different path, imports may fail.
Read the Servarr Docker and path guidance before posting.
What to Include When Asking for Help
Include enough detail for people to help.
For Provider / Usenet Questions
Include:
Provider name
Client name
SSL enabled or not
Server/port used, without sharing credentials
Connection count
Error message
Whether the issue affects all attempts or only some
Whether other results work
What you already tried
Do not include specific content titles.
For Indexer Questions
Include:
Indexer name, if allowed
Whether the issue is search, API, login, categories, or NZB retrieval
Whether you are using Prowlarr or NZBHydra2
Error message
Whether the issue affects one indexer or multiple
Whether the indexer account is free, trial, VIP, expired, or rate-limited
Do not ask for invites if prohibited by the rules.
For SABnzbd / NZBGet Questions
Include:
Client name and version
Operating system
Install type: native, Docker, NAS, seedbox, etc.
Provider settings, without credentials
Error message
Queue status
Whether repair/unpack failed
Disk space
Folder paths
Relevant log lines
Ask in:
For Sonarr / Radarr / Lidarr / Readarr / Prowlarr Questions
Include:
App name and version
Operating system
Install type: native, Docker, NAS, seedbox, etc.
Download client used
Indexer manager used, if any
Category settings
Root folder
Download folder
Remote path mappings, if any
Relevant logs
What changed recently
Ask in:
Suggested Reading Order
If you are new, read in this order:
This page
SABnzbd or NZBGet docs, depending on your client
Servarr Wiki if you are using automation
TRaSH Guides if you are tuning an automation stack
Useful Communities and Docs
Usenet
NZB Clients
Automation / *arr Stack
Final Advice
Start with the simplest setup that matches your comfort level.
If you are brand new, use a simple search experience or a basic provider + client + indexer setup.
If you want more control, move to a modular setup.
If you want automation, build toward the *arr stack after the basics work.
Do not add complexity until you understand what problem it solves.
When asking for help, include your setup, logs, error messages, and what you already tried. Do not include specific content titles or anything that violates subreddit rules.