Product facts · Info
Does WP Engine Include Backups? Frequency, Retention and Restores
Short answer
Yes, WP Engine includes backups on all plans as of November 2026. It makes a daily automatic backup checkpoint for each environment and keeps 30 days of backups in the User Portal. You can also create a manual checkpoint at any time and restore a checkpoint from the Backups page, with or without the database.
Key takeaways
- WP Engine makes a daily automatic backup checkpoint for production, staging, and development environments.
- WP Engine keeps 30 days of backups in the User Portal, as of November 2026.
- Every backup includes WordPress core files, themes, plugins, and the database.
- A restore is destructive, so files added after the checkpoint are removed when you restore it.
- A prepared backup ZIP stays available to download for up to 7 days.
- WP Engine does not auto-export its backups to another service, so keep your own offline copy too.
Does WP Engine include backups?
Yes, WP Engine includes automatic daily backups and manual backup checkpoints.
WP Engine's own support page says it has both automated and manual backups, with no bulky third-party application needed (Backup and Restore). That page is the main source for this guide, checked in November 2026.
A backup is a copy of your site files and database that you can put back after a bad update or a mistake.
WP Engine stores its backups offsite, so a problem on your live server does not take the backup with it. See how to back up WordPress for the two parts every full backup needs.
How often does WP Engine back up your site?
WP Engine makes a daily automatic backup checkpoint for each environment.
The checkpoint runs once a day without you doing anything. WP Engine's support page says daily backup checkpoints are made automatically, and it advises a fresh manual checkpoint before updates (Backup and Restore). Backups exist for all environments by default: Production, Staging, and Development, each with its own backup list.
The backups are stored offsite on Amazon S3 in the same region that the website is hosted in, encrypted in transit and at rest.
Amazon's S3 docs say server-side encryption with Amazon S3 managed keys is the base level of encryption for every bucket (Protecting data with server-side encryption). WP Engine says the backup location for the Tel Aviv data center is Frankfurt, Germany.
How long does WP Engine keep backups?
WP Engine keeps 30 days of backups in the User Portal as of November 2026.
That is the figure on WP Engine's support page, stated twice on the same page (Backup and Restore). If you need a point older than 30 days, the page says to contact support, but it does not promise that an older point can be found.
| Backup fact | What WP Engine says as of November 2026 |
|---|---|
| Automatic frequency | Daily checkpoint for each environment |
| Retention in the User Portal | 30 days |
| Manual checkpoints | Yes, any time from the Backups page |
| Storage | Offsite on Amazon S3, same region as the site |
| Encryption | Encrypted in transit and at rest |
| Prepared ZIP download window | Up to 7 days |
| Restore time | A few minutes to several hours |
Treat 30 days as your working window. If a problem is found after 30 days, the checkpoint you need may already be gone.
Which plans include WP Engine backups?
Daily and on-demand backups are listed under “All plans include” on WP Engine's pricing pages.
WP Engine's eCommerce pricing page lists “Daily & on-demand backups” in its all-plans section (Plans & Pricing for eCommerce Solutions). Its support page also says backups exist for all environments by default, with no plan named as an exception.
That matters because some hosts limit daily or on-demand backups to higher plans. On WP Engine, the backup feature is not presented as a paid add-on in the pages checked for this guide. See is managed WordPress hosting worth it for the wider trade-offs beyond backups.
What does a WP Engine backup include?
Every WP Engine backup includes WordPress core files, themes, plugins, and the database.
WP Engine lists those 4 items as the contents of every backup, manual or automated (Backup and Restore). That is the full set you need to rebuild a normal WordPress site.
The database part is the one people miss. WP Engine's restore page says the database includes all posts, pages, users, custom post types such as store orders, and certain settings. WordPress docs say a WordPress backup has two parts, database and files, and you need both (Backups).
What is left out of a WP Engine backup?
WP Engine leaves out temporary files, stock files, local backup files, log files, and obsolete software.
Those are the 5 buckets WP Engine names on its support page (Backup and Restore). The aim is to skip files that can be made again.
Examples from the page include:
- Cache and temporary files, such as
wp-content/cache - Sample files, such as
sample-wp-config.php - Local backup files, such as
.bakfiles andwp-content/backups - Log files, such as
.logfiles andwp-content/.logs - Obsolete software, such as timthumb
WP Engine also lists excluded paths such as wp-content/uploads/sucuri, wp-content/snapshots, and UpdraftPlus and BackupBuddy ZIP files. Most uploads are still backed up.
How do you create a manual backup on WP Engine?
Open the environment's Backups page and click “Create backup” before you make a change.
WP Engine's support page gives these steps (Backup and Restore):
- From the Sites page, select the environment name.
- Click Backups. You may need to expand the Manage dropdown first.
- Click Create backup.
- Add a backup description, such as “Before theme update”.
- List emails, separated by commas, to receive a notification when the backup completes.
- Click Create.
Use a clear description. Thirty daily checkpoints look alike in a list, while a named checkpoint is easy to find later. A status banner shows while a backup is in progress, and the Create backup button is disabled until it finishes.
How do you restore a backup on WP Engine?
Pick the checkpoint on the Backups page, open its three-dot menu, and select Restore.
WP Engine's support page gives these steps (Backup and Restore):
- From the Sites page, select the environment name.
- Click Backups. You may need to expand the Manage dropdown first.
- Find the backup in the list and expand its three-dot “more actions” menu.
- Select Restore.
- Choose whether to restore with the database, and list notification emails.
- Click Restore.
The automated restore can take a few minutes to several hours, depending on site size and file count, and WP Engine sends an email when it completes.
Why the restore choice matters
A restore is destructive, so it overwrites all content to match the backup point you pick.
Files that were not in that backup point are removed on restore. That includes posts, orders, uploads, and changes made after the checkpoint, so export anything new before you restore.
Restoring with the database brings back posts, pages, users, and store orders as they were at that point. Partial database selection is not an option in the portal restore. Developers can also restore through WP Engine's API, where the database is restored by default and a checkpoint is created first by default (Restore a backup).
How do you download a WP Engine backup as a ZIP?
Prepare a full or partial ZIP from the Backups page, then click Download ZIP once it is ready.
WP Engine's support page says backups can be downloaded as a ZIP archive, and can be requested as full or partial (Backup and Restore). A partial ZIP is useful for a large site, or when you only need one part.
The Prepare ZIP options are:
- Full Backup: all files and the database
- Entire database: the database file,
/wp-content/mysql.sql - Themes: the themes directory,
/wp-content/themes/* - Plugins: the plugins and must-use plugins directories
- Media uploads: the uploads directory,
/wp-content/uploads/* - All other files: all other site files not listed above
Partial database selection is not an option with this tool, so you cannot download only some tables. Once a backup is prepared, its Download ZIP link stays available for up to 7 days, and it cannot be deleted by hand.
To restore only one folder or only the database, download the ZIP, unzip it, and put the part you need back by hand with SFTP, SSH Gateway, or phpMyAdmin. For a plugin-based comparison, see UpdraftPlus vs your host's backups.
The same plugin route is covered step by step in how to restore a backup with UpdraftPlus.
Can you restore a backup to a different environment?
Yes, use the copy site feature with Push to, push type Custom, and Push from Backup point.
WP Engine moved this job out of the Restore menu and into its copy site feature (Backup and Restore). The steps on the support page are to follow the copy site instructions, select Push to, select the destination environment, select Custom for the push type, then select Backup point and pick the backup point.
This is the safe way to check an old checkpoint: push a production backup into staging and look at it there, instead of overwriting production.
Do you still need an offsite copy of your own?
Yes, keep your own offline copy even though WP Engine backs up your site daily.
WP Engine's terms say it is your responsibility to maintain offline backups at all times, and that you should keep a complete and accurate copy in an offline location independent of the service (Terms of Service). The terms page was updated January 1, 2026.
The same terms say WP Engine will only back up customer content to the extent described in an order, and does not guarantee there will be no loss or corruption of data.
There is also no automatic export. WP Engine's support page says there is no way to automatically export WP Engine backups to another service such as Amazon S3 (Backup and Restore). You have to download a ZIP yourself, or use your own backup integration to send a copy elsewhere.
WordPress docs advise keeping at least 3 to 5 recent backups, with copies stored in different locations (Backups).
If you cancel, act before the plan ends. WP Engine's terms say you lose access to the services and the User Portal after termination, and WP Engine will not help with migration tasks after that point.
What mistakes should you avoid?
Do not treat the 30-day portal window as a long-term archive.
The mistakes below come from the limits on WP Engine's own pages:
- Waiting more than 30 days to notice a problem, then finding the checkpoint gone.
- Restoring without exporting new posts, orders, or uploads first, then losing them because the restore is destructive.
- Assuming a files-only download covers you, when the database holds your posts and orders.
- Installing a local backup plugin that WP Engine disallows, such as WP DB Backup or BackupWordPress, instead of using the portal or an offsite tool.
- Storing your only extra copy on the same server, where the same failure can take both copies.
WP Engine's disallowed plugins page says it discourages backup plugins because they bloat the site and can store files in an insecure way (Manage List of Disallowed Plugins). For the wider choice, see cPanel backups vs plugin backups. Use the portal for quick restores, and keep a separate offsite copy for the long term.
Frequently asked questions
Does WP Engine back up staging and development sites too?
Yes. WP Engine says backups exist for all environments by default, including production, staging, and development. Each environment has its own backup list in the User Portal, so check the environment you mean before you restore or download anything.
Can I restore only the database on WP Engine?
Not with the one-click restore. The portal restore either includes the database or it does not, and you cannot pick specific tables. To restore only the database, download a backup ZIP, find wp-content/mysql.sql inside it, then drop the current tables and import that file through phpMyAdmin or SSH Gateway.
How long does a WP Engine restore take?
WP Engine says an automated restore can take a few minutes to several hours, depending on the size of your site and the number of files. You list notification emails when you start the restore, and WP Engine sends an email when it completes. Do not start a second restore while one is still running.
Can I download a WP Engine backup and keep it forever?
You can download a prepared ZIP and keep that file on your own storage for as long as you like. The download link itself stays available on the Backups page for up to 7 days. Download the file inside that window, then store it somewhere separate from your live server.
What happens to WP Engine backups if I cancel my plan?
WP Engine's terms say you lose access to the services and the User Portal after termination, and WP Engine will not help with migration tasks after that point. Download a full backup ZIP for every environment before you cancel, and keep those files offline.
Does WP Engine charge extra for backups or restores?
The WP Engine pages checked for this guide list daily and on-demand backups as included, and they list no separate restore fee. No restore charge was stated on the support page or the pricing page checked in November 2026, so confirm the current terms on your own plan before you rely on that.
Sources
- Backup and Restore WP Engine Support
- Plans & Pricing for eCommerce Solutions WP Engine
- Terms of Service WP Engine
- Backups WordPress Documentation
- Restore a backup WP Engine Developers
- Protecting data with server-side encryption Amazon S3 Documentation
- Manage List of Disallowed Plugins WP Engine Support
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.
