Knowledge base — Definition
WordPress Multisite
What WordPress Multisite is, how a network of sites shares one installation, and the trade-offs to weigh before choosing it over separate WordPress sites.
What Is WordPress Multisite?
WordPress Multisite is a built-in feature of WordPress that lets one installation run a network of separate websites, sharing the same core files, plugins, themes and user table while each site keeps its own content, settings and media. It is enabled by adding define( 'WP_ALLOW_MULTISITE', true ); to wp-config.php and then running the Network Setup screen.
Sites in a network can live on subdomains (east.example.com), subdirectories (example.com/east/), or, using WordPress's built-in domain mapping, their own domain names. A new role, the Super Admin, manages the whole network: installing plugins and themes, creating sites and controlling what individual site administrators can do. Universities, franchise brands, media groups and organizations with regional or language sites are typical users.
Why WordPress Multisite Matters
For the right organization, Multisite turns dozens of separate installs into one platform; for the wrong one, it couples sites that should have stayed independent.
- Centralized updates: Core, plugins and themes are updated once for every site in the network.
- Consistent brand and code: One approved theme and plugin set keeps locations, departments or brands visually and technically aligned.
- Shared users: A single login can be given roles on several sites, which suits staff who edit more than one site.
- Fast site creation: New sites can be launched from the network dashboard in minutes using the existing toolkit.
- Shared risk: A bad plugin update, a security breach or a server outage affects every site at once.
How WordPress Multisite Works
- Database structure: Global tables such as users are shared, while each site gets its own set of tables with a numbered prefix, for example
wp_2_postsandwp_2_options. - Media storage: Each site's uploads are kept in their own folder under
wp-content/uploads/sites/. - Plugins and themes: Only the Super Admin can install them. Plugins can be network-activated for all sites or left for site admins to activate individually; themes must be network-enabled before a site can use them.
- Roles and capabilities: Site administrators have fewer powers than on a single install; for example, they cannot install plugins or post unfiltered HTML by default.
- Domains and SSL: Subdomain networks need wildcard DNS and a matching certificate, and mapped domains each need their own DNS and SSL configuration.
Common WordPress Multisite Mistakes
- Choosing it for unrelated sites: Sites with different owners, budgets or plugin needs are usually better as separate installs.
- Assuming every plugin is compatible: Some plugins, especially licensing, caching and membership tools, do not support Multisite properly or need network-specific setup.
- Underestimating the exit cost: Splitting one site out of a network into a standalone install is possible but involves a careful database and media migration.
- Undersized hosting: The network shares one server and database, so traffic on one site can slow the others.
- Backups without per-site restore: Many backup tools restore the whole network, which makes rolling back one site without affecting the rest difficult.
Best Practices for WordPress Multisite
- Decide on structure early: Choose subdomains or subdirectories before launch; changing later affects URLs, SEO and SSL.
- Keep a tight plugin list: Network-activate only what every site needs, and vet each plugin for Multisite support. Our WordPress plugins entry covers vetting.
- Use hosting that supports Multisite: Not every plan does; check before you buy. See WordPress hosting.
- Plan backups per site: Use a backup approach that can export or restore individual sites.
- Govern who can do what: Document which roles exist on each site and keep Super Admin accounts to a minimum, with two-factor authentication.
WordPress Multisite at PerfectPixels
We help organizations decide whether Multisite or separate installs suits them, then build networks with a shared design system, carefully vetted plugins and clear roles for central and local editors. For multi-location or bilingual organizations, we also compare Multisite with single-site options for managing English and French content before recommending a structure. This work is part of our WordPress development service.
Frequently Asked Questions
Should I use Multisite for an English and French website?
It is one valid approach: each language becomes its own site, which keeps content cleanly separated. Translation plugins on a single site are often simpler for small teams. The right choice depends on how closely the two languages mirror each other and who edits them.
Can each site in a network have its own domain?
Yes. WordPress supports domain mapping natively, so a site can use its own domain once DNS points to the server and an SSL certificate covers it. Your host needs to support this configuration.
Can I convert an existing site to Multisite or back again?
An existing single site can be converted into a network, and the original site becomes the main site. Moving a site out of a network is more involved and usually requires a developer-led migration of its tables, media and users.
Related Resources
Further reading: Create a network — WordPress Developer Resources.