Lidarr

Open-source music collection management, honestly reviewed. What you get — and what you sign up for — when you add Lidarr to your self-hosted setup.

TL;DR

• What it is: GPL-3.0 open-source music collection manager — the music-focused sibling of Sonarr and Radarr. Monitors RSS feeds, auto-downloads from Usenet/BitTorrent indexers, then sorts, renames, and upgrades your library [README].
• Who it’s for: Self-hosters and data hoarders who already own or legally acquire music and want hands-off library management. Works as part of a stack: Lidarr grabs files, Navidrome or Plex streams them [1][3].
• Cost savings: Spotify runs $143.88/yr, Tidal HiFi Plus $239.88/yr. Lidarr is free software. Actual costs are a Usenet indexer subscription ($10–20/yr) and provider ($3–10/mo) — assuming infrastructure you already have [3].
• Key strength: Quality upgrades that no streaming service matches — Lidarr automatically replaces existing MP3s with FLAC when a better version hits your indexers, retroactively improving your whole library [README][4].
• Key weakness: Active metadata server infrastructure issues (GHI 5498) are impacting artist adds and library imports as of this review. And the primary use case for Usenet/torrent-sourced downloads sits in a legal gray area you need to think through honestly [README][1].

---

What is Lidarr

The GitHub repo description says it in five words: “Looks and smells like Sonarr but made for music.” That’s the most honest pitch available. Lidarr is part of the “arr” family of media automation tools — Sonarr for TV, Radarr for movies, Readarr for books, Lidarr for music. All of them follow the same architecture: watch for new content from things you care about, grab from configured sources automatically, sort and rename into a clean library structure.

Specifically, Lidarr monitors RSS feeds from multiple Usenet and BitTorrent indexers for new releases from artists you’ve added. When an album drops — or when you manually search — it sends the download job to your configured client (SABnzbd, NZBGet, qBittorrent, Deluge), waits for completion, then moves files into your music library folder with correct naming and metadata [README].

It also looks backward: scan an existing music library and Lidarr identifies what’s missing, then fills the gaps. A B-side you never grabbed, a remaster now available in FLAC when you only had MP3 320kbps — it finds and downloads those automatically without you thinking about it. That quality upgrade feature is genuinely useful and impossible in any streaming context. Your Spotify copy of a 2006 album is whatever Spotify has. Lidarr can find the 2024 remaster and swap it in automatically [README][4].

As of this review, Lidarr sits at 5,147 GitHub stars. Mature, actively maintained, with a comprehensive wiki at wiki.servarr.com and an active Discord community [README].

---

Why people choose it

The reviews point to automation depth, integration quality within the arr stack, and the fact that once configured correctly, you stop thinking about it.

Versus Headphones (the predecessor). The most direct competition is Headphones, the older Python-based music automation tool Lidarr effectively replaced. ShareConnector’s feature breakdown [4] is direct: Lidarr wins on nearly every dimension. Modern interface versus dated UI, active development versus stagnation, Prowlarr integration versus manual indexer management, automatic quality upgrade support versus no equivalent. The Geek Cookbook review [2] echoes this: Lidarr and Headphones “perform the same basic function,” but Lidarr is built on the arr stack and integrates with Prowlarr — a unified indexer manager that means you configure indexers once and every arr tool picks them up automatically. Nobody writing about Headphones recommends choosing it over Lidarr in 2026 [2][4].

Versus streaming services. This is the more honest comparison for this site’s audience. MakeTechEasier’s piece [3] is the most valuable counterweight to the self-hosting enthusiasm: they went all-in on self-hosting (music, video, cloud storage, everything), spent weeks on it, and went back to subscriptions. Their specific description of the Lidarr + Navidrome + Feishin stack as a Spotify replacement is accurate — and their conclusion that it’s complex, requires owned content, and demands ongoing maintenance is also accurate [3].

Versus doing nothing. For someone already managing a music folder manually, the before-Lidarr workflow is: notice an album exists, search for it, download it, move files, fix tags, rename folders, repeat for every gap. Lidarr automates everything after “artist I care about has released something.” The noted.lol review [1] describes the full automated stack delivering FLAC quality through a Deezer-sourced workflow — a capability streaming services don’t offer at any price.

The legal context. Self-hosters use Lidarr two ways: managing content they legitimately own (ripped CDs, purchased downloads), or automating downloads from Usenet and torrent indexers. Lidarr doesn’t distinguish. The noted.lol review [1] addresses this explicitly: they recommend being a paid Deezer subscriber and treat their setup as a personal backup mechanism, not a piracy shortcut. That’s the framing to bring to this tool. Downloading copyrighted music you haven’t purchased is infringement in most jurisdictions regardless of how automated and tidy the pipeline is.

---

Features

Based on the README and review coverage:

Core automation:

• Monitors multiple RSS feeds for new albums from configured artists [README]
• Scans existing library and identifies missing tracks or albums [README]
• Automatic quality upgrades — replaces files when better quality is indexed [README]
• Failed download handling — tries a different release if one fails [README]
• Manual search with full release browser — inspect every available release before committing [README]
• Fully configurable track renaming with token-based templates [README]

Download client integration:

• SABnzbd, NZBGet (Usenet) [README]
• Transmission, µTorrent, Deluge, qBittorrent (BitTorrent) [2]
• Blackhole (drop folder, works with any client) [2]
• Native Prowlarr integration — configure indexers once, all arr tools pick them up [2]

Media server integration:

• Kodi: notifications + library update + metadata [README]
• Plex: notifications + library update + metadata [README]
• Designed to chain with Navidrome for a complete self-hosted streaming stack [1][3]

UI and management:

• Calendar view: upcoming album releases at a glance [website]
• Queue management with active download status [4]
• Import lists: auto-follow artists from Last.FM or Headphones [README][website]
• Metadata writing: standardizes tags across your entire library [README][website]

Platform support:

• Windows (x64, x86 installer) [website]
• Linux (x64, arm, arm64, Musl) [website]
• macOS (Intel + Apple Silicon) [website]
• Docker via LinuxServer.io image — unofficial but de facto standard [2]
• NAS (Synology via SynoCommunity, with noted lag on package updates) [website]
• Raspberry Pi [README]

The “lidarr-on-steroids” fork. The noted.lol review [1] recommends not the official Docker image but youegraillot/lidarr-on-steroids — a fork with Deemix bundled in. Deemix downloads from Deezer. This fork ships both in a single Docker Compose stack and delivers FLAC quality with a Deezer premium account. It’s not official Lidarr, it’s widely used in self-hosting communities, and it carries the risks of any third-party fork [1].

Current known issue. The README carries an active warning: the Lidarr Metadata Server is “recovering and rebuilding the cache,” which is impacting adding artists and importing libraries [README]. This is tracked at GHI 5498. If you’re setting up today, check the current status before starting a large library import.

---

Pricing: SaaS vs self-hosted math

Lidarr has no SaaS version — it’s purely self-hosted. The comparison is against music streaming subscriptions.

Streaming services (what you’re replacing):

• Spotify: $11.99/mo individual (~$143.88/yr)
• Apple Music: $10.99/mo individual
• Tidal HiFi Plus: $19.99/mo (lossless + MQA)
• Amazon Music Unlimited: $10.99/mo

Lidarr self-hosted running costs:

• Lidarr software: $0 (GPL-3.0)
• Docker host or NAS you likely already have: $0 incremental
• Usenet indexer subscription (NZBGeek, NZBFinder): ~$10–20/yr
• Usenet provider (Frugal Usenet, Newshosting): ~$3–10/mo

For someone replacing Tidal HiFi Plus ($239.88/yr) to get lossless audio: self-hosted Lidarr with a Usenet subscription runs roughly $50–140/yr in indexer and provider costs. That’s $100–190/yr saved on top of infrastructure already running.

What this math hides. Two things. First, if you’re downloading copyrighted music you don’t own, you’re not saving money — you’re taking on legal risk instead of paying for access. MakeTechEasier [3] points out the second problem: to build a legitimately owned library from scratch, you buy music. Individual albums and season purchases add up fast. They cite $200 for 15 seasons of a single TV show as an example of the “sticker shock” [3]. The savings math works cleanly only if you already have a substantial owned collection.

The honest answer: Lidarr’s economics strongly favor self-hosting if you have existing owned content, infrastructure already running, and are comfortable with Usenet. They don’t favor self-hosting if you’re starting from zero and need to purchase everything legitimately.

---

Deployment reality check

Lidarr isn’t hard to install in isolation. It doesn’t do anything useful in isolation.

Minimum viable stack:

• Linux server or NAS (1GB RAM minimum, 2GB+ comfortable; Raspberry Pi works) [README]
• Docker with LinuxServer.io Lidarr image [2]
• Download client (SABnzbd/NZBGet for Usenet; qBittorrent/Deluge for torrents)
• Prowlarr (indexer manager) with at least one indexer configured [2]
• Storage — plan for it upfront

Common additions:

• Navidrome to stream your library to browsers and mobile apps [1][3]
• Reverse proxy (Caddy/nginx) + domain for HTTPS access
• Organizr or Heimdall as a dashboard for all arr tools [2]

What goes wrong:

Path configuration is the classic Docker pitfall [2]. Lidarr and your download client need shared volume paths so Lidarr can move files with hardlinks rather than copying. Get this wrong and your library fills with duplicate files or Lidarr can’t process downloads at all.

The metadata server issue (GHI 5498) is currently active. The README’s own warning says artist adds and library imports are impacted [README]. Don’t start a large library migration without checking this issue first.

Storage compounds faster than expected. MakeTechEasier [3] flagged this explicitly — a FLAC collection grows into terabytes. A 1,000-album library at FLAC quality needs 200–400GB minimum. Plan storage before you start.

NAS packages lag. Synology via SynoCommunity “typically has significant lag in providing updated packages,” per the official Lidarr website. Docker is the better path even on NAS hardware [website].

Realistic time estimates: Technically capable user deploying the full arr stack for the first time: 2–4 hours. Already running Sonarr/Radarr and adding Lidarr: 30–60 minutes. Non-technical user following a guide: budget a full day. MakeTechEasier [3] describes the music stack setup as taking them hours — and they’re tech-savvy enough to write about it.

---

Pros and cons

Pros

• Free software (GPL-3.0). No subscription, no per-user fees, no cloud dependency. Runs on your hardware, indefinitely, independent of whether the Lidarr project continues [README].
• Quality upgrades are genuinely powerful. Automatic format upgrades (MP3 → FLAC when available) don’t exist in any streaming service. Your library improves over time without action [README].
• Best arr stack integration. Prowlarr + Lidarr is the standard music automation path. One indexer configuration serves all arr tools [2].
• Fills library gaps automatically. Point it at an existing collection and it identifies and downloads what’s missing — useful for anyone with an incomplete library [README].
• Good UI by arr standards. Modern interface, useful calendar view, full manual search with release browser — a clear step above older tools like Headphones [4].
• Multi-platform. Works on Windows, Linux, macOS, Raspberry Pi, Docker, most NAS hardware [README][website].
• Active community and documentation. Discord, comprehensive Servarr wiki, wide self-hosting community knowledge base [README].

Cons

• Legal gray area is the central issue. Lidarr automates Usenet and torrent downloads. Using it for copyrighted music you haven’t purchased is infringement in most jurisdictions. This is not a small caveat [1].
• Active metadata server problems. The README’s own warning says adding artists and library imports are currently impacted by infrastructure issues [README]. Unresolved as of this review.
• Requires a full stack. Lidarr alone downloads nothing. You need an indexer, a download client, Prowlarr, and a music server to stream. Complexity multiplies [2][3].
• No music discovery. Lidarr manages artists you already know about. Finding new music is a separate workflow entirely — use Spotify, Last.FM, or Bandcamp for that, then import to Lidarr [README].
• Storage is entirely your problem. No CDN, no compression deal. A FLAC library grows into hundreds of gigabytes faster than expected [3].
• Deemix fork is unofficial. The highest-quality download path (lidarr-on-steroids + Deezer premium) is a third-party fork carrying its own maintenance risks [1].
• Setup is not casual. MakeTechEasier tried the full music self-hosting stack and went back to Spotify [3]. Their experience is representative of non-technical users.

---

Who should use this / who shouldn’t

Use Lidarr if:

• You have an existing music collection (ripped CDs, purchased downloads) you want automated management and gap-filling for.
• You’re already running arr tools (Sonarr, Radarr) — adding Lidarr is incremental work on infrastructure you already have.
• Audio quality matters to you: lossless files, properly tagged, stored locally, upgradable over time.
• You’re comfortable with Docker, self-hosting, and the legal context of what you’re downloading.
• You want to stop paying $11–20/mo for a streaming service you only use to access music you could own.

Wait until later if:

• The metadata server issue (GHI 5498) would affect your setup — check current status first before starting a large import.

Skip it if:

• You want music discovery, curated playlists, and new-release recommendations. Lidarr manages what you tell it about; it’s not a discovery platform.
• You’re starting from zero with no owned music and no appetite for the legal complexities of Usenet. The economics don’t work without existing content.
• You’re non-technical and MakeTechEasier’s experience [3] resonates — they tried this exact stack and returned to Spotify.
• Your NAS lacks Docker support and you don’t want stale package versions.

Skip Lidarr, use a music server only, if:

• You have a static library and just want to stream it. Navidrome or Jellyfin without Lidarr handles that fine. Lidarr adds value when you’re actively growing a collection.

Never choose Headphones over Lidarr:

• It’s effectively unmaintained and Lidarr superseded it completely [2][4].

---

Alternatives worth considering

Headphones — the predecessor. Python-based, older codebase, stagnant development. No reason to choose this over Lidarr in 2026 [2][4].

Beets — music library tagger and organizer. Different focus: metadata correction and library cleanup rather than download automation. Complements Lidarr rather than competing with it — Lidarr + Beets integration is documented [2].

Navidrome — not a competitor, a required collaborator. Navidrome is the streaming layer that serves your Lidarr-managed library to browsers and mobile apps. The standard self-hosted music stack is Lidarr + Navidrome [1][3].

Plex / Jellyfin (music library features) — both support music alongside video. If you’re already running either for movies and TV, Lidarr integrates natively (library updates, notifications) and adding music is an incremental step [README].

Deemix standalone — downloads from Deezer without the arr management layer. Useful for one-time bulk downloads; not for ongoing automated library management [1].

Spotify / Tidal / Apple Music — the honest alternative for anyone without existing content or without tolerance for the self-hosting complexity. MakeTechEasier [3] returned to subscriptions for legitimate reasons. $11/mo is worth paying if the self-hosting path costs you days of setup.

---

Bottom line

Lidarr is the right tool for a specific person: someone who already has a music collection, already runs arr-stack infrastructure, cares about audio quality above what streaming offers, and has thought through the legal context of their indexer setup. For that person, it’s excellent — automated gap-filling, quality upgrades, and a clean arr ecosystem integration that runs invisibly once configured. For everyone else, the honest answer is that it’s complex, requires owned content, and MakeTechEasier’s experience of returning to Spotify after weeks of effort [3] is a real outcome, not an edge case.

The metadata server issue in the README is worth checking before you start. The legal gray area around Usenet music downloads is worth thinking through before you automate. Neither disqualifies the tool — but both deserve honest consideration before you build the stack.

If the setup is the blocker, upready.dev deploys self-hosted stacks for clients. One-time fee, you own the infrastructure.

---

Sources

1. noted.lol — “Let’s Talk About The Perfect Self Hosted Music Stack - Lidarr, Deemix and Navidrome”. https://noted.lol/the-perfect-self-hosted-music-server/
2. Funky Penguin’s Geek Cookbook — “How to install Lidarr (Music arr tool) in Docker”. https://geek-cookbook.funkypenguin.co.nz/recipes/autopirate/lidarr/
3. MakeTechEasier — “Why Self-Hosting Isn’t Always Better Than Subscriptions”. https://www.maketecheasier.com/why-self-hosting-isnt-better-than-subscriptions/
4. ShareConnector — “Lidarr vs Headphones | Audio Automation & Downloader (2026)” (Jerone Jones). https://shareconnector.net/lidarr-vs-headphones/

Primary sources:

• GitHub repository and README: https://github.com/lidarr/lidarr (5,147 stars, GPL-3.0 license)
• Official website: https://lidarr.audio
• Servarr Wiki: https://wiki.servarr.com/lidarr
• Active issue GHI 5498 (metadata server): https://github.com/Lidarr/Lidarr/issues/5498