How much RAM does a WordPress VPS need in 2026

I have lost count of how many times a client opened a ticket saying "WordPress is slow" and the real problem was not the CPU or the network, it was RAM. WordPress itself is light, but the stack around it, PHP-FPM, MariaDB, Redis, Nginx, is what eats memory. Pick a VPS with too little RAM and the kernel starts swapping, every page load jumps from 200 ms to 2 seconds, and the site feels broken. This guide answers the exact question: how much RAM does a WordPress VPS need in 2026, with real numbers you can verify on your own server.

• 1 GB RAM, enough for one low-traffic site with a tuned stack, no WooCommerce, no page builder bloat.
• 2 GB RAM, the practical minimum for a normal business site, one or two sites, a cache plugin, and a reasonable safety margin.
• 4 GB RAM, what I recommend for WooCommerce, membership sites, or sites with real traffic spikes.
• 8 GB RAM, for multiple sites, heavy plugins, or when you want Redis and full page caching without thinking about memory.

Prerequisites

To follow the commands in this post you need a Linux VPS with Ubuntu 24.04 or Debian 12, root or sudo access, and a WordPress site already installed or ready to move. If you are still choosing a provider, a Linux VPS with a dedicated IPv4 and NVMe storage is the right base, the RAM question is independent of the provider.

What actually consumes RAM on a WordPress VPS

People think WordPress, the PHP application, is the memory hog. It is not. A single PHP-FPM worker process typically uses 80 to 150 MB depending on the theme and plugins. The real consumers are the supporting services, and each one reserves a baseline before WordPress even runs.

• MariaDB or MySQL: the InnoDB buffer pool is configurable, but defaults are greedy. On a 2 GB VPS, MariaDB alone can claim 200 to 400 MB.
• PHP-FPM: each worker holds memory. With pm.max_children set to 10, you are reserving roughly 1 GB of headroom for PHP alone.
• Nginx: light, usually 20 to 50 MB for a few worker processes.
• Redis or Memcached: if you cache objects in memory, plan 50 to 150 MB.
• The OS page cache: Linux uses free RAM for caching files. This is not "used" memory in the bad sense, but it masks how much you truly need.

This is why a WordPress site can run on a 512 MB VPS for a while, then collapse when traffic spikes. The cache gets evicted, PHP workers fight for memory, and the swap file takes over. The fix is not a magic plugin, it is sizing the VPS correctly from the start.

Why a 1 GB WordPress VPS is tight but workable

A 1 GB VPS can run WordPress, but only if you accept the constraints. You run one site, you avoid WooCommerce, you disable unused plugins, and you tune PHP-FPM and MariaDB aggressively. With a good cache plugin like LiteSpeed Cache or WP Super Cache, a static page can be served with almost no PHP involvement, which changes everything.

Here is the memory budget I use on a 1 GB VPS:

• OS baseline, 80 to 120 MB.
• Nginx, 20 to 30 MB.
• MariaDB, tuned down to 128 MB for the buffer pool.
• PHP-FPM, 3 to 4 workers at ~100 MB each.
• Cache plugin, file-based, almost no resident memory.

That fits under 700 MB and leaves room for page cache and spikes. The catch is that you cannot run heavy page builders like Elementor or Divi, they push a single PHP request past 200 MB and the whole site starts swapping. If your theme is light and your content is text and images, 1 GB works. If you need WooCommerce or a membership plugin, skip 1 GB and take 2 GB.

How much RAM does a WordPress VPS need for a normal business site

For a typical business website, a landing page, a blog, a contact form, no online store, 2 GB of RAM is the sweet spot in 2026. It gives PHP-FPM enough workers for concurrent visitors, leaves MariaDB a real buffer pool, and lets you run a cache plugin without counting megabytes. This is the plan I recommend to most people who ask "how much RAM does a WordPress VPS need" and the answer is almost always 2 GB.

On a 2 GB plan the typical breakdown looks like this:

• OS baseline, 150 MB.
• Nginx, 30 MB.
• MariaDB with a 256 MB buffer pool, around 350 MB total.
• PHP-FPM with 6 workers at ~120 MB each, around 700 MB.
• Redis for object cache, 128 MB.
• Remaining, 600 MB for page cache, spikes, and the OS.

That leaves a real margin. A traffic spike that doubles PHP workers does not crash the box, it just uses the idle memory. If you run WordPress VPS hosting from a provider with NVMe storage, the swap file on NVMe is fast enough to be a safety net, but you never want to live in swap, it still hurts latency.

When you need 4 GB or more for WordPress

Move to 4 GB when your site stops being a brochure and becomes an application. WooCommerce is the biggest trigger, a single product page can spawn several PHP workers for plugins, cart fragments, and AJAX calls. Add a page builder and a caching plugin with queue mode, and 2 GB starts feeling tight during sales or campaigns.

The second trigger is concurrency. If you get regular spikes of 50 to 100 simultaneous visitors, for example after an email newsletter or a social post, each visitor needs a PHP worker during uncached requests. With 4 GB you can run 20 to 25 PHP-FPM workers, which is more than enough for most WordPress sites. The third trigger is running multiple sites on one VPS, each site needs its own PHP-FPM pool and its own MariaDB database.

An 8 GB VPS is rarely about WordPress itself. It matters when you run several sites, a staging environment, Redis and a full page cache, plus monitoring tools, all on one box. It also gives you headroom if you expect to grow without migrating. But do not buy 8 GB hoping it fixes a slow site, if the bottleneck is a bloated theme or a missing cache plugin, more RAM only delays the real fix.

How to check your actual WordPress memory usage

Before you pick a plan, measure what your site actually uses. Do not guess. Run this on your current server and look at the real numbers:

free -h
ps aux --sort=-%mem | head -15
systemctl status php8.3-fpm mysql nginx

The free -h command shows total, used, and available memory, plus swap usage. If swap is above 200 MB during normal traffic, you need more RAM. The ps aux sorted by memory shows exactly which process is the biggest consumer, usually php-fpm or mysqld. The third command confirms all three services are running and which PHP version you have.

To see the PHP-FPM memory per worker, run:

ps -o rss,cmd -p $(pgrep -f php-fpm | head -5)

This prints the resident memory of five PHP-FPM workers. Multiply the average by your pm.max_children value in /etc/php/8.3/fpm/pool.d/www.conf and you get the real PHP budget. Do this during a traffic peak if you can, the idle numbers are always lower than reality.

RAM tuning tips that reduce what you need

Before upgrading your VPS, tighten the stack. These three changes often let a site run comfortably on a smaller plan.

Cap PHP-FPM workers. In www.conf set pm = dynamic with pm.max_children = 6 on a 2 GB VPS. This prevents PHP from spawning dozens of workers and exhausting memory. Pair it with pm.max_requests = 500 so workers recycle and release leaked memory.

pm = dynamic
pm.max_children = 6
pm.start_servers = 2
pm.min_spare_servers = 1
pm.max_spare_servers = 3
pm.max_requests = 500

Limit the MariaDB buffer pool. In /etc/mysql/mariadb.conf.d/50-server.cnf set innodb_buffer_pool_size = 256M on a 2 GB VPS. The default formula can grab a quarter of your RAM, which is wasteful for a small site. Restart MariaDB after the change and verify with SHOW VARIABLES LIKE 'innodb_buffer_pool_size';.

Use a real cache plugin. LiteSpeed Cache or WP Super Cache with page caching enabled means most visitors never hit PHP at all. Nginx serves the static HTML directly, which drops memory pressure dramatically. This single change does more for a low-RAM VPS than any other tweak.

What about WordPress on a Windows VPS

WordPress officially runs on Linux, but it also works on Windows Server with IIS and PHP. The reality is that Windows consumes more RAM for the same workload, the OS baseline alone is 600 to 800 MB before PHP even starts. A 2 GB Windows VPS runs WordPress but leaves almost nothing for PHP-FPM or MySQL, which is why I only recommend Windows for WordPress when the team already lives in the Microsoft ecosystem and needs IIS-specific features. If you want to see how the platforms compare for other workloads, read how to choose between Linux and Windows. For a pure WordPress site, a Linux Linux VPS with 2 GB or 4 GB is the better spend.

Swap as a safety net, not a solution

Adding swap on a low-RAM VPS keeps the box from OOM-killing processes, but it does not make the site fast. When the kernel swaps, every PHP request reads from disk instead of RAM, and latency climbs. On a VPS with NVMe storage, swap is faster than on spinning disks, but it is still orders of magnitude slower than RAM. If you are adding swap to fix slowness, the real fix is more RAM or a cache plugin. I cover the setup in detail in how to enable swap on a low RAM VPS, but treat it as a crash guard, not a performance feature.

Cost of each RAM size on a Vietnam VPS

RAM is where VPS pricing scales fastest. On a Vietnam provider, a 1 GB VPS starts around $2 to $3 per month, 2 GB around $4 to $6, 4 GB around $8 to $12, and 8 GB around $15 to $25. International providers like DigitalOcean or Vultr sit in a similar range. The point is that going from 2 GB to 4 GB is usually a few dollars a month, which is cheaper than a developer's hour spent fighting memory errors. Pricing changes over time, so check the current plans on VPS pricing before you commit.

WordPress VPS 内存 2GB 是大多数业务网站的最低推荐配置。

2 GB of RAM is the minimum I recommend for most business WordPress sites.

My recommendation for 2026

Here is the shortcut. If you are starting a new WordPress site and asking how much RAM it needs, take 2 GB. It runs a normal business site with room for traffic spikes and cached pages. If you plan WooCommerce, run a page builder, or expect real traffic from day one, take 4 GB and never think about memory again. Skip 1 GB unless you are hosting a single static-ish blog and you are comfortable tuning PHP-FPM and MariaDB yourself.

Whatever size you pick, enable a cache plugin before you go live, cap PHP-FPM workers, and set a sane MariaDB buffer pool. Those three actions matter more than the exact RAM number. A rent Linux VPS with 2 GB and NVMe storage, configured this way, runs a fast WordPress site for most people in 2026.

FAQ

Related articles

• Install WordPress on a LiteSpeed VPS in 2026
• Making WordPress fast with LiteSpeed and LSCache on a VPS
• Optimize PHP-FPM for WordPress on a VPS
• Moving a WordPress site from shared hosting to a VPS