WordPress Multisite: what it is, when it fits and what to watch for (2026)

What WordPress Multisite is

WordPress Multisite is a feature built into WordPress that runs a network of sites from one installation. WordPress.org’s Multisite handbook says it “enables you to create several instances of WordPress managed within one installation.” Each site gets its own database tables for posts and settings, and “only the user table is shared.”

You get one set of WordPress files, one set of plugins and themes, and one login area for a “super admin” who controls the whole network. Sites can live at subdirectories (example.com/boston/) or at subdomains and separate domains (boston.example.com or bostonexample.com). Domain mapping has been built in since WordPress 4.5.

It costs nothing extra, since it is part of WordPress. What it costs you is flexibility, and that is the trade to understand before you turn it on.

When multisite fits, and when it doesn’t

WordPress.org’s handbook gives the example of a business with regional sites that share a theme and plugins but publish different content. Typical fits:

• A franchise or company with one site per location, all on the same design.
• A school or university with a site per department.
• A brand with separate regional sites that one team manages.

It is a poor fit for a set of unrelated sites. WordPress.org’s Before You Create A Network page says: “If you plan on creating sites that are strongly interconnected, that share data, or share users, then a multisite network might not be the best solution.” WP Engine’s multisite guide adds that it isn’t a good fit for unrelated sites or sites with different designs, and advises staying with a single site when unsure.

A quick test: if you would ever sell one of the sites, hand it to a different owner, or give it a different look and plugin set, keep it as its own install.

For a site in two languages, a multilingual plugin on one site is usually simpler than a site per language. Our multilingual website guide compares those plugins.

What your hosting needs

• Rewrites turned on. The handbook says “You need to have rewrites enabled to use multisite.” On Apache that means mod_rewrite and .htaccess support.
• File access. You normally need FTP or a file manager like cPanel’s to edit wp-config.php and .htaccess. Our cPanel guide covers the file manager.
• Wildcard DNS for subdomain networks where sites are created on demand.
• A host that allows it. Plans differ. At WP Engine, for example, multisite is included on Premium plans, sold as an extension on shared Growth plans and above, and “cannot be purchased for Lite or Startup plans.”

There are setup limits too. WordPress won’t offer a subdirectory network if your existing install has been running for more than a month, and a subdomain network can’t run on localhost or an IP address. Ask your web hosting company before you start. Our web hosting comparison lists the hosts we cover.

How to create a network

The steps from WordPress.org’s Create A Network page:

1. Make a full backup of files and database, and confirm pretty permalinks work.
2. Deactivate all plugins. You can turn them back on afterward.
3. Add the line define( ‘WP_ALLOW_MULTISITE’, true ); to wp-config.php, above the line that says to stop editing.
4. Go to Tools, then Network Setup, and choose subdomains or subdirectories.
5. Back up wp-config.php and .htaccess, then add the lines WordPress shows you to wp-config.php and use its .htaccess lines in place of the existing WordPress rules.
6. Log in again. Your account is now the super admin, and the Network Admin screen is under My Sites.

Choose subdomains or subdirectories carefully. WordPress.org says switching later “might not be easy.”

Plugin and backup caveats

This is where most multisite surprises come from.

• Not every plugin works. The network administration page says “Not all plugins in the repository will work in a Multisite environment.” Check each plugin’s page before you rely on it.
• Only the super admin installs plugins and themes. “Site admins cannot install new themes or plugins.” That is good for control and frustrating for a client who wants to try a plugin.
• One update reaches every site. A network-activated plugin runs everywhere, so a bad update can break the whole network at once.
• Licenses may count every subsite. WP Engine warns that many premium plugins and themes treat each subsite as a separate activation. Complianz, for example, includes its multisite plugin only in its $399-a-year Agency plan.
• Backups need multisite support. UpdraftPlus presents multisite as a Premium feature, “from as little as $70,” per its feature page; its pricing page lists the Personal plan at $70 a year for 2 sites; it backs up the whole network and can restore one subsite, but can’t export a subsite as a standalone site. Jetpack says “Jetpack Backup and Jetpack Scan do not support multisite WordPress,” per its support page. Our WordPress backup plugins guide compares the options.
• Heavy plugins strain one server. The free Matomo analytics plugin, for one, recommends its On-Premise or Cloud versions for large multisite networks.

What it costs over 3 years

Multisite itself is free. The costs show up in two places: your host’s plan rules and plugin licenses. Two examples for a 10-site setup, from the vendors’ own pages:

UpdraftPlus Premium is $70 a year on its Personal plan (2 sites), but its pricing page doesn’t say how a multisite network counts against site licenses, so check before you budget. The pattern is the useful part: a network rarely saves money on plugins, and it can cost more when a tool needs its multisite edition.

Leaving multisite later

Getting a site out of a network is harder than putting one in. WordPress.org documents how to move sites into a network, but the handbook pages we read don’t describe a way to split one back out. WP Engine says its Copy Environment tool can’t move a single subsite, so you use WordPress’s export and import tools and then reinstall plugins and themes by hand. Before you build, decide whether any site might need to leave. That is the same question we ask of every builder, and our leaving your website builder guide covers what usually gets lost in a move.

Alternatives to multisite

The free MainWP Dashboard runs on your own WordPress site and manages updates, backups and reports for separate installs; MainWP says it “is 100% FREE and always will be,” with paid Pro add-ons. ManageWP says its core is “Free on unlimited websites, forever,” including a monthly cloud backup, with a paid backup add-on billed per website.

We build on WordPress every week, and for most small businesses with a handful of sites, separate installs plus a dashboard tool are easier to back up, move and sell than a network. Multisite earns its place when you truly run many similar sites under one owner.

What to do next

• Pick a backup plugin that supports your setup in our backup plugins guide, and read what website backups should cover.
• Check your host’s plan rules; see WP Engine and the other hosts in our hosting hub.
• Going multilingual instead? Start with the multilingual website guide.