Each active request can consume PHP worker memory and database/cache resources. Because Nextcloud's official memory figures are per process, simultaneous activity can raise whole-system RAM demand far more than the registered user count alone suggests.
For families, clubs or small teams moving from one or two occasional users to regular simultaneous sync and web access.Wymagania sprzętowe serwera Nextcloud: procesor, pamięć RAM, przestrzeń dyskowa i liczba użytkowników
Poznaj wymagania serwera Nextcloud dotyczące pamięci RAM, procesora, dysku SSD, baz danych, Redis, liczby użytkowników, Nextcloud AIO oraz sprzętu domowego serwera Zima.
Nextcloud server requirements at a glance
Size Nextcloud around concurrent PHP requests, database/cache activity and file storage rather than one universal user-count formula. A small personal cloud can be light; previews, Office, Talk, antivirus, full-text search and many simultaneous users add separate resource demand.
- CPU
- Nextcloud does not publish one universal CPU-core minimum for every server. A 64-bit CPU, OS and PHP stack is strongly recommended; extra cores become useful as concurrent requests, previews, Office, Talk, antivirus or background jobs increase.
- RAM
- Nextcloud's official memory requirement is per PHP process: at least 128 MB RAM per process and 512 MB per process recommended. This is not a whole-server RAM specification. Practical whole-system figures such as 2–4 GB come from third-party sizing guides and depend on concurrency and enabled services.
- Storage
- Keep database, cache and other latency-sensitive application data on responsive storage. Official Nextcloud AIO recommends SSD storage, discourages SD cards and notes that HDD storage can work more slowly. Size user files, redundancy and backups separately.
- Database and cache
- For normal persistent deployments, use a supported production database such as MariaDB or PostgreSQL. Nextcloud documents SQLite for testing and minimal instances. Official AIO uses PostgreSQL, Redis and APCu.
- Network
- Nextcloud publishes no single network-speed requirement for every deployment. Local sync depends on file size and concurrency; remote access is also limited by the server site's upload bandwidth, reverse-proxy path and Internet connection.
- Best Zima starting point
- Start with ZimaBoard 2 832 for a small personal or family Nextcloud when you add suitable SSD and data storage. Choose 1664 for more memory-intensive apps and co-hosted services, or ZimaCube 2 when multi-drive capacity, backup space and heavier collaboration become the larger requirement.
From official requirements to the right setup
Nextcloud sizing starts with users, enabled apps and concurrency, then separates PHP/database/cache resources from bulk file capacity, backup capacity and the other services sharing ZimaOS.
-
Official requirements
Use Nextcloud's official Administration Manual as the technical baseline: a 64-bit CPU, OS and PHP stack is strongly recommended, while memory is specified per process rather than as a single whole-server minimum.
-
Confirm your needs
Choose a production database and cache path deliberately. MariaDB and PostgreSQL are normal supported production choices, while SQLite is documented for testing and minimal instances. In AIO, PostgreSQL, Redis and APCu are included and pre-integrated.
-
Leave room to grow
Separate fast application state from bulk user files. Official Nextcloud AIO recommends SSD storage and discourages SD cards because its database and other components perform many writes; HDD storage can still be used where capacity matters more than latency.
-
Run it on ZimaOS
Install the ZimaOS package or deploy official Nextcloud AIO as a separate installation path, map persistent storage, then test file sync, large uploads, previews, background jobs and any Office or Talk workload with the real users and devices you expect.
Check every playback client
- Number of users and expected simultaneous activity
- Files-only use or Calendar, Contacts, Office and Talk
- Preview generation, antivirus and full-text search
- Database choice plus Redis/APCu cache configuration
- Application/database state on SSD or NVMe where practical
- User-data capacity, redundancy and future growth
- Local LAN sync or Internet-facing remote access
- Other ZimaOS containers, VMs, backups and media workloads
Official minimum requirements
Nextcloud does not publish a universal whole-server CPU/RAM table. Its Administration Manual gives platform, database, web/PHP and per-process memory requirements, while actual system sizing varies with users, apps, files and activity.
Use 128 MB RAM per process as the official minimum and 512 MB per process as the recommendation, not as total system RAM. Use a 64-bit stack, a production database for normal multi-user deployments and responsive storage for database/cache activity; size the whole server from concurrency and enabled apps.
| Requirement | Official minimum | What this supports |
|---|---|---|
| CPU architecture | 64-bit CPU, OS and PHP strongly recommended | Nextcloud still documents 32-bit support with limitations, including the 2038 date boundary and possible incompatibility with some external apps. |
| Memory per process | 128 MB minimum; 512 MB recommended per process | This is not the RAM requirement for the entire server. The built-in updater requires at least 256 MB, and total memory varies with users, apps, files and server activity. |
| Database | Use a supported production database for normal deployments | Current Nextcloud documentation supports MariaDB, PostgreSQL and other documented backends. SQLite is only recommended for testing and minimal instances; it should not be used as the basis for sizing a normal multi-user server. |
| Web and PHP stack | Apache or nginx with a currently supported PHP version | Supported PHP and database versions change between Nextcloud releases. Match the exact Nextcloud release you deploy instead of hard-coding a rapidly aging version into a hardware decision. |
| Application/database storage | No universal capacity; SSD recommended by official Nextcloud AIO | AIO discourages SD cards because database and application components perform many writes. HDD storage can work but is slower than SSD. |
| Official AIO stack | PostgreSQL + Redis + APCu + optimized PHP-FPM included | AIO uses APCu as local cache, Redis as distributed cache and for file locking, PostgreSQL as the database, and defaults to a maximum of 512 MB RAM per PHP process. That 512 MB limit is not a whole-server RAM recommendation. |
When to upgrade your hardware
Upgrade Nextcloud when concurrency, optional collaboration services or data growth changes the workload. Raw file capacity and application compute should be treated as separate upgrade triggers.
More users are active at the same time
Office, Talk, previews or search become important
The private cloud outgrows a two-drive storage plan
Official Nextcloud AIO can add Office, Talk high-performance services, antivirus, Imaginary previews and full-text search as separate containers or services. These workloads can materially increase CPU and memory demand beyond a basic Files, Calendar and Contacts instance.
For users turning Nextcloud from private file storage into a full collaboration platform.User files, versions, snapshots and backups usually become the dominant capacity requirement. Move to a multi-drive platform when storage growth, redundancy and recovery planning become the constraint rather than the PHP/database application stack.
For long-term photo, document and project archives that need easier multi-drive expansion and recovery planning.Plan hardware growth with confidence
Nextcloud scales most cleanly when latency-sensitive application state, bulk user files, backups and optional collaboration services are planned independently.
Keep database and cache workloads on SSD
Official Nextcloud AIO recommends SSD storage and specifically discourages SD cards for its write-heavy database and application components. Fast local storage reduces latency for database, cache, locking and metadata operations.
Use SATA or NVMe SSD for application/database state when practical, even if larger user-file capacity lives on HDD storage.Size user files separately from the application
Nextcloud publishes no fixed user-data capacity because documents, photos, videos, shared folders and version history vary enormously. Size disks from real data plus future growth rather than from the application footprint.
Use ZimaBoard 2 for a compact one- or two-drive cloud, or ZimaCube 2 when integrated multi-drive expansion and storage tiers become the stronger requirement.Plan backups as a separate capacity pool
A synchronized copy is not automatically a backup. Nextcloud AIO can optionally use BorgBackup and supports instance restore from a backup archive, but user data or external storage outside the protected scope still needs a deliberate backup plan.
Keep at least one recovery copy outside the live data pool and budget enough space for database/configuration plus the user files that cannot be replaced.Add collaboration services only when needed
AIO includes Redis/APCu in its core stack, while Office, Talk, Talk Recording, antivirus, Imaginary and full-text search are optional additions. Add CPU and memory for the services you will actually enable rather than sizing a Files-only server as if every optional component were active.
Choose more RAM and CPU for the optional services that will actually run instead of sizing a simple Files-only server as if every Nextcloud feature is enabled.Can it run on ZimaOS?
Nextcloud is currently listed in the ZimaOS App Store. The ZimaOS package is a convenient deployment path, while Nextcloud AIO is a separate official upstream installation method with its own managed multi-container architecture.
Install Nextcloud from the ZimaOS App Store
Use the ZimaOS App Store when you want Nextcloud integrated into the ZimaOS application workflow. Before migrating important data, verify the package version, persistent paths, database backend and update/backup behavior of the exact package installed.
Open Nextcloud in the ZimaOS App StoreDo not assume the ZimaOS package is Nextcloud AIO
Do not assume the ZimaOS App Store package is identical to Nextcloud AIO. AIO is the official upstream multi-container method and explicitly includes PostgreSQL, Redis, APCu and optional collaboration components. Treat these as separate deployment paths unless the installed package explicitly identifies itself as AIO.
Read the official Nextcloud AIO projectPlace database, cache and user data deliberately
Place latency-sensitive application/database state on responsive local storage and map bulk user files to the intended Zima storage pool before a large migration. Verify which paths are included in the backup method you choose.
Read the ZimaOS Docker app adaptation guideChoose Zima hardware for your Nextcloud workload
Separate application concurrency from storage growth. ZimaBoard 2 already has ample CPU and memory for a light personal cloud; ZimaCube 2 becomes more compelling when Nextcloud also needs integrated multi-drive capacity, larger backup space or heavier co-hosted services.
Will your Nextcloud data and backups fit comfortably in a compact one- or two-drive storage plan?
Yes — personal or family cloud with modest concurrency
Use ZimaBoard 2 with added SSD/data storage. The 832 already has substantial memory for a light personal or family deployment; choose 1664 when optional apps or co-hosted containers create a real need for additional RAM.
- Files, sync, calendar and light family use with added SSD/data storageZimaBoard 2 832
- More Nextcloud apps, containers or memory headroom on the same compact platformZimaBoard 2 1664
No — multi-drive growth or heavier collaboration is expected
Use ZimaCube 2 when integrated multi-drive expansion, larger backup capacity, more storage tiers or heavier collaboration and co-hosted services become the stronger requirement.
- Growing multi-drive private cloud with normal collaboration workloadsZimaCube 2 Standard
- More simultaneous users, containers, Office/Talk and faster shared-storage workflowsZimaCube 2 Pro
- Nextcloud plus a separate GPU, local AI or heavy VM/creator workloadZimaCube 2 Creator Pack
This is a workload guide, not a guaranteed user-count benchmark. Results depend on concurrent PHP workers, enabled Nextcloud apps, database/cache configuration, preview generation, Office/Talk services, file sizes, storage latency, Internet bandwidth and other ZimaOS workloads.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | A compact personal or family Nextcloud server with an added SSD for latency-sensitive application/database state and attached storage sized for user files and backups. | Files sync, mobile uploads, Calendar/Contacts, ordinary previews and a small number of concurrent household users. |
|
Do not size a growing private cloud around the 32 GB eMMC alone. User files, versions, previews, database state and backups should be planned on larger persistent storage, with SSD preferred for latency-sensitive AIO/application data. | Get Now |
| ZimaBoard 2 1664 | A compact Nextcloud server with more memory for optional apps, concurrent PHP workers and other ZimaOS containers. | Nextcloud plus databases, reverse proxy, document services or additional self-hosted applications while remaining within a compact storage plan. |
|
Choose 1664 for a measured or planned memory need, not because basic Nextcloud Files, Calendar and Contacts require 16 GB RAM. | Get Now |
| ZimaCube 2 Standard | A growing multi-drive Nextcloud private cloud where integrated storage capacity and separation of SSD application data from HDD user files matter more than simply adding RAM to a compact server. | Family or small-group file sync, photo/document archives, backups and ordinary Nextcloud apps with multi-drive storage. |
|
Eight gigabytes can fit many household deployments, but optional Office, Talk, antivirus, full-text search or many simultaneous PHP workers can justify more memory. Measure the actual service mix rather than using a fixed user-count rule. | Get Now |
| ZimaCube 2 Pro | A larger Nextcloud deployment with more simultaneous activity, optional collaboration containers and faster local storage/network workflows. | Nextcloud Files plus Office/Talk-style collaboration, previews, backups, databases and other always-on ZimaOS services. |
|
10GbE can improve large local transfers and backup/storage workflows, but it cannot remove a slow Internet uplink, database bottleneck or overloaded PHP/application stack. | Get Now |
| ZimaCube 2 Creator Pack | Nextcloud combined with a genuine dedicated-GPU, local-AI, creator or heavy-VM workload. | A mixed private-cloud and compute server where Nextcloud is one service among AI, GPU, creator or virtualization workloads. |
|
Usually excessive for Nextcloud alone. Choose Creator Pack only when local AI, dedicated GPU compute, large VMs or creator workloads are independently part of the system plan. | 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 RAM sizing, SSD placement, AIO, databases, user growth and Zima hardware questions that are not fully addressed above.
How much RAM does a Nextcloud server need?
Nextcloud does not publish one universal whole-server RAM number. Its official Administration Manual requires at least 128 MB per process and recommends 512 MB per process. Total RAM depends on concurrent PHP workers, database/cache services and enabled apps; figures such as 2–4 GB come from practical third-party sizing guides rather than the official minimum.
Is 8 GB RAM enough for Nextcloud?
Yes for many personal and family deployments. Eight gigabytes is well above Nextcloud's per-process figures, but the real question is how many PHP workers and companion services are active at once. Office, Talk, antivirus, full-text search, large preview jobs or many simultaneous requests can justify more memory.
Does Nextcloud need an SSD?
Not every user file has to live on SSD, but fast storage is strongly preferable for database, cache and application state. Official Nextcloud AIO recommends SSD, discourages SD cards and says HDD storage can work more slowly. Bulk user files can still live on larger HDD storage when the performance tradeoff is acceptable.
Should I use PostgreSQL, MariaDB or SQLite for Nextcloud?
For a normal persistent server, use a supported production database such as MariaDB or PostgreSQL. Current Nextcloud documentation reserves SQLite for testing and minimal instances. Official Nextcloud AIO uses PostgreSQL and also includes Redis and APCu.
What is Nextcloud All-in-One?
Nextcloud AIO is an official Nextcloud installation method that manages a multi-container stack. Its core stack includes Nextcloud, PostgreSQL, Redis/APCu caching and optimized PHP-FPM, while Office, Talk, backups, antivirus, previews and full-text search are optional components.
Can ZimaBoard 2 run Nextcloud?
Yes. ZimaBoard 2 uses an Intel N150, with 8 GB RAM on the 832 and 16 GB on the 1664, plus dual 2.5GbE and dual SATA. For a durable private-cloud setup, add suitable SSD storage for latency-sensitive application/database state and size separate persistent storage around user files and backups.
How many Nextcloud users can ZimaBoard 2 handle?
There is no responsible fixed user-count guarantee. Nextcloud itself says memory varies with users, apps, files and server activity, and official memory figures are per process. Third-party sizing tables can be useful planning examples, but simultaneous Office/Talk use, previews and large sync jobs matter more than registered-account count.
When should I choose ZimaCube 2 instead of ZimaBoard 2 for Nextcloud?
Choose ZimaBoard 2 when a compact one- or two-drive private cloud is enough. Choose ZimaCube 2 when the stronger requirement is integrated multi-drive capacity, backup space, storage tiers, heavier collaboration or several co-hosted services. Creator Pack is not necessary for ordinary Nextcloud.
What sources and further reading informed this Nextcloud hardware guide?
Nextcloud's Administration Manual is the primary authority for CPU architecture, database support and the official 128 MB minimum / 512 MB recommended memory-per-process figures. The official Nextcloud AIO repository defines its PostgreSQL, Redis/APCu, PHP-FPM and SSD guidance. RackDiff's 2026 user tables and the Nextcloud NAS Guide's 2-core/4 GB/128 GB SSD floor are third-party planning models for their specific scenarios, not universal Nextcloud requirements. StorageReview's 2–4 core, 8 GB and 500 GB recommendation is a 2024 homelab example. The Nextcloud Passwords wiki is app-specific and must not be used as the base Nextcloud Server hardware requirement.
