Hosting · Guide
How to Delete a Site From WP Engine (Step by Step)

Short answer
Download a backup first, point any live domain elsewhere, then open the WP Engine User Portal, select the site and delete each environment it contains. Deleting a site does not lower your bill, so change or cancel your plan separately.
Key takeaways
- A WP Engine site holds up to three environments.
- Download a full backup before deleting anything.
- Move or remove domains before deleting production.
- Only Owner or Full users can usually delete environments.
- Deleting a site does not cancel or reduce your plan.
How do you delete a site from WP Engine?
Log in to the WP Engine User Portal, open Sites, choose the site, delete each of its environments (production, staging and development), and confirm when asked.
On WP Engine, a site is a container for up to three environments. Each environment is a separate WordPress install with its own files, database and backups.
Deleting removes the environment's files, database and its backups from WP Engine. That is why the most important step happens before you click anything: download a backup.
Deleting a site also does not cancel your plan. Your bill stays the same unless you change or cancel the plan separately, which we cover at the end.
| What you want | What to do |
|---|---|
| Remove a test or staging copy only | Delete just that environment |
| Remove a whole site | Delete every environment in it |
| Move the site to another host | Migrate first, then delete |
| Stop paying WP Engine | Delete sites, then change or cancel the plan |
| Keep a copy for later | Download a backup before deleting |
Who can delete a site on WP Engine?
Only User Portal users with enough access, usually the account Owner or a Full user, can delete environments; partial users often cannot see the option.
WP Engine explains its permission levels on the User Portal users and roles page. If the delete option is missing, your role is the most likely reason.
Ask the account owner to upgrade your access or to carry out the deletion. Agencies often hold the owner role on behalf of clients, so check who that is first.
Step 1: Decide what you are actually deleting
Write down the site name, each environment name and the domains attached to them, so you delete the right thing and know what will stop working.
Environment names look similar and are easy to mix up. Deleting production instead of staging is the most common and most painful mistake.
Open the site in the portal and note:
- The production environment and its domains.
- Any staging or development environments.
- Whether any live domain still points here.
- Whether a newer copy of the site exists elsewhere.
If you only want to remove a staging copy, our guide on how to delete a WordPress staging site covers that case.
Step 2: Download a full backup
Open the environment, go to Backups, create a fresh backup and download it as a zip, then save it somewhere outside WP Engine.
The WP Engine User Portal overview shows where the backup tools live. You can usually choose a full backup that includes files and the database.
Download a backup of every environment that holds anything you might want later. Once an environment is deleted, its stored backups go with it.
Open the zip after downloading. Check that it contains the wp-content folder and a database file. A backup you never checked is only a hope.
If you are curious how WP Engine's own backups work, see our guide on whether WP Engine includes backups.
For extra safety, keep a separate database export too. If you use SSH, the WP-CLI db export command creates one in seconds. Our guide on how to back up a WordPress database explains the options.
Step 3: Point domains away or remove them
If the site is moving elsewhere, update DNS to the new host first; if the site is closing, remove the domain from the environment and tidy up DNS records.
Deleting an environment while a live domain still points at it leaves visitors with an error page. Plan that change before you delete.
For a migration, follow this order:
- Copy the site to the new host.
- Test it on a temporary address.
- Change DNS to point at the new host.
- Wait for DNS to update worldwide.
- Only then delete the WP Engine environment.
DNS changes can take a while to spread. Our guide on how long DNS propagation takes explains what to expect.
If you use your own Cloudflare account, remove records that still point at WP Engine. Cloudflare explains how in its guide to managing DNS records. Old records make troubleshooting confusing later.
Step 4: Delete the environments
In the User Portal, open the site, select the environment, find the Delete environment option, type the confirmation text if asked, and confirm.
The exact location of the button can move as WP Engine updates the portal. It is usually on the environment's overview page or in a menu next to the environment name.
Repeat this for each environment you want to remove. When a site has no environments left, it no longer appears as an active site in your list.
WP Engine's sites and environments documentation explains how sites and environments relate and is the best place to check the current steps.
Take your time on the confirmation screen. Read the environment name again before you click the final button.
Step 5: Check that the site is gone
Refresh the Sites list, confirm the environments no longer appear, and visit the old temporary WP Engine address to make sure it no longer loads the site.
Also visit your real domain. If it was migrated, it should load from the new host. If the site was closed, it should show whatever you planned, such as a holding page.
Search for any leftovers, such as:
- SFTP users you created for that environment.
- Extra portal users who only needed this site.
- Third-party services that pinged the old address.
- Uptime monitors still checking the domain.
What happens to your billing after deleting a site?
Deleting a site frees a site slot on your plan but does not lower your bill; to pay less, you need to change to a smaller plan or cancel.
WP Engine plans are priced by the number of sites and resources. Freeing a slot lets you add a different site later without upgrading.
If you are leaving WP Engine entirely, our guide on how to cancel WP Engine and get a refund covers the cancellation steps and the refund window.
Before cancelling, also look at add-ons like Global Edge Security or extra storage. These may be billed separately from your plan.
If price is why you are leaving, our guide to WP Engine renewal prices explains how renewals compare with first-term pricing.
Can you recover a site after deleting it from WP Engine?
Assume you cannot; deleted environments and their stored backups are generally gone, so your own downloaded backup is the only safe way back.
Contact WP Engine support right away if you deleted the wrong environment. Act quickly, but do not count on a recovery.
With your own backup, you can rebuild the site on a new WP Engine environment or anywhere else. Our guide on how to restore a WordPress site from backup walks through that.
What is the difference between deleting an environment and a site?
Deleting an environment removes one WordPress install, such as staging, while the site stays; a site is only fully gone when all of its environments are deleted.
This is useful when you only want to tidy up. You can delete an old development copy and keep production running untouched.
| Action | Production stays? | Backups of deleted copy kept? |
|---|---|---|
| Delete staging only | Yes | No |
| Delete development only | Yes | No |
| Delete production only | No | No |
| Delete all environments | No | No |
Some teams reuse an empty site container by adding a fresh environment later. Others prefer to delete everything and start clean. Either works.
What should you do before deleting if you might come back?
Download backups of every environment, export your content, keep a record of plugin licenses and settings, and save any custom code in a separate place.
A WordPress export gives you posts and pages in a portable format. The Tools Export screen documentation explains what it includes and what it leaves out.
Save license keys for premium plugins and themes. Some licenses are tied to a domain and need to be released before you can use them on a new site.
Keep a note of the PHP version and key settings too. Our guide on how to migrate a WordPress site to WP Engine is useful if you later move a backup back onto WP Engine.
Frequently asked questions
Does deleting a site on WP Engine cancel my plan?
No. Deleting a site only frees a site slot. Your plan and its price stay the same until you downgrade or cancel through your account settings or with WP Engine's billing team.
Why can't I see the delete option in the WP Engine portal?
Your User Portal role probably does not allow it. Owners and Full users can usually delete environments, while partial users cannot. Ask the account owner to delete it or to give you more access.
Are WP Engine backups kept after I delete a site?
You should assume they are not. Stored backup points are tied to the environment, so they go when it is deleted. Download a full backup zip and keep it somewhere outside WP Engine before you delete.
Can I delete only the staging environment on WP Engine?
Yes. Each environment can be deleted on its own. Removing staging or development leaves production running, which is handy for tidying up old test copies without touching the live site.
What happens to my domain when I delete a WP Engine site?
Your domain registration is not affected, but if DNS still points at WP Engine, visitors will see an error. Point the domain to the new host, or to a holding page, before deleting the production environment.
Sources
- Sites and Environments WP Engine
- User Portal Overview WP Engine
- User Portal Account Users and Roles WP Engine
- Tools Export Screen WordPress.org Documentation
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


