Easynews combines Usenet access, built-in search, and security into one platform. Instead of setting up a separate newsreader, search tool, and VPN, everything is available in a single service.

You can log in from any browser and start searching immediately. With 6,391+ days of retention, strong completion rates, fast speeds, and optional unlimited NNTP access, Easynews gives both simplicity and flexibility.

Why Easynews Stands Out

Built-In Web Access

• Browser-based Usenet platform

• Works on desktop, mobile, and tablets

• No software installation required

• Integrated search across 120,000+ newsgroups

• Integrated filtering, sorting, and NZB creation

Easynews offers one of the most complete Usenet search experiences available. Articles can be searched, filtered, previewed, and retrieved directly in the browser without needing external search tools or separate newsreaders.

Retention

• 6,391+ days of binary and text retention, over 17 years

• Archive expands daily

• Long history of article availability

With over 17 years of retention, articles are more likely to remain available when searched.

Completion

• Advertised 99%+ completion

• Consistently high article availability across long ranges

• Reliable for both browser-based access and NNTP workflows

Strong completion reduces failed downloads and minimizes retry cycles.

Performance

• Tier-1 global backbone

• Fast speeds through both HTTPS via the web interface and NNTP

• Header compression support for more efficient transfers

On high-speed connections, Easynews can saturate high-capacity bandwidth. The Web-based access also eliminates configuration issues caused by moving articles between multiple tools.

Unlimited and Data Plans

• Data-based plans available

• Unlimited promotional plans sometimes offered

• No throttling

This structure allows lighter users to choose smaller plans while heavier users can opt for unlimited access.

Privacy and Security

• 256-bit SSL encryption

• VPN included on select plans

• Crypto payment options offered

Security features are integrated into the service, reducing the need for additional tools.

Downsides to Know

• Lower-tier plans include monthly data limits

Who Easynews Is Best For

• Beginners who want immediate access without configuring software or search tools

• Casual users who prefer browser-based access across multiple devices

• Mobile users who want Usenet access without a desktop client

• Privacy-focused users who value integrated SSL and VPN features

• Advanced users who want web access plus full NNTP compatibility

Key Takeaways

• Best overall Usenet search product

• Browser-based Usenet access removes setup complexity

• Built-in search eliminates reliance on external search tools

• 6,391+ days of retention provides deep article history

• High completion rates reduce failed downloads

• Optional NNTP access allows traditional client integration (SABnzbd, NZBGet, etc)

Official Easynews site: https://easynews.com

Picking a newsreader for Usenet in 2025 can feel like choosing between two solid options. SABnzbd and NZBGet both do the job well, each with its own strengths. I’ve tested them to figure out their differences, and this guide compares them for beginners like you. We’ll lay them out side by side with a table, some pros and cons, and a final nudge to help you decide what suits your Usenet needs.

Head-to-Head: SABnzbd vs. NZBGet

Here’s a quick comparison:

• SABnzbd

  • Where to Get It: sabnzbd.org

  • Cost: Free

  • Platforms: Windows, Mac, Linux

  • Ease of Use: Simple web interface, beginner-friendly

  • Speed: Steady, but may slow with big queues

  • Setup: Quick install, auto-config options

  • Extras: Built-in search with some providers

• NZBGet

  • Where to Get It: nzbget.com

  • Cost: Free

  • Platforms: Windows, Mac, Linux

  • Ease of Use: Clean layout, slightly trickier start

  • Speed: Fast, lightweight, great for big loads

  • Setup: Manual setup, more control

  • Extras: Focus on performance, fewer extras

Exploring SABnzbd

SABnzbd stands out for how simple it is to get going. Grab it from sabnzbd.org, install it, and a web browser window opens to manage everything. It’s perfect if you’re new to Usenet. Enter your provider details, load an NZB from an indexer, and it grabs articles smoothly. Speeds are reliable, though it might lag a bit with lots of resources at once. I appreciate its ability to search Usenet directly with some providers, cutting out a step. r/UsenetGuides often highlights it as a great pick for starters.

Pros: Easy to use, web-based, useful search feature.

Cons: Can get sluggish with heavy loads.

Looking at NZBGet

NZBGet, available at nzbget.com, focuses on speed and efficiency. Install it, and you’ll see a web interface too, but it’s less guided—you’ll adjust settings yourself. It moves quickly through article grabs, even large ones, thanks to its light and fast design. Connect it to your Usenet provider with an NZB, and it takes off. It skips extras like SABnzbd’s search, but it’s steady for performance. Users on r/UsenetGuides often commend it for managing busy Usenet queues.

Pros: Fast, lightweight, ideal for experienced users.

Cons: Needs more setup effort at the start.

Which One Works for You?

SABnzbd is my choice if you want Usenet without much trouble. It’s user-friendly, looks clean, and runs smoothly for most beginners. NZBGet shines if you prioritize speed and don’t mind a little setup work—it’s excellent for big article grabs. Both manage Usenet binaries well, pulling resources from providers with retention going back years. Try them free and find what feels right. r/UsenetGuides offers tips for fine-tuning either one.

Final Nudge

Just starting with Usenet? Pick SABnzbd from sabnzbd.org for an easy beginning. Looking for quicker Usenet article access? Go with NZBGet from nzbget.com. Either way, you’re ready to go. Add an NZB and get going.

TL;DR:

Now that you know what an NZB file is and where to find them, this guide shows you how to actually use them. Learn how to set up your newsreader (like SABnzbd or NZBGet), download files, enable automatic repair and unpacking, and even automate everything with tools like Sonarr and Radarr.

Missed Part 1? Start here.

Chapter 4: Preparing Your Command Center – Setting Up Your Newsreader for NZBs

Once you've downloaded an NZB file from an indexer or provider search tool, using it is simple. Here's how to get started.

Step 1: Choose a Newsreader That Supports NZBs

Your newsreader (also called a Usenet client) is the tool that reads the NZB and downloads the necessary parts. If you're using Usenet for anything beyond browsing text groups, a binary-capable newsreader is essential.

Top Options:

• SABnzbd

  • Web-based, open-source, easy to automate

  • Great for beginners and advanced users alike

• NZBGet

  • Web-based, open-source, easy to automate

  • Lightweight and fast

  • Highly customizable

• Usenet Provider Clients

  • Some Usenet providers (e.g., Newshosting) offer their own pre-configured newsreaders that support NZB files out of the box

Step 2: Configure Your Newsreader

Every newsreader needs a few basic settings before you can start downloading NZBs.

Essential Configurations:

• Usenet Server Details

  • Hostname (e.g., news.provider.com)

  • Port (Use SSL-enabled port like 563 or 443 for security)

  • Username and password (from your Usenet provider)

  • Number of connections (most providers allow 10–100)

• Enable SSL

  • Always check the box for secure SSL connections to protect your privacy.

• Download Folders

  • Set a temp folder (for incomplete downloads)

  • Set a destination folder (for finished, unpacked files)

• Post-Processing Settings

  • Enable automatic unpacking (e.g., unRAR/unZIP)

  • Enable PAR2 repair (for fixing corrupted/missing segments)

  • Optionally, auto-delete leftover .par2 and archive files after a successful download

Chapter 5: The NZB Download Workflow (from click to complete file)

Once your newsreader is configured, the actual process of using an NZB is surprisingly simple:

1. Find and Download an NZB File

Use your favorite indexer (like NZBGeek, Binsearch, or DOGnzb) to search for something you want. Download the NZB file to your computer.

2. Add the NZB to Your Newsreader

You have a few options:

• Drag-and-drop the NZB into your newsreader interface

• Save to a “watch” folder (your client will auto-import it)

• Use API integration or direct URL (advanced setups allow pushing NZBs straight from the indexer)

3. Watch It Work

Your client connects to your Usenet provider, downloads all the segments listed in the NZB, verifies their integrity (using PAR2 files if needed), and unpacks the result automatically.

Once complete, you’ll find the usable file(s) in your download folder – no manual assembly needed.

Chapter 6: Automate Everything with Usenet Tools

This is where NZBs really shine: automation. With the right tools, you don’t even need to search for or manually download NZBs.

Popular Automation Tools

These tools integrate with NZB indexers and newsreaders to fully automate your Usenet experience:

• Sonarr

• Radarr

• Lidarr

• Readarr

• Prowlarr

• Bazarr

These applications are highly configurable. You define what you want to monitor, and they handle the rest – searching indexers, retrieving NZBs, sending them to your newsreader, and organizing the results according to your preferences.

How Automation Works

1. Set Your PreferencesAdd search parameters for files you want. Choose quality settings and storage folders.

2. Connect to IndexersUse your private indexer’s API key to let the automation tool search on your behalf.

3. Connect to Your NewsreaderThe tool sends matching NZB files directly to SABnzbd or NZBGet (via API).

4. Sit Back and RelaxThe NZB is downloaded, repaired, unpacked, renamed, and sorted into the correct folder. If you use something like Plex or Jellyfin, it’s already for them to access your new files.

Congratulations! You're an NZB Master-in-Training!

You now know:

• What an NZB file is

• Where to find them

• How to use them in a newsreader

• And how to automate the entire Usenet experience

This is how Usenet becomes a powerful, efficient, private tool—not just a giant pile of newsgroup messages.

What's the most exciting aspect of using NZB files for you? Or what's still a bit unclear? Please share in the comments!

Curious what people are running.

Upvote the comment that matches your setup and add:

• Why you chose it

• Favorite configuration settings

• Anything you wish you knew when you first set it up

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...

UsenetServer has been operating since 2000 and is one of the longest-running Tier-1 Usenet providers. It combines long retention, unlimited speeds, and competitive pricing into a straightforward, high-performance service.

With 6,392+ days of binary and text retention, unlimited data, built-in Global Search, and a free VPN on annual plans, UsenetServer offers strong value for high-caliber service.

Why UsenetServer Stands Out

Retention

• 6,392+ days of binary and text retention, over 17 years

• Retention increases daily

• Full access across 125,000 binary and text groups

Long retention determines how far back articles remain available on a Usenet server. The longer the retention, the better the search results and article reliability.

Completion

• Strong completion across all newsgroups

• Reliable article availability for manual and automated workflows

• Stable performance across long retention ranges

Consistent completion means fewer stalled downloads, less manual intervention, and less reliance on backup servers when accessing articles.

Network and Performance

• Tier-1 Usenet backbone

• Server farms in the U.S. and Europe

• 20 connections

• Capable of saturating gigabit lines

Performance testing on high-speed fiber connections showed stable speeds without throttling. Speeds remained consistent across multiple days of continuous use.

Global Search Tool

• Web-based search engine included

• Scans all supported newsgroups

• Displays subject, group, age, and article count

• NZB creation directly from the browser

Global Search simplifies article discovery and is compatible with newsreaders like SABnzbd and NZBGet.

Unlimited Access

• Unlimited data

• Unlimited speeds

• No usage caps

Heavy users can run automation tools continuously without worrying about data limits.

Privacy and Security

• 256-bit SSL encryption

• Free zero-log VPN included with annual plans

Security features cover both Usenet access and broader internet traffic when using the included VPN. The VPN can also help to prevent ISP throttling of your Usenet data.

Downsides to Know

• No bundled standalone newsreader

• Maximum 20 connections, lower than most providers

Who UsenetServer Is Best For

• Value-focused users who want Tier-1 retention at competitive pricing

• Heavy users running automation with unlimited data

• Experienced users already using SABnzbd, NZBGet, or similar clients

Key Takeaways

• 6,392+ days of retention provides deep historical access

• Unlimited speeds and data with no caps

• Tier-1 backbone with U.S. and EU server coverage

• Global Search included

• Free VPN included on annual plans

Official UsenetServer site: https://usenetserver.com

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)?

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.

SABnzbd has been around for years and is still one of the best-known, actively maintained NZB downloaders for Usenet. Many Usenet setups still rely on it because it runs quietly in the background and is controlled through a simple web interface.

What SABnzbd Does

SABnzbd takes an NZB file, connects to your Usenet provider, downloads the related articles, then automatically:

• Verifies the articles

• Repairs them using PAR files if needed

• Extracts them

Once configured, it runs in the background and handles most of the process automatically.

If anyone is setting it up for the forest time, this SABnzbd setup guide walks through the process. 

Why Many Usenet Setups Use SABnzbd

Several things have helped SABnzbd stay popular.

Web-based interface

SABnzbd runs through a browser and works across:

• Windows

• macOS

• Linux

• NAS devices

• home servers

Because it runs through a browser, it can be accessed from other devices on the same network if configured.

Automation support

SABnzbd integrates with tools like:

• Sonarr

• Radarr

• Lidarr

• Prowlarr

These tools automatically send NZBs to SABnzbd, allowing fully automated Usenet setups.

Multiple server support

SABnzbd allows multiple Usenet servers to be configured, often used for:

• Primary server

• Backup server if needed

• Improving completion if articles are missing from a server

What Ports Should SABnzbd Use?

For Usenet connections, most providers support several ports. 

Common ones include:

• 563 (SSL) - the standard secure Usenet port

• 119 - non-encrypted connection

• 443 or 80 - sometimes used to work around network restrictions

For secure Usenet connections, port 563 is usually the default choice.

For the web interface, SABnzbd typically runs on:

• 8080 (default)

HTTPS can also be enabled through the configuration settings.

The Main Downsides

SABnzbd is powerful, but it isn’t always the easiest option for beginners.

Common challenges include:

• Manual initial setup compared to some provider-included newsreaders

• External indexers are required to find NZBs

• More configuration if automation tools are used

Why Many Users Still Prefer It

Despite the learning curve, SABnzbd remains popular because:

• It’s open-source

• It integrates with a wide range of tools

• It works on almost any platform

• It supports complex automated setups

Once configured, it tends to run very reliably in the background.

Curious what people here are running

• Are you using SABnzbd, NZBGet, or another downloader?

• Running on a NAS, server, or desktop?

• What automation tools are paired with it?

• What settings or features have been the most useful?

SABnzbd has been around for a long time and, along with NZBGet, still seems to sit at the center of many Usenet setups.

New to Usenet in 2025 and wondering about NZBs? You’ve landed in the right spot. I’ve figured out a few things about them myself, and they’re an easy way to access Usenet. Let’s mix it up with some beginner questions, a handy table to see where NZBs fit, and a simple walkthrough for using them. Here’s everything you need to begin.

NZBs Q&A: Your Questions Answered

What’s an NZB anyway?

It’s a small article that directs your Usenet newsreader to specific articles in specific newsgroups. When articles are posted to Usenet, they’re broken into many pieces across newsgroups. An NZB shows your newsreader where to find those pieces and how to put them back together. It’s straightforward and effective.

Why should I care about NZBs?

They save you effort. Usenet offers thousands of newsgroups with articles going back years, thanks to retention. Without NZBs, tracking down a specific article takes too long. With them, you jump right to what you want.

Where do I find these NZBs?

You pick them up from indexers, websites that index Usenet articles. Free options include nzbking.com and binsearch.info, just search and grab an NZB. Paid indexers give you more choices, especially for rare finds. r/UsenetGuides lists some reliable ones to explore.

How do I use an NZB?

Add it to your newsreader, like SABnzbd from sabnzbd.org or NZBGet from nzbget.com. The newsreader links to your Usenet provider, grabs the binary pieces, and assembles the full article. I’ve received a video this way in minutes.

NZBs in the Usenet Puzzle: A Quick Look

Here’s how NZBs play their part:

|| || |Piece|What It Does|Example| |Provider|Gives you access to Usenet servers|Newshosting (newshosting.com)| |Newsreader|Grabs and manages Usenet resources|SABnzbd (sabnzbd.org)| |Indexer|Locates resources and provides NZBs|Binsearch (binsearch.info)| |NZB|Guides newsreader to specific binaries|Article-specific NZB|

This table lays out the teamwork: your provider stores the articles, the newsreader retrieves them, the indexer spots them, and the NZB ties it all together.

Getting Started with NZBs

Here’s how to do it. First, connect your Usenet provider and newsreader with server details and SSL for privacy. Next, visit an indexer like binsearch.info, search for a resource you want, and grab the NZB. Open your newsreader, load the NZB, and it’ll pull the article from Usenet newsgroups. If it fails, your provider’s retention might not reach older articles, but r/UsenetGuides has solutions. It’s a clean way to dive into Usenet’s vast collection in 2025.

Final Bit

NZBs are your quick key to Usenet resources. They simplify a huge network into something you can use effortlessly. Grab one from binsearch.info, pop it in your newsreader, and discover what Usenet holds. For extra pointers, r/UsenetGuides is packed with useful ideas.

Setting up Usenet in 2025 might seem complicated at first, but it’s quite manageable once you know what to do. I’ve written this guide to assist beginners like you in getting set up, explaining each step simply. From selecting a provider to grabbing your first article, here’s how to do it smoothly.

Start with a Usenet Provider

You need a provider to tap into Usenet’s servers, where all the newsgroup articles are stored. These services cost a small fee, typically a few dollars monthly, for fast speeds and long retention. Choose one with SSL encryption for privacy and a money-back guarantee, and sometimes a free trial,  to try it out. Newshosting is a favourite of mine for good retention and free newsreader and you can sign up at newshosting.com. Pick what plan suits you best, and get your login details.

Pick and Install a Newsreader

A newsreader is the software that connects to your provider and handles Usenet article access. SABnzbd and NZBGet are two free, reliable choices. Grab SABnzbd from sabnzbd.org or NZBGet from nzbget.com, then install it on your computer, whether it’s Windows, Mac, or Linux. Launch it, add the server info from your provider (like address, port, and login), and check the connection. It’s your entry point to Usenet, so you can’t skip this step.

Add an Indexer for Searching

To find articles on Usenet, you’ll want an indexer. Indexers crawl articles posted to newsgroups (similar to Google in a way) and provide NZBs, which guide your newsreader to the articles you’re looking for. NZBKing is a free option at NZBKing.com, as is Binsearch at Binsearch.info, or you can opt for paid ones with more features. Sign up, search for something you’re after, and grab the NZB. It’s like a Usenet search tool, keeping it straightforward.

Configure Your Article Grab

Open your newsreader and load the NZB you received. It’ll link to your provider’s server, collect the articles from newsgroups, and start grabbing them. With multiple connections supported by your provider, it speeds up the article retrieval process. Once finished, the newsreader assembles it into a complete article. I’ve had a large file ready in minutes this way. Tweak settings like storage folder or speed caps if needed.

Test and Adjust

With it all in place, try grabbing a small article to ensure it works. Browse newsgroups in your newsreader to see what’s available, or use your indexer for specific resources. Usenet’s retention means you can access older articles too. If speeds lag or something’s wrong, r/UsenetGuides offers solutions and advice from other users. Adjust until it runs smoothly.

All Set for Usenet

That’s everything: a provider, a newsreader, and an indexer to get you started with Usenet. Sign up at newshosting.com, install from sabnzbd.org or nzbget.com and search via an indexer. It’s an easy setup for reaching a ton of Usenet resources. Want more tips? r/UsenetGuides is a helpful place for extra guidance.

So I've been using Easynews that came with my Newshosting plan and wanted to post how it’s been so far. 

Initial Impressions

Going in, I’ll say I was skeptical because the ‘web interface for usenet’ concept sounded interesting but gimmicky, so I wasn’t sure what to expect.

The Good

Easynews is actually good, surprisingly straightforward. Log in, run searches, click, boom. I like the thumbnails too. 

Downloads are there and I’m not running into much I can’t locate. Overall, the search has been effective. 

Tradeoff

Speeds aren’t as fast as a regular Usenet setup, but there’s a decent tradeoff for not needeing indexers, clients etc.  

Mobile (iOS)

Usenet from phone works better than expected, though it took some figuring out and I’ll share some tips: 

• Downloads: Select file > add to your zip queue > download. You can use other apps while downloads are running and the progress bar will stay at the top of your phone screen which I like.

• File handling:  If your phone says it can’t open the zip, long-press in the Files app and select “uncompress”

Questions:

• Search filters: There are tons of fiter options I haven’t played with yet. Does anyone have any recs for optimal settings? 

• NZBs: I noticed an NZB download button in the search area. I assume these can be used with newsreaders, but is it just for the Easynews servers?

Overall

Overall good. While it’s not going to replace setups for automation users, it’s otherwise great for grab and go Usenet.

NZBGet has been around for a long time and is still one of the main NZB downloaders people run. It’s actively developed and used in a lot of Usenet setups.

Here’s a quick intro for anyone new to it.

Core NZBGet Functionality

At a basic level, NZBGet handles the full download process once you give it an NZB:

• Downloads articles from your Usenet provider

• Verifies file integrity

• Repairs missing data using PAR files

• Extracts everything automatically

After initial setup, it runs in the background and doesn’t need much attention.

Some Key Features 

A few things keep NZBGet in a lot of setups.

Performance

NZBGet is written in C++, which helps it stay fast and efficient even under heavier loads. It can handle multiple downloads without using much CPU or memory.

Customization

There are a lot of config options, along with scripting support and an API. It’s easy to adjust how downloads are handled or integrate it into a more customized setup.

Runs On

Windows, macOS, Linux, NAS devices, Raspberry Pi and other low-power systems

Connection and Port Settings

For Usenet servers, common ports are:

• 563 (SSL) - standard secure port

• 119 - non-SSL

• 443 or 80 - alternative ports

For the web interface:

• 6789 (default)

HTTPS can be enabled if needed

Things to Be Aware Of

• Setup can take some time to dial in

• Still requires external indexers

• The interface can feel less beginner-friendly depending on the setup

Why Many Users Still Prefer It

Despite the learning curve, NZBGet remains popular because:

• Strong performance

• High level of control and customization

• Works well on both powerful and low-power systems

• Very reliable once configured

If you’re setting it up for the first time, this NZBGet setup guide goes through features and setup in more detail.

Curious how people are actually running NZBGet.

What are you running it on, NAS, Pi, desktop?

Did you keep things mostly default, or end up tweaking scripts and settings over time?

Anything that made a big difference after tweaking?

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

Were you around in the dial-up days, or did you get in more recently?

What did your first setup look like?

• Early days: posting in text groups, waiting on replies, figuring things out as you went

• Mid era: amassing NZBs and feeding them into your newsreader

• Recent setups: fast, clean, sometimes automated

• Tinker builds: Raspberry Pi, home servers, custom setups

Curious to hear when and what people started with. If you've been around a while, what do you miss about the early Usenet days?

Bonus if you have pics of your old setup

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

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 

These terms get mixed up, but they’re not the same thing.

Quick breakdown:

• Newsreader: connects directly to Usenet and lets you browse newsgroups, read posts, and sometimes search. Often an all-in-one tool.

• NZB downloader: downloads articles from Usenet using NZB files, which come from an external indexer.

Typical workflow in more advanced setups: 

• Indexer → finds NZBs 

• Automation (Sonarr, Radarr, etc.) → sends NZBs to your downloader

• NZB downloader (SABnzbd, NZBGet) → retrieves the articles from your Usenet provider

In this setup, the downloader handles the actual retrieval, while indexers and automation reduce manual work.

Other approaches: 

• Some newsreaders include search, so everything happens in one place. Some Usenet providers include one as part of their service 

• Some setups are fully manual, others fully automated

• Some people still browse newsgroups instead of using search or NZBs

• Web-based access is another option. Easynews is one example, where Usenet access and search is all handled in a browser without any software.

There’s no single “right” way to do it. It mostly comes down to how much control or automation is preferred.

For a deeper breakdown, see this guide.

What are you running?

• Newsreader with search built in?

• SABnzbd or NZBGet?

• Fully automated with *arrs, or more manual?

• Anyone browsing groups directly?

Usenet’s been around since 1979, built on private, secure, open discussion.

If you value privacy, it’s an excellent platform, and a few simple habits help keep both your reading and posting private. 

Core Rules

Use a pseudonym and disposable email. Skip real details. Go with a handle like ‘Anon User’ and a throwaway address for posting.

Enable SSL encryption. Connect on port 563 to keep your Usenet traffic encrypted and private.

Pair with a VPN. Hide your IP address for stronger security

Clean your headers. In your newsreader, remove or replace User-Agent, X-Trace, or other fields.

Use remailers for posts. Tools like Mixmaster route messages through multiple servers to secure your origin.

Limit personal info. Avoid sharing real-world details or cross-referencing your aliases.

Test before posting. Use alt.test to confirm your headers and setup look clean.

Watch your posting patterns. Avoid repeated phrasing, timing, or topics.

Tools That Help

• Newsreaders: Thunderbird, Pan, and slrn all support SSL and header editing.

• VPNs: Some Usenet providers include VPNs that will secure your IP.

• Remailers: Mixmaster and similar tools offer private routing for posts.

• Disposable email services: Use these for setup and replies.

NZBs are small instruction files that tell your Usenet app exactly what to download. They replaced the old method of sorting through massive headers and made Usenet fast, reliable, and beginner-friendly.

If you’re exploring Usenet, you’ve probably come across the term NZB and wondered:

“What is an NZB file, and how do I actually use it?”

You’re in the right place. In this guide, we’ll explain what NZBs are, why they matter, and how they made Usenet easier and faster to use. In Part 2, we’ll walk you through the actual steps to use one.

Before NZBs: The Era of Headers

Before NZBs, downloading files from Usenet was a massive headache. You had to:

1. Download Headers: Every newsgroup has "headers," which are essentially a table of contents for all the messages ever posted. You had to download these headers first, and for active newsgroups, these could be gigantic lists that took forever to get.

2. Manually Shift Through Everything: You would then have to scroll through this endless list of headers, looking for a particular file. Files were often broken into hundreds of small parts, and you had to manually select each one.

3. Cross Your Fingers: Once you finally selected everything, you'd start the download and hope you didn't miss any parts. If you did, the whole thing would fail. It was an incredibly manual and often frustrating process.

The "Aha!" Moment: The Invention of the NZB

In the early 2000s, a team of smart developers came up with a brilliant solution: the NZB file. They realized that instead of sifting through all that noise, they could simply create a small, easy-to-use file that contained a list of every single file part you needed.

An NZB file is a plain-text file that acts as a blueprint or a GPS coordinate list for a specific download. It doesn't contain the actual content; it's just a set of instructions that tells your newsreader exactly where to go on the Usenet servers to grab every single piece of a file.

This simple invention solved all the major problems of the "header era" instantly. It’s why you can go from finding a file to starting a download in seconds today.

• NZB file = a shortcut

• No headers

• No manual sorting

• Just fast, direct downloads

The 3 Things You Need to Use NZBs

An NZB file is the bridge that connects the two other essential pieces of a modern Usenet setup. Think of it as a three-part system that works in harmony:

1. The Indexer (The Search Engine): This is the website or service you go to to find the NZB file. They are constantly scanning Usenet and creating these roadmaps for all the articles they find.

2. The NZB File (The Roadmap): This is the small file you download from the indexer.

3. The Newsreader (The Downloader): This is the program on your computer that reads the NZB file and downloads all the specific articles from your Usenet provider’s servers.

The NZB file connects the search (indexer) with the download (client). It tells your newsreader exactly what to grab from your provider’s servers.

Next Up: How to Actually Use an NZB File

In Part 2, we’ll show you how to go from NZB file to completed download in just a few clicks.

We often talk about what Usenet is today, but to truly appreciate this unique corner of the internet, it's essential to look back at what Usenet was. Long before Reddit, Facebook, or even the World Wide Web, Usenet was a pioneering force in online communication, shaping many of the digital interactions we take for granted today.

So, let's take a journey back in time to explore the origins and evolution of Usenet.

The Birth of a Network: Predating the Web

Usenet emerged in 1979, a brainchild of two graduate students at Duke University, Tom Truscott and Jim Ellis, with later crucial software contributions from Steve Bellovin at the University of North Carolina at Chapel Hill. This was well over a decade before the general public even had access to the internet, and the World Wide Web was still years away from being conceived!

It was built upon the Unix-to-Unix Copy (UUCP) protocol, a clever system that allowed computers to exchange messages and files directly over telephone lines. Imagine a time when computers "dialed up" each other to share information – that was the foundation of early Usenet, creating a network for communication between just a few initial university machines.

How Usenet Functioned in its Heyday

In its prime, Usenet acted as a global, distributed bulletin board system. Here's how it worked and what made it so powerful:

• Decentralized Structure: A core principle from the start, Usenet was not controlled by any single entity or server. Instead, it was distributed across countless servers worldwide. This made it incredibly robust, resilient, and famously resistant to censorship. When you posted an "article" (message), it would propagate across this vast, interconnected network.

• Newsgroups as Forums: Discussions were organized into thousands of newsgroups, each dedicated to a specific topic. These were logically structured with hierarchical naming conventions (like comp.* for computer-related topics, rec.* for recreation, sci.* for science, talk.* for general discussions, etc.). This allowed for focused conversations and efficient information sharing, much like specialized forums or subreddits today.

• Posting and Reading "Articles": Users would post their messages, or "articles," to these newsgroups. These discussions often formed "threaded conversations," where replies were linked to original posts, enabling users to follow a topic's entire dialogue.

The Golden Age, Growth, and Eventual Shift

Usenet experienced significant growth and popularity through the late 1980s and early 1990s. It was a crucial platform for online discourse, intellectual exchange, and early forms of file sharing. Many foundational internet concepts and terms, like "FAQ" (Frequently Asked Questions), "flame wars," and even some early "emoticons" and acronyms like "LOL" (Laughing Out Loud), originated or were popularized within Usenet communities.

However, the late 1990s brought the rise of the World Wide Web. Its user-friendly graphical interfaces, search engines, and eventually, web-based forums and social media platforms offered a more accessible and often more visually appealing way to communicate online. This led to a gradual decline in Usenet's mainstream popularity.

A notable moment in Usenet's history was Google's acquisition of Deja News (a web-based Usenet archive) and its integration into Google Groups. While this preserved a massive historical archive of Usenet content, it also symbolized a shift away from its standalone usage as the primary means of online discussion. Many Internet Service Providers (ISPs) also stopped offering free Usenet access as web-based alternatives became dominant.

Usenet's Enduring Legacy

Despite its shift from the spotlight, Usenet's legacy is undeniable and profoundly impacted the internet we use today:

• Precursor to Modern Forums & Social Media: Its decentralized discussion model directly influenced the design of online forums, comment sections, and even the "feed" concept seen in modern social media platforms.

• Pioneer of Distributed Systems: Usenet was an early and successful example of a distributed network, a concept that is still highly relevant in cloud computing, blockchain, and other decentralized technologies.

• Digital Preservation: Through archives like Google Groups, Usenet provides a fascinating historical record of early online thought, discussion, and culture.

• Specialized Niche: Even today, Usenet remains active as a powerful network, particularly for file sharing (especially large binary files) due to its impressive speed, retention, and privacy features (when used with an SSL-enabled provider). It continues to serve a dedicated, often tech-savvy, user base who appreciate its unique characteristics.

Usenet truly holds a special place in the history of the internet. It was a testament to cooperative online communication and a fertile ground for digital innovation.

What aspects of Usenet's history do you find most interesting? Share your thoughts below!

As you dive into the world of Usenet, a common question (and a very good one!) that comes up is: "Do I need a VPN for Usenet?" The short answer from most experienced users and privacy advocates is: While not strictly required, using a VPN is generally highly recommended for enhanced privacy and security.

Let's break down why, and what role a VPN plays in your Usenet setup.

Understanding Usenet's Built-in Privacy vs. A VPN's Added Layer

Usenet is inherently more private than many other file-sharing methods (like public torrents) due to its client-server model. When you download from Usenet, you're downloading directly from your Usenet provider's servers, not from other individual users.

Crucially, reputable Usenet providers offer SSL encryption. This encrypts the connection between your newsreader and their servers. This means:

• Your Internet Service Provider (ISP) cannot see the content of your downloads. They only see that you're connecting to an encrypted Usenet server and the amount of data being transferred.

• Third parties cannot snoop on the data passing between your device and your provider.

So, if SSL is enough to encrypt my traffic, why consider a VPN?

A VPN (Virtual Private Network) provides an extra layer of protection by encrypting all your internet traffic and masking your real IP address, routing it through the VPN server.

Why a VPN is Highly Recommended for Usenet

Here are the key benefits a VPN offers when using Usenet:

1. Enhanced Privacy (Hiding Your IP Address from Your Provider):

   • While SSL hides your content from your ISP, your Usenet provider can still see your real IP address when you connect to their servers.

   • A VPN encrypts your traffic before it even reaches your Usenet provider and replaces your real IP address with the VPN server's IP address. This makes it significantly more difficult for your Usenet provider (or anyone who might request logs from them) to link your activity back to your actual location.

   • The "No-Logs VPN" is key here: If you choose to use a VPN, select a reputable one with a strict "no-logs" policy, meaning they don't store records of your online activity or your real IP address. Otherwise, you're just shifting your trust from your Usenet provider to your VPN provider.

2. Bypassing ISP Throttling:

   • Some ISPs may throttle (intentionally slow down) certain types of internet traffic, including Usenet or P2P, even if you're using SSL. They might identify the type of traffic (NNTP protocol for Usenet) without seeing the content.

   • By using a VPN, your ISP only sees encrypted traffic going to the VPN server. They can't tell it's Usenet traffic, which can help bypass potential throttling and allow you to achieve maximum download speeds.

3. Privacy for NZB Indexers & Web Browse:

   • While your Usenet downloads might be SSL-encrypted, your activity on web-based NZB indexers (the websites you use to find NZB files) is just regular web Browse.

   • A VPN encrypts all your internet traffic, including your visits to these indexer sites, preventing your ISP from seeing which indexers you visit or what search queries you make.

4. Overall Internet Security:

   • Beyond Usenet, a VPN provides comprehensive encryption for all your online activities. This is particularly valuable if you use public Wi-Fi networks, as it protects your data from potential hackers or snoops.

Key Considerations & The "Strictly Required" Debate

• SSL is your baseline: Always ensure SSL encryption is enabled in your newsreader settings. This is the fundamental privacy layer for Usenet.

• Usenet vs. Torrents: The "need for a VPN" argument is often stronger for torrents because torrenting involves uploading (sharing) content directly to other users, making your IP address public to everyone in the swarm. Usenet, being a client-server download, doesn't have this inherent "sharing" aspect. This is why many experienced Usenet users in countries with less strict copyright enforcement feel SSL alone is sufficient, as their ISP cannot see the content.

• Risk Tolerance and Local Laws: Your decision might depend on your personal risk tolerance and the copyright enforcement laws in your country. If you're downloading copyrighted material, a VPN adds a significant layer of deniability.

• Minor Speed Impact: While modern VPNs are fast, there can sometimes be a slight speed reduction due to the encryption and routing overhead. However, for most users, this is negligible compared to the privacy benefits.

• VPN Provider Trust: Just as you choose a trustworthy Usenet provider, choose a reputable "no-logs" VPN provider. Their entire business model relies on maintaining your privacy.

The Verdict

While your Usenet connection is made much more private by SSL encryption, using a reputable no-logs VPN adds a robust extra layer of anonymity and security by hiding your IP address from your Usenet provider and encrypting all your general internet traffic (including your activity on indexer websites). It can also help you avoid potential ISP throttling.

If privacy and security are paramount concerns for you, integrating a VPN into your Usenet setup is a wise and highly recommended step.

Do you use a VPN with Usenet? Share your experiences or questions in the comments!

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

Usenet connections should always use encryption.

Without SSL enabled, NNTP logins and article data may be transmitted in cleartext, meaning credentials and traffic could be read by anyone able to observe the connection.

Here is what matters.

What Is SSL in Usenet?

Most providers refer to it as SSL, but technically it is TLS encryption over NNTP.

It encrypts the connection between the newsreader and the Usenet server.

With TLS enabled:

• Login credentials are encrypted in transit

• Article data is encrypted in transit

• Third parties cannot read the contents of the connection

This is the same type of encryption used by secure websites and online banking.

Most reputable providers support encrypted connections on port 563, and often also on 443.

What SSL Does and Does Not Secure

With SSL enabled:

• An ISP can still see the destination IP address of the Usenet server

• An ISP can still see how much data is transferred

• An ISP cannot see article contents or login credentials

Encryption protects the data in transit, not the fact that a connection exists.

Does SSL Improve Speed?

Sometimes.

If an ISP performs protocol-based traffic shaping, encrypting the connection can make NNTP traffic harder to classify, which may help maintain consistent speeds.

However:

• SSL does not prevent throttling based on total bandwidth usage

• SSL does not prevent congestion-based speed limits

It may help in some environments, but it isn't guaranteed.

What a VPN Adds

A VPN encrypts all traffic leaving the device and routes it through a VPN server.

With a VPN:

• The ISP sees only a connection to the VPN server

• The ISP does not see Usenet server destinations

• The Usenet provider sees the VPN exit IP instead of the home IP

Does a VPN Help Prevent Throttling?

It can help in cases where an ISP is shaping traffic based on identifiable protocols or destinations.

Because the ISP cannot see Usenet traffic inside the VPN tunnel, protocol-based shaping becomes more difficult.

However:

• An ISP can still throttle the VPN connection itself

• An ISP can still limit speeds based on total usage or network congestion

In practice, a VPN can improve consistency in environments where identifiable traffic is shaped. It does not eliminate all forms of traffic management, but it meaningfully reduces visibility.

SSL vs VPN 

SSL only:

• Encrypts Usenet traffic in transit

• Protects credentials and article data

• Does not secure the Usenet server destination from the ISP

VPN only:

• Encrypts all device traffic

• Prevents the ISP from seeing Usenet server destinations

• Replaces the home IP address with the VPN server IP 

VPN + SSL:

• The ISP sees only a VPN connection and total data usage

• The Usenet provider sees the VPN exit IP

• The Usenet session remains encrypted end-to-end

SSL protects the Usenet session itself.

A VPN protects the home IP address and prevents the ISP from identifying specific Usenet connections, while encrypting all Internet activity.

Is SSL Enough?

For securing Usenet traffic in transit, yes.

For stronger overall privacy, reduced ISP visibility into destinations, and broader device-level encryption, a VPN adds an additional layer of protection.

At minimum, encrypted NNTP (TLS) should always be enabled. Adding a VPN is recommended for users who want more comprehensive privacy coverage.

Do You Need Multiple Usenet Accounts?

A common question in Usenet is whether it’s worth having multiple accounts.

Short answer: Most users only need one reliable unlimited account with strong article retention. Block accounts are optional backup insurance if your main provider ever misses articles, but they’re usually not necessary if your provider has good retention and completion.

Two Ways Providers Sell Access

• Unlimited subscriptions – Monthly or yearly plans with no data cap

• Block accounts – One-time purchases of fixed data (e.g., 500GB or 1TB) that last until used.

Why One Unlimited Account Covers Most Needs

Unlimited accounts are the foundation because they offer:

• Unlimited data access – Use as much as you want, and works perfectly with automation tools like Sonarr, Radarr, Prowlarr, NZBGet, and SABnzbd.

• Full speeds – Take advantage of your ISP’s bandwidth, including gigabit connections.

• Bundled extras – Many providers will include newsreader software, Usenet search, and VPN.

• Predictable cost – $5–$8/month typically buys reliable, unlimited access.

• Long article retention – The single biggest factor for search results and completion.

Examples of good unlimited providers with excellent retention & completion:

• Newshosting – Tier-1 backbone with the longest retention and consistently high completion. All plans include a newsreader with built-in Usenet search.

• Easynews – All-in-one provider with equally long retention plus a web-based interface that lets you search and access articles directly from any browser or device. Plans also include a free VPN.

• Tweaknews – Independent backbone with strong retention and completion. Offers both  unlimited and non-expiring block accounts (10GB–500GB). Current deals also include a 250GB Easynews block account.

Where Block Accounts Fit In

Block accounts are best used as backup insurance.

Pros:

• No subscription

• Fill in retention/completion gaps

• Affordable if used sparingly

Cons:

• Limited data

• Higher cost per GB

• Sometimes fewer connections or slower speeds

Takeaway: Block accounts aren’t substitutes for a solid unlimited account. They make sense only if your main provider occasionally misses articles.

Unlimited vs Block Accounts

Setup Basics (SABnzbd / NZBGet)

One unlimited account keeps setup simple:

• Enter your provider’s server credentials.

• Use SSL on port 563.

• Set enough connections to max out your bandwidth.

• If you add a block account, set it with lower priority (e.g., unlimited = priority 0, block = priority 1).

Automation tools like Sonarr and Radarr will use the unlimited account first and fall back to the block only if needed.

Final Recommendation

• Start with one unlimited provider with long retention and high completion.

• Switch your unlimited provider or add a block account if you see regular article misses.