WordPress Multisite: when to use it and when not to

Use WordPress Multisite when one team runs many similar sites that should share a theme, plugins and user accounts, such as regional sites, branches or a network of schools. Do not use it when the sites have different owners, need different plugins or may need to move hosts separately later. In many cases you need neither: one WordPress site with well-structured sections, or separate installs, is simpler to run.

What is WordPress Multisite?

Multisite is a mode built into WordPress. You switch it on in the configuration (the official guide to creating a network walks through the steps), and a single installation becomes a network. Each site in the network has its own content, media and settings, but they all share:

• WordPress core, so every site updates at once.
• The themes and plugins installed on the network. A network admin installs them, and each site activates what it is allowed to use.
• One user table, so a person can have accounts on several sites with one login.
• One server, one database and one set of backups.

Sites can sit on subdomains, in subdirectories, or on their own mapped domains, which WordPress supports natively (domain mapping documentation).

When is Multisite the right choice?

When the sites are siblings. Multisite pays off when you have many sites that look and behave alike and are run by the same people:

• A franchise or chain with one site per branch.
• A university or school group with a site per department.
• A publisher running regional editions.
• An agency platform where every client site is built from the same theme and plugin set.

In each case, one update, one security policy and one backup routine cover every site. That is the real benefit.

How do roles and plugins work in a Multisite network?

Multisite adds a role above Administrator. The Super Admin controls the whole network from the Network Admin screens: creating sites, installing themes and plugins, and managing every user. A site Administrator in a network has less power than on a normal install. They cannot install plugins or themes, and by default they cannot post unfiltered HTML, so embed codes and scripts pasted into content can be stripped unless a Super Admin handles them.

Plugins can be switched on in two ways:

• Network activation turns a plugin on for every site at once, and site admins cannot turn it off. Use it for things every site must have, such as security, caching or SEO plugins.
• Per-site activation installs the plugin on the network but leaves each site to activate it. Site admins only see the Plugins menu if the Super Admin allows it in Network Settings.

Themes work the same way: a theme must be network-enabled before sites can use it, or enabled for one site at a time.

That central control is the point of Multisite for a chain or a school group. It is also why it frustrates teams that want each site to choose its own tools.

When should you avoid Multisite?

The warning signs are all about independence:

• Different owners. If a site may be sold, handed to another agency or moved, separating it from a network later is real work.
• Different plugins. Every plugin sits on the shared install. A heavy shop plugin needed by one site is installed for all of them.
• Plugin compatibility. Some plugins do not support Multisite properly. Check every plugin you rely on before committing.
• Shared risk. A bad update or a compromised plugin can affect every site in the network.
• Hosting limits. All the sites share one server, so one busy site can slow the others.

What hosting does a Multisite network need?

More than a single site of the same size, mainly because everything shares one server and one database.

• Database size. Each new site adds around ten tables of its own, with a numbered prefix such as wp_2_posts. Fifty sites means hundreds of tables in one database, so backups and restores take longer.
• PHP memory. WordPress sets a default memory limit of 64 MB for Multisite instead of 40 MB for a single site (wp-config.php documentation). Busy networks running page builders or WooCommerce usually need much more, set through WP_MEMORY_LIMIT and the server's own PHP limit.
• Caching. A persistent object cache such as Redis and full-page caching matter more, because one slow query can hold up every site.
• DNS and SSL. Subdomain networks need wildcard DNS and a wildcard certificate. Mapped domains need a certificate for each domain.
• Host support. Some budget and managed hosts restrict Multisite or charge more for it. Ask before you buy.

Related guide: Headless WordPress with Next.js: when is it worth it?

What are the alternatives to Multisite?

For a sub-brand or event run by the same small team, the last two rows are usually simpler than a network.

Related guide: How much does a Next.js website cost vs WordPress?

How have I handled sub-brands and events without Multisite?

• A sub-brand as a section. For IPL Biologicals, the Grow Organic sub-brand was added as new pages inside the existing WooCommerce site, as part of the monthly maintenance retainer I run for them. No second install and no network.
• Events inside the main site. On Ravens Ait, the venue's 20+ event pages live inside the main WordPress site on Bricks Builder, with Stripe bookings and HubSpot forms, rather than as separate microsites.
• Two brands, one admin. As a general pattern, a small business with a community brand and a founder's personal brand can often run both from one WordPress site, with the second domain pointing at its own section. That keeps one login and one set of updates.

How do you move a site out of a Multisite network later?

It can be done, but it is a project, not a button. A subsite's content lives in its own numbered tables, but its users sit in the network's shared user tables and its media sits in a numbered folder under wp-content/uploads/sites/. Extracting it usually means:

1. Setting up a fresh single WordPress install on the new host with the same theme and plugins.
2. Exporting the subsite's content with the built-in export tool and importing it, or copying the subsite's tables and renaming the prefix if you need settings and plugin data too.
3. Copying the media from the subsite's numbered uploads folder into the new uploads folder, then running a search and replace on the database so old file paths and URLs point to the new ones.
4. Remapping users. On import, WordPress asks you to assign each author to a user on the new site. For a database copy, you have to copy the right rows from the shared users and usermeta tables and rename their role keys.
5. Re-entering plugin licences, redirecting the old address and checking forms, emails and tracking.

Some migration plugins sell a network extension that automates part of this, but test the result carefully. This is the main reason I advise against Multisite when a site might leave.

Do plugin licences cost more on Multisite?

Often, yes. Many premium plugins, page builders and themes price by the number of sites, and vendors count network subsites differently. Some treat a whole network as one site, some count every subsite, and some count only subsites with their own mapped domain. Twenty subsites can push you from a single-site licence to an agency or unlimited tier. Read each licence before you build, and budget for the renewal cost across the whole network, not only the hosting saving.

What should you check before switching on Multisite?

1. 1

   List the sites and their owners

   Who edits each one, who pays for it, and who might take it elsewhere.

2. 2

   Compare plugin lists

   If the sites need very different plugins, Multisite adds weight to all of them.

3. 3

   Check plugin support

   Confirm every essential plugin works on a network, including licences that count sites.

4. 4

   Choose the address structure

   Subdomains, subdirectories or mapped domains. Mapped domains need SSL for each.

5. 5

   Plan backups and restores

   Decide how you would restore one site without rolling back the others.

6. 6

   Test on staging

   Build two sites in a staging network and run updates before going live.

How should you decide?

Write down who runs each site and what each one needs, then pick the simplest structure that fits. If you are weighing WordPress against other platforms entirely, see Next.js or WordPress for a marketing site. For moving or consolidating existing sites, my hosting migrations and maintenance service covers it, and the free Tech Stack Advisor gives you a first recommendation in seconds. Send me the list of sites through my contact page, or book a 20-minute call, and I will reply with a plan.