WordPress Multisite is one of the platform’s most powerful — and most misunderstood — features. Used correctly, it eliminates the overhead of maintaining separate WordPress installations. Used incorrectly, it creates complexity that’s difficult to unwind. This guide helps you decide clearly.

What is WordPress Multisite?

WordPress Multisite is a feature built into WordPress core that allows you to run a network of websites from a single WordPress installation. Instead of installing WordPress separately for each site, you manage them all from one dashboard — with one codebase, one hosting account, and a shared plugin and theme library.

Each site in the network has its own content, users, settings, and URL — but they all run on the same WordPress files and share the same database (with separate table prefixes per site).

How Multisite works technically

When Multisite is enabled, WordPress adds a new layer of administration — the Network Admin — above the regular WordPress dashboard. Sites can be structured in two ways:

  • Subdomain — each site gets its own subdomain: site1.yourdomain.com, site2.yourdomain.com
  • Subdirectory — each site lives in a folder: yourdomain.com/site1, yourdomain.com/site2
  • With domain mapping plugins, each site can also use a completely independent domain (site1.com, site2.com) while still being managed from one installation
⚡ Shared resources

All sites in a Multisite network share the same WordPress core files and the same plugin and theme files. The Super Admin installs and activates plugins network-wide; individual site admins can activate what the Super Admin permits.

When Multisite is the right choice

Multisite genuinely simplifies operations when you have a clear need for multiple related sites under central management. The strongest use cases are:

  • Educational institutions — a university running department sites (law.university.edu, medicine.university.edu) with central IT managing the network
  • News and media organizations — a publishing group running regional editions under one editorial system
  • SaaS products with site-per-customer architecture — each client gets their own subdomain site, all managed centrally
  • Franchise or multi-location businesses — each location has its own site with local content but shares global branding and functionality
  • Agencies managing multiple client sites internally — shared plugins, shared themes, one update cycle for everything
  • Multilingual sites — separate sites per language/region under one installation

When to avoid Multisite

Multisite introduces complexity that’s not worth it for most situations. Avoid it when:

  • You simply want two separate business websites — two independent WordPress installations are simpler and carry no shared risk
  • Your sites have very different technical requirements — Multisite forces a shared plugin and theme environment, which can create conflicts
  • You need different hosting resources per site — all Multisite sites share the same server resources
  • A single compromised site or failed plugin update affects your entire network — the shared infrastructure is a shared risk
  • You anticipate selling individual sites — extracting a site from a Multisite network is complex and time-consuming
⚡ Rule of thumb

If the sites need to share content, users, or administrative overhead — Multisite may be the answer. If they’re just independently operated websites owned by the same person, separate installs are almost always simpler and safer.

How to enable WordPress Multisite

1
Back up your entire site

Before enabling Multisite, take a complete backup of your files and database. Enabling Multisite makes changes to your wp-config.php and .htaccess that can be difficult to reverse.

2
Add the Multisite constant to wp-config.php

Add define('WP_ALLOW_MULTISITE', true); above the line that says ‘/* That’s all, stop editing! */’ in your wp-config.php file.

3
Run the network setup wizard

Go to Tools → Network Setup in your WordPress dashboard. Choose between subdomains and subdirectories, fill in your network title and admin email, then click Install.

4
Update wp-config.php and .htaccess

WordPress will display two code blocks to add to your wp-config.php and .htaccess files. Copy and paste them exactly as shown — do not modify them.

5
Log back in and access Network Admin

After saving the files, log out and back in. You’ll now see a ‘My Sites’ menu in the admin bar. Go to Network Admin → Dashboard to manage your network.

6
Create your first sub-site

Go to Network Admin → Sites → Add New. Enter the site address, title, admin email, and click Add Site. The new site is immediately available.

Managing a Multisite network

The Super Admin is the highest level of access in a Multisite network. They can:

  • Install and network-activate plugins (making them available to all sites)
  • Install themes and control which themes individual sites can use
  • Add, suspend, or delete sites from the network
  • Manage user roles across the entire network
  • Set storage limits per site and control file upload permissions

Individual site administrators manage their own content, users, and settings within the permissions granted by the Super Admin. They cannot install new plugins or themes unless the Super Admin allows it.

Frequently asked questions

Can I convert an existing WordPress site to Multisite?

Yes. You can enable Multisite on an existing WordPress installation. Your existing site becomes the primary site in the network. All your content, themes, and plugins remain intact. However, always take a complete backup first — the process modifies wp-config.php and .htaccess, and the changes are not trivially reversible.

Do all sites in a Multisite network share the same hosting resources?

Yes. All sites in a Multisite network run on the same server with shared CPU, RAM, and bandwidth. If one site experiences a traffic spike, it can affect performance for other sites on the network. This is why Multisite works best on managed WordPress hosting with scalable infrastructure (Kinsta, WP Engine).

Can each site in a Multisite network have its own domain?

Yes, with domain mapping. By default, sub-sites use subdomains or subdirectories. With a domain mapping plugin (or the native WordPress domain mapping feature in newer versions), each site can use a completely separate domain name while still being managed from the same WordPress installation.