What are the server requirements for WordPress Multisite?

Multisite requires more resources than a standard installation – more RAM, a performant MySQL database, proper PHP-FPM configuration, and object cache (Redis or Memcached). The server must support mod_rewrite (Apache) or proper Nginx configuration. For 20+ sites we recommend at least 2-4 GB RAM.

Can I migrate an existing WordPress site to Multisite?

Yes. Migration to Multisite requires transferring content, media, users, and plugin configuration. The reverse operation – extracting a site from Multisite to a standalone installation – is also possible. Both processes require experience and careful planning, but are fully feasible.

Knowledge Base

WordPress Multisite – What It Is, How It Works, Requirements, and Security

Q: Is WordPress Multisite secure?

Multisite is secure with proper configuration. Key measures: upload directory isolation, plugin installation restricted to Super Admin only, regular updates, daily backups, WAF, and malware scanning. A vulnerability in one shared plugin can affect all sites – so update testing is critical.

Q: Who is WordPress Multisite a good fit for?

Multisite works well for companies with multiple branches or brands, agencies managing client sites, universities, blog networks, and organizations needing multiple sites under central administration. It is not recommended when sites require completely different plugin sets or full infrastructure independence.

Published: March 20, 2026 · Author: Marcin Szewczyk-Wilgan

WordPress Multisite is a built-in WordPress feature that allows creating and managing a network of websites from a single installation. One WordPress core, one set of plugins, one set of themes – shared by dozens or hundreds of sites, each with its own content, users, and settings. This is not a plugin or external tool – it is a native WordPress capability, available in every installation since version 3.0. In this article, we explain what Multisite is, how it works technically, what server requirements it has, who it is a good fit for, what its limitations are, and how to approach security in a multi-site network.

What Is WordPress Multisite?

WordPress Multisite transforms a single WordPress installation into a network of sites. Each site in the network has its own content, media library, users, and settings – but shares the WordPress core, plugins, and themes with all other sites. Three URL structure options:

SubdirectoriesURL structure: example.com/site1, example.com/site2. Simplest configuration, no DNS setup needed per site. Recommended for most deployments.

SubdomainsURL structure: site1.example.com, site2.example.com. Requires wildcard DNS configuration (*.example.com) and an appropriate SSL certificate (wildcard or multi-domain).

Domain mappingEach site in the network can have its own independent domain – e.g. company-a.com, company-b.com. Requires additional DNS configuration, SSL certificates, and a domain mapping plugin (e.g. Mercator).

How WordPress Multisite Works Technically

Understanding the technical architecture is essential before deployment:

Shared coreAll sites share one WordPress installation – one set of core files, one wp-config.php. Updates to WordPress core apply to all sites at once. This is both an advantage (one update for all) and a risk (one bug affects all).

Shared plugins and themesPlugins and themes are installed once and available network-wide. They can be network-activated (active on all sites) or activated per site. Only the Super Admin can install plugins – individual site admins cannot.

Separate database tablesEach site in the network gets its own set of database tables (wp_2_posts, wp_2_options, etc.). With 30 sites, the database contains over 300 tables. Content, settings, and users are isolated per site at the database level.

Separate uploadsEach site has its own subdirectory within wp-content/uploads/sites/. Media files are isolated per site. The uploads directory structure is managed automatically by WordPress.

Roles and Permissions in WordPress Multisite

Multisite introduces a new role hierarchy that is critical for security and governance:

Super AdminFull permissions over the entire network: installing plugins and themes, creating/deleting sites, managing users, access to network settings, WordPress core updates.

AdministratorManages a single site in the network: content, media, site users, site settings. Cannot install plugins/themes or edit code – unless the Super Admin grants additional permissions.

Other rolesEditor, Author, Contributor, Subscriber – work identically to a standard WordPress installation, but within the context of a specific site in the network.

Server Requirements for WordPress Multisite

Multisite requires more server resources than a standard installation – proportionally to the number of sites and traffic:

RAMEach site in the network consumes additional RAM on page load. For networks with 20+ sites, we recommend at least 2–4 GB RAM, and for 50+ sites – 8 GB or more.

DatabaseEach site creates a separate set of MySQL tables. With 30 sites, the database contains over 300 tables. Requires a performant MySQL server, proper buffer configuration (innodb_buffer_pool_size), and regular optimization.

PHP-FPMPHP-FPM configuration must account for a higher number of concurrent processes. Pool size (pm.max_children), per-process memory limit (memory_limit), and execution time (max_execution_time) need tuning for network size.

CacheObject cache (Redis or Memcached) is practically mandatory for Multisite with multiple sites. Without it, every request generates numerous database queries. OPcache accelerates PHP code execution, which is proportionally more important in Multisite.

DisksSSD or NVMe drives – especially important with many database tables and media files. The wp-content/uploads directory is shared, but each site has its own subdirectory.

Web serverApache with mod_rewrite or Nginx with proper rewrite rules configuration. Nginx requires additional configuration for Multisite – standard WordPress rules are not sufficient. Configuration differs for subdirectories and subdomains.

Advantages of WordPress Multisite

When the use case is right, Multisite delivers significant operational and cost benefits:

Centralization

One dashboard for all sites

Updating WordPress core, plugins, and themes happens once – for the entire network. Instead of logging into 20 separate dashboards and running 20 separate updates, you do it from one place. This radically reduces administration time.

Cost

Lower maintenance costs

One server, one installation, one set of plugins (including premium). A premium plugin license applies to the entire network, not to each site separately. Hosting, backup, and administration costs are proportionally lower than with many separate installations.

Consistency

Uniform standards

All sites in the network use the same tested versions of WordPress, plugins, and themes. Uniform level of security, performance, and functionality – without the risk of one site being neglected.

Speed

Instant new site creation

A new site in the Multisite network is created in seconds – without installing WordPress, configuring a server, or purchasing hosting. The Super Admin creates a new site from the dashboard, and it immediately uses the entire network infrastructure.

Limitations and Risks of WordPress Multisite

Multisite is not without trade-offs. Understanding the limitations before deployment is essential:

Plugin compatibilityNot every WordPress plugin is compatible with Multisite. Some plugins do not support network activation, others behave unpredictably with multiple sites. Testing every plugin in a Multisite environment before deployment is essential.

Shared riskUpdating a shared plugin affects all sites simultaneously. If an update contains a bug – the entire network goes down, not just one site. A WordPress core or MySQL failure affects all sites. Shared infrastructure means shared risk.

MigrationExtracting a single site from a Multisite network to a standalone WordPress installation is more complex than a standard migration. Requires exporting content, media, users, and recreating plugin configuration. Reversible, but not trivial.

HostingNot every hosting provider supports WordPress Multisite – especially on shared hosting plans. Subdomain configuration requires wildcard DNS and an appropriate SSL certificate. Domain mapping requires additional server configuration.

ScalabilityWith very large site counts (100+), the database becomes a bottleneck. Thousands of tables in one MySQL database strain the server and slow queries. Such scenarios require advanced optimization or database splitting.

WordPress Multisite Security

Multisite security requires a proactive approach – a vulnerability in one shared component can affect the entire network:

Site isolationAlthough sites share the WordPress core and plugins, upload directories must be isolated. File permissions must prevent one site from accessing another site’s media. PHP open_basedir configuration restricts filesystem access scope.

Plugin permissionsIn Multisite, only the Super Admin can install plugins – individual site administrators do not have this permission. This is an important safeguard – it prevents installation of unverified plugins that could threaten the entire network.

UpdatesRegular updates of core, plugins, and themes are the foundation of Multisite security. One outdated plugin with a vulnerability exposes all sites. Updates should be tested on staging before production deployment.

BackupMultisite backups should cover both the entire installation (core + database + media) and allow restoring individual sites. Daily backups sent to an external data center are the minimum.

WAF and monitoringA Web Application Firewall (WAF) and daily malware scanning should cover the entire Multisite network. File integrity monitoring for WordPress core and plugins enables rapid detection of unauthorized code changes.

Who Is WordPress Multisite a Good Fit For?

Multisite shines in specific scenarios where centralized management of multiple sites delivers real value:

Companies

Regional branches and brands

Companies with multiple branches, brands, or market-specific sites. Each branch gets its own site with its own content, while sharing a consistent design, plugin set, and security level. Central IT manages the infrastructure.

Agencies

Client sites under one roof

Web agencies managing client sites. One infrastructure, one set of tools, centralized updates and backups. The agency maintains the network, clients manage their content. Scales efficiently with each new client.

Education

Universities and institutions

Universities, schools, and government institutions with sites for departments, faculties, projects. Central IT controls security and standards, each department manages its own content independently.

Networks

Blog and content networks

Networks of thematic blogs or portals. Shared design and functionality, independent content. Quick creation of new sites in the network. Monetization and analytics managed centrally.

Summary

WordPress Multisite is a powerful tool that, in the right hands and the right scenario, significantly reduces maintenance costs and simplifies administration of multiple sites. However, it requires configuration experience, awareness of architectural limitations, and a proactive approach to security. Before deployment, carefully analyze requirements – both current and future – and consult with a team that has production experience with Multisite.

At WebOptimo, we deploy, maintain, and optimize WordPress Multisite installations with dozens of sites. If you are considering Multisite for your organization or need support for an existing network – contact us or check our WordPress Multisite offer.

Frequently Asked Questions About WordPress Multisite

What is WordPress Multisite?+

A built-in WordPress feature for running and managing multiple sites from a single installation. Sites share core, plugins, and themes but have separate content, media, and database tables.

What are the server requirements?+

More resources than standard WordPress: more RAM (2–4 GB for 20+ sites), performant MySQL, proper PHP-FPM configuration, object cache (Redis/Memcached), mod_rewrite or Nginx rewrite rules.

Is WordPress Multisite secure?+

Yes, with proper configuration: isolated uploads, plugin installation restricted to Super Admin, regular updates, daily backups, WAF, and malware scanning. One vulnerable shared plugin affects all sites.

Who is Multisite a good fit for?+

Companies with multiple branches/brands, agencies managing client sites, universities, blog networks. Not recommended when sites need completely different plugins or full infrastructure independence.

Can I migrate an existing site to Multisite?+

Yes. Requires transferring content, media, users, and plugin configuration. The reverse (extracting from Multisite) is also possible. Both require experience and careful planning.