How much RAM does a VPS need? A practical guide
Most small websites run fine on 1 to 2 GB of RAM. A WordPress site with caching or a typical Node app is comfortable on 4 GB. A database server needs enough RAM to hold the data it reads most often, and that is the only case where guessing costs you.
By VPSRely Editorial, Editorial team. Published . 7 min read.
The short answer by workload
These are rules of thumb, not guarantees. Your own software decides the real number, so measure before you pay for more.
- Static site or small tool: 1 GB
- WordPress or a small Node, Python or PHP app: 2 to 4 GB
- App plus its own database on one server: 4 to 8 GB
- Busy database or several services: 8 GB and up
- Windows desktop over RDP: 4 GB or more, because Windows itself uses a lot
What actually uses the memory
The operating system takes a slice first. A bare Linux install is light, while Windows Server uses noticeably more before you run anything.
Then come your processes: the web server, your app runtime, background workers and any database. Each one grows with traffic and with the size of the data it keeps in memory.
Spare RAM is not wasted. Linux uses free memory as a disk cache, which makes repeat reads faster. A server showing high memory use is often just caching.
How to measure what your server really uses
On Linux, run free -h. Read the available column, not the free column. Available estimates how much memory programs can still use without swapping.
To see which processes use the most, run ps aux --sort=-%mem | head. Check it during your busiest hour, not at three in the morning.
To find out whether the server ever ran out, run dmesg | grep -i "out of memory". If it prints lines, the kernel ended a process to survive, and you need more RAM or a lighter setup.
Swap is a safety net, not extra RAM
Swap is disk space the system uses when RAM runs out. It prevents crashes, but it is many times slower than RAM.
A small amount of swap is fine as insurance. A server that swaps all day needs more RAM, not more swap.
Check what you use before you choose
If you already run the site somewhere, look at peak memory over a normal busy week, then add about a third as headroom. If it is new, start one size up from your estimate and watch it for a month.
You can move to a larger plan later. Our plans and prices list every size, and the Linux VPS page covers what each one suits.
Databases are the exception
A database runs best when its working set fits in memory. If your most-read data is 3 GB, a 2 GB server will keep hitting the disk and feel slow however fast the disk is.
Check the official guidance for your database before you size the server. For example, the PostgreSQL documentation explains how it uses shared memory and cache.
Three worked examples
Each one starts from the workload, then picks a size. Treat the numbers as a first guess and measure afterwards.
- A WordPress site with a caching plugin and a few thousand visits a day: start at 2 GB. Move to 4 GB if PHP and the database compete for memory.
- A Node.js API with one or two processes and its database hosted elsewhere: 1 to 2 GB is usually enough.
- A Postgres database holding 10 GB, serving one app: size RAM to cover the part of those 10 GB you read often. For many apps that means 8 GB or more.
When you should not buy a VPS
If you run one small WordPress blog and do not want to patch a server, shared hosting is cheaper and less work. A VPS means you handle updates, security and backups yourself.
Buy a VPS when you need root access, your own software stack, a Windows desktop, or resources that no one else can use.
A note on Windows
Windows Server needs more memory than Linux for the same job. Pick a larger plan on the Windows VPS page than you would on Linux, and check Microsoft's published requirements for the exact edition you run.