Sébastien Laframboise

Create a WordPress backup before a risky change

Create a WordPress backup before a risky change

You should create a WordPress backup before making changes whenever your action could alter files, data, or settings that are hard to undo. This includes a theme, a plugin, custom code, a PHP version, cache configuration, or a database operation.

A one-off backup does not replace your automated backups. Instead, it creates a specific restore point just before a given action. If the change causes an error, you can revert to the known site state rather than trying to fix things in a rush.

Changes that require a prior backup

As a precaution, make a full copy before any operation that affects site functionality. A small action in the admin can have broader effects than it appears.

  • Updating WordPress, a theme, or a plugin.
  • Installing, removing, or replacing a plugin.
  • Changing the theme or modifying a child theme.
  • Adding or modifying PHP, CSS, or JavaScript code, or rules in a configuration file.
  • Changing permalinks, cache settings, redirects, or user roles.
  • Cleaning tables, bulk-deleting content, or importing data.
  • Changing the PHP version, hosting settings, or database access.

WordPress recommends backing up files and the database before an upgrade. Its documentation on the updates screen explicitly reminds you of this. This precaution is equally relevant before a manual change that could break the site.

Conversely, you generally don’t need a full backup to fix a typo in a post or change a menu label. However, if your action deletes many items or changes global settings, create a copy before proceeding.

A full backup contains two parts

A WordPress backup before making changes must cover files and the database. The two parts complement each other because they store different content.

Site files

Files include WordPress itself, themes, plugins, uploaded media, and configuration files such as wp-config.php. They therefore preserve the appearance, code, and many of the resources needed for the site to function.

The database

The database stores posts, pages, comments, users, and many settings. Exporting the database usually produces an SQL file. However, it does not by itself protect your images, themes, or plugins.

The official WordPress backup guide notes that a full restore normally requires both files and the database. It also explains that the database is usually located outside the WordPress folder. So downloading only the site files is not sufficient.

To clearly distinguish these two components and avoid an incomplete copy, also consult how to back up WordPress files and database separately.

Checklist to follow just before you make changes

Keep this short procedure handy when you need to edit a live site. It reduces oversights and helps you know exactly which copy to restore if needed.

  1. Define the change. Note what you’re going to change, for example the plugin name, the setting concerned, or the specific file.
  2. Check the most recent automatic backup. It might help, but don’t assume it’s recent enough for your change.
  3. Create a full point-in-time backup. Include files and the database in the same backup set.
  4. Clearly identify the copy. Use a date, time and a description, like «before-theme-change» or «before-product-import».
  5. Store it somewhere other than the site. A copy that only exists on the same server can become inaccessible if the site goes down.
  6. Confirm the backup completed. Check for no error messages and for the expected files or archives.
  7. Prepare the rollback. Know where the restore function is and what access will be required.

An automatic copy remains essential between interventions. If your site doesn’t have one yet, see how to create a reliable automatic WordPress backup. Then use the point-in-time backup as an additional safety net before each sensitive change.

Give your restore point a useful name

A vague name like «backup-final.zip» quickly becomes useless. When a problem occurs, you need to be able to recognize the last good copy without opening multiple archives.

Use a simple, consistent format: date, time, site and reason for the copy. For example: 2026-09-06-1430-example-ca-before-plugin-update.zip. If your tool separates files and the database, keep both archives in the same folder named accordingly.

Also avoid overwriting your only recent copy. Keep at least the restore point created before the change until you’ve validated the site. Your overall policy can then determine how many copies you retain.

After the change: check before deleting the backup

A backup doesn't replace checks after a change. As soon as you finish, open the site in a private window. Then check the important pages, forms, navigation, mobile display, and any functions related to your change.

If you touched a commerce extension, also test the cart, test-mode payment, and transactional emails when your environment allows. If you changed a performance setting, clear the relevant cache before concluding that everything works.

Finally, a useful backup must be restorable. It's best to validate the procedure in a controlled environment, rather than discovering your tool's limits during an outage. The guide test restoring a WordPress backup before an emergency helps you prepare this step.

The right approach: make a copy just before, then perform a targeted change

Create a full backup when the change could affect the site's files, data, or settings. Don't wait to see if the change will cause a problem: by then, the original state might already be gone.

With a recent, clearly identified, and restorable copy, you can work more methodically. Above all, you protect your ability to quickly return to a working version if the result doesn't meet your expectations.