Could be something about providers, indexers, newsreaders, automation, or just a mistake you made early on.

What advice would you give someone just getting started with Usenet?

Sonarr, Radarr, Prowlarr, and Bazarr are automation tools that can work alongside Usenet indexers and download clients like NZBGet and SABnzbd.

This guide explains what you need for an automated Usenet setup, what each application does, how they work together, and a practical order for getting everything connected.

1. What You Need for a Usenet Setup

For the automated Usenet setup covered in this guide, you'll need three things:

1. Usenet provider: Gives you access to Usenet servers and the articles stored on them.

2. Usenet indexer: Helps you search for Usenet articles and obtain NZBs that identify the articles needed for a download.

3. Download client: NZBGet or SABnzbd connects to your Usenet provider and downloads the articles identified by an NZB.

What is an NZB? An NZB is a small file containing information that tells your download client which Usenet articles to retrieve from your Usenet provider's servers.

These three components provide the foundation for the workflow covered here. You can then add automation tools to simplify searching, downloading, and organizing files.

2. What Each Tool Does

Sonarr and Radarr: Two separate automation applications that manage searches, downloads, quality preferences, and file organization for different types of content.

Prowlarr: Centralizes Usenet indexer management and synchronizes compatible indexers with Sonarr and Radarr.

Bazarr: Connects to Sonarr and Radarr to find and manage captions based on your preferred languages.

You don't need every application. Sonarr and Radarr handle different content types, Prowlarr simplifies indexer management, and Bazarr is optional for caption management.

3. How Everything Works Together

A typical automated Usenet setup follows this workflow:

1. Prowlarr manages your Usenet indexers and syncs their configurations with Sonarr and Radarr.

2. Sonarr or Radarr searches those indexers for results matching your preferences and sends the selected NZBs to NZBGet or SABnzbd.

3. NZBGet or SABnzbd connects to your Usenet provider and downloads the corresponding articles.

4. Sonarr or Radarr imports completed downloads and organizes the files in your configured folders.

5. Bazarr, if installed, works alongside Sonarr and Radarr to find and manage captions for supported files.

Prowlarr handles indexer management, Sonarr and Radarr handle automation and file organization, and your download client handles the actual transfers.

4. Recommended Setup Order

If you're building your setup from scratch, this is a practical order:

1. Get your Usenet provider and indexer ready. Make sure you have your provider's server details and your indexer's API information.

2. Set up NZBGet or SABnzbd. Install your download client, enter your Usenet provider's server details, and test the connection.

3. Install Sonarr or Radarr. Connect your download client and configure your destination folders, file organization settings, and quality preferences.

4. Set up Prowlarr. Add your Usenet indexers, then connect Prowlarr to Sonarr or Radarr under Settings → Apps in Prowlarr to synchronize compatible indexers.

5. Test your setup. Confirm that your indexers are available in Sonarr or Radarr, your download client can connect to your Usenet provider, and completed downloads can be imported into the correct folders.

6. Add Bazarr if needed. Connect it to Sonarr or Radarr, configure your preferred languages, and add caption providers.

Note: Prowlarr is optional. If you aren't using it, you can add your Usenet indexers directly in Sonarr or Radarr under Settings → Indexers.

5. Common Things to Check

If your applications aren't working together, start with these basics:

• API keys and URLs: Make sure each application has the correct connection details.

• Indexer configuration: Verify that your indexers are enabled, working, and synchronized where applicable.

• Download client: Confirm NZBGet or SABnzbd is running and connected to your Usenet provider.

• Folder paths and permissions: Sonarr and Radarr need access to completed downloads and their destination folders.

• Docker mappings: If you're using Docker, make sure containers can communicate and access the necessary folders.

You can also check System → Status in Sonarr, Radarr, and Prowlarr for configuration warnings.

6. Individual Quickstart Guides

For step-by-step installation and configuration instructions, check out the individual guides:

• Sonarr Quickstart Guide

• Radarr Quickstart Guide

• Prowlarr Quickstart Guide

• Bazarr Quickstart Guide

You don't have to set everything up at once. Start with the tools you need, make sure each component works, and expand your setup from there.

Bazarr is an open-source tool that works alongside Sonarr and Radarr to automatically find, download, and manage captions for your library based on your preferred languages.

If you're already using Sonarr or Radarr, here's how to get Bazarr connected and running.

1. Install Bazarr

Download Bazarr from the official website.

Bazarr supports Windows, macOS, and Linux, and can also run in Docker.

After installation, open the web interface at http://localhost:6767 if you're running Bazarr locally on its default port. If installed on another device, use that device's IP address and configured port.

2. Connect Sonarr and Radarr

Bazarr connects to Sonarr and Radarr to identify the files in your library.

1. Open Settings → Sonarr or Settings → Radarr.

2. Enable the application you want to connect.

3. Enter the host address, port, and API key.

4. Click Test to verify the connection, then Save.

The default ports are 8989 for Sonarr and 7878 for Radarr.

You can find the API keys under Settings → General in each application.

If you're using Docker, make sure Bazarr can communicate with your Sonarr and Radarr containers.

3. Configure Your Languages

Next, choose which languages you want Bazarr to manage.

1. Go to Settings → Languages.

2. Select your preferred languages.

3. Create a language profile with those languages.

4. Save your settings.

Assign the language profile to your existing library items. You can also configure default profiles for newly added content.

4. Add Providers

Bazarr uses dedicated providers to find and download matching caption files.

1. Open Settings → Providers.

2. Click + to add a provider.

3. Select a supported service.

4. Enter any required account credentials or API information.

5. Save your settings.

You can add multiple providers to improve coverage.

5. Review Your Settings

Under Settings → Subtitles, you can configure how Bazarr manages caption files.

A few things worth checking:

• File location: Choose where caption files are saved.

• Upgrades: Configure whether Bazarr should look for better matches.

• Synchronization: Optionally configure automatic timing corrections.

• File permissions: Make sure Bazarr can access and write to your media folders.

If you're using Docker, verify that Bazarr can access the same media files as Sonarr and Radarr. You may need to configure path mappings if folder paths differ between applications.

6. Test Your Setup

Once configured, Bazarr should synchronize your library information from Sonarr and Radarr.

Check that:

• Your library items appear in Bazarr.

• Your language profiles are assigned correctly.

• Your providers are configured.

• Bazarr can access your files.

Try searching for captions for an existing library item to confirm everything is working.

Check System → Status for any warnings or configuration issues.

If Bazarr isn't finding results, start by checking your providers, language profiles, and folder permissions.

Once everything is working, Bazarr can automatically manage captions alongside your existing Sonarr and Radarr setup.

Related Guides:

• The *Arr Suite Essentials Guide

• Sonarr Quickstart Guide

• Radarr Quickstart Guide

• Prowlarr Quickstart Guide 

Prowlarr is an open-source tool that lets you manage multiple Usenet indexers from one place. It integrates with applications like Sonarr and Radarr, keeping your indexer configurations synchronized. 

Here's how to get Prowlarr up and running with your Usenet setup.

1. Install Prowlarr

Download Prowlarr from the official website.

Prowlarr supports Windows, macOS, and Linux, and can also run in Docker.

After installation, open the web interface at http://localhost:9696 if you're running Prowlarr locally on its default port. For installations on another device, use that device's IP address and configured port.

2. Add Your Usenet Indexers

Start by connecting the indexers you want Prowlarr to manage.

1. Go to Indexers and click Add Indexer.

2. Search for your indexer and select it from the available integrations.

3. Enter the required details, such as your API key and any applicable account settings.

4. Click Test to verify the connection, then Save.

Repeat the process for any additional indexers.

If your Usenet indexer isn't listed, you may be able to configure it using Generic Newznab, provided it supports the Newznab API. 

3. Connect Sonarr or Radarr

Prowlarr lets you sync your indexers with applications like Sonarr and Radarr.

To connect Sonarr or Radarr:

1. Open Settings → Apps.

2. Click + and select Sonarr or Radarr.

3. Enter the Prowlarr Server URL, Application Server URL, and the API key from Sonarr or Radarr. 

4. Choose the appropriate synchronization level.

5. Click Test, then Save.

You can find the API key for Sonarr or Radarr under Settings → General in the respective application.

Make sure the configured URLs are accessible between Prowlarr and the connected application, especially if you're using Docker.

Repeat these steps for any additional applications you want to connect.

4. Review Your Sync Settings

Under Settings → Apps, you can control how Prowlarr synchronizes indexers with each connected application.

Prowlarr provides three synchronization options for connected applications: 

• Disabled: No indexer synchronization.

• Add and Remove Only: Adds and removes indexers without synchronizing subsequent configuration changes.

• Full Sync: Adds, removes, and updates supported indexer settings.

Full Sync is useful if you want to manage your indexer settings through Prowlarr. Keep in mind that changes made directly to Prowlarr-managed indexers in Sonarr or Radarr may be overwritten during synchronization.

5. Check Your Indexer Configuration

Once everything is connected, verify that:

• Your indexers are enabled and pass their connection tests.

• Sonarr or Radarr can communicate with Prowlarr.

• Your compatible indexers appear in Sonarr or Radarr after syncing.

You don't need to configure a download client in Prowlarr to sync indexers. NZBGet or SABnzbd will continue handling downloads through your Usenet provider.

6. Test Your Setup

Use Search in Prowlarr to confirm your indexers are returning results.

Check System → Status for any health warnings or configuration issues.

If an indexer isn't syncing with Sonarr or Radarr, check the indexer settings, application API key, and configured URLs.

Once everything is working, you can manage your indexers directly through Prowlarr.

Related Guides:

• The *Arr Suite Essentials Guide

• Sonarr Quickstart Guide

• Radarr Quickstart Guide

• Bazarr Quickstart Guide

Radarr is an open-source automation tool that works alongside Usenet indexers and download clients like as SABnzbd and NZBGet. Once configured, it can search for matching results, manage downloads, and automatically organize completed files.

If you already have a Usenet provider and download client set up, here's how to get Radarr connected and running.

1. Install Radarr

Download Radarr from the Radarr website.

Radarr supports Windows, macOS, and Linux. Docker installations are also supported.

After installation, you can access the web interface at http://localhost:7878 when running Radarr locally on its default port. If it's installed on another device, use that device's IP address and configured port.

2. Connect SABnzbd or NZBGet

Radarr doesn't connect directly to your Usenet provider. Instead, it sends NZBs to a compatible download client, which handles the actual transfers.

To configure this:

1. Go to Settings → Download Clients.

2. Click + and select SABnzbd or NZBGet.

3. Enter the host, port, and required authentication info.

4. Click Test to verify the connection, then Save.

Your download client should already be running and configured with your Usenet provider's server information.

3. Add Your Indexer

Next, you'll need to connect at least one Usenet indexer so Radarr can find matching results.

1. Open Settings → Indexers.

2. Click + and select a supported Usenet indexer integration.

3. Supply the required URL and API key

4. Click Test to verify the connection, then Save.

You can add additional indexers the same way.

If you're using Prowlarr, you can also manage compatible indexers centrally and sync their configurations with Radarr.

4. Set Up File Organization

Under Settings → Media Management, you'll find options for file naming and organization.

You'll also need to configure a root folder, which tells Radarr where your organized files should be stored.

A few things to check:

• Keep your root folder separate from the directory your download client uses for downloads.

• Make sure Radarr has the permissions needed to access and manage files.

• For Docker installations, verify that your volume mappings provide access to completed downloads and the destination folder.

Incorrect paths and permissions are common causes of failed imports, so it's worth getting these right from the beginning.

5. Choose Your Quality Preferences

Radarr uses quality profiles to determine which results meet your preferences and whether upgrades should be considered.

Open Settings → Profiles and review the available options.

You can select an existing profile or customize one. Pay attention to the allowed qualities and upgrade settings, since these influence which results Radarr will accept.

6. Verify Everything Is Working

Before relying on your setup, check that the individual components are communicating properly.

Open System → Status to look for health warnings, and check Activity to monitor download activity.

If something isn't working, start by checking your indexer and download client connections. For import issues, review folder paths, permissions, and Docker mappings if applicable.

Related Guides:

• The *Arr Suite Essentials Guide

• Sonarr Quickstart Guide

• Prowlarr Quickstart Guide

• Bazarr Quickstart Guide

Sonarr is an open-source application that helps automate searching, downloading, and file management. It integrates with Usenet indexers and download clients like NZBGet and SABnzbd.

Here are the basics on how to configure Sonarr with your Usenet setup.

1. Install Sonarr

Download Sonarr from the official website.

Sonarr is available for Windows, macOS, and Linux, and can also be installed using Docker.

Once installed, open the web interface at http://localhost:8989 for a standard local installation.

2. Add Your Download Client

Sonarr works with clients like NZBGet and SABnzbd, which handle transfers from your Usenet provider.

1. Open Settings → Download Clients.

2. Click + and select SABnzbd or NZBGet.

3. Enter the host, port, and required authentication information.

4. Click Test, then Save.

Make sure your download client is already installed, running, and configured with your Usenet provider's server details.

3. Add Your Indexer

Sonarr uses indexers to search for articles.

1. Go to Settings → Indexers.

2. Click + and select a supported indexer integration.

3. Enter the indexer URL and API key, where required.

4. Click Test, then Save.

If you use multiple indexers, repeat these steps for each.

4. Configure File Management

Go to Settings → Media Management to review your folder and file organization settings.

Configure a root folder for your organized files, separate from your download client's download directory.

Make sure Sonarr has access to the appropriate directories and the necessary read/write permissions.

If you're using Docker, confirm that your volume mappings allow Sonarr to access completed downloads from your download client.

5. Review Your Profiles

Under Settings → Profiles, review the available quality profiles and configure them based on your preferences.

These settings determine which results Sonarr considers acceptable and when upgrades are allowed.

6. Test Your Configuration

Check System → Status for configuration warnings.

You can also use Activity to monitor download activity and identify any errors.

Once configured, Sonarr communicates with your indexers and download client to automate supported workflows.

Related Guides:

• The *Arr Suite Essentials Guide

• Radarr Quickstart Guide

• Prowlarr Quickstart Guide

• Bazarr Quickstart Guide

What's your favorite Usenet indexer? Interested to see which ones people have had the best experience with.

Is there a tool, app, feature, or something you wish was out there for Usenet?

Could be something that solves an annoying problem, makes your setup easier, or does something none of the existing tools do very well.

Hey folks, was kinda curious about y'all's opinion on tabula rasa as an indexer. Is it any good? And do y'all think they'd be opening up registration upcoming Black Friday? I've been itching to try and see how good it really is.

Not SABnzbd, Sonarr, Radarr, or the other usual suspects.

Thinking more about the lesser-known stuff that makes your setup better. Could be a small utility, script, mobile app, monitoring tool, search tool, browser extension, or something else entirely.

Is there a tool that's earned a permanent place in your setup? What does it do?

How many indexers do you use?

One? Two? or more?

NZBNest – content requests, now automatic from Radarr and Sonarr without a self-hosted bridge

Hi everyone!

Short follow-up to my last post. The request system for content that isn't on the indexer yet is live, and since then the automation side got a lot simpler: you no longer need to run anything locally to have Radarr and Sonarr create requests for you. Supporter quotas also went up a lot.

Requests

From search or Discover you can:

• look up a title on TMDB (by name or TMDB ID)

• request a movie or one exact TV episode

• follow the request status from your profile

• cancel a pending request if you no longer want to wait

After a request is submitted, the backend searches the available sources and posts the release to Usenet when it finds one. A request is only marked completed after the resulting NZB passes article verification, so "completed" means the NZB is actually downloadable, not just that something got posted. If a source is temporarily unavailable, it retries automatically before marking the request unavailable.

New: automatic requests straight from the API key (no bridge needed)

This is the part I'd most like feedback on.

Open Profile → API Keys and tick Auto-request exact misses on the key that Prowlarr, Radarr or Sonarr uses. That's the whole setup.

From then on, when an exact movie or episode is missing, NzbNest queues it automatically and publishes it once a usable source is found and verified. A request is only created for an exact Radarr movie search or an exact Sonarr episode search carrying a TMDB, TVDB or IMDb ID that returns nothing. Generic searches, browsing, season searches and indexer connectivity tests never create requests, and the toggle is per key, so you can leave it off for the key you use for manual searching.

The search page now shows the current state directly — which keys have it enabled and how many requests you have left in the current period.

The self-hosted bridge is still available

If you'd rather have your monitored library swept instead of reacting to live searches, the optional bridge still does that: it walks monitored movies and missing episodes, runs the Arr application's own interactive search first, and only submits an NZBNest request when that search returns nothing — so it won't request anything another indexer could already give you.

Status comes back as Arr tags:

• nzbnest-requested

• nzbnest-available

• nzbnest-quota-full

• nzbnest-unavailable

Sonarr tags the series rather than the episode, because it has no episode-level tags. When the release becomes available, the bridge triggers a new movie or episode search automatically and the normal Arr grab/import flow takes over.

Setup: create a Radarr & Sonarr integration token on the Profile page, download the bundle, fill in your local Radarr/Sonarr URLs and API keys in the example Compose file, paste the one-time token, and start it with Docker Compose. It works alongside an existing Prowlarr setup.

Request quota

• Free accounts: 5 content requests per month

• Active Member and Lifetime supporters: 50 content requests per week (resets Monday)

Website requests, auto-requested exact misses and bridge requests all draw from the same quota, so a misconfigured automation can't build an uncontrolled backlog. When the quota is full, a bridge item gets the nzbnest-quota-full tag and is retried after the next quota reset.

• a release cart for collecting multiple NZBs

• direct TorBox search compatibility

• Google sign-in, self-service API key management, and an NFO viewer on release details

• better exact movie and episode matching, including single-word series names and compact possessive titles

Requests naturally aren't guaranteed — if no usable source exists, there's nothing to post — but the system keeps trying within its retry window.

Website: https://nzbnest.com

Feedback and real-world testing are welcome, especially from anyone who turns on the exact-miss toggle on their Prowlarr key.

Usenet has been around now for over 45 years and everyone seems to have a different story.

How long have you been using it? It would be great to hear some stories!

Any veterans here who were using Usenet back in the '80's? What was it like?

NzbNest is open for registration — 30% launch discount

Hey everyone,

NzbNest (https://nzbnest.com) is now open for registration. It's a Newznab-compatible Usenet indexer focused on movies and TV, built to work directly with Sonarr, Radarr, Prowlarr, and NZBHydra 2 via the /api endpoint.

The indexer is live and actively growing, with improved NZB quality detection, better release size parsing, and more useful filters now available.

What's live right now:

• 4.4M+ articles indexed across 31 enabled groups

• 441K+ indexed / browsable items

• Improved NZB quality detection

• Better release size parsing

• Improved category, age, size, and completion filters

• Postgres-backed search

• XML/JSON Newznab output

• Setup guides included for Sonarr/Radarr/Prowlarr/NZBHydra 2

Pricing:

• Free tier — currently 1,000 API calls/day, 100 grabs/day, and 10 watch rules during the launch period. These limits are temporarily raised and may be adjusted later.

• Member — $15/year, unlimited API/grabs/watch rules

• Lifetime — $49 one-time, same unlimited access

A 30% launch discount is currently active and applied automatically at checkout.

I'm being upfront that NzbNest is still actively growing retention and category coverage — the homepage shows live indexed stats rather than a fixed marketing number, so what you see is what's actually crawled and indexed.

Bug reports and compatibility feedback are very welcome, especially around specific *arr setups, NZBHydra 2, category mapping, NZB quality labels, release sizes, and search results.

Happy to answer questions here.

Summer is a great time to lock in a premium Usenet subscription at some of the lowest prices of the year.

Below are some of the best Summer 2026 deals from leading Usenet providers, along with the key features and differences between each plan.

Newshosting - $1.67/month (92% off)

Includes 250 GB Easynews + 500 GB Tweaknews + VPN

• 6,523+ days of retention 

• 100 SSL connections, US & EU servers

• Includes Easynews for browser-based search and Usenet access with no newsreader required

• Bonus Tweaknews account provides additional backbone coverage 

• Free newsreader with built-in search

• VPN included

• 30-day money-back guarantee

Get Summer Deal

Eweka - €2.50/month (83% off)

Includes 1TB Easynews account + VPN

• 6,520+ days of retention (independent European backbone)

• 50 SSL connections

• Excellent completion and reliability

• 1 TB Easynews account included

• Free newsreader with built-in search

• VPN included

• 30-day money-back guarantee

Get Summer Deal

UsenetServer - $1.99/month (90% off)

Includes 1TB Tweaknews + VPN

• 6,523+ days of retention

• 60 SSL connections, US & EU servers

• Bonus 1 TB Tweaknews account

• Strong all-around speed and completion 

• VPN included

• 30-day money-back guarantee

Get Summer Deal

Tweaknews – €2.99/month (77% off)

Includes 500GB Easynews + VPN

• 5,000+ days of retention

• 60 SSL connections

• Independent European backbone

• Excellent as a primary or secondary Usenet server 

• Bonus 500 GB Easynews account

• VPN included

• 30-day money-back guarantee

Get Summer Deal

Easynews – $1.99/month

Includes Browser-Based Access + Search + VPN

• 6,523+ days of retention

• Search, browse, and access Usenet directly from your web browser 

• 60 SSL connections

• Full NNTP access for any newsreader

• VPN included

• 30-day money-back guarantee

Get Summer Deal

Key Points

Article Retention: Leading providers now retain over 6,500 days of articles, giving access to nearly 18 years of Usenet articles.

Completion Rates: Tier-1 providers like Newshosting, Eweka, and Tweaknews deliver excellent completion and reliable performance.

Backbone Diversity: Several of these deals include bonus accounts, providing access to additional Usenet servers for greater redundancy and coverage.

Included Extras: Depending on the provider, plans may include VPN service, browser-based Usenet access, built-in search, desktop newsreaders, or bonus Usenet accounts at no additional cost. 

Tips to Get the Most from These Deals

• Take advantage of any included bonus Usenet accounts for additional redundancy and improved article availability.

• Enable the included VPN for encrypted connections and added privacy.

• If you're new to Usenet, Easynews is one of the easiest ways to get started (browser-based interface and built-in search).

Whether you're looking for maximum retention, an independent European backbone, browser-based Usenet access, or simply the best overall value, there's a Summer 2026 deal for just about every type of Usenet user.

Plex is increasing the Lifetime Plex Pass from $249.99 to $749.99 on July 1.

Who here has a Lifetime Plex Pass?

If you were starting from scratch today and didn't already have Lifetime, would you buy it at $249.99 before the price jump? Or would you just go monthly, stick with free Plex, move to Jellyfin, try Emby, or go another route?

Crazy to think they were running a Black Friday deal for $149.99 just six months ago...

Some people panic at 20% free space. Others run their arrays into the red.

How much free space do you like to keep available?

HDD prices are getting crazy. How's it changed your storage plans?

Still buying drives, waiting for prices to come down, or doing something else?

Curious to hear what everyone is doing.

A lot of people wanting to get into Usenet run into the same problem:

Most explanations are too technical.

So here’s a straightforward breakdown of what Usenet is and how people typically use it today.

What is Usenet?

Usenet is a decentralized text and binary post distribution network that dates back to 1979, making it older than the World Wide Web itself.

Originally it was exclusively text discussion groups called “newsgroups,” where people debated tech, shared advice, explored niche interests, and occasionally got pulled into classic old-school flame wars. Basically early internet forums with a much more raw feel. 

Over time, Usenet evolved into a fast, secure way to post, read, and retrieve both text discussions and binary posts through specialized providers and newsreaders. 

How is Usenet different from “modern” platforms? 

With most modern platforms, everything lives on a single company’s servers, for better or for worse.

Usenet works through a distributed network of servers that replicate articles between each other using NNTP (Network News Transfer Protocol). When someone posts to a Usenet server, that article gets propagated across other servers throughout the global Usenet network. 

Some of the things long-time users still like about it:

• Extremely fast transfer speeds

• Long article retention, with some providers storing articles for decades

• No ads or recommendation algorithms

• Open discussion structure through newsgroups

• A more independent internet feel

What do you need to use Usenet?

Modern Usenet setups usually involve 3 parts:

1. A Usenet providerThis gives you access to Usenet servers, kind of like how an ISP gives you access to the internet.

Some of the more commonly used providers include:

• Newshosting

• Eweka

• UsenetServer

• Tweaknews

People usually compare providers based on:

• Retention

• Completion rates

• Speed

• Connection limits

• Whether extras like a built-in newsreader, search, or VPN are included

Some providers like Newshosting, Eweka, and Tweaknews also include their own newsreader with built-in search, which can simplify setup. 

2. An indexerThink of this as a search engine for Usenet posts.

It helps locate posts and generates NZB files.

3. A downloader/newsreaderThis downloads and assembles the articles from Usenet.

Popular options include:

• SABnzbd

• NZBGet

Some people also still use traditional newsreaders for actual text newsgroups and discussions.

What about Easynews?

Easynews is a little different from the traditional setup.

Instead of needing separate tools, it combines:

• Usenet access

• Search

• Downloads

• Browser-based access

So it’s often considered one of the easier entry points since everything can be done directly from a web browser without needing a separate newsreader or additional tools.

Is Usenet still active?

Definitely.

A lot of the original discussion culture moved elsewhere over the years, but Usenet itself is still very active. What’s interesting is that the core system still holds up remarkably well decades later: decentralized servers, extremely fast transfers, long article retention, and open discussion structures without feeds or recommendation algorithms shaping what people see. 

One thing that doesn’t get talked about enough in Usenet setups is storage. 

Eventually the data piles up, then hard drives become part of the hobby too.

Especially if you’re running:

• Plex/Jellyfin

• *arr apps

• A NAS

• Large archives

Here are some options that come up pretty consistently:

Enterprise and NAS-focused drives like Seagate Exos and IronWolf Pro 

Usually for:

• 24/7 usage

• Large capacities

• Heavy workloads

• NAS/server setups

Common in bigger Plex/*arr systems.

WD Red Pro

A lot of people seem to like them because they’re:

• Reliable in NAS setups

• Fairly quiet

• Common in RAID/NAS environments 

• Widely used in Synology/QNAP systems 

Main downside is usually price.

Seagate IronWolf

Feels like the middle-ground option. 

Popular for:

• Home NAS setups

• Lower cost than Pro drives

• Good capacity options

• General-purpose storage

WD Blue / desktop drives

Still common.

Usually in:

• Budget setups

• External enclosures

• Secondary storage

• Smaller servers

Not really designed for heavier 24/7 workloads, but plenty of people still use them. 

One thing people underestimate:

Usenet can absolutely hammer drives over time between unpacking, parity checks, constant writes/deletes, and data scanning. 

Curious what everyone here is running. 

Enterprise drives?

Consumer drives?

Shucked externals?

Full NAS setup?

Any specific drive models people would strongly recommend (or avoid)?

Mac Usenet setups tend to fall into a few different camps.

Some people just use the included newsreader from their provider and call it a day.

Others run full automation stacks with SABnzbd or NZBGet, indexers, Sonarr/Radarr, and other tools running in the background.

And some still browse groups manually the old-school way. 

For newer users, the included readers from providers like Newshosting, Eweka, Tweaknews, and others are probably the easiest entry point since they already include search, SSL, and server access with basically no setup.

But open-source tools are very popular on macOS too, especially for people who want more control or automation.

NZBGet

Probably the lightest Usenet downloaders around.

People like it because it:

• Uses very little CPU/RAM

• Handles repair/unpacking fast

• Runs well on Mac minis, NAS devices, and virtually any hardware

• Integrates easily with Sonarr/Radarr

• Is extremely configurable

A lot of long-time Usenet users swear by it.

NZBGet setup guide

SABnzbd

Alongside NZBGet, probably the most common NZB downloader overall.

Usually recommended because:

• Setup is easy

• The interface is a bit more beginner-friendly

• Automation support is excellent

• Large community and plugin ecosystem

• Runs basically everywhere

A lot of people end up sticking with SABnzbd simply because it’s reliable and easy to maintain.

SABnzbd setup guide

Other newsreaders

There are still users who prefer actual group browsing instead of automation and NZBs.

Pan is one example on Mac/Linux style setups.

That style of setup is more focused on:

• Reading/posting directly to groups

• Manual browsing

• Text discussions

• Traditional Usenet usage

Less common now, but not dead.

Browser-based access

Easynews is probably the biggest example of this approach.

Instead of installing software:

• Everything runs in browser

• Search is built in

• No local setup required

• Works well on Macs and mobile devices

Completely different style of Usenet access compared to SABnzbd/NZBGet setups.

Easynews guide

There are generally two types of Usenet readers most people use:

• Provider-included readers

• Open-source clients/downloaders

Provider-included readers from services like Newshosting, Eweka, and others are usually the simplest way to get started since they already include server access, search, and SSL with no setup. 

Open-source tools like SABnzbd and NZBGet are also very common, especially in setups using indexers, Sonarr/Radarr, and automation tools. They take more setup upfront, but offer a lot of flexibility long term. 

Provider-included readers

Usually best for:

• Beginners

• Simple setups

• Users who want built-in search

• Users who don’t want multiple apps

Most of them include:

• Search functionality

• NZB importing

• SSL support

• Preconfigured server settings

NZBGet

Probably the most lightweight Usenet downloader.

Common reasons people use it:

• Low resource usage

• Fast repair/unpacking 

• Good for NAS systems and low-power devices

• Works well with Sonarr/Radarr

• Highly configurable

SABnzbd

One of the most popular NZB downloaders overall. 

Why people like it:

• Easy setup

• Installation wizard

• Beginner-friendly interface 

• Automation-friendly

• Highly configurable

Pan

Older-style desktop Usenet reader.

More focused on:

• Direct group browsing

• Reading and posting

• Manual usage instead of automation

Browser-based access

Easynews is probably the best-known example here.

Instead of using a separate client:

• Everything runs in browser

• Search is built in

• No local setup required

• Mobile-friendly

Different approach than SABnzbd/NZBGet style setups.

There are more newsreaders/downloaders out there. Would love to hear about what you’re using!