How to Convert a WordPress Multisite into a Single Site

Want to turn your WordPress Multisite back into a standalone single installation? It’s definitely possible – although the process does require some technical know-how. This step-by-step guide will help you deactivate Multisite and return to a standard WordPress setup.

Important: Always make a full backup of your website – including files and database – before proceeding.

When Does It Make Sense to Switch Back?

WordPress Multisite is great for managing multiple related sites. But if you only need one site or want to simplify management, converting to a single site can be the better solution.

Step-by-Step: Disable Multisite

1. Create a Backup

Before making any changes, back up your full WordPress installation. Use a backup plugin or do it manually via cPanel/FTP and phpMyAdmin.

2. Adjust wp-config.php

Open your wp-config.php file located in the root directory of your WordPress installation and remove the following lines:

define('MULTISITE', true);
define('SUBDOMAIN_INSTALL', false);
$base = '/wordpress/';
define('DOMAIN_CURRENT_SITE', 'localhost');
define('PATH_CURRENT_SITE', '/wordpress/');
define('SITE_ID_CURRENT_SITE', 1);
define('BLOG_ID_CURRENT_SITE', 1);

Then find this line (if it exists):

define('WP_ALLOW_MULTISITE', true);

And change it to:

define('WP_ALLOW_MULTISITE', false);

3. Reset .htaccess

Edit your .htaccess file (also in the root directory) and replace the Multisite rules with the default WordPress single-site rules:

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /wordpress/
RewriteRule ^index\.php$ - [L]

# Add trailing slash to wp-admin
RewriteRule ^wp-admin$ wp-admin/ [R=301,L]

RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /wordpress/index.php [L]
</IfModule>
# END WordPress

Tip: If WordPress is installed in a subdirectory (e.g., /wordpress/), adjust RewriteBase and paths accordingly.

4. Clean Up the Database

Access phpMyAdmin (e.g., via cPanel) and delete the following Multisite-related database tables:

  • wp_blogs
  • wp_blog_versions
  • wp_registration_log
  • wp_signups
  • wp_site
  • wp_sitemeta

Be careful: Do not delete other tables to avoid damaging your content.

5. Log in and Test Your Site

Log back into your WordPress dashboard. Multisite features should now be removed. Test your website thoroughly – plugins, users, media, and links should work as expected.

Need Help with the Migration?

Switching from Multisite to a single site can be tricky, especially for larger or complex setups. The CURIAWEB Support Team is here to help. Simply open a support ticket if you need assistance.

Note: This service is not included in our free support and may be subject to additional charges.

Related Articles

Was this answer helpful? 0 Users Found This Useful (0 Votes)