The right architecture depends on how much the sites must share. A WordPress Multisite network is efficient when one team needs common code, plugins, users and coordinated updates. Separate WordPress installations are safer when sites have different owners, release schedules, plugin stacks or failure boundaries; separate databases and database users provide the strongest practical isolation on one server.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
There is no honest universal answer to “how many WordPress sites can one VPS host?” Capacity is determined by traffic patterns, uncached requests, plugin work, PHP worker limits, database queries, storage and backup requirements. Design the server in layers, measure under representative load and keep tested restores before adding more sites.
As an Amazon Associate I earn from qualifying purchases.
Recommended Free Tools
Choose the operating model before choosing server size
Start by deciding whether the sites are one coordinated product or several independent applications. This decision affects upgrades, authentication, routing, backups and the consequences of a compromise or configuration mistake.
| Architecture | How it works | Best fit | Main trade-off |
|---|---|---|---|
| Multisite network | One WordPress installation and database host multiple sites in a network. Core files, themes and plugins are shared; each site has its own content tables and media-upload directory, while the user table is shared. | Related sites managed by one organization that need coordinated code and administration. | A core, plugin or network-level error can affect every site, and sites cannot follow completely independent release schedules. |
| Independent installs, shared database | Each site has separate files and configuration, but installations use one database server or database with unique table prefixes. | Small portfolios needing separate files and settings while keeping database administration simple. | A database failure, credential exposure or destructive query can still affect multiple sites. |
| Independent installs, separate databases | Each site has its own files, configuration, database and database credentials. | Different owners, compliance boundaries, plugin stacks, release calendars or recovery requirements. | More databases, credentials, updates, monitoring and backup jobs must be maintained. |
When Multisite is appropriate
Use Multisite when sites are variations of the same service: for example, regional or departmental sites that share branding and are administered by the same team. Network administrators control the common codebase, and site administrators manage their own content within the permissions allowed by the network. A single plugin or theme update can be rolled out consistently instead of repeated for every installation.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
Multisite does not merge all content. Each site keeps separate post, options and metadata tables and its own uploads area. The user table is shared across the network, so identity and role planning must account for that shared scope. A network-wide plugin or vulnerable component also creates a wider blast radius than an isolated installation.
When independent installations are safer
Choose independent installs when a site needs a different PHP compatibility window, a different plugin set, a separate owner, a separate deployment schedule or a hard boundary around failures. Separate databases and database users make it possible to revoke one site’s credentials without changing the others and to restore one database without overwriting unrelated content.
Independent installs do not require separate physical servers. They can coexist on one VPS or dedicated machine when the web server, filesystem permissions, database credentials and monitoring are carefully separated.
Plan domains, DNS and request routing
Every hostname must resolve to the server and then be mapped by the web server to the correct WordPress codebase. DNS alone does not select a site; the web server uses the requested hostname, usually the HTTP Host header, to choose a virtual host.
Domain-based routing for independent sites
- Create an A or AAAA record for each domain or subdomain, pointing to the server’s public address. If you use a provider’s proxy or load balancer, point DNS to that service and ensure it forwards the original hostname.
- Create one NGINX
serverblock or Apache virtual host per site. Set the matchingserver_nameorServerName/ServerAlias, and give each site its own document root, such as/srv/www/site-a/current. - Enable HTTPS certificates for every hostname. Redirect HTTP to HTTPS only after confirming that WordPress’s home and site URLs, proxy headers and certificate coverage are correct.
- Pass PHP requests to the intended PHP-FPM pool or handler. A wrong socket or document root can expose the wrong site or produce a download prompt instead of executing PHP.
- Test each domain with an HTTP header check and a browser. Confirm that redirects, canonical URLs, media URLs and login cookies remain on the intended hostname.
Domain-based Multisite
A domain-based network can use wildcard subdomains or virtual hosts that send several domains to the same WordPress document root. WordPress then identifies the network site after the web server has delivered the request. Wildcard DNS is convenient for subdomains, but separately branded domains still need their own DNS records, certificate coverage and virtual-host aliases.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
Path-based Multisite
A path-based network uses addresses such as example.com/subsite and avoids separate hostnames. It can simplify DNS and certificates, but paths affect permalink design, migration procedures and assumptions in themes, plugins and cached URLs. Decide on subdomain versus subdirectory structure before publishing content; changing later can require URL rewriting and database search-and-replace work.
Free tools Windows power users keep installed
One-click scans. No signup required.
Build the server in layers
Edge and web server
Terminate TLS at the edge and route hostnames with NGINX or Apache. Keep each site’s document root explicit rather than placing all sites in one writable directory. Disable directory listing, serve only the intended public files and block access to configuration, version-control and backup files. If a reverse proxy or load balancer sits in front, configure trusted proxy headers so WordPress detects HTTPS and the original client address correctly.
PHP execution
Run a PHP version supported by the WordPress release, themes and plugins you actually use. Separate PHP-FPM pools per site when practical. A pool can have its own Unix user, process limits and environment, reducing the chance that one site’s runaway requests consume every PHP worker.
Size workers from measurements rather than site count. Watch active workers, queue time, memory per worker, request duration and 5xx responses during peak traffic. Too many workers can exhaust RAM and trigger swapping; too few create a queue even when the database is idle. Plugin-heavy admin requests and uncached searches usually require more PHP capacity than cached public pages.
Database layer
With independent installs, create a database and least-privilege database user for each site. Grant only the permissions WordPress requires on that database. Shared databases reduce administrative overhead, but separate credentials and databases limit accidental cross-site changes and make per-site restores more predictable.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
For a Multisite network, the database is shared by design. Schedule database backups that include all network tables, and document how to restore one site’s tables and uploads without damaging the rest of the network. Test this procedure on a staging copy rather than assuming a full-database dump provides convenient selective recovery.
Filesystem and identity
Run each independent site as a non-privileged Unix user where possible. Give the web process write access only to directories that need it, normally the uploads directory and carefully selected cache or update paths. Keep configuration files, environment files and private keys outside public document roots or protected by explicit deny rules. Never use a shared writable uploads directory for unrelated sites.
Caching
Put a reverse proxy such as NGINX or Varnish in front of PHP for cacheable pages. A cache hit can return the stored response without reaching PHP or the database, reducing repeated work. Exclude personalized pages, administrator paths, carts, checkout flows and requests carrying login cookies unless the cache configuration explicitly handles them.
Give each hostname a distinct cache key. Purge or bypass the correct site’s cache after publishing, updating menus or changing settings. A shared cache namespace that ignores the host header can serve one site’s HTML on another domain.
Install several independent WordPress sites
The following sequence works whether you use one database server or separate database servers; the database and Unix identities should remain distinct per site.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
- Inventory the site. Record the domain, expected traffic, PHP and plugin requirements, storage growth, email dependencies, administrator contacts, maintenance window and recovery objective.
- Create identities. Make a non-privileged Unix user and group for the site. Create its document root and ensure parent directories do not grant unnecessary write access.
- Create the database. Prefer a dedicated database and user. Generate a unique, stored credential; do not reuse a password from another site. If a shared database is unavoidable, assign a unique table prefix and document it.
- Deploy WordPress files. Place the release in a versioned directory and point a stable
currentsymlink or document root at it. Keep uploads in a persistent location when using release-based deployments. - Configure WordPress. Set database credentials, unique authentication salts, the correct site URL and filesystem paths. Protect
wp-config.phpfrom web downloads and keep secrets out of source-control repositories. - Configure the virtual host. Map the exact hostnames to this document root, pass PHP to the intended handler, enable HTTPS and add security headers and access restrictions appropriate to the site.
- Set permissions. Verify that the site user can write required upload and cache directories but cannot modify another site’s files. Remove temporary installers and disable unneeded write paths.
- Warm and verify caches. Request representative public pages, confirm cache headers and test that logged-in users receive uncached responses.
- Record the deployment. Store DNS, certificate renewal, database, cron, backup and rollback details in an operations runbook.
Create a Multisite network safely
Multisite changes the installation’s configuration and database structure, so take a verified file and database backup before enabling it. Put the site into a maintenance window if visitors could submit content during the change.
- Confirm that the existing installation, plugins and themes support Multisite and that you have administrator access.
- Back up the complete WordPress files, uploads and database, then perform a test restore on a non-production copy.
- Enable the network feature in the configuration as directed by the current WordPress “Create A Network” documentation.
- Use the Network Setup screen to choose subdomains or subdirectories. WordPress will provide configuration directives for the main configuration file and rewrite rules.
- Apply those directives exactly to the correct virtual host and rewrite context. A mismatch between Apache rules and NGINX configuration commonly causes redirect loops or missing permalinks.
- Configure network administrators, allowed themes and plugins, registration rules, upload limits and domain mapping only after the network loads correctly.
- Create a test site, upload media, publish a page and log in as both a network administrator and a site administrator. Verify that users, cookies, uploads and URLs stay within the intended network.
Do not treat Multisite as a substitute for tenant isolation. A network administrator, shared user table or network-enabled plugin can cross normal site boundaries. If one customer must be unable to affect another customer’s code or identity data, use independent installations instead.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Estimate capacity without a misleading site count
WordPress documentation does not publish a universal “sites per server” formula. A server hosting ten mostly cached brochure sites may have more headroom than one hosting a single busy store with uncached searches, background jobs and heavy imports.
Measure the limiting resources
- CPU: sustained utilization, PHP request CPU time and queueing during peak periods.
- Memory: PHP-FPM worker size, database buffers, object cache and operating-system headroom. Swapping is a warning that worker limits are too high for available RAM.
- Storage: uploads, database growth, temporary files, log retention and the extra space required for local backup sets.
- Database: slow queries, lock waits, connection counts, buffer-cache efficiency and replication or backup duration where applicable.
- Network: bandwidth for uncached media, backups, updates and API traffic.
- Concurrency: simultaneous PHP requests, queue length and the percentage of requests served from cache.
Use a repeatable load test
- Clone representative sites to staging, including their largest tables, media patterns and production-like plugins.
- Replay realistic anonymous page views, logged-in actions, searches, form submissions, scheduled jobs and administrator activity.
- Measure p95 and p99 response time, PHP worker saturation, database latency, error rates and memory during a sustained peak, not just a short burst.
- Add sites or traffic in controlled increments until a defined service limit is reached. Keep a safety margin for updates, backups and traffic spikes.
- Repeat after major plugin, PHP, database or caching changes. Capacity is a moving property of the workload, not a permanent number attached to the VPS.
Backups, restores and failure boundaries
Back up both files and databases. Files contain WordPress core, themes, plugins, uploads and configuration; a database-only backup cannot restore media or code, while a files-only backup cannot restore posts, settings and user data.
Choose granularity deliberately
Independent installations with separate databases allow a site-by-site schedule and restore. A full server snapshot is useful for disaster recovery but should not be the only backup, because restoring it may roll back unrelated sites. For Multisite, retain complete network backups and document a selective restore process for one site’s tables and uploads.
Make backups recoverable
- Keep copies off the production host so a disk failure or compromised server cannot erase every copy.
- Encrypt backups and restrict access to the minimum operators who need it.
- Retain several restore points, including one from before major updates or migrations.
- Perform scheduled test restores to an isolated environment. Check front-end pages, media, logins, cron jobs, HTTPS behavior and outbound integrations.
- Write recovery time and recovery point objectives for each site, then ensure backup frequency and storage meet them.
Security and operational controls
Isolation is a combination of identities, permissions and process. Separate Unix users, database credentials, document roots and cache namespaces. Keep WordPress, PHP, themes and plugins current, but stage updates when sites have different compatibility requirements. Remove abandoned plugins and unused administrator accounts.
Collect web-server, PHP, database and authentication logs centrally enough to investigate incidents without allowing one compromised site to erase its own evidence. Monitor certificate expiry, disk space, backup age, failed cron jobs, PHP queues, database errors and unusual login activity. Define who can deploy, who can restore and how emergency access is revoked.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteCommon failures and precise fixes
| Symptom | Likely cause | Checks and remedy |
|---|---|---|
| The wrong site appears for a domain | DNS points elsewhere, or the virtual host/default host is wrong. | Check DNS answers, the hostname in the request, virtual-host ordering and each document root. Test with an explicit host header before changing WordPress URLs. |
| Redirect loop after enabling HTTPS | WordPress does not recognize the original HTTPS connection behind a proxy. | Verify trusted proxy headers and the web-server HTTPS condition. Ensure only one layer performs the canonical HTTP-to-HTTPS redirect. |
| Permalinks return 404 | Rewrite rules were not applied to the selected server or path. | Check Apache rewrite modules and directory context, or add the equivalent NGINX fallback to index.php. Re-save permalinks after confirming the server rule. |
| One site consumes all PHP workers | Uncached traffic, a slow plugin, a loop or a background job is exhausting a shared pool. | Inspect slow requests and queue time, then isolate the site in its own pool, cap workers and fix or disable the offending workload. |
| Restored pages lack images | Uploads were omitted or restored to the wrong path. | Restore the matching uploads directory, verify ownership and URLs, and test media requests from the restored hostname. |
| A cache serves another site’s page | The cache key omits the hostname. | Include the host in the cache key, purge all affected objects and test two domains with identical paths. |
Operational cost is more than the server bill
One Multisite network usually reduces duplicated updates, databases and monitoring objects, which can lower routine administration. That convenience has a shared failure domain: a bad network-level change may require a coordinated rollback.
Independent installs require more patching, certificates, cron definitions, dashboards and backup policies. In exchange, they permit staged upgrades, per-site credentials and narrower restores. The economical design is the one that matches the cost of an outage and the staff time available for maintenance, not simply the one with fewer databases.
Quick Recap
A practical decision rule
- Choose Multisite when one organization owns the sites, users can be shared, code updates should be coordinated and a network-wide failure is acceptable.
- Choose independent installs with separate databases when sites have different owners, compliance needs, plugin stacks, release schedules or recovery objectives.
- Choose independent installs with a shared database service when file and release separation matters but the team can accept a larger database blast radius and additional table-prefix administration.
- Regardless of the model, use explicit hostname routing, least-privilege identities, measured PHP and database limits, cache keys that include the host, monitoring and tested file-plus-database restores.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
