How Many Websites Can One VPS Run
A practical guide to how many websites one VPS can run, based on workload, shared resources, monitoring, and when to resize or split.
Facts that can change should include a source and check date. Benchmark claims should state the plan, region, method, and test period.
How many websites can one VPS run? There is no universal maximum. One VPS can host multiple websites through virtual hosting, but the practical limit depends on the combined CPU, memory, storage, web-server configuration, database, traffic, and background-task demands. The useful number is therefore as many websites as the VPS can serve reliably within its available resources and required performance.
How one VPS serves multiple websites#
Virtual hosting allows more than one website to run on the same machine. Apache’s name-based virtual hosting lets multiple domains share one IP address, with each hostname mapped to its own document root. Nginx can use multiple server blocks on the same port and route requests according to the hostname requested by the visitor. See the Apache documentation and nginx request-processing documentation.
This makes the number of sites a configuration question, while the safe capacity is a workload question.
What affects the practical limit?#
| Workload | Capacity implication |
|---|---|
| Small static or brochure sites | These may coexist efficiently because they generally place less demand on application and database resources. Their traffic and storage still count. |
| Database-backed CMS sites | The application, database, traffic, and scheduled work all draw from the VPS’s shared resources. |
| Stores, media-heavy sites, and high-traffic applications | These usually require more capacity and closer attention to response quality under expected busy periods. |
These are workload guidelines, not a benchmark or a promise of a particular site count. Ubuntu notes that system requirements depend on the scenario, with memory and storage needs increasing as setups become more complex. Its performance guidance also emphasizes evaluating the specific workload and its bottlenecks.
Every site on the VPS shares the same underlying resources. A demanding site can reduce the resources available to its neighbors, and a faulty site can affect them as well. Keeping unrelated or resource-intensive workloads together may therefore create an operational risk even when the sites technically fit.
A practical way to assess your VPS#
- List what each site runs: static files, a CMS, a store, or another application. Record whether it needs a database.
- Estimate the expected traffic, storage needs, and background tasks for each site. Consider busy periods rather than only average activity.
- Add the workloads together. Capacity planning should account for the whole VPS, because the sites do not receive isolated CPU or memory by default.
- Monitor CPU, memory, storage use, and response quality after deployment. Compare normal operation with the busiest periods you expect.
- Resize the VPS or split workloads when resource pressure becomes recurring or response quality declines. If the sites remain healthy with comfortable headroom, reassess the combined workload before adding another one.
Make the decision from the software and expected workload, not from a target such as ten or one hundred websites. A group of light static sites may fit comfortably, while one busy database-backed application may justify a VPS on its own.
Sources
- Apache HTTP Server — Name-based Virtual Host Support Checked 2026-09-17
- nginx — How nginx processes a request Checked 2026-09-17
- Ubuntu Server — System requirements Checked 2026-09-17
- Ubuntu Server — Performance Checked 2026-09-17