"How much RAM does WordPress need?" has no single answer. It depends on traffic, plugins and caching. This guide gives realistic starting points so that you neither overpay nor crash on launch day.
Starting points by traffic
| Site | Visitors a day | Suggested VPS |
|---|---|---|
| Personal blog, portfolio | Up to 2,000 | 1 vCPU, 1 to 2 GB RAM |
| Small business, news site | 2,000 to 20,000 | 2 vCPU, 4 GB RAM |
| WooCommerce store, membership site | 10,000 and up | 4 vCPU, 8 GB RAM |
| High-traffic publisher | 100,000 and up | Dedicated CPU, 16 GB or more, plus a CDN |
These are guides, not guarantees. A well-cached site on 2 GB often beats a badly configured one on 8 GB.
What actually uses resources
- PHP workers. Each uncached page view takes a PHP process, roughly 50 to 150 MB of RAM. More workers means more simultaneous visitors.
- The database. MariaDB or MySQL needs memory for its buffer pool. 256 to 512 MB is fine for small sites.
- Plugins. Page builders, backup plugins and security scanners are the usual causes of slow sites.
- Images. Large unoptimised images waste bandwidth and CPU on every page.
The cheapest big speed-up: caching
- Page caching (a plugin such as WP Super Cache or Nginx FastCGI cache) serves most visitors a saved HTML file with no PHP at all.
- Object caching with Redis stores database results in memory.
- OPcache keeps compiled PHP in memory. It is built into PHP and should be on.
- A CDN serves images and scripts from servers near the visitor.
Why NVMe storage matters
WordPress reads many small files and runs many small database queries. NVMe disks handle those random reads far faster than SATA SSDs or hard disks, which shows up directly as faster page generation. Every plan we sell uses NVMe.
Choosing a location
Put the server near most of your visitors. A visitor 100 ms away feels every extra round trip. See how to choose a VPS location.
Next steps
Install the stack with our Nginx guide, secure it with the 15-minute checklist and automate backups.