Automating Your Movie Library With Radarr
Radarr is an open-source movie collection manager that watches for new releases, grabs them automatically through configured download clients, and organizes everything into a clean library structure. It runs as a background service on your home server, NAS, or even a spare PC, and once it’s configured, you rarely need to touch it again. The concept is straightforward: you add movies you want, set your quality preferences, and Radarr handles the rest – monitoring indexers, sending downloads to tools like qBittorrent or NZBGet, and renaming files when they finish.
Getting Radarr running from scratch takes about 30 to 60 minutes depending on your setup, but the payoff is a self-managed movie library that stays current without manual intervention. This guide walks through installation, connecting a download client, adding indexers, and configuring quality profiles so everything works together correctly from day one.

Installing Radarr on Your System
Radarr supports Windows, macOS, Linux, and Docker, with Docker being the most portable option for home server users. If you’re running something like Unraid, TrueNAS, or a plain Ubuntu box, Docker Compose gives you the cleanest install. Pull the official LinuxServer.io image by adding it to your compose file with the image tag lscr.io/linuxserver/radarr:latest. You’ll map three volumes: one for the config directory, one for your completed downloads folder, and one for the final movie library location. Getting these paths right at this stage matters – mismatched volume mounts are the single most common reason Radarr fails to move files after download.
For a bare-metal Linux install, the Radarr team provides an install script that handles the service setup automatically. On Debian or Ubuntu, you add their package repository, run apt install radarr, and the service starts on port 7878. Windows users can download the installer directly from radarr.video, which installs Radarr as a system tray application that launches at startup. Either way, once installed, the web interface is available at http://localhost:7878 and the setup wizard walks you through the initial configuration steps.
Before moving forward, set up authentication in Settings under General. Radarr has no login by default, which is fine on a local network, but if you’re exposing it through a reverse proxy or VPN, adding a username and password takes about 20 seconds and avoids an obvious security gap. Also confirm your root folder path here – this is where Radarr will place finished movies, so point it at your actual media storage drive, not a temp folder or the config directory.
Connecting a Download Client
Radarr doesn’t download anything itself. It finds releases and hands them off to a separate download client, which is either a torrent client like qBittorrent or Deluge, or a Usenet client like SABnzbd or NZBGet. Go to Settings, then Download Clients, and click the plus icon to add your client. Each client type has its own connection form asking for host, port, username, and password. If your download client is running in Docker on the same host, use the container’s service name or the host’s local IP rather than localhost – Docker networking doesn’t always resolve localhost the way you’d expect, and this catches a lot of people off guard.
After adding the client, hit the Test button. A green checkmark confirms Radarr can reach it. One setting worth enabling here is “Remove Completed Downloads” under the download client options – this tells Radarr to clear out finished items from the client’s queue after the files have been imported, which keeps the download client tidy over time. You can configure separate categories for Radarr downloads within the client too, so movies don’t get mixed in with other downloads from different applications.

Adding Indexers and Quality Profiles
Indexers are the search sources Radarr uses to find movie releases. For Usenet, services like NZBGeek or DrunkenSlug provide API access to their databases. For torrents, public indexers like RARBG or 1337x can be added directly, while private trackers typically require a Prowlarr or Jackett integration to bridge the connection. Prowlarr is the cleaner modern solution – it acts as a central indexer manager that feeds results to Radarr and other *arr apps simultaneously. If you’re building out a full media stack, setting up Prowlarr first and then syncing indexers to Radarr through it is worth the extra 15 minutes, since you manage everything in one place rather than duplicating entries across apps.
Quality profiles tell Radarr which video formats are acceptable and in what priority order. The default profiles – SD, HD Bluray, Ultra-HD – cover most use cases, but you can create custom ones. A typical setup for a home library might accept 1080p Bluray as the preferred format, allow 1080p WEB-DL as a fallback, and ignore anything below 720p entirely. You set cutoffs within the profile, which is the minimum quality Radarr will accept without continuing to look for upgrades. Once a download meets or exceeds your cutoff, Radarr stops searching for that movie. Without a cutoff set correctly, Radarr will keep grabbing better versions every time one appears, which can fill up storage quickly if you have hundreds of movies monitored.
Custom formats add another layer of control beyond basic quality. These are scoring rules that let you prioritize or penalize releases based on specific attributes – things like preferred release groups, HDR formats, audio codecs, or whether a release is a proper versus a scene repack. A custom format with a high score for DTS-HD audio, for example, will push Radarr to prefer that version over an otherwise identical release with standard Dolby Digital. This is optional configuration, but for anyone building a quality-focused library, custom formats are where real fine-tuning happens.
Once indexers and quality profiles are in place, adding a movie is just a search. Click Add Movie, type the title, select it from the results, pick your quality profile, and hit Add Movie. If you enable “Start search for missing movie” at this point, Radarr will immediately check all your indexers for a matching release. For building an existing watchlist into the library, the Discover and Import List features let you pull in full lists – from Trakt, IMDb, or RSS feeds – so you don’t have to add titles one by one. An IMDb watchlist sync, for instance, will automatically add anything you mark as wanted on IMDb directly into Radarr’s monitored queue.

File naming conventions are set under Settings, then Media Management, and this is one area that rewards careful attention upfront. Radarr can rename every downloaded file to a consistent format using tokens like {Movie Title} ({Release Year}) {Quality Full}, which produces clean, readable filenames that Plex, Jellyfin, and Emby all recognize without additional configuration. If you’re building a broader self-hosted media setup – for example, alongside a self-hosted file management server – having consistent naming from the start prevents the organizational headaches that come with mixed filename conventions across thousands of files. The difference between a library that scrapers read correctly on the first pass and one that requires constant manual correction almost always comes down to the naming template configured here.
Frequently Asked Questions
What download clients work with Radarr?
Radarr supports qBittorrent, Deluge, Transmission, SABnzbd, and NZBGet. You connect them through the Download Clients section in Settings.
Do I need Prowlarr to use Radarr?
No, but Prowlarr makes indexer management easier by syncing sources to Radarr and other arr apps from one place, which saves time on larger setups.
Why isn’t Radarr moving files after download?
Mismatched volume paths are the most common cause. Make sure the path Radarr uses for completed downloads matches the actual path the download client writes files to.





