Readarr's retirement announcement identifies unusable metadata as a central reason the project ended. More CPU or RAM does not repair an upstream metadata ecosystem that is no longer maintained.
Existing users seeing missing/broken metadata and searches.Requisitos de hardware do Readarr: RAM, armazenamento e implementação de versões legadas
Verifique os requisitos de hardware e Docker do Readarr para instalações ZimaOS existentes, incluindo o estado de descontinuação, orientações de armazenamento e decisões de atualização mais seguras.
Readarr requirements at a glance
Readarr does not publish a numerical CPU or RAM minimum, and the more important 2026 fact is that the project has been retired. The Servarr team says the metadata service became unusable, development has stopped and users should seek alternatives. ZimaOS still lists Readarr, so this page is best treated as legacy sizing guidance for existing installations rather than a recommendation for a new deployment.
- Project status
- Retired. The Readarr team says the retirement took effect immediately and encourages users to seek alternatives.
- CPU
- No numerical official minimum is published. The project historically supported Windows, Linux, macOS and Raspberry Pi-class systems.
- RAM
- No numerical official minimum is published. TrueNAS currently exposes a 4 GB memory limit by default for its community app, but that is a container limit, not Readarr's requirement.
- Storage
- Persistent config/database storage is required, plus the ebook/audiobook library and download-client paths. Large metadata databases can outgrow tiny boot storage.
- GPU
- No dedicated GPU is required. Readarr manages metadata, searches, imports, naming and download-client integration.
- Best Zima approach
- Existing Readarr installs fit comfortably on ZimaBoard 2-class hardware, but for a new 2026 server the first decision should be whether to migrate away from retired Readarr rather than buying stronger hardware for it.
From official requirements to the right setup
Readarr sizing now starts with whether you should keep the retired app at all.
-
Official requirements
Confirm this is an existing/legacy Readarr deployment. The upstream project is retired and explicitly recommends exploring alternatives.
-
Confirm your needs
If keeping Readarr temporarily, size it like a lightweight Arr database/application: persistent config, library scans, RSS/search activity and integrations with download clients and Calibre matter more than CPU cores.
-
Leave room to grow
Map book/audiobook and download paths correctly. The application can scan existing libraries and integrate with external download clients, so file-path layout and storage capacity are more likely to create problems than raw compute.
-
Run it on ZimaOS
Install or retain Readarr on ZimaOS only with a migration plan. Back up its config/database, monitor storage growth and avoid investing in hardware solely to extend a retired application.
Check every playback client
- Existing legacy deployment versus new installation
- Current Readarr database/config backup
- Ebook and audiobook library size
- Library scan/import frequency
- Indexer/RSS/search activity
- Download-client and Calibre integrations
- Persistent config and media path mappings
- Migration target or replacement plan
Official minimum requirements
Readarr's official project and retired documentation do not publish a numerical CPU or RAM minimum. Current sources are more valuable for project status and container compatibility than for hardware sizing.
Do not present TrueNAS's generic 2 CPU / 4 GB resource limit as a Readarr requirement. Existing Readarr installations are usually lightweight compared with media transcoding, but the project is retired and should not drive a new hardware purchase.
| Requirement | Official minimum | What this supports |
|---|---|---|
| Project status | Retired | The upstream team says the retirement is effective immediately and recommends alternatives. |
| CPU | No numerical minimum published | The repository historically lists Windows, Linux, macOS and Raspberry Pi among supported platforms. |
| RAM | No numerical minimum published | No current official Readarr source defines a memory floor. |
| Third-party container limit | TrueNAS default: 2 CPUs / 4096 MB memory limit | This is a configurable app resource limit and should not be interpreted as the amount Readarr consumes or requires. |
| Container status | LinuxServer image deprecated | LinuxServer says the image will not be updated or supported because upstream retired the project. |
| Persistent storage | Config/database plus book/audiobook paths | Library size and metadata growth determine real storage needs. |
When to upgrade your hardware
For Readarr in 2026, migration is usually a better response than hardware escalation.
The metadata workflow is failing
The config/database is outgrowing small system storage
The whole Arr/download stack needs more resources
Arr-style databases and metadata can grow with the library. A Raspberry Pi user, for example, reported Readarr data filling a very small internal storage device; this is a storage-layout problem rather than a CPU requirement.
Large libraries on tiny eMMC/boot volumes.If Readarr runs beside Prowlarr, download clients, Calibre and media applications, the combined stack can justify more RAM or storage. Upgrade for the surviving services you intend to keep after Readarr migration.
All-in-one media and ebook servers.Plan hardware growth with confidence
Protect the existing Readarr state, then spend growth budget on a replacement workflow and shared storage.
Back up Readarr before changing anything
With upstream retired and container support deprecated, preserving the existing database/config is more important than aggressive upgrades.
Keep backups on storage independent of the live appdata path.Keep appdata off tiny boot media
Metadata databases can expand even though ebook files themselves may be small. Tiny eMMC or system partitions are poor long-term appdata locations.
Use persistent SSD/NVMe/SATA application storage with comfortable free space.Do not allocate 4 GB just because TrueNAS shows it
TrueNAS exposes a 4 GB memory limit for the community app. A limit is a ceiling/configuration default, not proof that Readarr requires or reserves the entire amount.
Monitor actual process/container usage before changing memory allocation.Plan the replacement alongside storage growth
Readarr upstream recommends alternatives. New drive bays or RAM should support the future ebook/audiobook stack rather than lock you further into retired software.
Choose Zima hardware based on the replacement app, Calibre/audiobook needs and shared storage plan.Can it run on ZimaOS?
Readarr remains listed in the ZimaOS App Store, but its upstream status is retired.
Treat the ZimaOS Readarr app as legacy
The current ZimaOS App Store still lists Readarr, while upstream has retired the project. Existing installations may remain useful during transition.
Open Readarr in the ZimaOS App StoreDo not expect active upstream fixes
The Servarr team says support is limited to a brief transition period and encourages alternatives.
Read the Readarr retirement announcementRecognize container-image deprecation
LinuxServer has marked its Readarr image deprecated and says it will not be updated or supported.
Read LinuxServer Readarr deprecation noticeChoose Zima hardware for an existing Readarr workload
Readarr itself is not a reason to buy high-end hardware in 2026. Choose hardware for the ebook/audiobook storage and the replacement stack you intend to keep.
Are you maintaining Readarr temporarily or building a broader book/media server?
Temporary legacy Readarr plus light services
Current ZimaBoard 2 resources are more than sufficient for the control/database workload.
- Legacy personal Readarr instanceZimaBoard 2 832
- More replacement/ebook services during migrationZimaBoard 2 1664
Large multi-drive ebook/audiobook and media stack
Move up for storage and future replacement applications, not to accelerate retired Readarr.
- Integrated multi-drive libraryZimaCube 2 Standard
- Large all-in-one storage/application serverZimaCube 2 Pro
Readarr is retired. These product tiers describe capacity for an existing legacy workload and surrounding services, not an endorsement of a new Readarr deployment.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Keeping an existing personal Readarr instance online during migration. | Light Readarr database/search/import activity and a small set of companion services. |
|
The limiting factor is more likely project retirement or metadata failure than this hardware. | Get Now |
| ZimaBoard 2 1664 | Running legacy Readarr while testing replacement ebook/audiobook applications. | Readarr plus Calibre, indexers, downloaders and other lightweight containers. |
|
Buy the extra RAM for the migration stack, not for Readarr alone. | Get Now |
| ZimaCube 2 Standard | A large multi-drive book/audiobook archive that will outlive Readarr. | Library storage plus replacement automation and media services. |
|
The integrated bays are the reason to upgrade; Readarr itself does not require a Core i3. | Get Now |
| ZimaCube 2 Pro | A broader all-in-one storage and media environment. | Large libraries, backups, downloads and replacement services alongside any temporary Readarr instance. |
|
Do not justify 10GbE or stronger compute on Readarr alone. | Get Now |
What the Press Says
Highlights from trusted reviewers worldwide.
“ZimaCube 2: Not just another NAS, tested with 25TB storage, local AI agents, 4K transcoding, and real homelab workflows.”Read full review
“The ZimaBoard 2 is a compact x86 server board that can be turned into a mini NAS, home server, media box, or self-hosting hub.”Read full review
“ZimaCube 2: A modern, high-performance NAS with plenty of room to grow—built for users who want more than basic storage.”Read full review
“Coverage focused on ZimaCube 2's open hardware foundation, no monthly fee, and self-hosting flexibility.”Read full review
Loved by the Community
Stories and reviews from people who build with Zima every day.
★★★★★
Zima Blade Little yet Powerful
Maybe I am not digital natives but I live with PCs since 12 years old in 1984 when IBM PC clone come to my home. Many years have passed and many operating system I've tried. For me Zima blade and CasaOS was a quantum leap for home PC enthusiast and server lab machine to make me stay curious and relevant for this era.
★★★★★
Very good!!
I use ZimaCube Pro as 5th Proxmox cluster node. It runs several VMs and containers, including a VM with GPU passthrough to run a self-hosted LLM. A specific LXC container runs a Samba server for NAS capabilities using four of six RAID 6 SATA HDDs with ZFS.
★★★★★
Great innovation for mini server!
It is very useful and makes a powerful mini server for many purposes, including university and college students in engineering and electronics. Thank you so much for making this server.
★★★★★
Avaliação ZimaBoard 2
Construí um servidor de uso pessoal. O desempenho está muito bom e funciona perfeitamente onde quer que eu esteja. A surpresa é não dependermos de grandes estruturas para termos nosso próprio servidor de dados. Como iniciante, estou gostando bastante do ZimaOS, pois ele é simples e eficiente.
Frequently asked questions
These answers prioritize Readarr's retirement status over stale hardware advice.
Is Readarr still actively maintained?
No. The Readarr/Servarr team announced the project has been retired, citing unusable metadata and lack of resources to rebuild the metadata path.
How much RAM does Readarr need?
There is no numerical official RAM minimum. TrueNAS shows a configurable 4 GB memory limit for its community app, but that is not a Readarr requirement.
Can ZimaBoard 2 832 run Readarr?
Yes for an existing legacy instance. Its 8 GB RAM and modern CPU are far beyond the lightweight database/control-plane demands of Readarr itself.
Does Readarr need a GPU?
No. Readarr handles metadata, searches, imports, naming and integrations rather than video/audio transcoding.
Should I install Readarr on a new ZimaOS server in 2026?
A new deployment is difficult to recommend because upstream has retired Readarr and explicitly encourages alternatives. If the ZimaOS app remains available, treat it as legacy compatibility rather than an actively maintained choice.
Why is the LinuxServer Readarr image deprecated?
LinuxServer says the image is deprecated, unsupported and will not be updated because upstream retired the project.
When should I choose ZimaCube 2 for Readarr?
Choose it for a large multi-drive ebook/audiobook archive and the broader replacement/media stack. Do not buy ZimaCube-class compute simply for Readarr.
Does more CPU or RAM fix Readarr metadata problems?
No. The project's retirement announcement identifies the metadata service itself as unusable; host hardware cannot repair that upstream dependency.
What sources and further reading informed this Readarr hardware guide?
The Readarr website and GitHub repository are the primary sources for the retirement notice, historical platform support and application role. Servarr's retired Docker documentation and LinuxServer's deprecation notice establish the current container-support status. TrueNAS provides a third-party configurable 2 CPU / 4 GB resource limit, which is explicitly treated as a limit rather than a minimum. The ZimaOS App Store confirms Readarr remains listed for existing ZimaOS users.
