Some links on this page are affiliate links. If you sign up through them I may earn a commission at no extra cost to you.
WordPress Multisite runs many sites from one WordPress install. It is great for a network of similar sites, like campus departments or franchise locations, and a headache if you use it when separate sites would do. WP Engine supports it well, but not on every plan, and converting has a few steps you cannot skip.
Which WP Engine plans support Multisite
- Included on Premium plans.
- Available as an extension on shared plans from Growth upward, added from the Modify Plan page.
- Not available on Lite or Startup plans.
- Essential plans support it only as an extension on plans with three or more sites.
Plan names change from time to time. My WP Engine plans comparison has the current lineup.
Subdomain or subdirectory?
| Type | Example | Good for |
|---|---|---|
| Subdomain | site1.example.com | Sites that feel separate, or will get their own domains later |
| Subdirectory | example.com/site1 | Sections of one brand, sharing SEO authority |
Pick carefully. Switching types after you have content is a migration, not a setting.
How to convert an environment to Multisite
- Make a manual backup of the environment.
- In the User Portal, open the environment from Sites.
- Go to Advanced > Utilities.
- Under Multisite, choose Convert to Multisite and pick subdomain or subdirectory.
- Click Convert Environment.
Do it on staging first if you have an existing site with content.
Mapping custom domains
For the main site, add the domain in the User Portal, point DNS, then update the database values (siteurl, home, wp_site, wp_sitemeta, wp_blogs, and subsite tables) and DOMAIN_CURRENT_SITE in wp-config.php. WP Engine recommends the non-www version.
For subsites with their own domains, you need WP Engine’s Advanced Network. Point each domain with a CNAME, A record, or wildcard CNAME, then set the subsite address under Network Admin > Sites. Native WordPress domain mapping is the way to go; skip the old mapping plugin.
Copying Multisite between environments
- Copy Environment runs a search and replace for main site and subsite URLs, so set up domains first.
- Tables with the same names on the destination get overwritten.
- Old domain-mapping plugin tables are not copied.
- You cannot copy a single subsite this way. Use WordPress export and import, then reinstall themes and plugins.
Switching back to a single site
WP Engine lets you reverse it: Utilities > Convert to Single Site, choose whether to keep or delete subsite tables, and click Disable Multisite. Back up first, since deleting subsite tables cannot be undone.
Should you use Multisite at all?
Use it when sites share users, themes, and plugins and one team runs them all. Skip it when each site has its own owner, plugins, or update schedule. Separate installs are easier to move, sell, or hand off.
Planning a Multisite network? WP Engine includes Multisite on Premium plans and offers it as an add-on on others, with staging to test the conversion first.
FAQ
Does WP Engine support WordPress Multisite?
Yes. It is included on Premium plans and available as an extension on shared plans from Growth up, and on Essential plans with three or more sites. It is not available on Lite or Startup.
Can I convert a WP Engine multisite back to a single site?
Yes. Go to Utilities, choose Convert to Single Site, decide whether to keep subsite tables, and click Disable Multisite.
Can I map a custom domain to a multisite subsite on WP Engine?
Yes, with WP Engine’s Advanced Network. Point the domain with a CNAME or A record, then set the subsite address under Network Admin, Sites.