Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Nextcloud does not publish one universal server specification. The reliable starting point is its per-process memory guidance, a 64-bit software stack, and storage sized from your files and backup policy. CPU cores, total server RAM, disk capacity, and user limits must be matched to your workload and validated under realistic activity.
Need a server to try this on? Antihost offers Linux VPS plans with NVMe storage, full root access and a 14-day free trial.
What Nextcloud officially specifies—and what it does not
The Nextcloud Administration Manual provides useful memory and software-version guidance, but it is not a complete hardware-sizing table. It does not establish a single “minimum server” that applies to every installation. A personal instance with a few occasional users, a team sharing large folders, and a deployment running search, previews, office integration, or other apps create very different loads.
As an Amazon Associate I earn from qualifying purchases.
Free tools Windows power users keep installed
One-click scans. No signup required.
Three boundaries are important:
- Memory figures are per PHP process. They are not the total RAM requirement for the server.
- No official CPU-core minimum is stated in the published material covered here.
- No official disk-space minimum is stated. Capacity must come from your data, growth and backup requirements.
Use the official figures as a baseline, then size the database, operating system, web server, PHP workers, background jobs and storage around the way people will use the instance.
RAM requirements: interpret the per-process numbers correctly
The Administration Manual publishes these memory figures:
#1 Best Overall
- Entry-level NAS Personal Storage：UGREEN NAS DH2300 is your first and best NAS made easy. It is designed for beginners who want a simple, private way to store videos, photos and personal files, which is intuitive for users moving from cloud storage or external drives and move away from scattered date across devices. This entry-level NAS 2-bay perfect for personal entertainment, photo storage, and easy data backup (doesn't support Docker or virtual machines).
- Set Your Devices Free, Expand Your Digital World: This unified storage hub supports massive capacity up to 64TB.*Storage drives not included. Stop Deleting, Start Storing. You can store 22 million 3MB images, or 2 million 30MB songs, or 43K 1.5GB movies or 67 million 1MB documents! UGREEN NAS is a better way to free up storage across all your devices such as phones, computers, tablets and also does automatic backups across devices regardless of the operating system—Window, iOS, Android or macOS.
- The Smarter Long-term Way to Store: Unlike cloud storage with recurring monthly fees, a UGREEN NAS enclosure requires only a one-time purchase for long-term use. For example, you only need to pay $459.98 for a NAS, while for cloud storage, you need to pay $719.88 per year, $2,159.64 for 3 years, $3,599.40 for 5 years. You will save $6,738.82 over 10 years with UGREEN NAS! *NAS cost based on DH2300 + 12TB HDD; cloud cost based on 12TB plan (e.g. $59.99/month).
- Blazing Speed, Minimal Power: Equipped with a high-performance processor, 1GbE port, and 4GB RAM on Board, this NAS handles multiple tasks with ease. File transfers reach up to 125MB/s—a 1GB file takes only 8 seconds. Don't let slow clouds hold you back; they often need over 100 seconds for the same task. The difference is clear.
- Let AI Better Organize Your Memories: UGREEN NAS uses AI to tag faces, locations, texts, and objects—so you can effortlessly find any photo by searching for who or what's in it in seconds. It also automatically finds and deletes similar or duplicate photo, backs up live photos and allows you to share them with your friends or family with just one tap. Everything stays effortlessly organized, powered by intelligent tagging and recognition.
| Component or condition | Published memory guidance | How to interpret it |
|---|---|---|
| PHP process minimum | 128 MB | Minimum memory for an individual PHP process |
| PHP process recommendation | 512 MB | Recommended memory for an individual PHP process |
| Built-in Updater | 256 MB | Memory required by the updater while it runs |
These numbers do not mean that a server with 512 MB of RAM can safely serve Nextcloud. Web requests are handled by PHP processes, and several processes may exist at the same time. The host also needs memory for the operating system, web server, database, PHP’s shared components, caches, file indexing and any additional applications.
Why concurrency changes the total
If you configure four PHP workers and plan around the manual’s 512 MB recommendation per process, the workers alone represent about 2 GB when all four are using that amount. That arithmetic is an illustration of concurrency, not an official whole-server specification. Actual consumption varies with PHP configuration, request type, enabled apps and the amount of work each request performs.
The 128 MB figure is a floor for one process, not a sensible target for a busy installation. Running every process at the minimum can leave no headroom for large uploads, previews, search operations, administrative tasks or simultaneous activity. Conversely, allocating 512 MB to each process does not guarantee that every request will use all of it.
Account for the updater separately
The built-in Updater requires at least 256 MB while it runs. Treat that as an operational requirement in addition to normal web traffic: an update can temporarily compete with user requests and database activity. Schedule maintenance when usage is low and keep enough free memory for the updater rather than sizing the machine to the exact amount consumed by ordinary requests.
What determines the final RAM allocation
- Concurrent users and requests: Ten people uploading, browsing folders and generating previews at once need more worker capacity than ten people who log in briefly once a day.
- Enabled apps: Search, preview generation, document integration, workflows and other extensions can increase per-request memory or background-job usage.
- File characteristics: Many small files, large media files and frequent sharing operations exercise different parts of the stack.
- Database workload: A database that is short of memory can make the whole service feel slow even when PHP workers have room.
- Background jobs: Scheduled tasks can overlap with interactive requests unless they are planned and monitored.
Measure peak, not average, usage. A quiet test during installation tells you little about the memory needed when users upload, search and synchronize simultaneously.
Rank #2
- 【Advanced Home Data & Media Hub】For advanced home users who need phone backup, file storage, and centralized data management. Centralize family photos, 4K videos, movies, computer backups, and personal files in one place while running multiple apps for home entertainment and everyday data management. Suitable for households with growing digital libraries and multiple NAS use cases.
- 【Built for Creators, Media Servers & Advanced Apps】Powered by the Intel N100 Quad-Core CPU, 8GB DDR5 RAM, 2.5GbE networking, and dual M.2 NVMe slots, DXP2800 handles large files and heavier workloads with ease. Run Docker, virtual machines, and media server applications compatible with Plex—ideal for content creators, tech enthusiasts, and advanced home users managing 4K videos, RAW photos, personal media libraries, and multiple NAS apps.
- 【Up to 80TB for Growing Digital Libraries】 Supports up to 80TB of storage using two HDD bays and two M.2 NVMe SSD slots for family photos, movies, RAW photos, 4K videos, work files, and device backups. AI photo management supports recognition of people, objects, scenes, and locations, album organization, and duplicate photo detection. HDDs and SSDs are not included.
- 【AI-powered Home Surveillance】Turn DXP2800 into a centralized home surveillance hub by connecting compatible network cameras and storing recordings locally on your NAS. AI-powered features include Face Recognition, People Detection, and Pet Detection, helping advanced home users review important events more efficiently while managing home surveillance and personal data in one place.
- 【One data Center Across Your Devices】Keep files from desktops, laptops, phones, tablets, and other devices together instead of scattered across cloud accounts and external drives. Access, back up, organize, and share data across Windows, macOS, Android, iOS, web browsers, and compatible smart TVs—ideal for creators and advanced home users working across multiple devices.
CPU requirements: 64-bit is the baseline, core count is workload-dependent
The official guidance strongly recommends a 64-bit CPU, operating system and PHP environment. A 32-bit setup is supported with limitations, so it should be treated as an exception rather than the default for a new deployment. A 64-bit stack gives you the supported path for current operating systems, PHP versions and larger workloads.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The published material does not state a minimum CPU model, clock speed or number of cores. Do not turn an unverified core count into a supposed Nextcloud requirement. The right number of cores depends on how many PHP workers, database tasks, background jobs and supporting services must run at the same time.
Single-threaded request behavior
A Centron sizing discussion notes that each Nextcloud request runs in a single-threaded PHP process and therefore argues that throughput benefits from additional CPU cores. This is third-party guidance, not an official Nextcloud minimum. It is useful as a design principle: one request cannot make a single PHP worker use every core simultaneously, while several concurrent requests can use several workers and cores.
In practical terms, a fast single-core system may feel responsive for one user but queue work as concurrency rises. More cores help only when the web-server and PHP configuration can keep them busy and when the database and storage layers are not already the bottleneck. CPU speed, available cores, database behavior and disk latency should be evaluated together.
A defensible CPU-sizing process
- Define peak activity. Count people who may be active at the same time, not merely the number of accounts.
- List expensive operations. Include large uploads, thumbnail or preview generation, full-text search, synchronization bursts and scheduled jobs.
- Separate interactive and background work. A deployment that runs indexing or previews continuously needs more headroom than one that performs those tasks rarely.
- Test under concurrency. Reproduce the busiest realistic combination on a staging server and watch response time, CPU saturation and request queues.
- Leave growth capacity. A machine that is already at sustained high utilization has no room for more users, apps or larger files.
Because no official core minimum exists, report your chosen CPU as a tested capacity for a stated workload rather than as a universal Nextcloud rule.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Rank #3
- Your Personal Streaming Server - Build your own Netflix-style media library and stream 4K movies, shows and photos to any device without monthly fees
- Create Your Own Cloud - Store your entire photo, video and music collection; access from anywhere with fast 282 MB/s transfer speeds
- Creator-Grade Backup Solution - Protect your irreplaceable content with automated backups to cloud services, external drives and remote NAS
- Multi-Layered Data Protection - Combine RAID redundancy, automated backups and snapshot technology to prevent data loss from any cause
- Smart Home Surveillance - Support up to 30 IP cameras with AI detection, instant alerts and secure remote monitoring
Storage requirements: calculate capacity from data and protection copies
The official material covered here does not publish a minimum disk size. The correct starting capacity is therefore not “the Nextcloud minimum”; it is the amount of user data you need to store, plus operating-system, application, database, temporary and backup space.
Separate the capacity questions
- User-data capacity: The space required for files, versions, trash and other data retained by your policies.
- Database and application space: The database, configuration, logs, previews and installed application files also consume storage.
- Temporary working space: Uploads, updates, previews and maintenance tasks may need free space while they run.
- Backup capacity: A backup is an additional copy, not free space inside the production allocation. Retention and historical versions can multiply the required capacity.
- Growth reserve: Starting at 95–100% utilization leaves no safe room for updates or normal activity.
Keep enough free space for the largest routine operation you expect, not merely for today’s file total. A full volume can prevent uploads, database writes, logging and updates at the same time.
System volume versus data volume
For larger datasets, Centron’s third-party guidance recommends NVMe-backed volumes and moving bulk data off the system disk. That is a performance and operations recommendation, not an official capacity minimum. Separating the operating system and application volume from bulk user data can make expansion, monitoring and recovery easier, provided both volumes are backed up and their failure modes are understood.
Fast storage is most valuable when the workload is limited by metadata, database access, previews or many concurrent small operations. Capacity planning still comes first: a fast disk that is too small is not a viable design, and a large disk with poor latency can make browsing and synchronization feel slow.
How much storage can a deployment handle?
A Nextcloud community discussion mentions approximately 10 TB for a 50-user deployment. That is an anecdotal example, not a supported limit or a general sizing formula. It does not establish how much storage every 50-user installation needs, nor does it describe the same file sizes, retention rules, apps, hardware or activity pattern you may have.
Rank #4
- Entry-level NAS Home Storage: The UGREEN NAS DH4300 Plus is an entry-level 4-bay NAS that's ideal for home media and vast private storage you can access from anywhere and also supports Docker but not virtual machines. You can record, store, share happy moment with your families and friends, which is intuitive for users moving from cloud storage, or external drives to create your own private cloud, access files from any device.
- Smart Photo Backup & AI Album: Automatically back up photos and videos from your phone in real time and keep growing family memories organized with AI-powered photo albums. Semantic search, custom learning, and recognition of people, objects, pets, and similar photos help you quickly find the moments you want. Duplicate photo removal also helps keep your library organized—ideal for families and users with large photo collections.
- User-Friendly App & Easy Setup: Connect quickly via NFC, set up simply and share files fast on Windows, macOS, Android, iOS, web browsers, and smart TVs. You can access data remotely from any of your mixed devices. What's more, UGREEN NAS enclosure comes with beginner-friendly user manual and video instructions to ensure you can easily take full advantage of its features.
- More Cost-effective Storage Solution: Unlike cloud storage with recurring monthly fees, A UGREEN NAS enclosure requires only a one-time purchase for long-term use. For example, you only need to pay $629.99 for a NAS, while for cloud storage, you need to pay $719.88 per year, $1,439.76 for 2 years, $2,159.64 for 3 years, $7,198.80 for 10 years. You will save $6,568.81 over 10 years with UGREEN NAS! *NAS cost based on DH4300 Plus + 12TB HDD; cloud cost based on 12TB plan (e.g. $59.99/month).
- Your Data, You Control：No third-party clouds, no hidden access, UGREEN NAS provides a more secure and private data storage solution. It stores data locally on your private hard drives and does automatic backups. Thus, you can keep full control over it. The advanced encryption is TRUSTe certified in the United States and is awarded the first (and only) ETSI EN 303 645 certification mark for NAS products by TÜV SÜD Group.
Build your estimate from measured inputs: current data, monthly growth, expected version and trash retention, database growth, preview volume, and the number and retention period of backup copies. Revisit the estimate whenever you add users, enable storage-heavy apps or change retention policies.
Supported software versions shape the hardware baseline
Hardware cannot be considered separately from the software stack. The current stable Administration Manual lists these platforms:
| Layer | Current manual guidance | Planning implication |
|---|---|---|
| Operating system | Ubuntu 26.04 LTS and Red Hat Enterprise Linux 10 recommended; Debian 13 also listed | Choose a supported 64-bit distribution and plan its update lifecycle |
| Database | MySQL/MariaDB and PostgreSQL 14–18 recommended | Use a production database engine with resources appropriate to concurrency and data volume |
| Database for limited use | SQLite for testing and minimal instances only | Do not treat SQLite as the normal choice for a growing multi-user service |
| PHP | PHP 8.3, 8.4 and 8.5 supported | Verify that the selected operating system and extensions provide a supported PHP version |
| Unsupported PHP version | PHP 8.2 is no longer supported | Do not build a new installation around PHP 8.2 |
Version support changes between Nextcloud releases. Check the manual for the specific release you intend to deploy before buying hardware or finalizing an operating-system image. A server that meets a memory target but runs an unsupported PHP or database version is not a sound production baseline.
Practical sizing patterns without pretending there is a universal number
Personal or minimal instance
A single-user or lightly used installation can start with modest resources, but it still needs the supported 64-bit stack, sufficient memory for at least one PHP process and the updater, and storage for both files and backups. SQLite is listed for testing and minimal instances; reassess the database choice as soon as concurrent use or workload grows.
Small team
For a team, size for simultaneous requests rather than account count. Multiple PHP workers, database memory, background jobs and free storage become material design concerns. Measure a representative upload, synchronization and browsing burst, then increase resources if workers queue or the database remains saturated.
Best Value
- Value NAS with RAID for centralized storage and backup for all your devices. Check out the LS 700 for enhanced features, cloud capabilities, macOS 26, and up to 7x faster performance than the LS 200.
- Connect the LinkStation to your router and enjoy shared network storage for your devices. The NAS is compatible with Windows and macOS*, and Buffalo's US-based support is on-hand 24/7 for installation walkthroughs. *Only for macOS 15 (Sequoia) and earlier. For macOS 26, check out our LS 700 series.
- Subscription-Free Personal Cloud – Store, back up, and manage all your videos, music, and photos and access them anytime without paying any monthly fees.
- Storage Purpose-Built for Data Security – A NAS designed to keep your data safe, the LS200 features a closed system to reduce vulnerabilities from 3rd party apps and SSL encryption for secure file transfers.
- Back Up Multiple Computers & Devices – NAS Navigator management utility and PC backup software included. NAS Navigator 2 for macOS 15 and earlier. You can set up automated backups of data on your computers.
Larger or app-heavy deployment
Large file collections, many active users and intensive apps require capacity planning as an ongoing process. Use fast storage where latency is limiting, separate bulk data when appropriate, monitor database and PHP behavior, and validate upgrades and peak jobs on a staging system before changing production.
A repeatable checklist for choosing a server
- Inventory the workload: users, peak concurrent activity, file sizes, synchronization patterns and enabled apps.
- Choose the supported platform: a 64-bit operating system, supported PHP release and production database.
- Estimate PHP concurrency: use the 512 MB per-process recommendation as a planning reference, then add memory for the operating system, database, web server and other services.
- Reserve updater headroom: ensure at least 256 MB is available for the built-in Updater while maintenance runs.
- Plan storage by policy: include live data, versions, trash, previews, database files, temporary space, backups and growth.
- Design for recovery: place backups on independent storage and confirm that restoring files and the database is practical.
- Load-test a staging copy: reproduce the busiest realistic activity and record CPU, memory, storage latency, database behavior and request response times.
- Recheck after changes: reassess after adding users, enabling apps, changing retention or upgrading Nextcloud.
Common sizing mistakes and their fixes
Confusing per-process RAM with total RAM
Symptom: The server has only the recommended amount for one PHP process and starts swapping as soon as several requests arrive.
Fix: Multiply the planning allowance by expected concurrent workers, then add the operating system, database, web server, caches and maintenance headroom.
Looking for a magic CPU-core number
Symptom: A specification claims that a fixed core count is the official Nextcloud minimum.
Fix: Treat the absence of an official core minimum explicitly. Select cores and CPU speed from measured concurrency, background jobs and database load.
Buying only enough disk for today’s files
Symptom: Uploads or updates fail when versions, previews or backups consume the remaining free space.
Fix: Model retention and growth, maintain free working space and store backups separately from production data.
Using SQLite for a growing service
Symptom: A test installation works, but concurrent production activity does not scale as expected.
Fix: Use SQLite only within the manual’s testing and minimal-instance scope; plan MySQL/MariaDB or PostgreSQL for a production deployment that is expanding.
Ignoring software support
Symptom: Hardware appears adequate, but the chosen PHP or operating-system combination is outside the supported matrix.
Fix: Select versions from the current manual and check the matrix again before each major upgrade.
The bottom line on Nextcloud hardware requirements
Use 128 MB as the published minimum for one PHP process, 512 MB per process as the recommendation, and 256 MB as the Updater requirement—but do not mistake any of those figures for total server RAM. Run a 64-bit stack, choose CPU capacity from concurrent workload rather than an invented core minimum, and size storage from user data, retention, backups and growth because no official disk minimum is stated. The only dependable way to turn those baselines into a user count is to test your actual apps and activity on representative hardware.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
