Setup & site building · Explainer
When Multisite Makes Sense (And When It Doesn't)
Short answer
WordPress Multisite runs several sites from one installation, sharing core files, plugins and themes while each site keeps its own content, media folder and database tables. It makes sense when one team runs related sites with the same toolset, such as university departments or franchise locations. It is the wrong choice when sites need different plugins, different owners or a future move apart.
Key takeaways
- Multisite runs several sites from one WordPress installation, in core since version 3.0.
- All sites share core files, plugins and themes, but each keeps its own content, media folder and database tables.
- Subdomain and subdirectory address types cannot be changed later, so choose before installing.
- A subdirectory install is blocked when the existing site is more than a month old.
- Multisite fits one team running related sites with the same toolset, not client sites that may leave.
What is WordPress Multisite?
WordPress Multisite is a core feature that runs several sites from one WordPress installation.
The Advanced Administration Handbook describes a network as several instances of WordPress managed within one installation.
All the sites share the same core files, and they can share plugins and themes. Each site is virtual: it has no directory of its own on the server, but it does have its own media folder and its own tables in the database.
Multisite has been part of WordPress core since version 3.0, according to the WordPress.org Network screen documentation. A network is run by a super admin, who manages every site from a Network Admin dashboard. Each site still has its own dashboard, its own content and its own users, with roles set per site.
The best-known example is WordPress.com itself. The handbook notes that the sites in a network are separate, much like the separate blogs on WordPress.com. One install, many sites, each with its own address and content.
When does Multisite make sense?
Multisite makes sense when one team runs several related sites that share the same tools.
Universities are the classic case: each department gets its own site, while the IT team updates core, plugins and themes once for all of them. The same shape fits franchises, where each location gets a site with the same design and plugins, and regional sites that share branding but publish their own content.
It also fits sites that share users. One account can belong to several sites in the network, with a different role on each. That saves the team from creating and managing the same accounts again and again.
The deciding question is whether the sites share a toolset. If every site needs the same plugins and the same theme framework, one network update covers them all. If each site needs different plugins, the shared install buys little and costs flexibility.
Choose hosting that supports a network before you commit to one.
When should you avoid Multisite?
Avoid Multisite when the sites need different plugins, different owners or a future move apart.
The handbook warns that the sites in a network are not interconnected, even though plugins can add links between them.
If your sites share data or share users as one product, the handbook says a network might not be the best solution. A single site with plugins that switch themes or capabilities often does that job better.
Client sites are a poor fit. A client who later wants their site moved to their own host, sold or handed to another owner faces a hard migration out of a network. Separate installs move cleanly, while a network site has to be untangled from shared tables and shared files.
Traffic differences also argue against it. Sites in a network share one install, so a traffic spike or a bad plugin on one site can slow or break the rest, since every site runs the same code.
Shared hosting may not give you the control a network needs, so check when an upgrade makes sense.
How do subdomain and subdirectory networks differ?
A network gives each site either a subdomain address or a path address, and the choice is hard to undo.
A subdomain network uses addresses such as site1.example.com and site2.example.com. A subdirectory network uses paths such as example.com/site1 and example.com/site2. The WordPress.org Network screen documentation states the rule plainly: you cannot change this later.
Subdomain networks need wildcard DNS. The handbook explains that a domain-based network maps different domain names to the same directory, and on-demand subdomain sites need wildcard subdomains configured in DNS.
A wildcard DNS record uses * as the leftmost label, such as *.example.com, so new subdomains resolve without a separate record each time. You can also map fully separate domains, such as example1.com, onto network sites, although the handbook suggests a plugin for that.
Subdirectory networks are simpler to set up, since they need no wildcard DNS. The catch is age: you cannot choose a subdirectory install if the existing WordPress installation is more than a month old, because of conflicts with existing permalinks. That rule comes from the handbook page “Before You Create A Network”.
| Network type | Site address | Needs wildcard DNS | Best for |
|---|---|---|---|
| Subdomain | site1.example.com | Yes, for on-demand sites | Separate brands or regions |
| Subdirectory | example.com/site1 | No | Departments under one domain |
| Domain mapped | example1.com | Depends on the setup | Sites that need their own domain |
What do you need before you create a network?
You need file access, a backup, pretty permalinks and a host that allows the setup.
The handbook states that you must be the administrator of a WordPress installation, and you normally need access to the server file system to edit files.
You also need to make sure the server can use the more complex rewrite rules Multisite requires. On Apache, that means mod_rewrite loaded, .htaccess support and the right AllowOverride setting.
Back up first.
The “Create A Network” guide warns that your existing site will be updated when the network is created, and it tells you to back up your database and files unless the install is fresh.
Confirm pretty permalinks already work, and deactivate all plugins before you start, since you can turn them back on after the network exists.
Check the limits too.
You cannot create a network if the WordPress address uses a port other than 80 or 443.
You cannot choose a subdomain install if the WordPress address has a path in it, is localhost or is an IP address such as 127.0.0.1. Shared hosting may block some of these steps, so confirm with the host first.
Pointing a domain at hosting is a separate job from creating the network, so plan the DNS step early.
How do you create a network?
Creating a network takes six steps, and WordPress prints the exact code to add.
First, back up the database and files, and confirm pretty permalinks work. Second, deactivate all active plugins. Third, open wp-config.php and add one line above the line that says “That is all, stop editing!”:
define( 'WP_ALLOW_MULTISITE', true );
Fourth, refresh the dashboard and open “Tools” then “Network Setup”.
Choose subdomains or subdirectories, enter the network title and the admin email, and click “Install”.
Fifth, back up wp-config.php and .htaccess, then add the lines WordPress shows you to each file. Sixth, log in again.
After login, “My Sites” appears in the toolbar, with a Network Admin menu beside it.
The handbook notes that your account is now the super admin, and the Network Admin screen is where you add sites and enable themes and plugins.
Add sites under “Network Admin” then “Sites” then “Add New”, and enable themes and plugins for the network before each site can use them.
How is running a network different day to day?
A network adds one dashboard above the sites, and it changes how updates and plugins work.
The Network Admin dashboard manages the whole network: sites, users, themes, plugins and settings. Each site keeps its own dashboard for its own content, menus and settings. A super admin can edit any site, while a site administrator only controls their own site.
Plugins and themes behave differently in a network.
The “Create A Network” guide explains that each site can activate a theme or plugin, but it cannot install one.
Only the super admin installs code, and network activation makes a plugin run on every site. That keeps the toolset consistent, but it also means one bad plugin affects every site at once.
Updates are faster and riskier at the same time. One core update covers every site, which saves hours on a large network. The same update can also break every site at once, so the network needs a staging copy and a tested backup before each update round.
Rehearse updates and restores on a staging copy before you touch the live network.
How do you check whether Multisite fits your site?
Run through five questions, and choose Multisite only when all five answers are yes.
- Does one team maintain every site?
- Do the sites need the same plugins and the same theme framework?
- Will no site ever need to leave the network, be sold or move to another host?
- Does the host support Multisite, including wildcard DNS and rewrite rules?
- Can you accept that one bad plugin or one failed update affects every site at once?
Hosting support is a real constraint.
Kinsta's multisite documentation states that multisite needs a Single 65k visits plan, a Single 40GB bandwidth plan, a Build plan or above, and that sites on the Single 35k visits plan must upgrade.
Kinsta counts a multisite with any number of subsites as one install, since all the subsites share the same core files and database.
If any answer is no, separate installs are the safer choice. Tools that manage many separate sites from one dashboard give most of the convenience without the shared fate. A network is the right tool when the sites are truly one family, run by one team, for the long term.
What mistakes should you avoid?
The most common mistakes are picking the wrong address type, skipping the backup and converting a live site without a rehearsal.
First, do not rush the subdomain or subdirectory choice. The Network screen documentation says you cannot change it later, and switching after sites exist means changing every site address. Decide with the team before you click “Install”, and write the choice down.
Second, do not convert a site that is more than a month old and expect the subdirectory option. WordPress blocks it because new site paths can collide with existing post and page addresses. Plan the address type around the age of the site, not around preference alone.
Third, never create a network on a live site without a tested backup. The conversion edits wp-config.php, .htaccess and the database, and a mistake there can lock you out of the dashboard. Rehearse on a staging copy first, and keep the backup where you can reach it.
Fourth, do not network-activate a plugin for every site when only one site needs it. Each site should activate only the plugins it uses, so a fault in one plugin stays as small as possible.
Frequently asked questions
How many sites can a Multisite network hold?
Yes. A network can hold any number of sites, from two to hundreds, and WordPress.com itself runs on Multisite. The limit is your server, not WordPress, so watch database size, traffic and the number of plugins as the network grows.
Can I move one site out of a Multisite network later?
It is hard work. A site has to be untangled from shared tables and shared files, and its users, media and settings moved by hand or with a migration plugin. If a site may leave one day, start it as a separate install instead.
Do sites in a network share content with each other?
No. Each site has its own content, media folder and database tables, and its own dashboard. Only the core files, the installed plugins and themes, and the user accounts are shared across the network.
How do plugins work on Multisite?
Each site activates the plugins it needs, and only the super admin can install new ones. Network activation switches a plugin on for every site at once. Use that only for plugins every site truly needs, such as a security plugin.
What is the difference between subdomain and subdirectory Multisite?
A subdomain network uses addresses such as site1.example.com, while a subdirectory network uses paths such as example.com/site1. Subdomains need wildcard DNS; subdirectories do not. You cannot change the choice later.
Can I run Multisite on shared hosting?
Yes, if the host allows it and the plan covers it. Some hosts only support Multisite on higher plans, and some shared hosts block the wildcard DNS or rewrite rules it needs. Confirm support with the host before you start.
Sources
- Create A Network WordPress Developer Resources
- Before You Create A Network WordPress Developer Resources
- Tools Network screen WordPress.org
- Get Started - Multisite Network Kinsta
- Wildcard DNS record Wikipedia
- WordPress 7.1.4 WordPress.org
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
