DD DevDome Track. Protect. Grow.
Site Care

WordPress Update Broke Your Site? How to Roll Back Safely

Five plugins updated overnight and the checkout is dead. You do not need the whole backup. You need the one update that did it, and a way to undo it.

On this page
  1. Step 1: find out what changed
  2. Step 2: get the site back
  3. Step 3: roll back the one thing
  4. Step 4: when you really do need the backup
  5. When the culprit is a theme or core
  6. What a restore point actually saves
  7. Step 5: make the next one reversible

When a WordPress update broke your site, the fastest fix is almost never the full backup. It is finding the single update that caused it and putting that one thing back. A full restore from last night also deletes every order, comment and edit since then; a rollback of one plugin keeps all of that. Here is how to identify the culprit, undo it even when the admin is a white screen, and set up restore points so next time is one click.

Step 1: find out what changed

Three places tell you:

The recovery email. When a plugin or theme causes a fatal error, WordPress emails the admin a recovery mode link that names the plugin. Open it; the link logs you in with the broken plugin paused.

The activity log. A log that records plugin and theme updates with timestamps shows exactly which five updated overnight and in what order. DevDome Activity Log records those events locally and for free. We make it, so weigh that; any log of plugin changes does the job, and the point is to have it running before the update.

The updates and plugins screens. If you can reach the admin, the plugins list shows versions and the site health screen sometimes names the error. Match the version numbers against what updated.

If you cannot reach the admin and have no email, the host’s error log names the file that fatalled, and the file path contains the plugin folder.

Step 2: get the site back

If the admin works: go to the next step and roll back.

If it is a white screen or fatal: use FTP, SFTP or the host’s file manager. Navigate to wp-content/plugins and rename the suspect plugin’s folder, adding -off to the name. WordPress treats a missing folder as a deactivated plugin and the site comes back. For a theme, rename its folder and WordPress falls back to a default theme.

If it is the database connection error: that is rarely an update. Check with the host before touching anything.

Step 3: roll back the one thing

Install the previous version of the plugin or theme over the current one:

  • For WordPress.org plugins, the plugin page’s Advanced View lists every previous version as a zip. Download the one you had, upload it through Plugins, Add New, Upload, and choose to replace the current version.
  • For premium plugins, the vendor’s account area usually keeps old versions. Download and upload the same way.
  • If you renamed the folder in step 2, delete the renamed folder once the old version is installed.

Then check the thing that broke. If it works, you are done; note the plugin and version and watch for the vendor’s fix before updating again.

If it still breaks, you rolled back the wrong one. Go back to the list from step 1 and try the next.

Step 4: when you really do need the backup

Restore a full backup only when several things broke at once, when a core update failed halfway, or when you cannot identify the cause. Before restoring, export anything created since the backup: orders, form entries, posts. Restore, then re-import what you can.

A partial restore, files only or database only, is often enough: a broken plugin update is files, so restoring last night’s plugins folder fixes it without touching today’s orders in the database.

When the culprit is a theme or core

Plugins cause most breakages, but not all. A theme update that removed a template or changed a function name produces a fatal on the front end while the admin still works; rename the theme folder to drop to a default theme, then install the previous theme version the same way as a plugin. A core update that failed halfway leaves the site reporting one version while running a mix of files; the Updates screen’s reinstall option replaces every core file with the official copy for the version WordPress believes it is, which usually fixes it. If the admin is unreachable after a core update, uploading the core files by FTP from the official package for that version, without touching wp-content or wp-config.php, does the same job by hand.

What a restore point actually saves

The difference between a backup and a restore point is scope and speed. A nightly backup is the whole site as of last night. A restore point is the site as of the minute before this update, which means rolling back loses nothing that happened in between, and because it is taken moments earlier it restores in moments too. The automatic rollback adds the last step: a check after the update that the site still answers, and an automatic return to the restore point if it does not, so an overnight auto-update that breaks the site undoes itself before anyone is awake.

Step 5: make the next one reversible

Restore point before every update. A tool that snapshots the site before each update and rolls back automatically if the site fails afterwards turns this whole post into a non-event. DevDome Backup & Migration is built around exactly that: a restore point before every update, automatic rollback if the site breaks, plus full backups and migration. We make it; the principle of a pre-update snapshot is what matters.

Update one at a time. Bulk updates give you five suspects. One update, check the site, next update, gives you one.

Stage on a copy if you can. A staging site that mirrors production catches most breakages before they reach visitors.

Be selective with automatic updates. Turn them on for plugins with a long clean record and security plugins that need to be current. Leave the page builder and the checkout off auto-update and do those by hand with a check.

Monitor. An uptime monitor that checks content, not just status, tells you within minutes if an overnight auto-update broke something, instead of the customer telling you at nine.

The next time an update breaks the site, it should be a two-minute rollback. If it is still an afternoon, one of the steps above is missing.

Related reading: The Monthly WordPress Maintenance Checklist (One Hour, Twelve Items).

Disclosure: DevDome publishes this blog and makes the products it mentions. We describe what they do rather than promise results.

Key takeaways

  • Find which update did it before restoring anything. The activity log or the updates screen tells you what changed and when.
  • Roll back the one plugin or theme to its previous version. A full backup restore loses everything that happened since.
  • If the site is a white screen, rename the plugin folder over FTP or the host file manager to deactivate it, then roll back.
  • A restore point before every update makes this a one-click undo instead of an afternoon.
  • Update in stages: one at a time, check the site, next. Bulk updates are how five suspects become one.

Sources

  1. WordPress.org: Common WordPress errors : the white screen and fatal error recovery steps
  2. WordPress.org: Recovery mode : the recovery link WordPress emails on a fatal error
  3. WordPress.org: Plugin advanced view and previous versions : where previous plugin versions are downloaded

Links last checked October 17, 2026.

Frequently asked questions

How do I get into WordPress after an update caused a white screen?

You usually cannot through the admin. Use FTP, SFTP or the host's file manager to rename the folder of the plugin that updated, which deactivates it. The site comes back, you log in, and you install the previous version of that plugin.

Where do I get the previous version of a plugin?

For plugins on WordPress.org, the Advanced View on the plugin's page lists every previous version as a zip. For premium plugins, the vendor's account area usually keeps old versions. Install the old zip over the new one.

Should I restore a full backup instead?

Only if you cannot identify the cause or several things broke at once. A full restore from last night also discards every order, comment and post since then. Rolling back one plugin keeps all of that.

How do I stop this happening again?

Stage updates one at a time with a check between each, keep automatic updates on only for plugins with a good track record, and use a tool that takes a restore point before every update and rolls back automatically if the site breaks.

DevDome Team WordPress plugin builders

The DevDome team builds lightweight, performance-first WordPress plugins and free tools for site owners, founders and marketers. We write about the exact problems our plugins solve, in plain language for people who run real sites.