How Much RAM Do You Need for a VPS? Size by Workload
How much RAM do you need for a VPS? Sizes for WordPress, WooCommerce, n8n, Nextcloud, and cPanel, plus the three signs your server is really short.
How much RAM do I need for a VPS? For most people the honest answer is 2 to 8 GB, and the right number depends on what the server runs, not on how many visitors you expect. RAM (the server's working memory) is the resource that hurts most when it runs out. Too little makes a site slow or makes it crash, and too much is money you pay every month for nothing.
The short answer: size by workload#
Here is what we recommend for the stacks our customers run most often. These are the same picks our Solutions guides make, and the memory figures below are read live from our plan data.
| What you are running | Plan | RAM |
|---|---|---|
| A blog or brochure site on WordPress | F30 Foundational VPS | 6 GB |
| A business site that earns money | P20 Performance VPS | 4 GB |
| WooCommerce, or a busy site with search | P40 Performance VPS | 8 GB |
| n8n for most automation setups | P20 Performance VPS | 4 GB |
| Nextcloud for a family or small team | F40 Foundational VPS | 8 GB |
| Nextcloud with office document editing | P40 Performance VPS | 8 GB |
| cPanel and WHM | P40 Performance VPS | 8 GB |
| A reseller or agency panel with many client accounts | D40 VDS | 8 GB |
The number in each plan code is the size class, and it is the same across our lines. A P40, an F40, and a D40 all have the same memory; what changes is the processor, the storage, and whether the cores are shared.
What actually uses the memory#
A server's memory bill is a stack of small line items. The ones that matter, from the bottom up:
- The operating system. A minimal Linux install idles in a few hundred megabytes. Windows Server needs far more, and our Windows VPS post puts the practical floor at 4 GB.
- The web server and PHP workers. Each PHP-FPM worker (a process that runs one request at a time) holds tens of megabytes. More workers serve more visitors at once, and each one costs memory whether it is busy or not.
- The database. MySQL and PostgreSQL keep hot data in their own memory buffer. A database that fits its working set in RAM answers from memory; one that does not reads from disk on every query.
- Everything else. A control panel, a mail stack with spam filtering, a cache like Redis, or a few Docker containers each take their own slice. A full control panel is the biggest jump, which is why cPanel sits on the P40 in the table above.
Add those up for the heaviest hour of your week, not an average one, and leave a quarter of the total free.
How to tell if your VPS needs more RAM#
Do not read the "used" number and panic. Linux fills spare memory with a disk cache on purpose and hands it back the moment a program asks. The figure that matters is the available column in free -h. Three signs you are really short:
- Available memory sits under about 10% at your busy hour. The server is one traffic spike away from trouble.
- Swap is in steady use. Swap is disk space used as overflow memory. Even on NVMe it is far slower than RAM, so a server that lives in swap feels slow everywhere.
- The OOM killer appears in the logs. When Linux runs completely out of memory, it kills a process to survive, usually the database.
dmesg | grep -i oomwill show it.
The usage graphs in the Cloud Panel show memory over days, which beats one reading from a quiet afternoon. A small swap file is a sensible safety net, and growing the disk and adding swap walks through it. Treat swap as an airbag, not as extra capacity.
When RAM is not the problem#
Plenty of slow servers have memory to spare. If available stays healthy and pages are still slow, look at the processor and the disk instead. A site that waits on one busy core wants faster cores, which is the case for our Performance VPS line on AMD EPYC with NVMe storage. A server that slows down only when neighbours get busy may be waiting on shared CPU time, which we cover in what a dedicated CPU VPS really buys you. Buying more memory for either problem changes nothing but the invoice.
Start smaller and upgrade#
You do not have to guess right on day one. Every one of our plans can be upgraded from the Console. The amount due is shown before you confirm, your data stays, and some resource changes need one reboot. Start one size smaller than your worst-case estimate, watch the graphs for two weeks, and move up if the numbers say so. The Performance, Foundational, or VDS guide helps pick the line before you pick the size.
If you are leaving shared hosting, shared hosting vs VPS covers what else changes besides memory.
FAQ#
Is 1 GB of RAM enough for a VPS?
For a static site, a VPN, or a small bot, often yes. For WordPress with a database on the same server it is tight, and a plugin update or a traffic spike can tip it into swap. 2 GB is a more forgiving floor.
How much RAM does WordPress need on a VPS?
A starter blog runs comfortably in the memory of our F30. A site with WooCommerce, search, and real traffic wants the P40, because every PHP worker and the database buffer grow with the catalogue.
Is 4 GB or 8 GB better for a VPS?
4 GB covers most single sites and small apps. 8 GB is the point where a full control panel, several sites, or a busy store stop fighting for memory. Pick the smaller one if you are unsure, since upgrading keeps your data.
Does more RAM make a VPS faster?
Only if the server was short of it. Once the working set fits, extra memory sits idle as cache. Speed then comes from the processor and the storage.
How much RAM does a game server need?
That depends heavily on the game. Our Minecraft RAM guide and the other game requirement posts size each one separately.
