Independent testing Updated August 2026 387 self-hosting guides 5 VPS providers tested

guide

Nextcloud VPS Requirements 2026: RAM, CPU and Storage

Nextcloud VPS sizing for 2026: practical RAM, CPU and storage tiers for small teams, plus Redis, database, previews and backup headroom.

Last verified:

Nextcloud does not publish one universal VPS size. Its current administration manual says memory demand varies with users, apps, files and activity. It specifies at least 128 MB of RAM per PHP process and recommends 512 MB per process, which is not the same as saying the whole server needs only 512 MB.

For a VPS that also runs the database, web server, cron jobs and cache, 4 GB is a sensible starting point for a small installation. The tiers below are planning guidance for a single-server deployment, not official Nextcloud limits.

What the official requirements actually say

Official references checked on September 3, 2026: system requirements, memory caching and preview configuration.

Practical VPS sizes by workload

WorkloadStarting VPSWhy
Personal files, 1 to 3 active users2 vCPU, 4 GB RAMLeaves room for PHP workers, a database, Redis and background jobs on one server.
Family or small team, 5 to 20 active users4 vCPU, 8 GB RAMBetter for concurrent sync, office apps, previews and several enabled apps.
Large photo library or frequent office collaboration4 to 8 vCPU, 16 GB RAMPreview generation and concurrent PHP workers need more memory and CPU headroom.
More than 50 active usersMeasure before buyingSeparate database, object storage or cache services may matter more than simply adding cores.

Count active users, not registered accounts. Ten people synchronizing files at once create a different load from 100 dormant accounts. Start with the second tier if you enable Collabora, OnlyOffice, antivirus scanning or extensive preview generation.

Storage planning

Do not size the disk from uploaded files alone. Reserve space for the database, application data, previews, temporary upload chunks, deleted-file retention and file versions. Keep backups outside the VPS so a disk failure or account problem cannot remove both the live data and its backup.

For example, a 60 GB file library should not be placed on an 80 GB system disk. A 160 GB or larger volume gives the operating system, previews and database room to grow, while the separate backup needs capacity for retention history.

Which VPS fits a small Nextcloud server?

These are existing partner destinations. Using them may earn us a commission without changing your price. The links do not affect the sizing recommendations above.

If you already know the application you want, compare the full provider set in our VPS comparison. Choose a region near the users, confirm the included storage and traffic, and verify the current checkout price before ordering.

Setting up Nextcloud on your VPS

  1. Install a currently supported 64-bit Linux distribution.
  2. Install Apache or Nginx, PHP and a supported MariaDB or PostgreSQL version.
  3. Install Nextcloud from its official distribution or a maintained deployment image.
  4. Configure HTTPS, cron, APCu and Redis before importing a large file library.
  5. Put backups on another system and test a restore before relying on the server.
  6. Monitor RAM, swap, CPU wait, free disk space and background-job duration during real use.

FAQs

What is the minimum RAM required to self-host Nextcloud?

Nextcloud documents at least 128 MB per PHP process and recommends 512 MB per process, but it does not define one minimum for an entire VPS. For a single server that also runs the database and cache, start at 4 GB for a small installation.

Can I run Nextcloud on a low-spec VPS?

It may start on a low-spec VPS, but memory pressure appears quickly once PHP workers, the database, Redis and background jobs run together. A 2 vCPU and 4 GB VPS is a safer small-server baseline.

Is it possible to expand resources after setting up Nextcloud?

Most VPS providers let you resize compute or attach storage, but shrinking disks and moving between regions may not be seamless. Confirm the providerโ€™s resize rules first, keep a tested backup, and monitor RAM, swap, CPU wait and disk usage before upgrading.

The right starting size is the smallest VPS that leaves headroom for peak concurrent activity, not the smallest one that completes the installer.