Categories
Reviews Web Hosting WordPress WP Engine

WP Engine vs Bluehost: Managed vs Shared WordPress Hosting

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.

I have run client sites on both. Bluehost is where a lot of people start because the first-year price is tiny. WP Engine is where a lot of those same people end up once the site matters. They are different kinds of hosting, so the comparison is less “which is better” and more “which stage is your site at”.

The short version

Bluehost (shared)WP Engine (managed)
Hosting typeShared server with many other sitesManaged WordPress platform
PriceA few dollars a month to start, higher on renewalHigher, see my WP Engine pricing breakdown
Control panelBluehost dashboard and cPanel-style toolsWP Engine User Portal
StagingBasicProduction, staging, and development environments
BackupsVaries by plan and add-onsDaily, 30 days, one-click restore
Caching and CDNPlugin-based, mostly up to youBuilt-in page cache and CDN
SupportGeneral hosting supportWordPress-specialist support
Non-WordPress appsYesNo, WordPress only

Watch the renewal price

Bluehost’s headline price is an introductory rate on a long term. Early in 2026 the entry shared plan was listed around $3.99 a month on a three-year term, renewing at about $9.99. That is still cheap, but budget for the renewal, not the promo, and check current prices before you buy.

Where Bluehost wins

  • Lowest cost for a brand-new or hobby site.
  • Email hosting and non-WordPress apps on the same account.
  • Fine for low-traffic brochure sites that rarely change.

Where WP Engine wins

  • Speed under load, thanks to server-level caching and a CDN instead of a stack of plugins.
  • Real staging you can push live, plus daily backups with 30-day retention and one-click restores.
  • Support that knows WordPress. My experience is in WP Engine Support.
  • Tools like Smart Plugin Manager that update plugins and roll back if a visual check fails.
  • Security handled at the platform level, including managed core updates.

When to move from Bluehost to WP Engine

  • The site makes money and downtime costs more than hosting.
  • Pages get slow when traffic spikes.
  • You are spending hours on caching plugins, malware cleanups, or updates.
  • You manage several client sites and want one dashboard.

If two or more of those are true, the price gap usually pays for itself. I made that case in more detail in Is Managed WordPress Hosting Worth It?. Moving is not hard either: WP Engine’s migration plugin copies the site for you.

A third option

If WP Engine feels like too big a jump, Pressable is another managed host owned by Automattic with a lower entry price. I compared them in Pressable vs WP Engine.

Ready for managed hosting? WP Engine includes staging, daily backups, a CDN, and WordPress-specialist support on every plan.

FAQ

Is WP Engine better than Bluehost?

For business sites that need speed, staging, and expert support, yes. For a low-traffic hobby site on a tight budget, Bluehost is usually enough.

Why is WP Engine more expensive than Bluehost?

WP Engine is managed WordPress hosting. The price covers server-level caching, a CDN, backups, staging, security, and WordPress-specialist support. Bluehost shared hosting puts many sites on one server and leaves more of that work to you.

Can I move my site from Bluehost to WP Engine?

Yes. WP Engine’s Site Migration plugin copies a WordPress site from Bluehost or any other host into a WP Engine environment.

Related

Categories
Web Hosting WordPress WP Engine

WP Engine Multisite: Plan Requirements, Setup, and Domain Mapping

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?

TypeExampleGood for
Subdomainsite1.example.comSites that feel separate, or will get their own domains later
Subdirectoryexample.com/site1Sections 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

  1. Make a manual backup of the environment.
  2. In the User Portal, open the environment from Sites.
  3. Go to Advanced > Utilities.
  4. Under Multisite, choose Convert to Multisite and pick subdomain or subdirectory.
  5. 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.

Related

Categories
Web Hosting WordPress WP Engine

WP Engine Backups: How to Create, Restore, and Download a Backup

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.

Backups are the feature you ignore until the day you need one in a hurry. On WP Engine they are automatic, but there are a few details worth knowing before something breaks: what a restore actually overwrites, how to grab only the database, and how long a download link sticks around.

How WP Engine backups work

  • Automatic: WP Engine takes a daily backup checkpoint of every environment.
  • Retention: backups are kept for 30 days.
  • Manual: you can create a backup any time from the User Portal. Do this before every plugin update, theme change, or launch.
  • Per environment: production, staging, and development each have their own backup list.
  • Exclusions: cache folders, logs, and old backup files are left out.

One rule trips people up: only one backup, restore, or copy can run on an environment at a time. If a button is greyed out, something else is still running.

How to create a manual backup

  1. Log in to the User Portal and open Sites.
  2. Select the environment (production, staging, or development).
  3. Open Backups. You may need to expand Manage in the left menu.
  4. Click Create backup and type a description you will recognize later, like “before WooCommerce 9 update”.
  5. Add a notification email if you want to know when it finishes, then click Create.

The description matters more than it seems. Thirty daily checkpoints all look the same in a list, so a named manual backup is the one you will reach for first.

How to restore a backup

  1. Go to Sites, pick the environment, and open Backups.
  2. Find the backup, click the three-dot menu, and choose Restore.
  3. Decide whether to include the database.
  4. Click Restore.

A restore can take a few minutes or a few hours depending on site size. It is destructive: files that were not in the backup get removed. If you added uploads after the backup was taken, download them first.

Restoring only the database or one folder

The portal restore is all or nothing for files. For anything more surgical you work from a downloaded ZIP:

  • Database only: download the backup, unzip it, and find wp-content/mysql.sql. Drop the current tables in phpMyAdmin (or over SSH), import the file, then purge the cache.
  • One folder: download and unzip the backup, then upload the folder over SFTP or SSH. Reset file permissions and clear the cache.

WP Engine does not support restoring individual database tables. If you only need one table, import the full dump into a local site (I use Local for this) and copy the rows across.

How to download a backup

  1. On the Backups page, open the three-dot menu next to a backup.
  2. Choose Prepare ZIP.
  3. Pick a full backup or a partial one: database, themes, plugins, media uploads, or other files.
  4. When the ZIP is ready, click Download ZIP.

Prepared ZIPs stay available for 7 days. WP Engine does not push backups to outside storage on a schedule, so if you want an off-host copy, download one now and then or use a plugin that sends backups to S3 or similar.

Using a backup to copy between environments

You can push a backup to another environment with Copy Environment and the “Push to” option. This is the normal way to move a tested staging site to production, or to pull production down to staging before you start work.

My backup habits on WP Engine

  • Manual backup before every update day, even with automatic updates on.
  • Named backup right before a launch, alongside the Go Live Checklist.
  • A downloaded database dump once a month for anything that sells online.
  • Check that notification emails are not landing in spam. They often do.

Not on WP Engine yet? Every plan includes daily backups with 30-day retention, one-click restores, and staging environments.

FAQ

How long does WP Engine keep backups?

WP Engine keeps 30 days of backups. Daily checkpoints run automatically, and you can create manual backups whenever you want.

Can I restore just the database on WP Engine?

Not from the restore button. Download the backup ZIP, take the mysql.sql file from wp-content, and import it through phpMyAdmin or SSH after dropping the current tables.

How long are backup downloads available?

A prepared ZIP is available for 7 days, then it expires and you have to prepare it again.

Related

Categories
Web Hosting WordPress WP Engine

How to Point Your Domain to WP Engine (DNS Records and SSL)

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.

Pointing DNS is the last step of moving a site to WP Engine, and the one most likely to cause a nervous hour. It is not hard. You add the domain in the portal, change two records at your DNS host, and wait. Here is the exact order I use.

Before you touch DNS

  • Make sure the site is fully migrated and working on its temporary WP Engine URL. The migration plugin guide covers that part.
  • If you bought Global Edge Security, enable it first. It changes which DNS values you use.
  • Lower the TTL on your current records to 300 seconds a day ahead if your DNS host allows it. Changes then spread faster.
  • Write down your current MX and TXT records. You will not change them, but you want a copy.

Step 1: Add the domain in the User Portal

  1. Go to Sites and select the production environment.
  2. Open Domains (under Manage if the menu is collapsed).
  3. Click Add domain, enter the root domain, and choose Add and set up domain.
  4. Verify ownership when asked.
  5. Pick automatic setup (handled by Entri for supported DNS providers) or manual setup.

Your exact CNAME target and IP addresses are under View DNS Details in the three-dot menu next to the domain. Use those values, not ones from a blog post.

Step 2: Set the DNS records

RecordNamePoints toNotes
CNAME (flattened)@ or example.comYour WP Engine CNAMEPreferred for the root if your DNS host supports CNAME flattening
A (two records)@The two WP Engine IPsUse this if flattening is not available. Add both IPs.
CNAMEwwwexample.comIf www already points at the root, leave it
CNAMEblog, shop, etc.Your WP Engine CNAMEFor any subdomain on the same site

Delete the old A record for the root before you add the new one. Also delete any AAAA (IPv6) records on the root unless you use Cloudflare, because WP Engine does not serve over IPv6 and a stale AAAA record sends some visitors to the old host.

If your registrar only lets you change nameservers, move DNS to Cloudflare and use its CNAME flattening. My WP Engine and Cloudflare post explains how the two fit together.

Step 3: Wait, then check

  • Most changes show up within minutes. The official ceiling is 48 hours.
  • Automatic setup through Entri uses a one-hour TTL, so it usually settles in about an hour.
  • Use Refresh Status on the Domains page, or check from several locations at WhatsMyDNS.net.

SSL

Once DNS points at WP Engine’s network, SSL and HTTPS are turned on for you. A red certificate warning in the first few minutes is normal while things propagate. If you need a third-party certificate instead, add it on the SSL page in the portal.

Things that go wrong

  • Email stops working: automatic setup can remove records it sees as conflicting. Review the change list before you approve it and compare it to your saved MX and TXT records.
  • Half your visitors see the old site: an old A or AAAA record is still there. Remove it.
  • Mixed content warnings: the database still has http:// links. Run a search and replace for the old URL.
  • Cached old pages: clear the WP Engine cache after the switch.

Moving to WP Engine? Free SSL, a global CDN, and automatic domain setup for supported DNS providers are included on every plan.

FAQ

Should I use a CNAME or an A record for WP Engine?

WP Engine recommends a flattened CNAME for the root domain. If your DNS host cannot flatten CNAMEs, use two A records pointing to both WP Engine IP addresses.

How long does DNS take to point to WP Engine?

Usually minutes, sometimes up to 48 hours. Automatic setup through Entri uses a one-hour TTL, so it often finishes in about an hour.

Does WP Engine give me a free SSL certificate?

Yes. Once DNS points to WP Engine, SSL and HTTPS are enabled automatically. You can also upload a third-party certificate on the SSL page.

Related

Categories
Pressable Web Hosting WordPress WP Engine

How to Change Your PHP Version on WP Engine and Pressable

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.

A PHP upgrade is one of the cheapest speed boosts a WordPress site can get, and on managed hosts like WP Engine and Pressable it is a dropdown, not a server rebuild. The risky part is not the switch. It is the old plugin that throws a fatal error on the new version. Here is how to change PHP on both hosts and how to test first.

Why bother upgrading PHP

  • Newer PHP versions run WordPress faster with no code changes.
  • Old versions stop getting security fixes.
  • Your host will eventually move you anyway, on its schedule, not yours.

Changing PHP on WP Engine

WP Engine currently lists PHP 7.4, 8.2, and 8.4 (8.4 in beta for WordPress 6.7 and newer). 7.4 is on a temporary extended support period.

  1. Open Sites in the User Portal and select the environment.
  2. In the Updates section, click the PHP version number.
  3. Choose the new version and click Confirm.

The change happens in place, with no downtime and no DNS changes. Each environment has its own PHP setting, and copying an environment does not copy its PHP version, so check staging separately.

Test drive before you switch

WP Engine’s PHP Test Driver lets you preview a different version without changing it for visitors. Click Preview PHP on the environment, log in to WP Admin, and a Test Drive banner confirms you are on the alternate version. Only your browser sees it. On multisite subsites you can add ?wpengine_php=8.2 to the URL while logged in as an admin.

Changing PHP on Pressable

  1. Log in to MyPressable and open the site.
  2. Choose the version from the PHP Version dropdown.
  3. The change takes effect right away.

Pressable also lets you set a default PHP version for every new site on the account, and change PHP on many sites at once with Bulk Operations. That second one is handy for agencies, but only after each site has been tested.

A safe upgrade routine for either host

  1. Copy production to staging (WP Engine, Pressable).
  2. Update WordPress core, plugins, and themes on staging. Premium plugins often hide updates in WP Admin, so check with their vendors.
  3. Switch staging to the new PHP version.
  4. Click through the front end, checkout, forms, and the admin. Watch the error log.
  5. If it is clean, switch production and repeat the quick check.

What if something breaks?

On WP Engine you can flip back to the previous version while it still exists on the server, but treat that as a stopgap. On Pressable, pick the old version from the same dropdown. Either way, the real fix is updating or replacing the plugin or theme that failed.

Forced upgrades

WP Engine supports each PHP version for about two years of full support, then critical security fixes only, and removes it after roughly three years. Sites still on a retired version get upgraded automatically, and that cannot be deferred. They email your technical contacts first, so keep those contacts current. Pressable offers current PHP releases too, so there is little reason to sit on an old one. Upgrading on your own timeline is less stressful.

Want PHP updates without the server work? Both of these hosts let you switch PHP versions from a dropdown and test on free staging first.

FAQ

Does changing the PHP version cause downtime?

No. On both WP Engine and Pressable the switch happens in place. A plugin that is not compatible can still break the site, which is why testing on staging first matters.

Which PHP versions does WP Engine support?

WP Engine lists PHP 7.4 (on temporary extended support), 8.2, and 8.4 (beta, for WordPress 6.7 and newer).

Can I change PHP on many Pressable sites at once?

Yes. Pressable’s Bulk Operations feature can update the PHP version across multiple sites, and you can set a default version for new sites.

Related