One VPS per WordPress Site or Many Sites on One Server?
- Bandwidth per site
- GB/month
- Result
- Monthly traffic (visits)
- 50000
- You entered
- Average page size
- 2 MB
- You entered
You can run many WordPress sites on a single VPS, and for most people that is the better choice, but one site per VPS makes sense when that site is large, mission-critical, or needs strict isolation. The right answer depends on your traffic, budget, and how much you value simplicity over cost savings.
Formula
Estimated bandwidth (GB/month) = (monthly visits × average page size in MB / 1024) × number of sites. The division by 1024 converts megabytes to gigabytes. Each variable is: t = total monthly visits (visits), s = average page size (MB), v = number of WordPress sites. The result is a rough upper bound for the data transferred, assuming every visit downloads the full page and all assets.
Worked Example
Using the default values: t = 50,000 visits, s = 2 MB, v = 3 sites. First compute per-site bandwidth: 50,000 × 2 / 1024 = 97.65625 GB. Then multiply by 3 sites: 97.65625 × 3 = 292.96875 GB. So the calculator shows about 293 GB per month total, or about 98 GB per site. That is the amount of data your VPS will push out if every visit loads the full 2 MB page.
What a VPS Actually Gives You
A Virtual Private Server (VPS) is a slice of a physical server. You get dedicated CPU cores, RAM, and storage that are reserved for you, unlike shared hosting where resources are shared with hundreds of other accounts. On a VPS you have root access, meaning you can install and configure software, adjust PHP settings, set up caching, and run multiple websites. The key limits are the resources you rent: CPU, RAM, disk I/O, and bandwidth. When you run one WordPress site, all those resources go to that single site. When you run many, they share the pool.
Many Sites on One VPS: The Common Setup
Most WordPress agencies, freelancers, and small businesses run several sites on one VPS. This is done using a control panel like CyberPanel, HestiaCP, or manually with Nginx or Apache virtual hosts. Each site gets its own directory, database, and configuration files, but they all use the same PHP processor, the same MySQL or MariaDB server, and the same operating system. This approach is popular because it is dramatically cheaper. A VPS that costs $20 per month can easily host 10 to 20 low-traffic WordPress sites, whereas a managed WordPress host might charge $20 per site per month.
The trade-off is that a single compromised plugin or theme on one site can potentially affect the whole server. If one site is hacked, the attacker may be able to read other sites’ files or databases, especially if permissions are not locked down. Also, a sudden traffic spike on one site can exhaust CPU or RAM and slow down all the other sites on that VPS. For low-traffic sites (under a few thousand visits per month each), this is rarely a problem in practice.
One Site per VPS: When It Makes Sense
There are clear cases where one WordPress site per VPS is the right call:
- High traffic: A site with hundreds of thousands of monthly visitors needs most of a VPS’s resources. Sharing would cause slow response times and downtime.
- E-commerce or membership sites: These handle sensitive data (credit cards, personal info) and need strong isolation to reduce risk. A compromise on one site should not expose another.
- Custom server requirements: If one site needs a specific PHP version, a different database, or special extensions that would conflict with other sites, separate VPSs avoid those conflicts.
- Compliance or client contracts: Some clients require that their site be on dedicated resources for performance or security guarantees.
For a single high-value site, the extra cost (often $10–$50 per month) is worth the peace of mind and predictable performance.
How to Choose: A Practical Checklist
Before deciding, ask yourself these questions:
- What is the total monthly traffic across all sites? If it’s under 100,000 visits, one VPS with 2–4 GB RAM is usually enough.
- What is the peak traffic? A site that gets 10,000 visits in one hour (e.g., a product launch) needs more headroom than one that spreads visits evenly.
- Do any sites handle payments or personal data? If yes, consider isolating them.
- How comfortable are you with server administration? Running many sites means managing updates, security, and backups for each one. If you prefer a managed solution, one site per VPS (or managed WordPress hosting) is simpler.
- What is your budget? Compare the cost of one large VPS vs. several small VPSs. Often one large VPS is cheaper than two small ones, but not always.
Common Problems and How to Avoid Them
Running many sites on one VPS can lead to a few recurring issues:
- Resource exhaustion: A single site with a memory leak or a runaway script can consume all RAM. Solution: set PHP memory limits per site, use a process manager like PM2 or systemd, and monitor with tools like htop or Netdata.
- Security cross-contamination: If one site is hacked, others are at risk. Mitigate by running each site under a separate system user (using a panel like CyberPanel does this), isolating PHP sessions, and keeping all software updated.
- Backup complexity: You need to back up each site’s files and database separately. Automate with a script that loops through all sites, or use a panel that supports per-site backups.
- SSL certificate management: With multiple domains, you need an SSL certificate for each. Let’s Encrypt makes this free and automated, but you must configure it correctly for each domain.
Cost Comparison: One Big VPS vs. Several Small Ones
To illustrate, consider a typical VPS provider (prices vary, but these are realistic). A 2-core, 4 GB RAM, 80 GB NVMe VPS costs about $20–$30 per month. A 4-core, 8 GB RAM, 160 GB NVMe VPS costs about $40–$60 per month. If you need to host 5 WordPress sites with moderate traffic, one 4-core VPS at $50 is far cheaper than five 2-core VPSs at $20 each ($100). Even with a control panel license (some are free), you save money. But if you have 5 sites that each need 4 GB RAM (unlikely for most), then you’d need 5 VPSs anyway.
Also consider managed WordPress hosts like WP Engine or Kinsta. They charge per site (often $20–$30 per month per site) but handle security, caching, and backups. For non-technical users, that can be worth the cost. For developers, running many sites on one VPS is a skill that pays off.
Security and Isolation Best Practices
If you choose to run many sites on one VPS, follow these practices to reduce risk:
- Use a control panel that creates separate system users for each site (e.g., CyberPanel, HestiaCP).
- Set strict file permissions: each site’s files should be owned by its own user, not the web server user.
- Use PHP-FPM with per-site pools so a crash in one site doesn’t kill others.
- Install a firewall (like UFW) and only open ports 80, 443, and SSH.
- Enable automatic updates for WordPress core, plugins, and themes, but test on a staging site first.
- Take daily backups of each site’s files and database, and store them off-server.
Frequently Asked Questions
Can I host 100 WordPress sites on one VPS?
Technically yes, if the sites are extremely low traffic (e.g., personal blogs with a few hundred visits per month) and the VPS has enough RAM (8 GB or more). In practice, you’ll run into resource limits and management overhead. A better approach is to use a VPS with a control panel and start with 10–20 sites, then monitor resource usage.
Is it safe to host multiple WordPress sites on one VPS?
It can be safe if you isolate each site with its own system user, keep everything updated, and use strong passwords. The biggest risk is that a compromised site gives an attacker access to the server, which could then affect other sites. Using per-site PHP-FPM pools and proper file permissions significantly reduces this risk.
What are the signs that I need to move a site to its own VPS?
If you see high CPU or RAM usage consistently (e.g., above 80% for more than a few minutes), slow page loads, or if one site’s traffic spike causes other sites to become unresponsive, it’s time to isolate that site. Also, if a site gets hacked, move it to a separate VPS to clean it without risking others.
How much RAM do I need for 10 WordPress sites?
For low-traffic sites (under 5,000 visits per month each), 4 GB RAM is usually enough. For moderate traffic (up to 20,000 visits per month per site), go with 8 GB. Each WordPress site with caching uses about 50–100 MB of RAM for PHP, plus MySQL overhead. Monitor with free -m to see actual usage.
Should I use a control panel like cPanel or CyberPanel for multiple sites?
Yes, a control panel simplifies managing multiple sites, SSL certificates, and backups. CyberPanel is free and works well with OpenLiteSpeed. cPanel is more expensive but widely used. If you’re comfortable with the command line, you can skip the panel and use Nginx config files, but that’s more error-prone.
What is the difference between a VPS and shared hosting for WordPress?
Shared hosting puts many users on one server with no dedicated resources, so a neighbor’s traffic spike can slow your site. A VPS gives you dedicated CPU, RAM, and storage, and root access. For multiple sites, a VPS is almost always better because you can isolate and configure each site.
Related
Formula used
in t | Monthly traffic (visits) | - | 50000 | 0 in s | Average page size | MB | 2 | 0 in v | Number of sites | - | 3 | 1 out bw | Estimated bandwidth | GB/month | (t * s / 1024) * v | 1 out per_site | Bandwidth per site | GB/month | (t * s / 1024) | 1
Each line is one input (in, sel, list) or one result (out: label, unit, formula, decimals). How the calculators work
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.