WordPress Multisite: What It Is, When to Use It, and How to Set It Up

WordPress Multisite lets you run multiple WordPress sites from a single installation. Instead of managing 10 separate WordPress installs with 10 separate dashboards, logins, and update cycles, you manage everything from one place. It's powerful when used correctly and a headache when used for the wrong reasons.

Here's what Multisite actually does, when it makes sense, and how to set it up properly.

How WordPress Multisite Works

A standard WordPress installation runs one site. When you enable Multisite, that installation becomes a network capable of hosting many sites. All sites in the network share:

One set of WordPress core files. Updates apply to every site at once.
One database (with separate tables per site). Each site gets its own posts, pages, and settings, but they all live in the same database.
One plugin and theme directory. The network admin decides which plugins and themes are available. Individual site admins can activate what they need from the approved list.
Centralized user management. Users can be members of multiple sites with different roles on each.

Sites in the network can use subdomains (site1.example.com, site2.example.com) or subdirectories (example.com/site1, example.com/site2). You choose during setup.

When Multisite Makes Sense

Multisite is the right choice in specific scenarios:

University or school networks. Each department or faculty gets their own site, but IT manages one installation.
Corporate intranets. Different departments need separate sites with shared branding and user accounts.
Franchise businesses. Each location gets a site with the same theme and plugins, but unique content.
Agencies managing client sites. If all clients use the same stack, Multisite centralizes management. (But read the "when not to use it" section below.)
Multilingual sites. Some teams use Multisite to run separate language versions of the same site, though plugins like WPML or Polylang are often simpler.

When Multisite Is the Wrong Choice

Multisite creates tight coupling between sites. That's efficient when sites are related, but problematic when they're not.

Unrelated sites with different needs. If each site needs different plugins, different themes, or different PHP versions, Multisite adds friction instead of removing it.
Sites with different traffic patterns. One viral site in the network can slow down every other site because they share resources.
Client sites you'll eventually transfer. Extracting a single site from a Multisite network is painful. If a client might leave, keep their site separate from the start.
Sites that need independent scaling. You can't put one Multisite site on a bigger server while keeping others on a smaller one. They all run on the same infrastructure.

If you're unsure, err on the side of separate installations. Individual WordPress sites are easier to migrate, troubleshoot, and scale independently.

Setting Up WordPress Multisite

Before you start, make sure you have:

A fresh WordPress installation (Multisite is much easier to enable on a new install)
FTP or file manager access to edit wp-config.php and .htaccess
A hosting plan with enough resources. Multisite uses more memory per request than a standard install. At least 256MB PHP memory limit is recommended.

Step 1: Enable Multisite in wp-config.php

Add this line to your wp-config.php file, above the line that says "That's all, stop editing!":

define( 'WP_ALLOW_MULTISITE', true );

Save the file and refresh your WordPress admin. You'll now see a "Network Setup" option under the Tools menu.

Step 2: Run Network Setup

Go to Tools > Network Setup. Choose between subdomains and subdirectories:

Subdomains require a wildcard DNS record (*.yourdomain.com pointing to your server). This is the better option if sites need distinct identities.
Subdirectories work without DNS changes and are simpler to set up. Note: WordPress only offers subdirectories if your site is less than one month old. After that, you're locked into subdomains.

Give your network a name, enter your admin email, and click Install.

Step 3: Update Configuration Files

WordPress will display two blocks of code. One goes in wp-config.php and the other replaces your .htaccess rules. Copy them exactly as shown.

The wp-config additions define constants like MULTISITE, SUBDOMAIN_INSTALL, and DOMAIN_CURRENT_SITE. The .htaccess rules handle URL routing for the network.

After saving both files, log out and log back in. You'll now have a "My Sites" menu and a "Network Admin" dashboard.

Step 4: Configure Network Settings

In Network Admin > Settings, configure:

Registration. Decide whether new users can register and whether they can create new sites.
Upload settings. Set file upload limits and allowed file types.
Default theme. Choose which theme new sites get by default.

Managing a Multisite Network

Day-to-day management happens in the Network Admin dashboard. Key tasks:

Plugins. Install plugins through Network Admin > Plugins. You can "Network Activate" a plugin (active on all sites) or make it available for individual site admins to activate.
Themes. Install themes through Network Admin > Themes. Enable themes you want to make available, then each site admin picks their own.
Updates. Core, plugin, and theme updates happen once and apply everywhere. This is the biggest time saver.
User management. Add users at the network level and assign them to specific sites with specific roles.

Common Pitfalls

Plugin compatibility. Not all plugins work with Multisite. Test thoroughly before deploying to the network. WooCommerce, for example, works on Multisite but requires careful configuration since each site has its own store.
Database size. Each site adds tables to the database. A network with 50+ sites can have hundreds of database tables. Keep your database optimized and backed up frequently.
Resource usage. Multisite is heavier on server resources than a single site. Plan for more RAM, faster storage, and higher PHP worker counts.
SSL certificates. If using subdomains, you'll need a wildcard SSL certificate or individual certificates for each subdomain. Make sure your hosting supports this.
Backup complexity. You can't easily back up individual sites. Network-level backups capture everything, but restoring a single site from a network backup requires specialized tools like UpdraftPlus Premium or ManageWP.

Hosting Requirements for Multisite

Multisite needs more from your hosting than a standard WordPress installation. Look for:

At least 512MB PHP memory limit (1GB preferred for larger networks)
NVMe SSD storage for fast database queries across many tables
Wildcard SSL support if using subdomains
Enough PHP workers to handle concurrent requests across multiple sites

For small Multisite networks (under 10 sites), shared hosting with adequate resources works fine. For larger networks, a VPS gives you the control and resources to scale properly.

See WordPress hosting plans →