Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Explainers · Explainer

What Is WordPress Multisite? A Plain Explanation

What Is WordPress Multisite? A Plain Explanation

Short answer

WordPress Multisite is a built-in feature that runs many WordPress sites from one install. All sites share the same WordPress files, themes, and plugins, while each site keeps its own content, media, and database tables. A Super Admin manages the whole network from one login, and it has been part of WordPress since version 3.0 in 2010.

Key takeaways

  • Multisite runs many WordPress sites from one install, with one login for the network.
  • Sites share core files, themes, and plugins, but keep their own content and tables.
  • Only the user table is shared between sites in a network.
  • Sites use subdomains, subdirectories, or mapped domains for their addresses.
  • A Super Admin manages the network; site admins manage one site each.

What is WordPress Multisite?

WordPress Multisite is a built-in feature that runs many WordPress sites from one WordPress install.

The WordPress developer handbook defines it plainly: Multisite "enables you to create several instances of WordPress managed within one installation" (Developer handbook). Each site in the network is called a subsite, and the network admin manages all of them from one login.

Multisite is not a plugin and not a separate product. Every WordPress install already contains it, and it stays dormant until you switch it on. It has been part of WordPress since version 3.0, released in 2010, when the WordPress Multiuser project was merged into core.

One install, one set of core files, and one dashboard for the whole network: that is the whole idea. The sites share the code and differ in content, design, and settings.

How does Multisite work?

All sites in a network share the same WordPress files, themes, and plugins, while each site keeps its own content.

The Learn WordPress lesson on Multisite explains that each subsite “can have its own look, feel, and content” while all subsites “share the same themes and plugins” (Learn WordPress). Each subsite also has its own media directory and its own database tables, so one site's posts do not appear on another.

The database is shared in one way only: the handbook states that content has its own tables per site and “only the user table is shared between the instances” (Developer handbook). A user can therefore exist once in the network and hold different roles on different sites.

Updates work the same way. When you update WordPress core, a theme, or a plugin, every site in the network gets the update at once, since they all use the same files.

Should sites use subdomains or subdirectories?

Each site in a network gets its own address, either as a subdomain such as “site1.example.com” or as a path such as “example.com/site1”.

The developer handbook says you can build a network that "works with subdirectories ('path-based') or use domains or subdomains ('domain-based')" (Developer handbook). The “Before You Create A Network” page gives the same two patterns: “site1.example.com” and “site2.example.com” for subdomains, and “example.com/site1” and “example.com/site2” for paths (Developer handbook).

ChoiceExample addressWhat it needs
Subdirectoriesexample.com/site1Rewrite rules; no extra DNS
Subdomainssite1.example.comDNS record per site, or a wildcard record
Mapped domainsshop.example.netDomain mapping setup per site

Subdirectories are simpler to start: one domain, one certificate, and no DNS work. Subdomains give each site a clearer identity and make it easier to move a site to its own domain later.

You choose the structure when you create the network, and changing it later is a migration, not a setting. The handbook also notes that a subdomain install needs WordPress installed in the root of the web path (Developer handbook).

What is a Super Admin?

A Super Admin is the network administrator, the one role that manages the whole network instead of a single site.

Multisite adds this role above the normal Administrator role. The Learn WordPress lesson states plainly: "The Super Admin or Network Admin manages the entire network of sites" (Learn WordPress). Only a Super Admin can add or delete sites, install or delete themes and plugins for the network, and change network settings.

A normal site admin manages one subsite only. They can write posts, change their site's settings, and use the themes and plugins the Super Admin has made available, but they cannot install new plugins or themes for the network.

On a network that lets users create their own sites, the Super Admin also sets the rules for who can create a site. The handbook notes you can allow users to create their own sites or set the network so only admins can create them.

When should you use Multisite?

Multisite fits when you run several sites that share themes, plugins, and updates, and each site needs its own content.

The handbook gives business sites as an example: sites "that share some resources, such as the theme or plugins, and have different content for their regions" (Developer handbook). A company with a site per country, a university with a site per department, and a school district with a site per school all match that pattern.

Other good fits are a network of blogs on one topic, a chain of shops with one site per branch, and a test network where each subsite is a separate demo. In each case, one update covers every site, and one login reaches the whole network.

Multisite also helps when the sites must share users. Since the user table is shared, a person can log in once and work on each site where they hold a role, without a separate account per site.

If your sites share a host and a team, check how much server room the network needs with our guide on how much RAM WordPress needs.

When should you avoid Multisite?

Avoid Multisite when your sites need to share content or data with each other, since each site in a network stays separate.

The handbook warns: "The sites in a multisite network are separate, very much like the separate blogs at WordPress.com. They are not interconnected like things in other kinds of networks" (Developer handbook). If your sites must share posts, products, or users in close sync, Multisite is likely the wrong tool.

The handbook compares network sites to the separate blogs at WordPress.com, which run as separate sites in the same style of network.

Also avoid it when the sites have nothing in common. If each site needs different plugins, different themes, and different update times, separate installs give each site its own pace. A shared network forces shared updates on all of them.

The handbook adds a practical test: if all you want is for different page collections to look very different, you can probably do that in a single site with a plugin that switches themes or templates (Developer handbook). Multisite is for separate sites, not for varied page designs.

Traffic is another factor: a traffic spike on one subsite can slow the whole network, since they share one install and one database. Our guide on how much traffic WordPress can handle helps you size the hosting first.

What do you need before you create a network?

You need to be the administrator of a WordPress install, with file access, working permalinks, and a backup.

The handbook says you must have rewrites enabled to use Multisite (Developer handbook). Pretty permalinks must work before you start, since the network adds more rewrite rules on top of them.

Back up the full site first: files, the database, “wp-config.php”, and the “.htaccess” file if your server uses Apache. Creating a network edits those files, so a backup is your way back if a step fails.

Check the server too. A subdomain network needs DNS records for each subdomain or a wildcard record, and a host that routes those names to your install. Our guide on whether you need a VPS for WordPress covers the hosting side.

Server capacity matters as well: our guide on how many PHP workers WordPress needs covers the capacity a busy network needs.

Search the Plugin Directory for “multisite” to find plugins that add network tools, such as extra admin screens and user management.

Deactivate plugins before you run Network Setup, then switch them back on one at a time after the network exists. That way a single bad plugin cannot block the setup, and you can spot the problem plugin fast.

How do you turn on Multisite?

Turning on Multisite takes two stages: enable the feature in “wp-config.php”, then run Network Setup in the dashboard.

First, open “wp-config.php” in the root of your WordPress install and add this line above the “That is all, stop editing” comment:

define( 'WP_ALLOW_MULTISITE', true );

The Learn WordPress setup lesson gives this exact step: edit “wp-config.php” and define the PHP constant “WP_ALLOW_MULTISITE” as true (Learn WordPress).

Second, refresh the dashboard and open “Tools”, then “Network Setup”. Pick subdomains or subdirectories, enter a network title and the admin email, and WordPress shows the code to add to “wp-config.php” and “.htaccess”. Paste both blocks, save, and log in again.

Adding only the first constant does not finish the job: the network exists only after Network Setup writes its code and you log back in. After that, a “Network Admin” menu appears in the admin bar for Super Admins.

How do you check if a site is part of a network?

Look for a “Network Admin” menu in the admin bar, or check the dashboard for a “My Sites” list.

When you log in as a Super Admin, the admin bar at the top shows “My Sites” and a “Network Admin” link. That menu appears only on a Multisite install, so its presence confirms the network.

In the dashboard, go to “Network Admin”, then “Sites”, to see the full list of subsites with their addresses and user counts. Each row is one site in the network.

From the outside, a subdomain network is easy to spot: several sites share one domain, such as “paris.example.com” and “tokyo.example.com”. A subdirectory network looks like one site with many sections, so only the dashboard or the page source can confirm it.

What are common myths about Multisite?

The first myth is that Multisite links sites together so they share content.

They do not. The handbook is clear that the sites are separate, and plugins are needed to create any links between them (Developer handbook). Each subsite has its own tables and media, and content stays where it was written.

The second myth is that each subsite needs its own WordPress install. It does not: one install serves the whole network, and one core update covers every site.

The third myth is that site admins can install plugins. They cannot. Only the Super Admin installs and deletes themes and plugins for the network, and site admins use what is made available to them.

The fourth myth is that Multisite saves hosting on every setup. It saves update work and admin time, but the network still needs enough server room for all its sites at once. Our guide on free versus premium WordPress plugins explains the shared plugin list each subsite draws from.

What mistakes should you avoid?

The most common mistake is creating a network before deciding how site addresses should work.

  • Pick subdomains or subdirectories before you run Network Setup, since changing the structure later is a migration.
  • Back up files and the database first, and confirm the backup restores, before you edit “wp-config.php”.
  • Do not turn on Multisite on a live site without deactivating plugins first, since a plugin can break the setup screen.
  • Do not promise shared content between subsites, since the handbook states the sites are separate and only the user table is shared (Developer handbook).
  • Keep the network updated as one unit, and check the server capacity before you add many sites at once.

Frequently asked questions

When should I use WordPress Multisite?

Use Multisite when you run several sites that share themes, plugins, and updates, and each site needs its own content. Good fits are a company with a site per country, a university with a site per department, and a network of blogs on one topic. One update then covers every site, and one login reaches the whole network.

Can subsites in a network share content with each other?

No, not by default. The developer handbook states that the sites in a network are separate, very much like the separate blogs at WordPress.com, and they are not linked like things in other kinds of networks. Each subsite has its own tables and media, so content stays where it was written unless a plugin links the sites.

Do I need a plugin to use Multisite?

No. Multisite is a built-in WordPress feature, not a plugin, and it has been part of WordPress since version 3.0 in 2010. Every install already contains it, and it stays dormant until you switch it on by adding a line to wp-config.php and running Network Setup in the dashboard.

How do I turn on Multisite?

Add define( 'WP_ALLOW_MULTISITE', true ); to wp-config.php above the stop-editing comment, then refresh the dashboard and open Tools, then Network Setup. Pick subdomains or subdirectories, enter a network title and admin email, and paste the code WordPress shows into wp-config.php and .htaccess. Then log in again.

Does each subsite need its own hosting?

No. All subsites share one WordPress install, one set of files, and one database, so they share the hosting too. That is the point of a network: one update covers every site. The trade-off is that a traffic spike on one subsite can slow the whole network, so size the hosting for all sites together.

Sources

  1. WordPress Multisite / Network Developer.WordPress.org
  2. Before You Create A Network Developer.WordPress.org
  3. What is WordPress Multisite? Learn WordPress
  4. Setting up a WordPress multisite network Learn WordPress

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.

About the editors

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.