Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Setup & site building · Guide

How to Set Up WordPress Multisite

How to Set Up WordPress Multisite

Short answer

To set up WordPress Multisite, back up your site, add define( 'WP_ALLOW_MULTISITE', true ); to wp-config.php, then open Tools > Network Setup and click Install. WordPress then gives you code to paste into wp-config.php and .htaccess, after which you log in again as super admin and add sites from Network Admin > Sites > Add New.

Key takeaways

  • Multisite runs many sites from one WordPress install, with shared core files and separate database tables per site.
  • Choose subdomains or subdirectories before you click Install, because the address type is hard to change later.
  • Subdomain networks need a wildcard DNS record, while subdirectory networks need only working pretty permalinks.
  • Only the super admin can install plugins and themes; each site admin can only activate them.
  • WordPress will not offer subdirectories if your site has published content older than 1 month.

What is WordPress Multisite?

A WordPress Multisite network is a collection of sites that share one WordPress installation, one set of core files, and one database.

Every site in the network runs from the same WordPress files. The sites share plugins and themes at the network level, but each site keeps its own media folder and its own database tables for content, as the WordPress Learn lesson on setting up a multisite network explains.

A network can feel like your own small version of WordPress.com. The Create A Network guide says a multisite network can be very similar to a personal version of WordPress.com, where end users can create their own sites on demand.

One large live example is Make WordPress. The WordPress Learn lesson notes that each contributor team has its own subsite on the Make WordPress network. If you want the background first, read what WordPress Multisite is.

Should you use Multisite or separate WordPress installs?

Use Multisite when your sites are similar but need to stay separate, and use separate installs when the sites share users, data, or logins.

The Before You Create A Network guide warns that sites in a network are separate, and if you plan sites that are strongly interconnected, share data, or share users, Multisite might not be the best solution.

Multisite fits groups of related sites. The WordPress Learn lesson lists higher education websites, non-profit organizations, and open-source projects as typical examples. One admin team can update the core, plugins, and themes once for all sites.

Separate installs fit sites that need different plugins, different hosts, or full independence. If one site going down must never affect the others, separate installs give you that wall. Our guide to when to use WordPress Multisite walks through the same choice in more detail.

What do you need before you start?

You need a full backup, working pretty permalinks, deactivated plugins, and file access to wp-config.php and .htaccess.

Work through this checklist before you touch any code:

  1. Back up your database and files. The Create A Network guide says to back up unless this is a fresh install with nothing to lose.
  2. Confirm pretty permalinks work. Open a post and check its URL loads. Multisite depends on them.
  3. Deactivate all active plugins. You can turn them back on after the network is created.
  4. Confirm you are an administrator and you can edit files on the server, by FTP, SFTP, or your host file manager. The Before You Create A Network guide says you normally need access to the server file system.
  5. Check your server can use the rewrite rules Multisite needs. On Apache, the same guide says mod_rewrite must be loaded, .htaccess support must be on, and AllowOverride should be set to All for your site.

If your host uses Nginx, the manual method does not apply in the same way.

The WordPress Learn lesson notes that Nginx does not support the .htaccess file used to enable Multisite by hand, so many Nginx hosts ask you to create the network during site setup instead. If you are unsure, test the whole process on a staging site first.

How do you enable Multisite in wp-config.php?

Add one line to wp-config.php above the “That's all, stop editing!” comment, and the Network Setup menu appears under Tools.

Open wp-config.php in your WordPress root folder and add this line:

define( 'WP_ALLOW_MULTISITE', true );

Place it above the line that reads /* That's all, stop editing! Happy publishing. */.

The Editing wp-config.php guide says WP_ALLOW_MULTISITE defaults to false when the setting is absent, so nothing happens until you add it.

Save the file and refresh your WordPress dashboard. A new item called “Network Setup” appears under the “Tools” menu.

If it does not appear, check that you edited the wp-config.php file in the right folder and that the line sits above the stop-editing comment. Read our WordPress backup guide before you edit the file, so you can restore it if a typo breaks the site.

How do you choose between subdomains and subdirectories?

Pick subdomains for addresses like site1.example.com, or subdirectories for paths like example.com/site1, and decide before you click Install.

The two address types behave differently, and the choice is hard to change later. The Tools Network screen guide states it plainly: you cannot change this later.

Address typeExample site addressWhat it needs
Subdomainssite1.example.comWildcard DNS record and a wildcard SSL certificate
Subdirectoriesexample.com/site1Pretty permalinks only, no DNS changes

Subdomains give each site its own address, which looks cleaner for separate brands or departments. You need a wildcard DNS record for your domain, written as *.example.com, so any subdomain name resolves to your server.

The wildcard DNS record reference explains that the asterisk matches names that do not exist yet in the zone.

Subdirectories are simpler. They need no DNS work and one certificate covers the whole network.

But WordPress will not offer subdirectories if your site has published content older than 1 month. The Before You Create A Network guide gives the reason: a new site path could collide with an existing post URL.

Two more limits apply. You cannot pick subdomains if your WordPress address is localhost or an IP address such as 127.0.0.1. You cannot create a network at all if your WordPress address uses a port other than 80 or 443, as the same guide states.

How do you run Network Setup and install the network?

Open Tools > Network Setup, pick subdomains or subdirectories, check the network title and admin email, then click Install.

The Network Setup screen fills in most fields for you. It shows the server address, a network title, and the network admin email. Change the title to the name of your network, and check the email address is one you read, because network notices go there.

Click the “Install” button. WordPress creates the extra database tables the network needs and adds its own data to them.

This step takes seconds on a small site and longer on a large one. Do not close the tab while it runs.

WordPress then shows an “Enabling the Network” page with two blocks of code. Those blocks are made for your install only. Copy them exactly, as the next section explains.

How do you add the generated code to wp-config.php and .htaccess?

Paste the code WordPress shows you into wp-config.php and .htaccess, then log in again as the network super admin.

Follow the two steps in the order WordPress shows them:

  1. Back up your current wp-config.php and .htaccess files first. The Create A Network guide says to do this unless the install is fresh with nothing to lose.
  2. Add the lines to wp-config.php, just after the WP_ALLOW_MULTISITE line you added earlier. They look like this, with your own domain in place of example.com:
define( 'MULTISITE', true );
define( 'SUBDOMAIN_INSTALL', false );
define( 'DOMAIN_CURRENT_SITE', 'example.com' );
define( 'PATH_CURRENT_SITE', '/' );
define( 'SITE_ID_CURRENT_SITE', 1 );
define( 'BLOG_ID_CURRENT_SITE', 1 );
  1. Add the lines to .htaccess, replacing the existing WordPress rules with the new ones. If you have no .htaccess file, create one in the same folder as wp-config.php.
  2. Log in again with the link WordPress gives you. You may need to clear your browser cache and cookies first, as the Create A Network guide notes.

After login, “My Sites” appears as the second item in your toolbar. Your account is now the super admin, and a “Network Admin” menu sits under My Sites. If the login page loops or shows an error, restore the two backed-up files and check each pasted line for a missing quote or semicolon.

How do you create your first site on the network?

Go to My Sites > Network Admin > Sites > Add New, then enter the site address, title, and admin email.

Fill in the three fields and save. WordPress creates the site with its own tables and media folder. The new site appears in the Sites list, where the super admin can edit, archive, or delete it.

Open the new site address in a fresh browser tab and check it loads. Log in to its dashboard from the Sites list and confirm you can add a post. Each site has its own dashboard, its own users, and its own settings, even though the files are shared.

If you plan to add many sites, set the rules first. Go to Network Admin > Settings to control who can create sites, whether new users can register, and which themes and plugins are available. Decide this before you invite people, so the network grows in the shape you want.

How do you manage plugins and themes on a network?

The super admin installs plugins and themes for the whole network, and each site admin can only activate them.

This split is the part most new network owners miss. The Create A Network guide states that each site can activate plugins and themes, but install neither. Only the super admin can install or delete them, from Network Admin > Plugins and Network Admin > Themes.

A plugin installed on the network is not active anywhere until a site turns it on. The super admin can also network-activate a plugin, which turns it on for every site at once. Use that only for plugins every site truly needs, such as a security plugin.

Updates work the same way. The super admin updates the core, plugins, and themes once, and every site gets the new code. That saves time, but it also means one bad update can affect every site.

Keep a backup routine and update on a staging copy first when a change is large. Our guide to managing multiple WordPress sites covers routines that work well for networks too.

How do you check the network works?

Visit each new site, log in to its dashboard, publish a test post, upload an image, and confirm the permalink loads.

Run these checks on the main site and on one new site:

  1. Open the site front page while logged out and confirm it loads without errors.
  2. Log in to the site dashboard and publish a short test post, then open its permalink.
  3. Upload an image to the post and confirm it shows, which proves the site media folder works.
  4. Go to Network Admin > Sites and confirm the site count and addresses look right.
  5. Check Settings > Permalinks on the new site and save it once, which refreshes the rewrite rules.

If a new site shows a 404 page, the .htaccess rules are the first thing to check. Open the file and confirm the Multisite rules replaced the old WordPress rules, with nothing left over above them.

If the dashboard shows a database error, check that the wp-config.php constants match the ones WordPress generated, with no typos in the domain name.

What mistakes should you avoid?

Do not skip the backup, do not pick subdomains without wildcard DNS, and do not change the address type after sites exist.

These mistakes cause most failed setups:

  • Converting a live site with no backup. The install edits wp-config.php, .htaccess, and the database. Without a backup, a bad paste leaves you with no quick way back.
  • Picking subdomains and forgetting DNS. Without a wildcard record, new subdomain addresses will not resolve, and visitors will see a browser error.
  • Picking subdirectories on an old site. WordPress blocks this for installs older than 1 month, but forcing it with a constant can break existing post URLs.
  • Editing the wrong wp-config.php. Some hosts keep a copy in a folder above the site root. Edit the one WordPress actually loads, and keep a copy of the original.
  • Letting every site admin install plugins. Only the super admin can install them, so keep it that way and review each request before you add code to the network.

Set aside 30 to 60 minutes for a first setup on a fresh install, and longer on a live site with content. Most of that time goes to the backup, the DNS change, and the checks at the end, not to the install itself.

Frequently asked questions

Can I turn an existing WordPress site into a Multisite network?

Yes, you can convert an existing single site by adding the WP_ALLOW_MULTISITE line to wp-config.php and running Tools > Network Setup. Back up the database and files first, deactivate plugins, and confirm pretty permalinks work. On installs older than 1 month, WordPress only offers subdomains, not subdirectories.

Do I need a wildcard DNS record for a subdirectory network?

No. Subdirectory networks use paths under one domain, such as example.com/site1, so they need no DNS changes at all. A wildcard DNS record is only needed for subdomain networks, where each site gets an address like site1.example.com. You also need a wildcard SSL certificate to serve those subdomains over HTTPS.

What happens if I paste the wrong code into wp-config.php?

A typo in wp-config.php can break the whole site with a blank page or a PHP error. Restore the backup copy of the file, then paste the code again exactly as WordPress showed it on the Enabling the Network page. Always keep a copy of the original wp-config.php and .htaccess files before you edit them.

Can each site on a Multisite network use a different theme?

Yes. The super admin installs themes for the whole network, and each site admin can activate any theme the super admin has made available. A site can also have its own plugins turned on, as long as the super admin installed them first. Only the super admin can install or delete plugins and themes.

How long does it take to set up WordPress Multisite?

Allow 30 to 60 minutes for a first setup on a fresh install. The install itself takes minutes, but the backup, the DNS change for subdomain networks, and the checks at the end take most of the time. On a live site with content, allow more time and do the work during a quiet period.

Sources

  1. Create A Network WordPress Developer Resources
  2. Before You Create A Network WordPress Developer Resources
  3. Setting up a WordPress multisite network WordPress Learn
  4. Editing wp-config.php WordPress Developer Resources
  5. Tools Network screen WordPress.org Documentation
  6. Wildcard DNS record Wikipedia

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.