A VPS has no fixed limit on the number of websites it can host—it can handle anywhere from 1 to 50 or more domains depending on the resources provisioned and the actual consumption of each site. The constraint isn't domain count; it's available RAM, vCPUs, and bandwidth.
This guide helps you estimate how many projects fit on your VPS, which factors reduce that capacity, and how to optimize for hosting more with less.
Domain Count Is Not the Real Limit
A web server like Apache or Nginx can serve hundreds of virtual hosts with near-zero configuration overhead. What actually consumes resources is what runs behind each site:
- PHP-FPM: each pool reserves processes in RAM. A pool with 5 workers at ~30 MB each uses ~150 MB.
- Database: MySQL/MariaDB can consume 256 MB to several GB depending on concurrent query load.
- Cache: Redis or OPcache in RAM reduces disk I/O but also occupies memory.
- Traffic: simultaneous visitor spikes drive CPU and RAM usage up at the same time.
That's why two high-traffic sites can saturate a 4 GB VPS, while twenty low-traffic sites with active caching fit comfortably on the same plan.
Capacity Estimates by VPS Plan
The table below assumes WordPress sites with WP Rocket or LiteSpeed Cache, PHP-FPM in ondemand mode, and low-to-moderate per-site traffic (fewer than 500 visits/day). For higher-traffic sites, divide the estimate by 2–3.
| VPS Plan | RAM | vCPU | Est. WP Sites | Notes |
|---|---|---|---|---|
| Entry | 1 GB | 1 | 1–3 | Light sites only; no Redis |
| Basic | 2 GB | 1–2 | 5–10 | Good for a small agency portfolio |
| Standard | 4 GB | 2 | 15–25 | Comfortable with caching; handles 1–2 stores |
| Mid-range | 8 GB | 4 | 30–50 | Medium agency portfolio |
| High | 16 GB | 6–8 | 60–100+ | With reseller panel; mixed load |
These numbers are guidelines. The only definitive answer comes from monitoring your server's actual usage with tools like htop, free -h, or Netdata.
Factors That Drastically Reduce Capacity
Online Stores (WooCommerce, PrestaShop)
An e-commerce site with an active cart can't be served 100% from static cache—every user session and checkout step requires live PHP and database. A single store with moderate traffic can consume the equivalent of 5–8 cached blogs.
PHP Without OPcache
Without OPcache, PHP recompiles every script on every request. Always enable it: it saves CPU and up to 30% of process RAM.
Heavy or Poorly Optimized Plugins
Page builder plugins (Divi, legacy Elementor) or SEO plugins with active crawling generate extra database queries on every page load.
Concurrent Backups and Cron Jobs
A database backup running at 2 a.m. while another cron re-indexes search can spike CPU to 100% for minutes, slowing every active site on the server.
How to Maximize the Number of Sites on Your VPS
- PHP-FPM in ondemand mode: processes only spawn on incoming requests, freeing RAM when a site is idle.
- Full-page caching: reduces CPU time per visit by up to 90% on content sites and blogs.
- Properly sized OPcache: allocate at least 128 MB of
opcache.memory_consumptionfor medium portfolios. - One shared MariaDB instance: more efficient than one instance per site; tune
max_connectionsto your RAM. - Redis for sessions and object cache: reduces database pressure from the busiest sites.
- Staggered backups: spread cron backup jobs across different hours to avoid simultaneous spikes.
If you manage multiple clients from an agency, it's worth evaluating whether a VPS with a reseller panel or an entry-level dedicated server gives you better cost-per-site economics at scale.
When Does a VPS Stop Being Enough?
Signs that your VPS has outgrown your needs:
- RAM usage stays above 85% consistently—not just during spikes.
- CPU load average exceeds your vCPU count for more than 10 minutes straight.
- Response times increase even though traffic hasn't changed.
- You start seeing intermittent 502 or 504 errors with no recent code changes.
When those symptoms appear, the first step is to scale vertically (more RAM/CPU on the same VPS). If you've hit the provider's maximum plan, it's time to evaluate a dedicated server or a cloud environment with autoscaling.
At elenlace.com we help agencies and businesses choose the right infrastructure—from entry VPS to dedicated servers—with server configuration included so you get maximum performance from day one.
Key Takeaways
- A VPS has no domain limit; the real limit is available RAM and CPU.
- With 2 GB RAM and active caching, 5–10 lightweight WordPress sites fit comfortably.
- A single online store can consume the resources of 5–8 cached blogs.
- PHP-FPM in ondemand mode and OPcache are the two highest-impact optimizations.
- Monitor actual RAM and CPU usage—not domain count—to know when to scale.
FAQ
Can a 1 GB RAM VPS host multiple websites?
Yes, but with restrictions. With PHP-FPM in ondemand mode, full-page caching, and no high-traffic database, 2–3 lightweight sites can coexist. Without optimization, a single WordPress install already consumes 300–500 MB and leaves little room for others.
How many sites does a VPS with cPanel/WHM support?
The control panel itself adds ~200–400 MB of overhead. On a 4 GB VPS with cPanel, the effective memory available for sites is roughly 3–3.5 GB. Within that budget, the number of sites still depends on per-site consumption, not the panel itself.
Is it better to have one database per site or a shared instance?
A single shared MariaDB instance with multiple databases is usually more efficient than several separate instances. Multiple instances double the engine's memory overhead. The exception is when one site has query spikes that need to be isolated from the rest.
Does the number of sites affect the speed of each one?
Only if sites compete for the same resources simultaneously. If one site gets a traffic spike while the others are idle, the others aren't affected. Cross-site impact occurs when multiple sites receive concurrent traffic and exhaust the shared RAM or CPU.
Prefer it done for you? El Enlace handles hosting and professional web development.
Further reading
Other providers and guides worth comparing:
