PERSONAL CLOUD
Nextcloud for a household, with the memory sum written out.
Nextcloud is a file and collaboration server you host yourself. It replaces the sync folder, not the backup. The decision is whether you want Google or Dropbox to operate the quota, or whether you will operate PHP, a database and the disks.
Reviewed 30 October 2026 against the Nextcloud 36 administration manual. How estimates differ from published requirements.

What Nextcloud is for
At home, Nextcloud usually means a folder that syncs between a laptop and a phone, plus sharing links, and sometimes calendars or office files if you enable those apps. Each app adds PHP work and background jobs. The server manual is clear that memory depends on users, apps, files and activity. There is no single "a family needs this many gigabytes of RAM" line, and this guide will not invent one.
What the manual does publish, for Nextcloud 36, is a per-process figure: a minimum of 128 MB of RAM per process, and a recommendation of 512 MB per process. The built-in updater needs at least 256 MB. Those numbers are not the size of the whole computer. They are the allowance for each PHP process that is actually doing work.
Google Drive, Dropbox and a server you run
A standard Google Account includes up to 15 GB shared across Drive, Gmail and Photos. That is the figure on Google's plan page. Dropbox Plus is described in Dropbox's own help as a 2 TB plan, and deleted files on Plus can be restored for 30 days. Help pages updated in 2026 list that 30-day window for Basic, Plus and Family. UK checkout prices for either product were not confirmed for this guide. Use the live plan pages.
| Question | Google Drive or Dropbox | Nextcloud |
|---|---|---|
| Storage limit | The plan quota | The free space you leave on disk, plus versions and the deleted-file bin |
| Who applies updates? | The provider | You, including PHP and the database |
| Sync versus recovery | Sync, plus a retention window that depends on the plan | Sync, plus whatever trash and version settings you configure. Still not an off-site backup |
| Clients the project names | The vendor's apps | Desktop: Windows 10 or later, macOS Monterey or later, 64-bit Linux. Files app: iOS 17 or later, Android 9 or later |
| A good database | Not your problem | PostgreSQL or MariaDB for real use. SQLite is for testing and tiny installs |
Three picks
Keep the managed drive
Choose Google Drive or Dropbox when the quota is acceptable and you will not patch a server. You still need a backup that is not the sync folder. A 30-day deleted-file window ends. After that, the file is gone from that service too.
Nextcloud on hardware you already have
Choose this for one household, a modest file set, and a person who will update Linux, PHP and Nextcloud. Put the operating system, Nextcloud and the database on SSD. Bulk files can sit on a larger disk. The manual recommends current PHP, with 8.3 and 8.4 supported and 8.5 recommended, on a 64-bit system. Recommended databases include MariaDB and PostgreSQL. SQLite 3.24 or newer is listed only for testing and minimal instances. Do not start a family archive on SQLite because the install screen allowed it.
A managed Nextcloud host
Choose a host that runs Nextcloud for you when you want the apps and the quota on your terms, without owning the PHP upgrades. You still export a backup. A managed app is not a second copy unless the contract says you can restore files the host has lost.
Turn the per-process figure into a machine size
Here is the arithmetic, labelled as a plan rather than a Nextcloud specification. The manual recommends 512 MB per process. Four busy PHP processes at that recommendation are 4 times 512 MB, which is 2 GB, and that is only PHP. The database, the operating system, file cache and any office or talk app sit on top. A machine whose entire RAM is 2 GB is therefore at the recommendation for those four processes and has nothing left. That is why a small home install is more comfortable with several gigabytes free after Linux has booted, and why you should measure a real sync before you buy a larger box.
On the server, after a desktop client has synced a few gigabytes, read the memory line:
free -hLook at available memory, not only the word "free". Linux uses spare RAM as cache. If available memory collapses and the server swaps while one person syncs, add RAM or reduce PHP workers before you invite the rest of the household. The manual also warns that low-memory machines may need apps turned down or off.
Supported platforms in that same Nextcloud 36 manual include Ubuntu 24.04 LTS and 26.04 LTS, Debian 13, and current enterprise distributions. A 32-bit system is still mentioned, with hard limits: dates before 1970 and after 2038 are not supported, and some apps will not run. Use 64-bit. The web server it recommends is Apache 2.4 with mod_php or php-fpm, or nginx with php-fpm. Browsers it names are current Edge, Firefox, Chrome or Chromium, and Safari. Talk's full call features want a current Firefox or Chromium.
For MySQL or MariaDB, InnoDB is required. MyISAM is not supported. The transaction isolation level needs to be READ COMMITTED, and 4-byte Unicode has to be enabled if you want emoji in file names and comments. Those are install-day settings. Finding them after a year of uploads is a migration, not a checkbox.
A worked file layout
Suppose the household has 400 GB of documents and photos to sync, and you allow another 20 percent for versions and the deleted-file bin. That allowance is a planning choice, not a Nextcloud default. 400 GB plus 80 GB is 480 GB of live file storage. The database and Nextcloud code stay on an SSD of 100 GB or more so the system disk is not the file disk. A second copy of the 400 GB, on a disk that is not in the same machine, is the backup. Versions on the server are useful for a mistaken overwrite. They are still on the same server.
Put those numbers into the personal cloud storage calculator and change the 20 percent if your own version history is longer. Then look at free space the way the server sees it:
df -h
du -sh /var/www/nextcloud /path/to/dataReplace the paths with the ones you actually used. If df shows the data disk over about 80 percent full, treat that as the moment to add a disk or to move old versions out, not as a surprise for next month. Nextcloud also needs room to unpack updates. A completely full disk fails an upgrade in a way that looks like a broken app.
External storage apps can attach another disk or an S3-style bucket. That does not remove the need for a database backup. The database is small compared with the files and it is the part a file copy of the data directory can miss if you forget config.php and the database dump together. A restorable copy is files, config and database. Practise that once. Our personal cloud project walks through a staged first setup.
Maintenance that decides whether this was a good idea
The manual's reason for dropping old PHP is specific. PHP stops security fixes on old branches. Nextcloud cannot ship those language fixes while it still supports the old syntax. Performance improves on newer PHP as well. So the upgrade job is "PHP and Nextcloud", not only the Nextcloud tarball. If you need a long freeze, Nextcloud sells an enterprise subscription with a longer maintenance window. A home install does not need that subscription. It does need a person who will apply updates.
Exposing the server to the internet adds HTTPS, a firewall and a habit of reading the updater output. Keep the first month on the home network, or reach it through a VPN, until a backup restore has worked. HTTPS is the certificate part. It does not patch PHP for you.
Background jobs have to run. A Nextcloud that never runs cron will look idle and then surprise you with a huge catch-up. Use the system cron the install docs describe, and confirm in the admin overview that jobs are moving. A weekly look at that page is a better monitor than a dashboard you do not open.
Questions that change the decision
Is Nextcloud private by default?
The files are on hardware you choose. Apps you enable can talk to other services. A public share link is public for as long as it exists. Privacy here is an operating practice, not a logo.
Can an old laptop run it?
Often, for one or two people, if it is 64-bit, it has SSD for the system and database, and it stays cool enough to leave on. Measure with free -h during a sync. If the laptop is the only copy of the files, it is not a backup target as well.
What about Talk and office documents?
They are extra apps with extra memory and, for video calls, a preference for current Firefox or Chromium. Add them after file sync and backup work. A video call is a poor first test of a machine that is already swapping.
Will this cost less than Google One?
Sometimes, once the disks exist. A new pair of disks, electricity and your time can cost more than a small quota for years. Compare renewal prices, not a first-year headline, and include the second copy.
Verdict
Run Nextcloud when file location and quota are the problem you want to own, and someone will keep PHP current. Stay with Drive or Dropbox when sync without a server is the whole requirement. Size the PC from the published 512 MB per process, then add the database and the operating system, and prove it with free -h during a real sync. Keep PostgreSQL or MariaDB, keep SQLite for experiments, and keep a copy of the files that sync cannot delete.
Sources checked 30 October 2026: Nextcloud system requirements, Google One plans, Dropbox Plus, and Dropbox deleted-file recovery.