What Is Autobrr? The Complete Guide to Torrent Automation

You’ve got a seedbox. It’s fast, always on, and ready to download the moment something drops on your private tracker. The only problem? You’re still manually checking announce channels and hitting grab before anyone else does – and you keep missing it. Autobrr is a modern torrent automation tool that monitors IRC announce channels and RSS feeds from private trackers and automatically pushes matched releases to your download client the instant they’re announced.

It’s the missing link between your private tracker membership and a fully hands-off seedbox setup.

Table of Contents

1. What Is Autobrr?
2. Autobrr: Key Facts
3. How Autobrr Works: IRC, RSS, and Filters
4. How to Install Autobrr on a Seedbox
5. Autobrr vs Prowlarr: What’s the Difference?
6. Autobrr vs Sonarr and Radarr
7. Setting Up Autobrr Filters
8. Who Should Use Autobrr?
9. Autobrr and RapidSeedbox: Why They Work Well Together
10. Common Autobrr Mistakes and Limitations
11. Frequently Asked Questions About Autobrr
12. Autobrr – Final Words

What Is Autobrr?

Autobrr is an open-source torrent filter and automation application that connects to IRC announce channels, RSS feeds, and indexers to find matching torrents in real time and send them directly to download clients like qBittorrent, Deluge, rTorrent, or Transmission. It’s usually used for ratio maintenance on private trackers, automated collection building, and freeleech sniping on seedboxes.

Autobrr works by listening to IRC announce bots that fire the instant a new torrent is added to a private tracker – often seconds before the web interface even updates. You define filters based on criteria like category, resolution, size, codec, or release group, and autobrr evaluates each announcement against your rules. When there’s a match, it automatically downloads to your configured client. No browser, no clicking, no waiting.

Autobrr: Key Facts

What it is: Open-source torrent filter and IRC/RSS automation tool
How it works: Monitors IRC announce channels and RSS feeds, evaluates torrents against user-defined filters, pushes matches to download clients
Main components: Filter engine, IRC client, RSS reader, download client integrations, Prowlarr/indexer support
Key benefits: Real-time grabs, ratio building automation, freeleech detection, multi-tracker support
Difficulty level: Intermediate (basic Linux/Docker comfort recommended)
Best for: Private tracker users, seedbox operators, ratio-conscious downloaders
Alternatives: Prowlarr (indexer manager, not real-time), Sonarr or Radarr (media management, not IRC-native), FlexGet (older and more complicated)
Default port: 7474
Last updated: May 2026

How Autobrr Works: IRC, RSS, and Filters

Autobrr’s core architecture separates into three layers: sources (where it watches), filters (what it matches), and actions (what it does on a match).

Sources: IRC and RSS

IRC is the most powerful source. Private trackers run IRC bots that announce every new upload to a channel in real time – sometimes within one second of the torrent being added. Autobrr connects directly to these IRC channels using the built-in IRC client functionality. This gives it a big speed boost compared to polling an RSS feed, which usually refreshes every 5-15 minutes.

RSS feeds are the secondary source. If your trackers don’t support IRC announcements, or if you’re using Prowlarr for indexing, Autobrr can poll RSS feeds at whatever interval you like. The Prowlarr integration is really helpful here. If you’re already using Prowlarr to manage your indexers, autobrr can access that list without you having to set up each source manually.

Filters: The Logic Engine

Filters are where autobrr earns its reputation. Each filter is a rule set you create that defines exactly what you want. You can match on:

• Category (Movies, TV, Music, Games)
• Resolution (1080p, 2160p, HDTV)
• Codec (x264, x265, HEVC)
• Release group
• File size (min/max)
• Freeleech status
• Season/episode (via regex or Sonarr/Radarr integration)
• Upload time (to limit grabs to the first N minutes after announce)

Filters support AND/OR logic, regex, and macros. You can set priority levels so that if two filters match the same torrent, only the higher-priority action fires. This prevents double-downloads.

Actions: Pushing to Download Clients

When a torrent matches a filter, autobrr executes the configured action. The most common action is pushing the torrent directly to a download client. Autobrr supports:

• qBittorrent (including label and category assignment)
• Deluge (with label plugin)
• rTorrent / ruTorrent
• Transmission
• SABnzbd (for NZB workflows)
• Webhook (custom HTTP calls for advanced setups)
• Watch folder (dropping .torrent files into a directory)

You can also set up test filters that log matches without downloading, which is handy for tuning a new filter before it’s put live.

How to Install Autobrr on a Seedbox

Most seedbox providers support custom application installs via SSH or Docker. Here’s how to get autobrr running from scratch.

If you are using RapidSeedbox, you get autobrr as a one-click installer!

Option 1: Docker Compose

Docker is the cleanest way to run autobrr, especially if you’re already running other *arr apps in containers.

Step 1: Create the Docker Compose file

Create a file called docker-compose.yml in your autobrr directory:

Step 2: Start the container

Step 3: Access the web interface

Open http://your-server-ip:7474 in a browser. On first launch, autobrr will prompt you to create an admin account.

Step 4: Add your first IRC network

Go to Settings -> IRC and add your tracker’s IRC server details. You’ll need the server address, port, your IRC nickname, and the NickServ password if your tracker requires identification. Autobrr’s documentation at autobrr.com maintains a tracker-specific setup list.

Option 2: Binary Install

If you prefer not to use Docker:

Create a systemd service file to keep it running on reboot. The autobrr GitHub repo includes a sample .service file you can adapt.

Autobrr vs Prowlarr: What’s the Difference?

This is the most common comparison people make, and it makes sense – both tools deal with indexers and torrents. But they solve completely different problems.

Choose autobrr when: You’re on private trackers and need to grab uploads within seconds of announcement – for ratio maintenance, freeleech racing, or building a collection automatically.

Choose Prowlarr when: You want to manage multiple indexer configurations in one place and feed them into Sonarr, Radarr, or Lidarr without caring about announce timing.

The good news is that they’re not mutually exclusive. A lot of setups use Prowlarr as the indexer manager and autobrr for the real-time IRC layer, with the two connected via autobrr’s Prowlarr integration.

Autobrr vs Sonarr and Radarr

Sonarr and Radarr handle your media library. They keep track of what shows and movies you want, monitor episode status, and start searches or RSS grabs when new content is available. Autobrr isn’t a media manager. It doesn’t keep track of what you’ve watched or when you’ve finished an episode.

Here’s how the integration works: autobrr can send matched torrents straight to Sonarr or Radarr as an import trigger. That way, those apps can handle file renaming and library organization. You get the best of both worlds with autobrr’s speed on IRC and Sonarr/Radarr’s library management.

In practice, autobrr handles the grab, and Sonarr/Radarr handles the organize. They work well together, not against each other.

Setting Up Autobrr Filters

Let’s say you want to automatically grab all 1080p Blu-ray remuxes from a specific release group on a private tracker, the moment they’re announced.

1. Create a new filter

In the autobrr web interface, go to Filters -> Add Filter. Give it a name.

2. Define match criteria

In the filter editor:

• Resolutions: 1080p
• Sources: Blu-ray
• Codecs: AVC, HEVC
• Release groups: comma-separate the different groups
• Indexers: Select your tracker IRC channel

3. Set the action

Under Actions, add a new action:

• Type: qBittorrent
• Category: select the category
• Tags: autobrr, 1080p

Click Save.

4. Test with a dry run

First, enable test/dry run mode. This logs what would’ve been grabbed without actually downloading. Just wait a few hours, check the logs, and make sure the filter is matching the right things before switching to live mode.

Here’s a helpful tip: Use the Size filter (like 20GB to 80GB for remuxes) to avoid false matches for fake or wrongly labeled releases.

Who Should Use Autobrr?

1. Private Tracker Members

• Profile: Users who pay attention to their ratio and want to seed early to earn upload credit.
• Why it works: Autobrr grabs within seconds of announcement, when peer demand is highest, and you can accumulate the most uploads without any active seeding time.
• Getting started: Connect to your tracker’s IRC channel and set a freeleech filter as your first test.

2. Seedbox Operators

• Profile: Users with a dedicated seedbox who want fully automated, hands-off downloading.
• Advanced features: Multi-tracker IRC support, webhook integrations, and scheduled filters (e.g., only grab during off-peak hours).
• Optimization tips: Run autobrr on the seedbox itself to minimize latency between IRC announce and download start.

3. *arr Stack Users

• Profile: Anyone running Sonarr, Radarr, or Lidarr with a private tracker membership.
• Key advantage: Autobrr bridges the gap between IRC-speed announces and the slower RSS polling that *arr apps rely on by default.
• Common workflow: Autobrr watches IRC -> matches filter -> pushes to Sonarr as import trigger -> Sonarr handles library organization.

4. Freeleech Hunters

• Profile: Users who want to maximize upload credit during freeleech events without manually watching announce channels.
• Key feature: Autobrr’s freeleech filter flag lets you create rules that only fire during freeleech periods, with optional size limits to avoid filling your disk.

Common Autobrr Mistakes and Limitations

1. Connecting to IRC Without NickServ Registration

A lot of private trackers require you to register your IRC nickname with NickServ and identify it before the announce bot will send you anything. If autobrr connects but you see zero matches, that’s usually the reason. First, register your IRC nickname in the tracker’s IRC server using a standard client. Then, set up the credentials in autobrr’s IRC settings.

2. Overly Broad Filters

If you use a filter with no size limits and a vague category match, it’ll flood your download client. Just remember to always set a maximum file size and test with dry-run mode before enabling live actions.

3. Ignoring the Default Port (7474)

If you’re using a shared seedbox or you’re behind a firewall, port 7474 might not be accessible. You can change the port in the autobrr config file (config.toml). If you’re accessing the web interface externally, check your seedbox provider’s port forwarding documentation.

Windows Support Is Limited

Autobrr is mostly a Linux app. It runs on Windows, but the community support, documentation, and integrations are all optimized for Linux and Docker environments. If you’re on Windows, running autobrr inside WSL2 or a Docker Desktop container is a better option than a native Windows install.

Autobrr is Not a Media Manager

Autobrr has no concept of “I already have this movie” or “I’m missing Season 3 Episode 4.” It only knows what IRC announces and whether your filter matches. For media library awareness, you need Sonarr or Radarr alongside it.

Autobrr and RapidSeedbox: Why They Work Well Together

RapidSeedbox servers run Linux and support Docker-based installations via SSH, so autobrr is a natural fit. The server’s always on, so your IRC connection stays live 24/7 without you needing to keep a home machine running. The low-latency connection between the seedbox and tracker servers also means that the time between autobr detecting an announcement and the download starting is measured in seconds.

A typical RapidSeedbox + autobrr workflow looks like this:

1. Autobrr connects to tracker IRC on the seedbox
2. New upload announced -> autobrr evaluates the filters -> match found
3. Autobrr pushes .torrent to qBittorrent running on the same box
4. Download starts at seedbox speeds
5. You’re seeding within 30-60 seconds of the original announcement

For private tracker users focused on ratio maintenance, this setup is about as efficient as it gets.

Frequently Asked Questions About Autobrr

What is autobrr?

Autobrr is an open-source torrent automation tool that connects to private tracker IRC announce channels and RSS feeds, evaluates new releases against custom filters, and automatically sends matching torrents to download clients like qBittorrent or Deluge. It’s mostly used for ratio building and freeleech automation on seedboxes.

How is autobrr different from Prowlarr?

Autobr and Prowlar are used for different things. Prowlarr is an indexer manager that aggregates RSS feeds for Sonarr, Radarr, and similar apps. Autobrr is a real-time IRC listener that grabs torrents in seconds after they’re announced – much faster than RSS feeds. You can use the two tools together. Prowlarr manages indexers, and autobrr handles the IRC layer.

Is autobrr better than Sonarr for private trackers?

Autobrr and Sonarr work well together, even though they’re both in the same field. Sonarr handles your TV show library and runs searches, or RSS grabs when new episodes are available. Autobrr adds real-time IRC announce speed on top – it can grab a release seconds after it appears, then trigger Sonarr to import it. Most serious private tracker users run both.

What download clients does autobrr support?

Autobrr natively supports qBittorrent, Deluge, rTorrent, ruTorrent, Transmission, SABnzbd, and Sonarr/Radarr as action targets. It also supports watch folders and webhook actions for custom integrations.

What is autobrr’s default port?

Autobrr uses port 7474 by default for its web interface. You can change this in the config.toml configuration file if the port conflicts with another service or is blocked by a firewall.

Autobrr – Final Words

I’ve seen a lot of seedbox setups where the hardware can get 100Mbps, but the operator still has to log in twice a day to manually push downloads. Autobrr closes that gap completely. Once your IRC connection is up and running and your first filter is working, you can stop worrying about the grab and start focusing on what matters – ratio, collection, and actually watching what you download.

Start with a single tracker, a simple freeleech filter, and dry-run mode enabled. Just give it a day, check the logs, and see what was taken. If you need to tighten the filter, just flip it to live, and you’re all set. From there, autobrr runs quietly in the background and does exactly what it’s supposed to.

Disclaimer: This post is for informational purposes only. Autobrr is a third-party open-source project – RapidSeedbox is not affiliated with it and does not provide official support for it. Always ensure your use complies with the terms of service of any platform or private tracker you use.