Source: https://quadevs.com/insights/wordpress-multisite-vs-one-codebase/

Title: WordPress multisite vs many sites on one codebase | quadevs

[Home](https://quadevs.com/)/ [Insights](https://quadevs.com/insights/)/ WordPress multisite or many sites on one codebase

# WordPress multisite or many sites on one codebase

Two ways to manage multiple WordPress sites: one installation for all of them, or one codebase and an installation each.

Published 2026-11-19 Updated 2026-11-19 4 min read

A **WordPress multisite** network is a group of sites that run on one WordPress installation. The other way to manage multiple WordPress sites keeps an installation for each site and shares only the code: one theme and one block library.

We keep [a fleet of WordPress sites](https://quadevs.com/case/wordpress-fleet/) the second way. Their owners are realtors, clinics, retailers, B2B stores and politicians. This note explains the choice and where multisite is still the better tool.

## What multisite shares

The [WordPress documentation](https://developer.wordpress.org/advanced-administration/multisite/create-network/) defines a network as "a collection of sites that all share the same WordPress installation core files". The sites can also share plugins and themes. A site in the network can switch a plugin or theme on, but it cannot install one; only the network can. Each site keeps its own tables in the database.

## Where multisite fits

Multisite suits one owner with many similar sites: the departments of a university, the branches of one company, a network of blogs. The sites live with one host, use one set of plugins and get every update together. One login can manage them all.

## Where it gets in the way

The sites we look after belong to different owners in different trades. Before our work, hosting differed from site to site. On one installation, every site would have had to move to the same host, and a plugin update would have reached all of them at once. A fault in that update would have reached all of them too.

## One codebase, many installations

So each site keeps its own installation, and the code is shared. All sites run one theme. A site gets its brand and settings through ACF options, and editors build pages from a Gutenberg block library without touching HTML. The admin follows one pattern on every site, so an editor who moves between brands finds a familiar screen.

Rules apply to the whole fleet. Speed budgets are checked at deploy time. Accessibility to WCAG 2.2 AA is required from a site's first version. Hosting on LiteSpeed is offered under contract to owners who ask for it, and the other sites stay where they are. Developers ship an update across the fleet and do not patch sites one by one.

## How to choose

Three questions settle it. Do the sites have one owner? Can they all sit with one host? Should they always run the same plugins? Three yes answers point to multisite. A single no points to separate installations on shared code, which is how our [WordPress maintenance](https://quadevs.com/wordpress-maintenance/) works.

1. [What multisite shares](https://quadevs.com/insights/wordpress-multisite-vs-one-codebase/#what-multisite-shares)
2. [Where multisite fits](https://quadevs.com/insights/wordpress-multisite-vs-one-codebase/#where-multisite-fits)
3. [Where it gets in the way](https://quadevs.com/insights/wordpress-multisite-vs-one-codebase/#where-it-gets-in-the-way)
4. [One codebase, many installations](https://quadevs.com/insights/wordpress-multisite-vs-one-codebase/#one-codebase)
5. [How to choose](https://quadevs.com/insights/wordpress-multisite-vs-one-codebase/#how-to-choose)

## Common questions

What is WordPress multisite?

A feature of WordPress that runs a network of sites on a single installation. The sites share the core files and can share plugins and themes, while each keeps its own database tables.

   Can sites in a multisite network use different plugins?

Partly. A plugin is installed once for the network, and each site can then switch it on or leave it off. A single site cannot install a plugin of its own.

   How do you manage multiple WordPress sites without multisite?

With one shared theme and block library deployed to separate installations. Each site keeps its own host and settings, and checks for speed and accessibility run on every deploy.

## We built this in production

[### WordPress site fleet

Web · WordPress  WordPress · ACF · Gutenberg · LiteSpeed View case](https://quadevs.com/case/wordpress-fleet/)   [### Brand site for a long-running AR and VR studio

Emerging tech · brand site  WordPress · WebGL · video CDN View case](https://quadevs.com/case/ar-vr-brand-site/)   [### Multi-clinic web platform

Healthcare · web  Next.js · headless · Twilio · ADA View case](https://quadevs.com/case/multi-clinic-web/)

Service [WordPress maintenance services and support](https://quadevs.com/wordpress-maintenance/)

Practice [WordPress development and support](https://quadevs.com/wordpress-development/)

[Send a brief. Reply within 1 business day](https://quadevs.com/contact/)  [or email hello@quadevs.com](mailto:hello@quadevs.com)
