model family, resolution, batch size, offloading and simultaneous generation jobs. Time the job and identify CPU, storage or external-service waits before replacing hardware.
Imports, processing and simultaneous users.Requisitos de hardware do Fooocus: RAM, CPU, armazenamento e GPU para execução de tarefas e armazenamento de modelos
Planeie a RAM, a CPU, o armazenamento persistente e as dependências de serviços do Fooocus, com dimensionamento do ZimaOS baseado na carga de trabalho, cópias de segurança e escolhas práticas de hardware.
Fooocus hardware requirements at a glance
Fooocus supports local image-generation presets and model pipelines. Size it around model family, resolution, batch size, offloading and simultaneous generation jobs, including the complete service stack and durable data. Match the model and workflow to a supported accelerator. CPU execution or offloading support does not imply practical interactive generation on an N150. Use a separate GPU worker when necessary.
- RAM
- The linked source does not establish a fixed numerical whole-host baseline for this complete workload. Size the full stack during the busy operation described below.
- CPU
- The linked source does not establish a fixed numerical whole-host baseline for this complete workload. Measure CPU use during realistic activity.
- Storage
- Persist checkpoints, text encoders, VAE files, workflows, generated output and temporary caches.
- Required services
- Follow the service topology in the linked upstream deployment for the chosen edition; include every required database, worker and storage service.
- Main sizing variable
- model family, resolution, batch size, offloading and simultaneous generation jobs.
- Practical Zima starting point
- Supporting storage/control services; inference or generation requires a separately verified backend. A Zima device is not certified here for the chosen model, accelerator or interactive generation speed.
From official requirements to the right setup
Plan the complete Fooocus workload before selecting a server.
-
Official requirements
Choose the exact edition, stable release and supported container/runtime. Follow the service topology in the linked upstream deployment for the chosen edition; include every required database, worker and storage service.
-
Confirm your needs
Test a representative busy operation: model family, resolution, batch size, offloading and simultaneous generation jobs. Record peak resident memory, CPU, disk latency and completion time, including other containers.
-
Leave room to grow
Place active state on reliable persistent storage. Persist checkpoints, text encoders, VAE files, workflows, generated output and temporary caches. Budget working space for an upgrade or import and test recovery before relying on the deployment.
-
Run it on ZimaOS
Verify the project has a supported headless/runtime deployment before using ZimaOS. The README hardware table varies by GPU and operating system. Low-memory fallback can require substantial swap/free disk and be slow; check maintenance and model compatibility before selecting it for a new deployment.
Check every playback client
- Exact edition and stable release
- Compatible amd64 image/runtime
- All required companion services
- Realistic peak activity
- Persistent data and file ownership
- Free host ports and reachable URLs
- Working space and backup retention
- Successful database/file restore
Official minimum requirements
Reviewed October 30, 2026 against the linked upstream deployment documentation. Numerical values retain their stated minimum, recommendation or example scope; select release-compatible instructions before installation.
The README hardware table varies by GPU and operating system. Low-memory fallback can require substantial swap/free disk and be slow; check maintenance and model compatibility before selecting it for a new deployment. Numerical examples above retain their stated deployment scope; co-hosted services and independent backups need additional capacity.
| Requirement | Official minimum | What this supports |
|---|---|---|
| RAM guidance | The linked source does not establish a fixed numerical whole-host baseline for this complete workload. Size the full stack during the busy operation described below. | Official guidance keeps its original test, recommendation or example scope. |
| CPU guidance | The linked source does not establish a fixed numerical whole-host baseline for this complete workload. Measure CPU use during realistic activity. | Core counts do not predict a fixed user, device or document capacity. |
| Storage planning | Persist checkpoints, text encoders, VAE files, workflows, generated output and temporary caches. | Installation space is separate from retained content, working files and backups. |
| Service topology | Follow the service topology in the linked upstream deployment for the chosen edition; include every required database, worker and storage service. | Include every stateful companion service in the host budget. |
| Persistent state | Persist checkpoints, text encoders, VAE files, workflows, generated output and temporary caches. | An image rebuild or container replacement is not a backup. |
| Deployment boundary | The README hardware table varies by GPU and operating system. Low-memory fallback can require substantial swap/free disk and be slow; check maintenance and model compatibility before selecting it for a new deployment. | Check the linked project instructions for the selected edition and release. |
When to upgrade your hardware
Use observed Fooocus workload pressure to decide when an upgrade is warranted.
Busy operations exceed the available window
The complete stack runs short of memory
Persistent data approaches available capacity
Inspect the application and each required service for OOM events, sustained swap or growing queues. Reduce unnecessary concurrency before adding capacity.
Shared hosts and background work.Persist checkpoints, text encoders, VAE files, workflows, generated output and temporary caches. Track primary state and backup retention separately.
Long-lived installations and growing collections.Plan hardware growth with confidence
Address storage, memory, compute and deployment limits separately.
Use suitable active storage
Put latency-sensitive application/database state on durable local SSD storage and keep recoverable copies.
SATA or PCIe SSD according to measured data growth.Add memory for the complete stack
Choose a higher-RAM host when peak application and companion-service usage leaves inadequate OS headroom.
ZimaBoard 2 1664 or ZimaCube 2 Pro according to the measured constraint.Separate capacity from compute
A multi-drive system helps when retained content and backup storage are the problem; it is not automatically a faster application.
ZimaCube 2 when a broader multi-drive workload justifies it.Fix the observed bottleneck
The README hardware table varies by GPU and operating system. Low-memory fallback can require substantial swap/free disk and be slow; check maintenance and model compatibility before selecting it for a new deployment.
Check service configuration, I/O and network behavior before selecting a stronger CPU.Can it run on ZimaOS?
Official one-click ZimaOS availability has not been certified for this guide. Use the supported upstream runtime and service topology; consider Custom Install only when a maintained compatible container and all required host capabilities are available.
Custom install Fooocus in ZimaOS
Follow the service topology in the linked upstream deployment for the chosen edition; include every required database, worker and storage service. Persist: Persist checkpoints, text encoders, VAE files, workflows, generated output and temporary caches.
Custom install Fooocus in the ZimaOS app ↗Use the official Fooocus deployment instructions
Keep the selected stable release, persistent paths and companion services aligned with upstream documentation.
Review Fooocus official installation ↗Check workload-specific deployment details
The README hardware table varies by GPU and operating system. Low-memory fallback can require substantial swap/free disk and be slow; check maintenance and model compatibility before selecting it for a new deployment.
Review Fooocus deployment details ↗Which Zima hardware fits Fooocus?
Supporting storage/control services; inference or generation requires a separately verified backend.
Which workload best matches your Fooocus deployment?
Model artifacts, workflow files and supporting services
Use Zima for durable assets and validated supporting services while an appropriately sized compatible worker handles compute.
- Supporting storage optionZimaBoard 2 1664
These are practical workload recommendations, not official app requirements, compatibility certification, measured capacity limits or performance guarantees. Include all co-hosted services and independent backups.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 1664 | Model artifacts and supporting services | Retained assets, configurations and a verified compatible control layer; heavy inference/generation runs on its own supported worker. |
|
The README hardware table varies by GPU and operating system. Low-memory fallback can require substantial swap/free disk and be slow; check maintenance and model compatibility before selecting it for a new deployment. | Get Now |
| ZimaCube 2 Pro | Model artifacts and supporting services | Retained assets, configurations and a verified compatible control layer; heavy inference/generation runs on its own supported worker. |
|
The README hardware table varies by GPU and operating system. Low-memory fallback can require substantial swap/free disk and be slow; check maintenance and model compatibility before selecting it for a new deployment. | 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
Answers to Fooocus RAM, CPU, storage, Docker, database and ZimaOS sizing questions.
How much RAM should I plan for Fooocus?
The linked source does not establish a fixed numerical whole-host baseline for this complete workload. Size the full stack during the busy operation described below. Include ZimaOS, the application and its companion services rather than reserving the entire machine for one container.
What drives the CPU requirement?
The linked source does not establish a fixed numerical whole-host baseline for this complete workload. Measure CPU use during realistic activity. The workload to test is: model family, resolution, batch size, offloading and simultaneous generation jobs.
Which data must survive a container update?
Persist checkpoints, text encoders, VAE files, workflows, generated output and temporary caches. Preserve a consistent database/file set and verify that your recovery procedure restores a working application.
What other services belong in the budget?
Follow the service topology in the linked upstream deployment for the chosen edition; include every required database, worker and storage service.
Does this workload need a dedicated GPU?
The README hardware table varies by GPU and operating system. Low-memory fallback can require substantial swap/free disk and be slow; check maintenance and model compatibility before selecting it for a new deployment.
Can I deploy it on ZimaOS?
Use an amd64 container and the current upstream service topology through Custom Install when a suitable maintained image is available. Container availability alone is not a compatibility certification.
What should I check before upgrading hardware?
The README hardware table varies by GPU and operating system. Low-memory fallback can require substantial swap/free disk and be slow; check maintenance and model compatibility before selecting it for a new deployment. Measure the same representative operation before and after a configuration or hardware change.
Which Zima device is a practical starting point?
Supporting storage/control services; inference or generation requires a separately verified backend. Choose the inference worker from the model/backend requirements rather than assuming an 8 GB or 16 GB NAS can run every model.
What sources informed this Fooocus hardware guide?
This guide was reviewed against the linked project deployment documentation on October 30, 2026. Zima device choices are editorial workload guidance, separate from upstream requirements and measured performance.
