FFmpeg conversion adds per-stream CPU demand that direct playback avoids.
Remote listeners and mixed client/device codec support.Requisitos de hardware de Ampache: RAM, CPU, almacenamiento y transcodificación
Planifica el hardware para Ampache 8 en cuanto a RAM, CPU, MariaDB, almacenamiento de música y transcodificación opcional, con recomendaciones prácticas para la instalación personalizada de ZimaOS.
Ampache requirements at a glance
Ampache 8 is a PHP-based music streaming server. Current upstream installation docs require a web server, PHP 8.5+ and a supported database stack, but do not publish a numerical hardware sizing table.
- RAM
- No numerical official minimum published. PHP, the database and other containers share the host memory budget.
- CPU
- No numerical official core minimum. Direct streaming is light; optional FFmpeg transcoding can make CPU the primary bottleneck.
- Storage
- No universal official minimum. The music library, album art, database, transcode cache and backups dominate capacity.
- Software
- Ampache 8 currently requires PHP 8.5+ and a web server; its current install documentation uses a database-backed stack such as MariaDB/MySQL.
- GPU
- No GPU is required for normal music serving. Ampache's documented transcoding path is FFmpeg-based and should be sized as a separate workload.
- Best Zima starting point
- ZimaBoard 2 832 suits a small direct-streaming library; ZimaCube 2 Standard is a better storage-first choice for large local music collections.
From official requirements to the right setup
Size Ampache by separating direct file streaming from optional transcoding and by treating the music library as the primary storage workload.
-
Official requirements
Start with current Ampache 8 software prerequisites: web server, PHP 8.5+ and a supported database. Upstream does not publish a universal CPU/RAM minimum.
-
Confirm your needs
Decide whether clients can direct-play source audio. Direct streaming is lightweight; on-the-fly FFmpeg transcoding adds CPU use per active stream.
-
Leave room to grow
Measure library size, album art and backup retention. Media capacity usually dwarfs the application/database footprint.
-
Run it on ZimaOS
On ZimaOS, use Install Custom App with Ampache's official Docker package, mount the music library read-only where practical, persist the database/config data, and monitor any transcoding workload.
Check every playback client
- Music library size
- Concurrent listeners
- Direct play versus transcoding
- Source codec/bitrate
- Database persistence
- Album-art/cache growth
- Backup retention
- Other media apps on the host
Official minimum requirements
Ampache 8's current documentation defines software prerequisites rather than numerical server hardware minimums.
Do not invent a 1 GB or 2 GB official minimum for Ampache. A small direct-streaming deployment is lightweight; library size and optional FFmpeg transcoding are the two variables that most change Zima hardware needs.
| Requirement | Official minimum | What this supports |
|---|---|---|
| RAM minimum | No numerical official minimum published | Upstream focuses on PHP, web-server and database prerequisites. |
| CPU minimum | No numerical official minimum published | Transcoding can create a much heavier CPU workload than direct streaming. |
| Storage minimum | No numerical official minimum published | Music, artwork, database and backups determine capacity. |
| PHP | PHP 8.5+ for Ampache 8 | Current Ampache 8 requirement. |
| Web server | Apache, lighttpd, nginx or IIS supported | Ampache receives the most testing with Apache. |
| Container deployment | Official ampache/ampache Docker package | The official Docker repository documents Docker and Compose deployment. |
When to upgrade your hardware
Ampache scales when music capacity or active transcoding grows, not because the PHP front end is inherently heavy.
Multiple clients require transcoding
The music library outgrows current disks
Library scans and other media apps compete for I/O
Lossless collections can consume terabytes while the Ampache application remains small.
Large FLAC or archival music libraries.Ampache may share storage with Navidrome, Jellyfin or download tools, making disk activity the broader bottleneck.
Consolidated media servers.Plan hardware growth with confidence
Scale Ampache around media storage first and transcoding compute second.
Keep the database/config on SSD
Small fast persistent storage improves metadata and application responsiveness.
Use SATA/NVMe with ZimaBoard 2 or an SSD tier on ZimaCube 2.Use multi-drive capacity for a large music archive
Music files, especially lossless libraries, are the dominant long-term storage workload.
ZimaCube 2 Standard provides six HDD bays and SSD expansion.Add CPU headroom only when transcoding demands it
Direct playback is light; stronger CPU is useful when FFmpeg must convert multiple streams.
ZimaCube 2 Pro provides a stronger Core i5 platform.Add RAM for a broader media stack
Ampache alone is light, but databases and other media containers increase whole-host memory use.
ZimaBoard 2 1664 offers 16 GB for larger all-in-one stacks.Can it run on ZimaOS?
Ampache is not currently confirmed as a public official one-click ZimaOS App Store page in the sources checked for this guide. It can still be deployed through Install Custom App using Ampache's official Docker package.
Custom install Ampache in ZimaOS
Use Install Custom App with the official Ampache Docker/Compose setup, persist database/config data, mount the music library, and expose the web service through your preferred ZimaOS port/reverse proxy.
Custom install Ampache in the ZimaOS app ↗Use the official Ampache Docker package
Ampache maintains an official Docker repository with both docker run and Compose examples plus persistent media/data mounts.
Review Ampache Docker deployment ↗Match Ampache 8 software requirements
Current Ampache 8 documentation requires PHP 8.5+ and a supported web-server/database stack.
Review Ampache installation ↗Choose Zima hardware for Ampache
Ampache is usually storage-bound rather than compute-bound until on-the-fly transcoding is enabled.
Will clients mostly direct-play music, or will the server transcode multiple streams?
Direct streaming / small library
ZimaBoard 2 is ample; prioritize reliable media and database storage.
- Best starting pointZimaBoard 2 832
- More app headroomZimaBoard 2 1664
Large library or more active transcoding
Use ZimaCube for multi-drive capacity and stronger CPU when FFmpeg conversion becomes significant.
- Storage-first platformZimaCube 2 Standard
- More transcoding CPUZimaCube 2 Pro
These are practical recommendations, not guarantees for simultaneous streams. Codec, bitrate, transcoding settings, storage performance and co-hosted media apps can change capacity.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Small direct-streaming Ampache libraries. | Ampache, database, library scans and direct audio playback. |
|
Add durable music/database storage; capacity rather than CPU will usually be the first limit. | Get Now |
| ZimaBoard 2 1664 | Ampache as part of a larger media-app stack. | Ampache, database and many companion media/download containers. |
|
16 GB is whole-stack headroom, not an Ampache minimum. | Get Now |
| ZimaCube 2 Standard | Large local music collections. | Ampache plus multi-drive FLAC/music storage, backups and broader NAS duties. |
|
Its main advantage here is six-bay storage; heavy transcoding may justify the Pro CPU instead. | Get Now |
| ZimaCube 2 Pro | Larger library plus more CPU-intensive FFmpeg transcoding. | Ampache, multiple active streams, transcoding and other media services. |
|
Actual concurrent transcode capacity depends on source/target codecs and FFmpeg settings. | 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 cover Ampache RAM, CPU, music storage, PHP, transcoding and ZimaOS deployment.
How much RAM does Ampache need?
Ampache does not publish a numerical official server RAM minimum. Practical memory depends on PHP, the database and other services sharing the host.
How many CPU cores does Ampache need?
There is no numerical official core minimum. Direct audio serving is light; FFmpeg transcoding can make CPU demand much higher.
How much storage does Ampache need?
There is no universal official disk minimum. Your music library, artwork, database, transcode cache and backups determine capacity.
What PHP version does Ampache 8 need?
Current Ampache 8 installation documentation requires PHP 8.5 or newer.
Does Ampache need a GPU?
No GPU is required for normal music serving. Optional transcoding is documented around FFmpeg and should be sized according to the actual codec workload.
Can ZimaBoard 2 run Ampache?
Yes. The 8 GB ZimaBoard 2 is a strong small-server option for direct streaming and can host a substantial music library on attached storage.
When should I choose ZimaCube 2 for Ampache?
Choose ZimaCube mainly when the music library and backups need multi-drive capacity, or when stronger CPU is useful for more transcoding.
Can Ampache run on ZimaOS?
Yes through Install Custom App using Ampache's official Docker package. A public official one-click ZimaOS page was not confirmed in the sources checked for this guide.
What sources informed this Ampache hardware guide?
The guide uses current Ampache 8 installation and official Docker documentation plus current Zima product pages for practical hardware matching.
