WordPress Multisite makes sense when the sites are alike, one team runs them and they need the same plugins and themes: on our test bench a 10 site network updated 6-10 times faster than 10 separate installs, used ten times fewer inodes and seven times less OPcache memory. Separate installs win when the sites belong to different owners, need different plugins or may move one day: you can pull a site out of a network, but it is manual work with tables, users and upload paths. Below are the numbers, tested nginx configs and a list of what breaks.
How we tested
On 10 November 2026 we built a test bench: an Ubuntu 24.04 container with nginx 1.24, PHP-FPM 8.3, MariaDB 10.11, WP-CLI 2.12, WordPress 7.1.3 updated to 7.1.4 (the latest release on that day) and WooCommerce 11.2.1 updated to 11.2.2. We compared a 10 site Multisite network with 10 separate installs holding identical content (20 posts and one photo per site), tested nginx rules for subdirectory and subdomain networks, mapped a custom domain with a certificate from a local test CA and moved one site out of the network. WordPress and WP-CLI documentation was checked the same day. These are test bench numbers, not RichHost server numbers.
One network or 10 separate sites: bench results
Multisite means one copy of the WordPress files, one database and shared user tables for every site. Each site in the network gets its own set of tables with the prefix wp_2_, wp_3_ and so on, and its media goes to wp-content/uploads/sites/N/. We deployed both setups with the same content and measured what a hosting account usually counts.
| Metric | Network of 10 sites | 10 separate installs |
|---|---|---|
| Database tables: core only / with WooCommerce | 108 / 508 | 120 / 520 |
| Database size (data and indexes): core / with WooCommerce | 6.2 / 29.5 MB | 7.2 / 30.5 MB |
| Site files on disk: core / with WooCommerce | 214 / 286 MB | 1.3 / 2.0 GB |
| Inodes: core / with WooCommerce | 4,311 / 10,842 | 42,111 / 106,341 |
| Core update 7.1.3 to 7.1.4 including database upgrade | 7.6 s | 49.6 s |
| WooCommerce update 11.2.1 to 11.2.2 | 3.1 s | 30.9 s |
| Peak PHP memory per home page request, OPcache 512 MB | 6.1 MB, 23 DB queries | 6.0 MB, 22 DB queries |
| OPcache memory: core / with WooCommerce | 30 / 54 MB | 210 / 449 MB |
| Home page request with WooCommerce, OPcache 128 MB | 12.6 MB, 110 ms | 52.9 MB, 392 ms |
Table counts are almost the same: the network saves only the user tables and adds six of its own (wp_blogs, wp_site, wp_sitemeta and others). A plugin with its own tables multiplies them per site in both setups: WooCommerce added 36-40 tables per site. So “one database is simpler” is about convenience, not size.
Files are where the gap is. One copy of WordPress with the three default themes takes 4,200 inodes, 10,611 with WooCommerce. Ten copies mean ten times the count, and on shared hosting this is often the first resource to run out, see our guide to the inode limit on hosting. Updates multiply too: WP-CLI boots each install separately, so ten core updates took 49.6 seconds against 7.6 for the network.
PHP memory and OPcache: the difference that matters for hosting
A single request is not cheaper in a network: peak memory per page is nearly the same (6.1 MB against 6.0 MB), and the network runs one extra database query to load network settings. The difference is in OPcache, the shared cache of compiled PHP code. The network uses the same 510 files for all ten sites, while ten installs live at different paths, so OPcache stores 4,961 copies of the same code.

As long as everything fits in the cache, speed is the same. We cut OPcache to 128 MB, the PHP default on Ubuntu, and ten installs with WooCommerce no longer fit: peak memory per request grew from 12.5 to 52.9 MB and response time from 118 to 392 ms, because PHP compiled the code again on every request. The network behaved the same at 128 MB as at 512 MB. The provider sets the OPcache size, so on shared hosting you usually cannot change it, and it pays to know such limits in advance, see hidden shared hosting limits.
Subdomains or subdirectories
You choose the network type when you create it, and switching later is not easy. The WordPress documentation (checked 10.11.2026) sets a few hard limits: you cannot create a network if the site address uses a port other than :80 or :443; subdirectories are not offered if the install is more than a month old, because of conflicts with existing permalinks; subdomains are not offered on localhost or an IP address.
| Subdirectories: example.com/shop/ | Subdomains: shop.example.com | |
|---|---|---|
| DNS | Nothing extra | A record per subdomain, or wildcard *.example.com for sites created on demand |
| SSL | One certificate per domain | Wildcard certificate; it covers one level only |
| nginx | Extra rewrite rules required | server_name example.com *.example.com and a plain try_files |
| Login | One address, one set of cookies | Cookies for the whole network domain |
| Existing site older than a month | Not available | Available |
For a subdirectory network the main trap is nginx. Without the extra rules the sites’ home pages load, so the problem is easy to miss, but the dashboard and login break. Here is what the bench returned before and after adding the block from the official WordPress nginx guide:
# server {} of a subdirectory network
location / { try_files $uri $uri/ /index.php?$args; }
if (!-e $request_filename) {
rewrite /wp-admin$ $scheme://$host$request_uri/ permanent;
rewrite ^(/[^/]+)?(/wp-.*) $2 last;
rewrite ^(/[^/]+)?(/.*\.php) $2 last;
}
# without the if block
/site3/ 200
/site3/wp-admin/ 302 -> /site3/wp-admin/ (redirect loop)
/site3/wp-login.php 404
/site3/wp-includes/css/dashicons.min.css 404
# with the if block
/site3/wp-admin/ 302 -> /site3/wp-login.php?redirect_to=...
/site3/wp-login.php 200
/site3/wp-includes/css/dashicons.min.css 200 text/css
A subdomain network works with a plain try_files, but it needs a wildcard DNS record and a wildcard certificate. On the bench blog.net-sub.test loaded with the *.net-sub.test certificate, while curl rejected a.blog.net-sub.test with “no alternative certificate subject name matches target host name”: a wildcard covers one level only. Setup details are in our article on wildcard DNS and wildcard SSL. Two smaller findings: WordPress sends a non-existent subdomain to the signup page wp-signup.php, and wp site create in an HTTPS network created sites with http addresses, which we had to fix by hand.
A custom domain for a network site
Domain mapping has been built into WordPress since 4.5: in Network Admin open Sites, then Edit, and enter the full address in the Site Address (URL) field. The documentation recommends SSL on every domain, served via SNI. On the bench we mapped shop.net-sub.test to myshop.test and hit three problems:
- Until nginx knew the new domain, it served another site’s certificate, so a browser would show a certificate error.
- In a subdomain network WordPress binds cookies to the network domain. Login on
myshop.testfailed with “Cookies are blocked or not supported by your browser”. TheCOOKIE_DOMAINline from the documentation fixed it. - The old address did not redirect to the new one: WordPress sent it to the signup page. We had to add a permanent redirect in nginx.
# map site 3 to its own domain (same as Site Address in Network Admin)
wp db query "UPDATE wp_blogs SET domain='myshop.test' WHERE blog_id=3"
wp --url=https://myshop.test/ search-replace 'https://shop.net-sub.test' 'https://myshop.test'
# Success: Made 5 replacements. (only wp_3_* tables)
# login on myshop.test before the fix
Set-Cookie: wordpress_logged_in_...; path=/; domain=.net-sub.test; secure; HttpOnly
Error: Cookies are blocked or not supported by your browser.
# wp-config.php, after the multisite lines
define( 'COOKIE_DOMAIN', $_SERVER['HTTP_HOST'] ?? '' );
# login again
Set-Cookie: wordpress_logged_in_...; path=/; domain=myshop.test; secure; HttpOnly
/wp-admin/ 200
# nginx: old address to the new domain
server {
listen 443 ssl;
server_name shop.net-sub.test;
return 301 https://myshop.test$request_uri;
}
After the fix, a login on the network’s root domain still works on all its subdomains, but on the mapped domain the admin logs in separately: browsers do not share cookies between different domains.
What breaks in a network
Network-activated plugins
A plugin is installed once per network, so every site runs the same version. An update hits all sites at once, so test it on a WordPress staging site first, not on the live network. On the bench, network activation of WooCommerce created tables only for the main site. The other sites got theirs on the first page load: the first request to site 3 took 2.2 seconds and ran 1,155 database queries, the next one took 0.12 seconds. On a live network, trigger this yourself instead of leaving it to the first visitor.
Upload paths
The main site keeps media in wp-content/uploads/, other sites in wp-content/uploads/sites/N/, and that path is written into the content of every post with an image. When you move, change a domain or pull a site out of the network, these URLs have to be replaced together with the site address.
Backups and restoring one site
A regular network backup holds one database for all sites. Restoring it in full rolls back every site at once. To restore just one, you need its wp_N_ tables (plugin tables included), its users from the shared tables and the uploads/sites/N folder. Plan for this in advance; the general approach is in our guide to website backup on hosting.
Moving a site out of the network: a tested order
We moved site 7 (an editor with access to this site only, a post with an image, a WooCommerce product, a custom tagline) into a standalone install. The commands took about 5.5 seconds, 1.7 of them to copy 197 MB of files. On a real site the time depends on the size of uploads.
# 1. all tables of site 7, plugin tables included
wp db tables --url=http://net-dir.test/site7/ --scope=blog | wc -l # 20
wp db tables --url=http://net-dir.test/site7/ --all-tables-with-prefix 'wp_7_*' | wc -l # 50
wp db export site7.sql --tables=$(wp db tables --url=http://net-dir.test/site7/ --all-tables-with-prefix 'wp_7_*' --format=csv)
# 2. users of this site only, into wp_7_users / wp_7_usermeta
CREATE TABLE standalone7.wp_7_users LIKE ms_dir.wp_users;
INSERT INTO standalone7.wp_7_users SELECT * FROM ms_dir.wp_users
WHERE ID IN (SELECT user_id FROM ms_dir.wp_usermeta WHERE meta_key='wp_7_capabilities');
-- the same for wp_usermeta (WHERE user_id IN ...)
# 3. files: clean core, the same plugins and themes, uploads/sites/7 into uploads
cp -a wp-content/uploads/sites/7/. /srv/www/standalone/wp-content/uploads/
# 4. keep the prefix: wp_7_user_roles and wp_7_capabilities stay valid
wp config create --dbname=standalone7 --dbuser=... --dbpass=... --dbprefix=wp_7_
# 5. addresses and upload paths
wp search-replace 'http://net-dir.test/site7/wp-content/uploads/sites/7/' 'http://extracted.test/wp-content/uploads/' --all-tables-with-prefix
wp search-replace 'http://net-dir.test/site7' 'http://extracted.test' --all-tables-with-prefix
wp search-replace 'wp-content/uploads/sites/7/' 'wp-content/uploads/' --all-tables-with-prefix
# 6. plugins that were network-activated
wp plugin activate woocommerce
# 7. nginx of the network, BEFORE the multisite if block
rewrite ^/site7/wp-content/uploads/sites/7/(.*)$ http://extracted.test/wp-content/uploads/$1 permanent;
rewrite ^/site7(/.*)?$ http://extracted.test$1 permanent;
What broke and what we had to fix:
wp db tables --scope=bloglisted 20 tables instead of 50: plugin tables only show up with--all-tables-with-prefix. Without it WooCommerce would have moved without its orders, sessions and service tables.- WooCommerce was inactive in the standalone install, because WordPress stores network activation in the network settings, not in the site. The product page returned 404 until we activated the plugin.
- The users came with 18 stray role entries for other network sites plus network service fields. We removed them with an SQL query.
- There is no super admin outside a network, so admin rights must come from a regular role on the site.
- A redirect from the old address in a separate
locationdid not work for/site7/wp-...paths: the network rules in theifblock run first. Put the rules at server level, before them. wp site delete 7dropped all 50 site tables and deleted its media files, leaving only an empty folder. Delete the site from the network only after the new copy has passed checks and you have a fresh backup, or use--keep-tables.
For comparison we moved another site with a WXR export and the WordPress Importer plugin. Posts, pages and the product arrived in two seconds, but no media was imported (the importer downloads files from the old address, which was unreachable on the bench, as happens once the old site is switched off). The editor became a subscriber without the old password, the tagline and store settings were lost, links in the content still pointed to the old address, and the WooCommerce product lookup table stayed empty. The table method takes longer to prepare but keeps the whole site.
What it means for hosting
A network saves inodes, disk space, OPcache and update time, but not database size or memory per request. Separate installs are better isolated: a plugin failure, a broken theme or a bad update hits one site, not all of them. RichHost plans have no limit on the number of sites, so both setups are possible without running into a site count limit. Before deploying ten copies, count files and disk usage, and check the RichHost hosting plans.
Decision table
| If | Do |
|---|---|
| Sites of one organisation with the same theme and plugins (branches, departments, regions) | Multisite with subdirectories, if all sites live on one domain |
| Sites of different clients or with different plugin sets | Separate installs |
| Sites must be created on demand with their own subdomains | Subdomain Multisite with wildcard DNS and wildcard SSL |
| A network site needs its own domain | Site Address in Network Admin, a separate certificate via SNI, COOKIE_DOMAIN and a 301 from the old address |
| The existing site is more than a month old and you want subdirectories | Subdomains, or a fresh install with the content moved over |
| The site is being sold, handed to a client or needs a different plugin | Move it out with the table method: all prefixed tables, users, uploads, plugin reactivation |
| The host counts inodes or memory and you run 10 or more sites on the same core | Network: one copy of the files and one copy of the code in OPcache |
| Sites must be restored from backup independently | Separate installs, or per site table backups |
FAQ
Is Multisite faster than separate sites?
Not per request: on the bench peak memory and response time were the same. The network wins when separate installs run out of OPcache: at 128 MB ten WordPress copies with WooCommerce responded 3.5 times slower than the network.
Can different sites in a network use different plugins?
Yes. Only the super admin installs plugins, and site admins activate the ones they need, if the network settings give them the Plugins menu. The plugin version is still one for the whole network, and a network-activated plugin runs on every site.
Do I need a wildcard SSL certificate for a network?
Not for a subdirectory network, one certificate for the domain is enough. For subdomains created on demand, yes, and it covers one level only. Every mapped custom domain needs its own certificate.
How long does it take to move a site out of a network?
On the bench the commands took about 5.5 seconds for a site with 197 MB of files, plus checks of login, media, plugins and redirects. Plan a separate window and do not delete the site from the network until the new copy passes the checks.



