WordPress Multisite lets you run dozens or hundreds of WordPress sites from a single installation. One codebase, one set of plugins, one admin area. For educational institutions, media networks, agencies, and SaaS platforms built on WordPress, Multisite solves real management problems. But it’s not for everyone – and setting it up wrong creates headaches that are difficult to undo. This guide covers everything from the decision to enable Multisite through to managing a live network.
What WordPress Multisite Actually Is
WordPress Multisite is a feature built into WordPress core (since version 3.0) that transforms a single WordPress installation into a network of sites. Each site in the network gets its own content, users, and customization options, but shares the same WordPress files, database (in separate tables), and installed plugins and themes.
Sites in a Multisite network can be organized as subdomains (site1.yourdomain.com, site2.yourdomain.com) or subdirectories (yourdomain.com/site1, yourdomain.com/site2). Domain mapping is also possible, allowing each network site to use an entirely separate custom domain while still being managed from one installation.
The network has one or more Super Admins who can manage all sites, install plugins and themes network-wide, and create new sites. Individual site administrators can customize their site but are limited by what the Super Admin makes available – they typically cannot install new plugins or themes without Super Admin approval.
When to Use Multisite (and When Not To)
Good Reasons to Use Multisite
- Shared branding, separate content: A university network with departments each needing their own site under a main domain. A media company running multiple verticals. A franchise with location sites under a parent brand.
- Centralized plugin and theme management: Update 50 sites’ plugins at once rather than logging into 50 separate installs. One security update reaches every site in minutes.
- User single sign-on: Users can be members of multiple network sites and log in once to access all of them. Essential for any multi-site educational or membership platform.
- WordPress-based SaaS: Platforms that give users their own WordPress site upon registration (like WordPress.com itself) use Multisite to provision new sites programmatically.
Reasons to Avoid Multisite
- Just want to manage multiple separate sites: For managing client sites or unrelated properties, a tool like MainWP or InfiniteWP handles multi-site management without the complexity of a shared installation.
- Sites with very different plugin needs: In Multisite, activating a plugin network-wide affects all sites. Sites with conflicting plugin requirements are better served as separate installations.
- Existing single sites you want to “combine”: Migrating existing single-site WordPress installations into a Multisite network is complex and error-prone. Multisite is easier to start fresh than to retrofit.
- Shared hosting environments: Multisite requires more server resources and specific hosting configurations. Most shared hosting providers don’t support Multisite well, and it’s not recommended without at least a managed VPS or managed WordPress host that explicitly supports it.
Prerequisites Before Enabling Multisite
Verify all of these before proceeding. Skipping prerequisites is how Multisite setups go wrong.
- Clean WordPress installation (or a site with no content you’re not prepared to lose – backup before proceeding)
- Apache or Nginx web server with mod_rewrite enabled (shared hosts on LiteSpeed require additional configuration)
- Ability to edit wp-config.php and .htaccess files on your server
- Permalink structure set to Post name (/sample-post/) – Multisite will not enable on Default (plain) permalinks
- No active plugins that are incompatible with Multisite (most are compatible, but check documentation for any unusual plugins)
- Wildcard subdomains configured at your DNS level if you plan to use the subdomain structure
Step-by-Step: Enabling WordPress Multisite
Step 1: Deactivate All Plugins
Before enabling Multisite, deactivate all active plugins from the Plugins screen. This is a precautionary step – some plugins interact with the Multisite activation process in unexpected ways. You’ll re-activate them network-wide after Multisite is set up.
Step 2: Add the Multisite Constant to wp-config.php
Open your wp-config.php file (located in the WordPress root directory) in a text editor. Find the line that reads /* That's all, stop editing! Happy publishing. */ and add the Multisite enable constant immediately above it. The constant to add is: define( 'WP_ALLOW_MULTISITE', true );
Save the file and upload it back to your server. The placement of this constant matters – it must appear before the “stop editing” comment, or the multisite setup wizard won’t appear.
Step 3: Run the Network Setup Wizard
Log back into wp-admin. You’ll now see a new menu item: Tools → Network Setup. Click it to open the setup wizard.
The wizard asks you to choose between subdomains or subdirectories. This is a permanent decision – switching later requires significant migration work. Choose based on your intended use case and whether you’ve configured wildcard DNS for subdomains.
Enter your network title and admin email, then click Install. WordPress will display a screen with two code blocks that you need to add to your files – one for wp-config.php and one for .htaccess (or nginx.conf for Nginx servers).
Step 4: Update wp-config.php with Network Configuration
The wp-config.php code block WordPress provides contains several constants: MULTISITE (set to true), SUBDOMAIN_INSTALL (true for subdomains, false for subdirectories), base path, domain, site ID, blog ID, and secret keys. Add all of these constants exactly as shown by the wizard to your wp-config.php, again above the “stop editing” comment.
Step 5: Update .htaccess
Replace the existing WordPress rewrite rules in your .htaccess file with the Multisite-specific rewrite rules provided by the wizard. The Multisite rules are different from single-site rules and must be used in their entirety. Don’t try to merge them manually – replace the entire WordPress rewrite block with the new one.
For Nginx servers, the wizard provides equivalent rewrite rules for your nginx.conf or site configuration file. Restart Nginx after updating the configuration.
Step 6: Log Back In
After updating both files, log back into wp-admin. The standard WordPress admin will have been replaced with the Network Admin interface. You’ll see a new “My Sites” menu in the admin bar and a Network Admin menu item.
Managing Your Multisite Network
The Network Admin Dashboard
Network Admin (accessed via My Sites → Network Admin) is the control center for your entire WordPress network. From here you can create new sites, manage all users across the network, install and activate plugins and themes network-wide, view network-wide settings, and monitor all sites from one screen.
Creating Network Sites
New sites are created from Network Admin → Sites → Add New. You provide the site address (the subdomain or subdirectory slug), site title, site language, and admin email for the site. The new site is provisioned instantly with its own WordPress admin area, content tables, and default settings.
Sites can also be created programmatically using the wpmu_create_blog() function. This is how SaaS platforms on WordPress Multisite provision new user sites automatically upon registration.
Plugin and Theme Activation in Multisite
In Multisite, plugins are managed at two levels. A Super Admin can Network Activate a plugin, which activates it on every site in the network simultaneously and cannot be deactivated by individual site admins. Alternatively, a plugin can be made available for site admins to activate or deactivate per-site. For most use cases, critical security and functionality plugins should be network-activated, while optional enhancement plugins should be left for site admins to control.
Themes follow the same pattern: network-enabled themes are available to all sites, while themes not enabled by the Super Admin are not visible to site admins at all. This prevents site admins from activating themes that haven’t been vetted for the network.
Domain Mapping: Custom Domains per Site
Domain mapping allows individual network sites to use completely custom domains instead of subdomains or subdirectories. The site site1.yourdomain.com can appear to visitors as www.completelydifferentdomain.com. This is the setup used for white-label WordPress network platforms where each customer gets their own branded URL.
WordPress 4.5+ includes built-in domain mapping support via the Sunrise.php functionality. To enable it, uncomment the SUNRISE constant in wp-config.php, then create a sunrise.php file in wp-content/ with the mapping logic, or use the Mercator plugin which provides a polished domain mapping system built on the same architecture.
For each custom domain, the site owner also needs to point their domain’s DNS to your server’s IP address. Most managed hosting providers have documentation for this process.
Multisite Performance and Hosting Considerations
WordPress Multisite does not inherently perform worse than multiple single-site installations – in fact, the shared file cache and opcode cache across a single PHP installation can be more efficient than separate installations. But the database structure and the shared codebase create specific performance considerations.
All sites in a Multisite network share the same MySQL server. High-traffic sites in your network can create database bottlenecks that affect all other sites. Object caching with Redis or Memcached is highly recommended for Multisite installations – it reduces the per-request database load significantly. Kinsta, WP Engine, and Cloudways all support Multisite with Redis object caching.
WordPress Multisite is not simpler than separate installations – it’s more capable, but also more complex. Understand the constraints before enabling it, especially the shared database architecture.
Backing Up a Multisite Network
Backing up a Multisite network requires backing up the entire network – you cannot back up individual sites independently using most standard backup plugins. The database contains network-wide tables (wp_users, wp_usermeta, wp_site, wp_sitemeta) plus per-site tables (wp_2_posts, wp_3_posts, etc.) that must all be backed up together to have a coherent restore point.
UpdraftPlus, BlogVault, and Jetpack VaultPress Backup all support Multisite (check the current plan requirements – some limit Multisite to premium tiers). For Multisite, the “Backup files” option must include the shared wp-content/uploads/sites/ directory structure, not just the main uploads directory.
Managing Users Across a Multisite Network
Multisite has a two-level user management system that differs significantly from single-site WordPress. At the network level, Super Admins have access to every site and network settings. At the site level, users have roles (Administrator, Editor, Subscriber) that apply only to that specific site. A user can be an Administrator on Site A and a Subscriber on Site B – roles are per-site assignments, not network-wide.
User registration in Multisite can be configured three ways: registration disabled (no new signups), user accounts only (users can register but not create sites), or both users and sites (full network membership with site creation). For a private educational network, you typically want user accounts only with manual site creation by the Super Admin. For a public site hosting service, you want both enabled. For a private company intranet, registration is usually disabled with users added manually by the Super Admin.
Common Questions About WordPress Multisite
Can I convert an existing WordPress site to Multisite?
Yes. The Multisite conversion process works on an existing WordPress installation and preserves all existing content, settings, and users. Your existing site becomes Site 1 (the main site) in the new network. However, the conversion is not easily reversible. Once enabled, disabling Multisite requires editing wp-config.php and running database cleanup scripts. Before converting, create a complete backup, test the conversion on a staging copy of your site first, and verify that all your existing plugins are Multisite compatible. Some plugins designed for single-site installations behave unexpectedly or break entirely in a Multisite context.
Do all sites in a Multisite network share the same domain?
By default, subsites use subdomains (site1.network.com) or subdirectories (network.com/site1) of the network domain. However, Multisite supports domain mapping, which allows each subsite to use a completely separate custom domain. A network running network.com can have a subsite mapped to client-a.com and another mapped to client-b.com. The WordPress core domain mapping feature (added properly in WordPress 4.5+) handles this, though some hosts have their own domain mapping tools. Each mapped domain still resolves to the same WordPress installation – only the URL presentation changes.
Can I run different themes on different sites in the same network?
Yes, this is one of Multisite’s strengths. The Super Admin controls which themes are network-enabled (available for site administrators to activate) and can also assign specific themes to specific sites. A Super Admin can force a theme on a site, preventing site administrators from changing it. This is useful for brand consistency in agency or franchise setups where different clients get their own subsite but must use an approved theme. Plugins work similarly – network-activated plugins run on all sites, while non-network-activated plugins can be enabled per-site by site administrators if the Super Admin grants that permission.
Is Multisite Right for Your Project?
If you’re managing two or three separate WordPress sites for different clients or projects, Multisite is almost certainly more complexity than you need. A tool like MainWP lets you manage multiple separate WordPress installations from one dashboard without the shared infrastructure constraints.
If you’re building a platform where users each get their own WordPress-powered site, or managing a genuine network of 10+ related sites under organizational control, Multisite is built exactly for your situation. Start on a capable host that explicitly supports Multisite, enable it on a fresh installation, and build from there.
For your Multisite hosting needs, see our guide to choosing the right WordPress hosting – Multisite networks need at least managed VPS or cloud-tier hosting to perform reliably. Once you have your network running, our list of must-have WordPress plugins will help you configure each subsite with the right foundation.
WordPress Development WordPress Multisite WordPress Networks wordpress plugins WordPress Tips
Last modified: April 6, 2026
