How Much RAM Does a VPS Need? A Complete Guide

Most websites run well on a VPS with 2 to 8 GB of RAM. A small blog fits in 2 GB. A busy WooCommerce store wants 6 to 8 GB. Game servers and databases can ask for far more.

The right figure depends on your workload. It also depends on how many people use your server at once, and how much spare room you want. 

This guide starts with a sizing table. Next, it shows the math behind each row so that you can check the numbers against your own setup.

Finally, it explains how to read live memory usage and catch trouble before your site slows down.

How Much RAM Does a VPS Need? Quick Sizing by Workload

Use this table as a starting point. Each row lists a floor and a comfortable level. The floor keeps the server running. The comfortable level leaves room for traffic spikes, updates, and growth.

Workload	Minimum RAM	Comfortable RAM	What drives memory use
Static site or landing page	1 GB	2 GB	Web server only
WordPress blog	2 GB	2 to 4 GB	PHP workers and plugins
Business WordPress site	2 GB	4 GB	Plugins, database, caching
Page-builder site (Elementor, WPBakery)	4 GB	4 to 6 GB	Heavy page rendering and admin work
WooCommerce store	4 GB	6 to 8 GB	Uncached cart and checkout requests
High-traffic news site	8 GB	8 to 16 GB	Concurrent readers, database, cache
cPanel hosting server	2 GB	4 GB	Panel services plus hosted sites
Dedicated database server	4 GB	8 GB or more	Size of your working dataset
Small vanilla game server	2 GB	4 GB	Players, map size, view distance
Modded game server	6 GB	10 GB or more	Modpack size and player count
Private VPN	1 GB	2 GB	Light, steady load

These figures come from the WordPress project, cPanel documentation, and hosting provider sizing guides. Every stack differs, so treat them as starting points.

Now apply the headroom rule. Plan for 25 to 30% of memory to stay free under normal load. Servers that sit near 100% tend to stall or kill processes during the first spike.

What Uses RAM on a VPS? How to Calculate Your Number

Every VPS memory budget has the same parts. Add them up, then add headroom.

Total RAM = OS + web server + (PHP workers x memory per worker) + database + cache + headroom

Here is what each part means in practice:

• Operating system. A bare Linux server idles at a few hundred megabytes. Run free -h on a fresh install to see your exact figure.
• Web server. Nginx adds modest overhead. Apache can grow quickly when it spawns many processes.
• PHP workers. Each PHP-FPM worker handles one request at a time. A WordPress worker often uses 40 to 100 MB. Heavy plugins push that figure higher.
• Database. MariaDB and MySQL keep hot data in memory. The InnoDB buffer pool is the largest slice.
• Cache. Redis and Memcached reserve memory up front. A busy WooCommerce store may give Redis 256 MB to 1 GB.
• Headroom. Add 25 to 30% on top. That buffer stops updates and spikes from triggering swap.

Measure your own worker size instead of guessing. Run this command and replace 8.3 with your PHP version:

ps -C php-fpm8.3 -o rss= | awk '{s+=$1} END {printf "%.0f MB average\n", s/NR/1024}'

Worked Example: A Mid-Size WordPress Site

These numbers are illustrative. Replace them with your own measurements.

• Operating system: 0.4 GB
• Nginx: 0.1 GB
• PHP: 10 workers at 70 MB each, or 0.7 GB
• MariaDB: 0.8 GB
• Redis: 0.25 GB
• Subtotal: 2.25 GB

Next, divide the subtotal by 0.7 to leave 30% of memory free. That gives about 3.2 GB. Round up to the next plan size. A 4 GB VPS fits this site well.

Why Concurrency Sets Your Worker Count

Monthly visitors tell you little about memory. Simultaneous requests tell you far more.

A site with 100,000 monthly visits may never run more than five requests at once. Meanwhile, a store running a flash sale can hit fifty at the same moment.

Cached pages skip PHP entirely, so they use almost no worker memory. Uncached pages, such as checkout, tie up a worker for every request.

How Much RAM Does a WordPress Site Need on a VPS?

WordPress itself is light. Plugins, themes, and traffic are what add memory.

Blogs and Business Sites

The WordPress project recommends at least 512 MB of RAM for a production install. That figure covers WordPress alone.

Your VPS also runs the operating system, the web server, and the database. A realistic floor for a blog is 2 GB.

Older guides still claim that 256 MB is enough. That advice is outdated. Do not confuse it with the PHP memory limit. A limit of 256 MB caps what one request may use. It does not set the size of your VPS.

Business sites with several plugins usually fit in 2 to 4 GB. Many hosting guides place a typical small business site at 4 GB. Pick 4 GB if several plugins query the database on every page.

Page Builders and Heavy Plugins

Elementor and WPBakery add heavy rendering work. Sizing guides place these sites at 4 GB. The admin dashboard takes the biggest hit, since editing, imports, and plugin updates all run uncached.

A site that feels smooth for visitors can still choke while you update plugins.

WooCommerce Stores

Cart and checkout pages cannot use full-page caching. Each request runs PHP and database queries from scratch. As a result, a store needs more memory than a blog with the same traffic.

Sizing guides place typical WooCommerce stores at 6 to 8 GB. Add a Redis object cache to cut database load. Budget 256 MB to 1 GB for it. News and publishing sites with heavy traffic sit higher, at 8 to 16 GB.

How Much RAM Do Databases and Caching Layers Need?

Databases and caches trade memory for speed. Size them on purpose, instead of letting them take whatever they find.

• MySQL and MariaDB. The InnoDB buffer pool should come close to the size of your hot data. On a server that also runs a web stack, give it a modest share. On a dedicated database server, it can take 70 to 80% of RAM.
• Dataset check. Run this query to see how much data you hold:

SELECT ROUND(SUM(data_length + index_length) / 1024 / 1024) AS size_mb

FROM information_schema.tables;

• Redis. It holds its reserved memory even when traffic is low. Set a maxmemory limit and an eviction policy, so it never crowds out PHP.
• Varnish. It stores whole pages in memory. Size it by the number of pages you want cached.

Budget each cache as its own line in your memory plan. Then watch real usage for a week and trim.

Move the database to its own server when PHP workers and the buffer pool compete for memory at peak. A separate server also isolates a runaway process.

How Much RAM Do Game Servers and Apps Need?

Game servers vary more than websites. Title, version, mods, and player count all change the answer. Check your game’s documentation before you buy. These ranges give you a first estimate:

• Minecraft, vanilla or Paper. 2 to 4 GB for small groups of up to 10 or 20 players.
• Minecraft, modded. 6 to 10 GB is common. Large modpacks want more.
• Rust. 8 GB is the minimum for a real map. Bigger maps need more.

Follow these rules when you set up the server:

• Leave 0.5 to 1 GB for the operating system when you set the Java heap.
• Avoid an oversized heap. It can lengthen garbage-collection pauses.
• Watch the CPU too. Minecraft leans on single-thread speed, and extra RAM cannot rescue a slow core.
• Confirm that your plan gives you dedicated RAM. Some cheap plans sell burstable memory that neighbors can squeeze.

Private VPNs

A private VPN is one of the lightest workloads you can run. Most setups need 1 to 2 GB. That leaves room for a small side project on the same server.

Developer Apps and Containers

Add up the footprint of each service, then add headroom. Node, Python, and database containers all count. Set a memory limit on every container, so one service cannot starve the rest. Besides that, give a staging server the same stack as production, or your tests will mislead you.

Hypervisors and Virtual Machines

Each guest virtual machine reserves its full allocation. Sizing, therefore, starts from the guests, not the host. Check that your provider allows nested virtualization first. Most people who need this are better off with a larger plan or a dedicated server.

How Do Traffic Spikes and Concurrent Users Change RAM Needs?

Spikes hurt when they hit uncached pages. Use this method to plan for them:

• Find your peak. Open your analytics and server logs. Pick the busiest hour of the past month.
• Estimate workers. Multiply uncached requests per second by average response time in seconds. For example, 20 requests per second at 0.5 seconds needs about 10 workers.
• Convert to memory. Multiply the worker count by your measured worker size.
• Add headroom. Keep 25 to 30% free. That buffer covers launches, sales, and email campaigns.

Cache before you buy more RAM when spikes land on cached pages. However, add RAM when spikes hit checkout, search, or logged-in users. Those requests bypass the page cache, so everyone needs a worker.

Linux or Windows VPS: Does the Operating System Change Your RAM Math?

Yes, and the gap is large. Microsoft lists 512 MB as the minimum for Windows Server 2022 with Server Core. The Desktop Experience needs 2 GB, and Microsoft recommends 4 GB. A bare Linux server idles at a few hundred megabytes.

As a result, a Windows VPS with a desktop should start at 4 GB for comfortable use. Choose Linux for typical web hosting.

Choose Windows when you need ASP.NET, SQL Server, or remote desktop apps. Set a memory cap on SQL Server, since it claims memory aggressively by default.

Control panels add their own load. The cPanel documentation lists 2 GB as the minimum, and hosting guides recommend 4 GB.

A 2 GB VPS running cPanel, therefore, leaves almost nothing for your sites. Other panels have their own minimums. Check the vendor’s current documentation before you buy.

How to Tell Your VPS Has Too Little RAM

Check usage at your busiest hour, not at midnight. A quiet server hides the problem.

• free -h. Read the available column, not free. Linux fills spare RAM with disk cache, so free looks low on healthy servers.
• htop. Sort by memory to see which process holds the most. A single plugin or worker pool is often the culprit.
• Swap. Steady swap use means the server is short on memory. Swap lives on disk, so it runs far slower than RAM.
• OOM killer. Run journalctl -k | grep -i “out of memory” to check. Linux kills processes when memory runs out. The database is often first, since it holds the most.

Watch for these symptoms too:

• Random 502 or 503 errors
• Database connection errors
• A slow WordPress dashboard
• Services that stop without warning

Now decide between tuning and upgrading. Tune first when one process eats most of the memory. Upgrade when you have sized everything sensibly, and available memory still drops below roughly 20% at peak.

If memory climbs and never falls, suspect a leak. Fix that before you pay for more RAM.

RAM vs CPU and Storage: What Else to Size

RAM cannot fix a CPU bottleneck. A VPS with plenty of memory and too few cores still stalls under heavy PHP or database work.

As a starting point, pair 2 GB with 1 to 2 vCPUs. Pair 4 GB with 2 vCPUs. Move to 4 vCPUs for WooCommerce stores in the 6 to 8 GB range. Game servers and PHP-heavy sites may need more cores still.

Storage plays a smaller role. Quick NVMe disks soften the cost of swapping. They do not replace RAM.

FAQs

Match Your VPS Plan to Your Workload

Size your workload, add 25 to 30% headroom, then adjust from measured usage. That rule works better than any fixed tier. Find your row in the sizing table. Run the worked example with your own numbers. Round up to the next plan size.

Ready to pick a plan? Compare Truehost VPS plans and match your result to a RAM tier. After launch, run free -h at your busiest hour. If available memory stays healthy, you sized it right.