To activate Multisite in a self-hosted WordPress installation, first back up the database and files, then deactivate every plugin. Add define( 'WP_ALLOW_MULTISITE', true ); to wp-config.php above the /* That's all, stop editing! */ comment. After refreshing the dashboard, go to Tools > Network Setup, choose subdomains or subdirectories, enter the network details, and paste WordPress’s generated snippets into wp-config.php and .htaccess. Log in again to finish.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
This converts the current site into the first site in a network that shares one WordPress codebase. The conversion changes the existing installation, so the backup and preparation steps are not optional.
As an Amazon Associate I earn from qualifying purchases.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →What WordPress Multisite activation actually does
WordPress Multisite is a network mode in which one self-hosted WordPress installation can manage multiple sites. The sites use the same WordPress files and network administration area, while each site can have its own content and site address. The site you already have becomes the first site in the network when you create the network.
Adding WP_ALLOW_MULTISITE does not by itself turn on Multisite. That constant only unlocks the Network Setup screen. The setup screen creates the network-specific configuration, including the MULTISITE setting and rewrite instructions. Those generated lines must be copied exactly where WordPress tells you to put them.
The instructions below apply to a self-hosted, single-site WordPress installation being converted into a network. Dashboard labels and generated rewrite text can change between WordPress releases, so use the text shown by your own Network Setup screen when it differs from an example.
Prepare the site before enabling the network
1. Make two backups
Create a complete database backup and a backup of the WordPress files before changing configuration. Keep both copies outside the live WordPress directory or in another recoverable location. The database contains posts, pages, users, settings and network data; the files include WordPress core, themes, plugins, uploads and configuration.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsDo not begin until you know how to restore those backups. A backup that has never been tested may not be usable if a configuration edit produces a fatal error or the new rewrite rules prevent requests from reaching the site.
2. Confirm that pretty permalinks work
On the single site, open Settings > Permalinks, select a human-readable permalink structure if one is not already active, save the settings, and test a few front-end URLs. WordPress’s network-creation process expects the existing site to use working pretty permalinks. If ordinary post or page links already return 404 errors, fix that problem before creating the network.
3. Deactivate every plugin
From Plugins > Installed Plugins, deactivate all plugins for the setup. They can be reactivated after the network exists, one at a time. Deactivation reduces the chance that a plugin’s hooks, redirects or rewrite rules interfere with the conversion and makes troubleshooting a failed setup much easier.
Record which plugins were active so you can restore the previous operating state deliberately. Do not delete plugins merely because they are deactivated.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstall4. Check the hosting environment
Make sure you can edit wp-config.php and the web server’s rewrite configuration, usually .htaccess on an Apache-style setup. If your host uses a control panel, a managed WordPress service, an Nginx configuration, or a one-click installer, check its Multisite procedure before editing files. The WordPress screen supplies Apache-style .htaccess instructions, but an Nginx server does not read that file; its rewrite configuration must be handled in the server configuration by the host or administrator.
For a subdomain network, the domain and DNS arrangement is especially important. Many installations need a wildcard DNS record so newly created subdomains resolve to the WordPress server, but the exact record and whether it is permitted are host- and DNS-provider-dependent. Confirm this requirement with the people managing your DNS before choosing subdomains.
Choose subdomains or subdirectories
Network Setup asks how the sites in your network should be addressed. This choice affects URLs, DNS and rewrite behavior, so decide before you complete the screen.
| Network type | Example site address | Operational consideration |
|---|---|---|
| Subdomains | site2.example.com |
Each site is addressed on a subdomain. DNS and hosting must route those subdomains to the WordPress installation; a wildcard DNS arrangement is commonly needed, but the exact requirement is host-dependent. |
| Subdirectories | example.com/site2/ |
Each site is addressed in a path below the main domain. Existing permalink and rewrite behavior must support the additional paths, and WordPress will generate the rules for your installation. |
WordPress may restrict or explain an option based on the current site’s URL structure. Read the warning on the Network Setup screen rather than forcing a choice that conflicts with the existing installation. If you are uncertain whether DNS or server routing is ready, pause and resolve that host-level question first; changing the network type later is not a routine toggle.
Activate WordPress Multisite step by step
Step 1: Open wp-config.php
Locate the wp-config.php file for the WordPress installation. Use your host’s file manager, SFTP or another administrator-approved method. Download a copy before editing so you can restore the original file if a syntax error prevents WordPress from loading.
Step 2: Add the activation constant
Insert this exact line:
define( 'WP_ALLOW_MULTISITE', true );Place it above the line containing /* That's all, stop editing! */. Keep the semicolon, quotation marks and parentheses exactly as shown. Do not add MULTISITE manually at this stage. WordPress generates the network-level settings later, after you submit Network Setup.
Save the file without adding a second conflicting definition elsewhere. If your editor offers a choice of encoding, retain the file’s existing encoding and line endings.
Step 3: Refresh the WordPress dashboard
Sign in to the administration area and refresh the page, or sign out and back in if the menu does not update immediately. A new item named Network Setup should appear under Tools. If it does not, confirm that the edited file belongs to the active installation, that the constant is above the stop-editing comment, and that the line contains no typographical changes.
Free tools Windows power users keep installed
One-click scans. No signup required.
Step 4: Open Network Setup
Go to Tools > Network Setup. The screen is available only after the constant is recognized. Read any notices at the top of the page before filling in the form; WordPress can warn about URL structures, existing content or the network type available to this installation.
Step 5: Enter the network details
Provide a Network Title and the Network Admin Email. Use a title that administrators will recognize when several networks or environments exist. Use an email address that the network administrator can monitor for administrative messages.
Select Sub-domains or Sub-directories according to the DNS and URL plan you prepared. Review the displayed site address and any warning before clicking the button to install or create the network.
Step 6: Copy both generated code blocks
After submission, WordPress displays instructions containing code for two files. One block belongs in wp-config.php; the other belongs in .htaccess. Copy the generated text from the screen, not from a generic tutorial, because the values can reflect your domain, path and selected network type.
When inserting the wp-config.php block, preserve the existing WP_ALLOW_MULTISITE line and place the new network definitions exactly where WordPress indicates. Do not paste the .htaccess rules into wp-config.php, and do not omit a line because it looks repetitive.
For an Apache-style server, open the site’s .htaccess file and replace or update the WordPress rewrite section as instructed. Make a copy of the original first. If the server does not use .htaccess, stop and ask the host or server administrator to translate the generated rules into that server’s configuration; simply creating an unused file will not activate the rewrites.
Step 7: Log in again
Return to the dashboard and log in again when WordPress prompts you. The reauthentication completes the transition and returns you to Network Setup as the network administrator. If the login page loops, shows a redirect error or produces a server error, restore the last known-good file, inspect the inserted snippets for missing punctuation, and involve the host if the server configuration is the cause.
Verify that the network is active
Do not immediately reactivate every plugin. First confirm the core network behavior:
Recommended Free Tools
- The administration area loads without a PHP or server error.
- The network administration menus are available to the account that created the network.
- The original site’s home page, posts and pages still load at their previous addresses.
- Permalinks resolve without unexpected 404 responses.
- The address format matches the selected subdomain or subdirectory model.
Once these checks pass, reactivate plugins individually or in small, related groups. Test the front end and administration area after each change. A plugin that worked on a single site may not be suitable for network activation, and a plugin can behave differently when it is enabled for one site versus the entire network. Use the plugin’s own documentation or the developer’s support channel for that compatibility decision rather than assuming activation is safe.
What the generated settings mean
WP_ALLOW_MULTISITE
This is the gate that exposes Network Setup. It is the first line you add, and it belongs above the stop-editing comment. It is not a substitute for the network configuration generated by the setup screen.
The network definitions in wp-config.php
The second configuration block tells WordPress that the installation is a network and records values such as the network path and domain. WordPress creates this block for the choices you made. Because those values are installation-specific, copy the generated block rather than retyping an example.
The rewrite rules
The second generated block routes requests for network sites through WordPress. On Apache-style hosting, these rules are placed in .htaccess. A mismatch between the selected URL model and the active rewrite rules can make the dashboard load while site pages return 404 errors, which is why both generated blocks are required.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Troubleshooting common activation problems
Network Setup is missing from Tools
- Open the active installation’s
wp-config.php, not a backup or staging copy. - Check that the line is exactly
define( 'WP_ALLOW_MULTISITE', true );. - Confirm it is above
/* That's all, stop editing! */. - Save the file, clear any host or page cache, and refresh the dashboard.
- Check for a PHP syntax error introduced immediately before or after the line.
The setup screen rejects the URL arrangement
Read the message on the screen and compare it with your current permalink and site address. Do not switch to subdomains merely to bypass a warning. A subdomain network may require DNS and server support that is not present, while a subdirectory network may conflict with an existing path. Correct the underlying URL or hosting condition, then reopen Network Setup.
Pages or posts return 404 after the snippets are pasted
Recheck that the entire generated rewrite block was copied into the correct .htaccess file and that the file is in the WordPress directory used by the live domain. Confirm that pretty permalinks worked before conversion. If the server is Nginx or another non-Apache system, the .htaccess block will not be interpreted; ask the server administrator to apply equivalent rules in the active server configuration.
Subdomains do not resolve
Check DNS records, the host’s domain or alias configuration, and the web server’s routing. A WordPress setting cannot create DNS records. If wildcard DNS is required by your setup, verify that it points to the correct server and that the host permits wildcard subdomains. Allow for DNS changes to propagate according to your provider’s normal behavior, then test a newly created network site.
The dashboard loops back to login
Inspect the generated wp-config.php block for missing quotes, semicolons or duplicated definitions. Check that the domain and path match the address used to access the site, and clear browser cookies for the domain. If the problem began immediately after editing files, restore the backup copy, regain access, and repeat the procedure carefully. Persistent loops can also come from host-level redirects or cookie configuration and require server support.
A plugin breaks the network
Deactivate the last plugin you enabled and test again. Continue reactivation in a controlled order so the conflicting plugin is identifiable. Keep plugins deactivated while diagnosing rather than editing network configuration to accommodate an unknown conflict.
After activation: a safe operating sequence
- Confirm the original site and administrator login work.
- Open the network administration area and review the available network settings.
- Create a test site only after DNS or path routing is ready for the selected network type.
- Visit the test site’s front end and dashboard, checking links, media and login behavior.
- Reactivate plugins gradually, testing after each change.
- Keep the pre-conversion database and file backups until the network has operated normally and the restore path is documented.
Remember that activating the network is a structural change to the existing installation, not a temporary dashboard preference. Future site creation, user permissions, themes and plugins should be managed with the distinction between network-wide administration and an individual site’s administration in mind.
When to stop and get host assistance
Ask your hosting provider or server administrator for help before continuing if you cannot edit the required files, the server does not use Apache-style .htaccess, wildcard DNS is unavailable for a planned subdomain network, or a managed installer imposes its own Multisite process. The WordPress Network Setup screen can generate the application settings, but it cannot change DNS, rewrite a provider’s server configuration or override a host’s product limitations.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
