Automated music library
new albums imported as artists release
// official site: lidarr.audio ↗
MEDIA STACK · PRO TIER
Lidarrpro
Lidarr is the music counterpart in the *Arr stack — monitors artist releases via MusicBrainz, fetches new albums automatically, tags + organizes by artist/album/track. Music PVR with the same Sonarr/Radarr UX.
// What it is
A closer look.
Lidarr is the music counterpart in the *Arr stack — monitors artist releases via MusicBrainz, fetches new albums automatically, tags + organizes by artist/album/track. Music PVR with the same Sonarr/Radarr UX.
For music collectors building offline libraries via Usenet / torrent indexers, Lidarr is the canonical automation tool.
// Use cases
What it's for.
Concrete scenarios where teams pick Lidarr over the SaaS alternative.
Discography completion
track + fill gaps in artist discographies
Quality profiles
FLAC for favorites, V0 MP3 for the rest
Tagging via MusicBrainz
accurate metadata across formats
Folder organization
Plex / Navidrome / Jellyfin friendly structure
// Who it's for
Built for these teams.
If your team profile matches one of these, Lidarr is a strong fit out of the box.
Music collectors
building offline libraries
Audiophiles
with FLAC / hi-res requirements
Cord-cutters from Spotify
rebuilding lossless collections
DJs / podcasters
maintaining curated track libraries
Privacy-conscious listeners
avoiding streaming tracking
// Differentiators
Why teams pick Lidarr.
When evaluating self-hosted options for this category, here are the dimensions on which Lidarr consistently lands above the alternatives.
- ✓GPLv3 — fully open
- ✓Sonarr-family UX — familiar if you know Sonarr/Radarr
- ✓MusicBrainz native — best metadata source for music
- ✓Quality profiles — handle FLAC vs MP3 vs OGG cleanly
- ✓Active development — improvements quarterly
- ✓Strong ecosystem fit — Prowlarr + media servers + Bazarr (N/A)
// Integrations
Connects to.
The stack you'll plug Lidarr into — services, protocols, and adjacent apps in the BluixApps catalog.
◇
Indexers
via Prowlarr or direct
◈
Download clients
Transmission, qBittorrent, Deluge, SABnzbd, NZBGet
◆
Music servers
Navidrome, Plex Music, Jellyfin, Funkwhale
▣
Metadata
MusicBrainz primary, AllMusic fallback
▦
Tagging
beets / Picard compatible post-processing
▩
Notifications
Discord, Slack, Apprise, custom webhook
▼
Request mgmt
community add-ons (no official Overseerr-equivalent)
// Adoption & deployment
Notable users & community
- 4k+ GitHub stars
- Standard music PVR in self-hosted media stacks
- Active r/lidarr + Discord
- LinuxServer.io Docker image maintained
- Featured in self-hosted music guides alongside Navidrome / Jellyfin
What we ship
- LinuxServer.io image:
lscr.io/linuxserver/lidarr:latest - Volume layout:
/opt/lidarr/config,/opt/media/music,/opt/media/downloads - PUID/PGID 1000 default
- Port 8686 exposed
- Pairs with Prowlarr (indexers) + Navidrome (playback)
- HTTPS via Let's Encrypt reverse proxy
- Backup hook covers
/opt/lidarr/config
// Tips & operations
Run it properly.
Operational guidance from running this in production — what to lock down, what surprises people.
// PERFORMANCE
MusicBrainz API rate limits
initial library scan can be slow; expect overnight for large
// SECURITY
Quality profile examples
"FLAC > V0 > 320 MP3" works for most collectors
// OPERATIONS
Same root folder always
don't move libraries mid-stream; Lidarr loses tracking
// RELIABILITY
Disable manual import warnings
for bulk import scenarios
// DEPLOYMENT
Backup /config regularly
DB rebuild from scratch is painful with large library
// SCALING
Tagging pipeline
Lidarr → beets post-process for consistent tags
256
// min ram (MB)
4
// min disk (GB)
8686
// access port
http
// protocol
pro
// bluixapps tier
// Alternatives in Media stack
Compare with
Project resources
Official sitelidarr.audio ↗