Yes, you can return a WordPress Multisite network to a single-site installation, but it is not a one-click process. You must either convert the main site into a standalone installation or export each subsite and import it into a fresh single-site WordPress, then remove the multisite constants from your configuration.
Background: Why WordPress Multisite Exists
WordPress Multisite is a mode that lets you run multiple websites from one WordPress installation. It was introduced in WordPress 3.0, merging the former WordPress MU (multi-user) project into the core. A network shares the same core files, plugins, and themes across all sites, but each site has its own content, users, and media library. Administrators manage the entire network from a super admin dashboard.
People typically enable Multisite when they need a family of related sites—a university with department blogs, a franchise with location sites, or a company with separate blogs for each product line. It centralizes updates and user management. However, the tradeoffs become apparent over time: a plugin update can break every site, one site’s heavy traffic affects all others, and backups become more complex.
How Multisite Is Structured and Why It Complicates Reversal
In a standard single-site WordPress, the database has tables like wp_posts and wp_options. In Multisite, the main site uses those same tables, but each additional site gets its own set of tables with a numeric prefix: wp_2_posts, wp_3_posts, and so on. The network also adds shared tables: wp_blogs, wp_site, wp_registration_log, and wp_signups.
Simply deleting the multisite constants from wp-config.php will not work. If you remove define('WP_ALLOW_MULTISITE', true); and the MULTISITE and SUBDOMAIN_INSTALL constants, WordPress will try to load the main site’s tables, but it will still see the extra network tables and may throw errors or lose access to the subsites. The subsites’ content is physically in the database, but a single-site WordPress has no mechanism to read wp_2_posts.
Method 1: Convert the Main Site (Least Data Loss)
If you only care about the main site and want to discard the subsites, you can keep the existing database and files. Here is the general process:
- Back up the entire database and the
wp-contentfolder. - Remove the multisite constants from
wp-config.php:define('MULTISITE', true);,define('SUBDOMAIN_INSTALL', false);(ortrue),define('DOMAIN_CURRENT_SITE', ...);, anddefine('PATH_CURRENT_SITE', ...);. Also removedefine('WP_ALLOW_MULTISITE', true);if you want to fully disable the network. - Delete the network-only tables from the database:
wp_blogs,wp_site,wp_sitemeta,wp_registration_log,wp_signups, and all tables with a numeric prefix (wp_2_posts, etc.). - Edit
wp_optionsin the main site: remove theactive_pluginsentries that were network-activated (they are stored inwp_sitemeta, so they may be gone already). Also check thesiteurlandhomeoptions to ensure they point to your single domain. - Log in and verify. You may need to reset permalinks by visiting Settings → Permalinks and saving.
This method is fastest but destroys all subsite content. Only use it if you are certain you no longer need the subsites.
Method 2: Export Each Subsite and Import into a Fresh Install
If you need to keep the subsites as separate single sites, the safest route is to export each one and import it into a brand-new WordPress installation. This avoids database corruption and gives you clean, independent sites.
- On the network admin, go to Sites → All Sites. For each subsite, click its name, then go to its dashboard.
- Use Tools → Export to download an XML file of the site’s posts, pages, comments, and custom fields. Note: the built-in exporter does not include media files (images, PDFs) or theme customizer settings. You will need a plugin like “WordPress Importer” to import media, but the media files themselves must be downloaded separately via FTP from
wp-content/uploads/sites/2/(replace 2 with the site ID). - Create a fresh WordPress installation for each subsite. Install it on the desired domain or subdomain.
- Use Tools → Import in the new site to upload the XML file. The importer will fetch media from the old site if you check “download and import file attachments,” but that requires the old site to remain online during the process.
- Re-upload any missing media files to the new site’s media library.
- Re-configure themes, menus, widgets, and customizer settings manually, since these are not fully exported.
This method preserves all content but requires significant manual work. For a network with many subsites, consider using a migration plugin that can handle multisite to single-site conversions, but always test on a staging copy first.
Common Problems and How to Avoid Them
The most frequent issue is broken media links. Subsite media lives in /wp-content/uploads/sites/N/ and the XML export references those paths. When you import into a new site, the importer rewrites URLs only if you check the appropriate option, but files may still be missing. Always download the entire sites/N folder and upload it to the new site’s uploads folder, then use a search-replace tool to update the URLs in the database.
Another common problem is user data. In Multisite, users are shared across the network. When you export a subsite, the XML includes the author’s display name, but not their password or email. You will need to recreate users manually on the new site. If you had many authors, this can be tedious.
Plugin and theme settings are also not exported. Network-activated plugins are stored in wp_sitemeta; when you convert the main site, those settings are lost. You must re-activate and re-configure plugins individually on the new single site.
Comparing the Two Approaches
Here is a quick comparison to help you decide:
- Main-site conversion: Fast, keeps the existing database and files, but loses all subsites. Best when you only need the primary site.
- Export/import: Slower, but preserves each subsite as an independent site. Best when you need to keep the subsites alive separately.
- Fresh install + manual rebuild: Most reliable for a clean break, but you lose all existing settings and must rebuild from scratch. Good if the network was small or you want to start over.
There is no built-in “convert to single site” button in WordPress. The core team has discussed it but never shipped a tool, so you must choose a manual method or a third-party plugin.
Costs and Risks
If you are on a managed WordPress host, some hosts offer a “multisite to single” migration service, but that may incur a fee. Doing it yourself costs only time, but the risks are real:
- Data loss if you delete the wrong tables.
- Broken links and missing images if you skip the media download.
- SEO impact if you change URLs or lose redirects. Set up 301 redirects from old subsite URLs to new ones.
Always take a full backup before starting, and test the entire process on a staging copy of your site.
Frequently Asked Questions
Can I just remove the multisite constants and keep my subsites? No. Removing the constants disables the network, but WordPress will not read the subsite tables. You will lose access to the subsites and may see errors. You must either keep the network or export the subsites first.
Will my main site’s SEO be affected? If you keep the same domain and URL structure, minimal. If you change any URLs, set up 301 redirects. Also, if you delete subsites that had backlinks, those will 404 unless you redirect them.
Do I need to delete the network tables manually? Yes, if you are converting the main site. There is no core function to clean them. Use phpMyAdmin or a plugin like “WP-CLI” to drop the tables. Be very careful to only delete the network tables and not the main site’s tables.
Can I convert a subsite into a single site without exporting? Technically, you could copy the subsite’s tables and files into a new installation, but you would need to rewrite the table prefixes and fix all URLs. This is error-prone and not recommended for non-developers. Export/import is safer.
What about user passwords? They are not exported. Users will need to reset their passwords on the new site. You can send them a password reset link, or use a plugin to import users with a temporary password.
Is there a plugin that does this automatically? Several plugins claim to convert multisite to single site, but they vary in quality. Always test on a staging site and verify the result before applying to production. The safest approach is still manual export/import.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.
More cards in this drawer
- API Governance for Public Data: What Growing Portfolios Need
- Samsung Smart Speaker Rollable Display: Facts
- HP 9730e: Wide Prints, Not A3 Scans
- What 8888 Does When You Use It as DNS Server
- Credential Manager: Seamless Sign-In Explained
- Enterprise AI Hidden Cost: Data Architecture ROI