“How much RAM does WordPress need?” is the wrong first question. The right one is: “how much RAM is my WordPress site using right now?” On a $5/month VPS — typically 1–2 GB of RAM — the gap between those two questions is the difference between paying for a 4 GB plan you don’t need and running comfortably on 1 GB for years. This article shows you how to measure real usage, trim the biggest consumers, and know exactly when the $5 tier is genuinely not enough.
Why published “WordPress RAM” figures mislead you
A fresh WordPress install with a default theme and no plugins idles under 200 MB. That single number starts most of the RAM advice on the internet — and it’s nearly useless for planning, because real sites don’t look like fresh installs. Three things break the simple math:
- Plugins add up fast. A page builder adds roughly 60–120 MB per PHP worker. WooCommerce adds 80–150 MB. Caching, security, and analytics plugins each add 20–50 MB. Ten plugins is typical, not extreme.
- PHP workers multiply. WordPress runs PHP code in worker processes. With PHP-FPM defaults, a burst of traffic can spawn 10–20 workers, each holding 100–300 MB. Peak memory is what kills a small VPS, not idle memory.
- Databases and caches sit on top. MariaDB/MySQL keeps buffers in RAM, and Redis or Memcached object caches deliberately consume memory to speed things up.
The result: a well-optimized WordPress site can run on 1 GB, while the same theme with 15 plugins and no caching can chew through 2 GB without breaking a sweat. Guessing is pointless — measuring takes fifteen minutes.
Measure what your site actually uses
On a VPS you have SSH access, which means you can see exactly what’s happening. Run these commands during a normal business hour, then again during your busiest period:
free -m— total, used, and available RAM plus swap usage.htop— sort by memory and look at the top ten processes; PHP-FPM and MySQL should dominate.ps aux --sort=-%mem | head -15— per-process memory in a plain list.grep pm.max_children /etc/php/*/fpm/pool.d/www.conf— the maximum PHP workers allowed; multiply by the average worker size for the PHP ceiling.
Sample 3–4 times across a week and plan for the peak, not the average. A site that idles at 400 MB at 3 AM but hits 1.1 GB during a weekday rush needs the peak number.
A realistic RAM budget for a $5 VPS
| Component | Typical usage |
|---|---|
| OS + base services (nginx, SSH, cron) | 150–250 MB |
| PHP-FPM (4–6 workers) | 300–500 MB |
| MariaDB / MySQL | 200–400 MB |
| Redis object cache | 50–100 MB |
| Total baseline | 700 MB – 1.2 GB |
That baseline fits a 1 GB plan only if you’re disciplined about plugins and caching. A 2 GB plan — the standard $5–$6 tier in 2026 — covers the same site with comfortable headroom for traffic spikes and a second site.
Trim the biggest consumers before paying for more RAM
- Deactivate plugins one at a time and watch
htop. You’ll often find one plugin consuming 200+ MB that you forgot existed. - Cap PHP memory per worker at 128–256 MB instead of the default 512 MB. Few sites need more, and the cap stops runaway workers.
- Use a lightweight theme and avoid stacking page builders. GeneratePress or Kadence with blocks keeps every page cheap to render.
- Enable page caching. A cached page bypasses PHP and the database entirely — static HTML served by nginx uses almost no RAM. This is the single biggest lever on a 1 GB box.
- Add an object cache (Redis or a free plugin such as LiteSpeed Cache) so repeated database queries don’t pile up.
- Match PHP-FPM workers to RAM: (available RAM − OS − database) ÷ average PHP process size. Four workers at 150 MB beats twelve workers at 300 MB.
Add a 1–2 GB swapfile as a safety net against out-of-memory kills during spikes. Swap is 10–100× slower than RAM, so if you’re regularly paging, that’s an upgrade signal — not a reason to add more swap.
When the $5 plan is genuinely not enough
- WooCommerce with many plugins and concurrent checkout traffic.
- Membership sites with thousands of logged-in sessions.
- Multiple WordPress installs or apps sharing one box.
- Sustained CPU above 80% — RAM pressure plus CPU pressure.
If you hit these regularly, RAM isn’t the fix — a bigger plan or a second server is. When you’re ready to compare what the next tier up actually costs across providers, our VPS comparison table lists real specs and renewal pricing side by side, and the notes on what to check at budget price tiers explain where the extra money goes.
The bottom line
Measure first, trim second, upgrade last. Most personal and small-business WordPress sites run fine on 1–2 GB with page caching and a disciplined plugin list. If you’re shopping for a new box and want headroom without paying for it, InterServer’s budget VPS plans start at 2 GB with generous bandwidth, a sensible default for WordPress in 2026.
Related Articles：
Low Cost VPS Hosting in 2026: What $5-$15/Month Plans Actually Deliver
Budget VPS RAM Guide: How Much Memory You Actually Need in 2026
5 Budget VPS Mistakes That Inflate Your Hosting Bill—and How to Avoid Each One
Budget VPS for E-commerce Stores: Best Affordable Hosting Options for Online Shops in 2026
