Check out the FAQ, API documentation and other guides
See all your upcoming albums in one convenient location.
Find all the releases, choose the one you want and send it right to your download client.
Automatically integrates with Calibre library.
Import lists from other supported services like Goodreads and LazyLibrarian.
Readarr is supported natively on Windows. Readarr can be installed on Windows as Windows Service or system tray application.
A Windows Service runs even when the user is not logged in, but special case must be taken since Windows Services cannot access network drives (\\server\share or X:\ mapped drives) without special configuration steps.
It's therefore advisable to install Readarr as a system tray application if the user does not need to log out, the option to do so is provided during the installer.
Download the Windows Installer with the following link and execute it.Download Windows x64 Installer Download Windows x86 Installer
http://localhost:8787 to start using Readarr.
It is possible to install Readarr manually using the x64 .zip download. However in that case you must manually deal with dependencies, installation and permissions.
An aur helper can install readarr and its dependencies easily, or follow the AUR Installing Packages wiki for manual installation.
For example, to use yay to install the readarr package:
yay -S readarr
sudo systemctl daemon-reload sudo systemctl enable --now readarr
to start using Readarr.
The community has put together an Installation Guide to help you install this on Debian or Ubuntu.
Generic .tar.gz downloads are available for linux, but dependencies, installation and permissions will need to be done manually.
The easiest way to install Readarr on macOS is to use the App archive with the steps described below.
Open the archive and drag the Readarr icon to your Application folder.
Open Readarr.app in your Application folder.
http://localhost:8787 to start using Readarr.
A generic download is available for linux, but dependencies, installation, and permissions will need to be done manually.Download Linux .tar.gz
The Readarr team does not offer an official Docker image. However, a number of third parties have created and maintain their own.
These instructions provide generic guidance that should apply to any Readarr Docker image.
There are two common problems with Docker volumes: Paths that differ between the Readarr and download client container and paths that prevent fast moves and hard links.
The first is a problem because the download client will report a download's path as
/torrents/My.Book/, but in the Readarr container that might be at
/downloads/My.Book/. The second is a performance issue and causes problems for seeding torrents. Both problems can be solved with well planned, consistent paths.
Most Docker images suggest paths like
/downloads. This causes slow moves and doesn't allow hard links because they
are considered two different file systems
the container. Some also recommend paths for the download client container that are different from the Readarr container, like
The best solution is to use a single, common volume inside the containers, such as
Your books would be in
/data/Books, torrents in
and/or usenet downloads in
If this advice is not followed, you may have to configure a Remote Path Mapping in the Readarr web UI (Settings › Download Clients).
Permissions and ownership of files is one of the most common problems for Readarr users, both inside and outside Docker. Most images have environment variables that can be used to override
the default user, group and umask, you should decide this before setting up all of your containers.
The recommendation is to use a common group for all related containers so that each container can use the shared group permissions to read and write files on the mounted volumes.
Keep in mind that Readarr will need read and write to the download folders as well as the final folders.
For a more detailed explanation of these issues, see The Best Docker Setup and Docker Guide wiki article.
To install and use these Docker images, you'll need to keep the above in mind while following their documentation. There are many ways to manage Docker images and containers too, so installation and maintenance of them will depend on the route you choose.
doesn't specify any default volumes, besides
/config. Images are automatically updated multiple times in an hour if upstream changes are found. Hotio also builds our Pull Requests which may be useful for testing.
on how to install the image.
is one of the most prolific and popular Docker image maintainers. They also maintain images for most of the popular download clients as well.
LinuxServer specifies a couple of optional default volumes such as
/downloads. The default volumes are not optimal nor recommended. Our recommendation is to use a single volume for the data, as mentioned above.