Whisparr Docker Setup Guide for Beginners (Step by Step)
Deploy Whisparr as a container in minutes: image choice, volumes, ports and first-run configuration.
Read guide →
If you found Whisparr, you have probably already met Radarr or Sonarr. All three belong to the *arr family and share the same architecture, which is great news: nearly everything you learned in one applies to the others. The differences come down to what kind of library each app is built to manage.
The shared DNA
All *arr apps follow the same loop: monitor a list, search indexers, hand grabs to a download client, then import, rename and upgrade. They share the concepts of quality profiles, root folders, custom formats-style scoring, an Activity queue and a Wanted list, and they all pair with Prowlarr for centralized indexer management. Visually, the web interfaces are close siblings — if you can navigate one, you can navigate them all.
What each app is for
| Sonarr | Radarr | Whisparr | |
|---|---|---|---|
| Library type | TV series (episodes, seasons) | Movies (single items) | Adult media libraries |
| Data model | Series → seasons → episodes | One entry per film | Varies by branch (v2 vs v3) |
| Community size | Very large | Very large | Smaller, active |
| Documentation | Extensive | Extensive | Lighter — sites like this fill the gap |
The practical takeaway: you do not choose between these apps. Each manages a different kind of library, and most people run the ones they need side by side in the same stack.
What transfers from Radarr/Sonarr to Whisparr
- Deployment knowledge: the Docker patterns are identical — PUID/PGID, a
/configvolume, one shared/dataparent. Our Docker guide will feel familiar. - Indexers: if Prowlarr already feeds Radarr and Sonarr, adding Whisparr is one more application entry.
- Download clients: the same SABnzbd/NZBGet/qBittorrent connection, ideally with a separate category per app.
- Folder philosophy: hardlink-friendly layouts work the same way; just give Whisparr its own library folder under the shared data parent.
What does not transfer
- Databases: you cannot import a Radarr or Sonarr database into Whisparr — each app keeps its own.
- Metadata expectations: matching and naming behave differently because the underlying library types differ; expect to tune Whisparr's naming scheme separately (see best settings).
- Version assumptions: Whisparr's v2/v3 branch split is its own story — do not assume its versions line up with Radarr's or Sonarr's.
Running all of them together
A tidy multi-app stack gives each app its own config volume and its own download category, but shares one /data mapping and one Prowlarr. Ports typically line up as a sequence (Sonarr 8989, Radarr 7878, Whisparr 6969), which keeps bookmarks memorable and firewall rules simple.
