Arr media automation: hardware requirements
Sonarr, Radarr, Prowlarr and download clients — automated media fetching.
Hardware tiers
| Tier | CPU | RAM | Storage | GPU | VRAM | Network |
|---|---|---|---|---|---|---|
| Minimum sensible | 2 cores | 4 GB | 2 TB (hdd) | None | — | 1 GbE |
| Recommended | 4 cores | 8 GB | 8 TB (hdd) | None | — | 1 GbE |
| Comfortable | 8 cores | 16 GB | 24 TB (hdd) | None | — | 2.5 GbE |
| Overkill | 13 cores | 26 GB | 48 TB (hdd) | None | — | 2.5 GbE |
- Minimum sensible: The smallest build that genuinely works — tight, focused, no fluff.
- Recommended: The sweet spot: handles the service plus the usual side-services.
- Comfortable: Real headroom — this service will never be the bottleneck.
- Overkill: More than you will ever use for this service alone — spend the money elsewhere.
Beyond Comfortable — 8 cores, 16 GB RAM, 24 TB: headroom you will never use for this service alone.
Runs well with
Plex, Jellyfin
Frequently asked questions
How much RAM does Arr media automation need?
4 GB is the sensible minimum, 8 GB covers most real setups, and 16 GB gives comfortable headroom.
How many CPU cores does Arr media automation need?
2 cores are the minimum, 4 cores the sweet spot, and 8 cores comfortable when shared with other services.
Can I run several services on one machine?
Yes — most services share resources. Use the planner and select several services; the engine sums and overlaps the requirements instead of stacking them.
What if I already have hardware?
Register it in My hardware and the analysis shows exactly which services your current system can comfortably run — including an honest “do nothing”.