A WordPress Update Broke Your Site? How to Roll Back
A step-by-step way back after a failed WordPress update: recovery mode, disabling the plugin, reinstalling the previous version, rolling back core and restoring a backup as the last step.

Start by not restoring the backup. A full restore is the right answer for a minority of failed updates, and it throws away every order, signup and form entry made since the backup ran. Most of the time you can roll back a WordPress update by returning one plugin to its previous version, which takes minutes and loses nothing.
Think of the steps below as a ladder. Start at the bottom and stop at the first rung that brings the site back.
Before you touch anything, save the evidence
Five minutes here saves an hour of guessing later.
- Copy the exact error text and note the time it started.
- List what was updated. If automatic updates did it, the email from WordPress names each plugin and version. Otherwise sort the plugin folders by date with
ls -lt wp-content/pluginsand see which changed last. - Read the last fatal error in the log. In
wp-content/debug.logor the server's PHP error log, the newest "PHP Fatal error" line contains a file path, and the path names the plugin or theme. - Back up the broken site as it is. This copy holds the newest orders and entries, and it means nothing you try next can make matters worse.
Get back into the admin
Use the recovery mode email
When a plugin or theme causes a fatal error, WordPress sends an email with the subject "Your Site is Experiencing a Technical Issue" to the administration address. It names the extension at fault and contains a link. Open the link, log in, and you are in recovery mode: the faulty plugin is paused for your session so the admin loads again.
Two things to know. Visitors still get the error until you deactivate or replace the plugin, because the pause applies only to you. And the link expires, after a day by default. If the mail never arrives, check the spam folder and whether RECOVERY_MODE_EMAIL in wp-config.php points it somewhere else. Recovery mode covers fatal errors in plugins and themes only, and it depends on the site being able to send mail at all.
Disable the plugin without the admin
Over SFTP or the host's file manager, rename the plugin's folder, for example from wp-content/plugins/the-plugin to the-plugin.off. WordPress cannot find it and deactivates it. With WP-CLI, tell the command not to load the broken code while it runs:
wp plugin deactivate the-plugin --skip-plugins --skip-themes
# if the theme is the cause, switch to a default theme
wp theme list --skip-plugins --skip-themes
wp theme activate default-theme-slug --skip-plugins --skip-themes
A different symptom needs a different fix. If the site shows "Briefly unavailable for scheduled maintenance" long after the update, the update was interrupted. Delete the .maintenance file in the WordPress root folder, then reinstall whatever was half updated. We go through that case in WordPress stuck in maintenance mode.
Roll back the plugin or theme, not the whole site
With the site reachable again, put the previous version of the one faulty extension back.
- From WordPress.org. On the plugin's directory page, open "Advanced View" and scroll to "Previous Versions". Download the version you were on.
- Upload it over the current one. On the screen for adding a plugin, choose "Upload Plugin" and select the zip file. WordPress compares the installed and uploaded versions and offers "Replace current with uploaded".
- Or do both from the command line with the WP-CLI plugin install command:
wp plugin install the-plugin --version=1.2.3 --force
wp theme install the-theme --version=1.2.3 --force
Premium plugins are not in the directory. Look in the vendor's account area for older downloads, or ask their support. Failing that, your last backup contains the old folder: extract only wp-content/plugins/the-plugin from it and upload that. Restoring one folder is not restoring the site.
Then finish the job. Switch off auto-updates for that plugin, or it will update itself again within hours. Clear the page cache and any object cache. Test the feature that broke. Send the log line to the plugin's author, because they can only fix what they hear about.
Database updates do not roll back with the files
This is the limit of the simple rollback. Stores, learning platforms, form plugins and page builders sometimes change their database tables or convert stored data as part of an update. The old plugin files then meet a newer data structure. That can work, fail loudly or damage records quietly, and you cannot tell which from the outside.
Signs that a migration ran: the admin showed a "database update" notice after the update, the changelog mentions a migration or schema change, or the plugin moved to a new major version. In that situation you have two sound options and one poor one.
- Fix forward. Keep the new version and repair what cannot cope with it. Very often the real casualty is a small add-on or a piece of custom code that has not caught up, and deactivating that add-on restores the site while you wait for its update.
- Restore files and database together from the backup taken before the update, accepting the loss described below.
- The poor option is downgrading the files alone on a site with data you care about, and hoping.
Rolling back WordPress core
Check twice before you blame core. When errors appear after a core update, the log almost always points into a plugin or theme that was not ready for the new version, and the fix is to update or replace that extension. Minor releases, which change only the third number, are very rarely the cause, and you should not undo a security release.
If you do need the previous version back, WP-CLI can install it over the current one:
wp core update --version=X.Y.Z --force
By hand, download the old package from the WordPress releases archive and replace the wp-admin and wp-includes folders and the PHP files in the root. Leave wp-content and wp-config.php alone.
Know what you are doing to the database. A major core update upgrades it, and WordPress has no routine for taking that upgrade back. Stepping back one version is usually tolerated, but nobody tests it. Treat a core rollback as a way to hold position for a few days while the real fix is prepared, never as a place to stay.
Restoring the backup, and what it costs
The full restore is the top rung. Use it when you cannot identify the cause, when several rollbacks have not helped, when a migration ran and fixing forward is not possible, or when an interrupted update left files in a mixed state.
The cost is everything that happened on the site since the backup was taken. On a brochure site that may be nothing. On a store it is real orders. So restore with care:
- Put up a maintenance page so no new data arrives while you work.
- Export what is new since the backup: orders, users, form entries. The copy of the broken site you made at the start also holds them.
- Restore files and database from the same point in time. Mixing new plugin files with an old database recreates the problem you are escaping.
- Clear every cache, test the site, then re-enter or import what was created in the gap.
- Keep the offending update switched off and reproduce the failure on a staging copy before you try again.
A host snapshot is usually the fastest restore, but check what it covers before you press the button. Some snapshots roll back the whole account, mailboxes included. If you have never restored one of your backups, read a backup strategy you can restore from before the next update, not during it.
Knowing when to stop and hand it over
A single plugin that broke a content site is well within reach of a careful owner with the steps above. Stop and get help when the site sells or enrolls and a database migration is involved, when no route into the admin or the server works, when the error survives the plugin rollback, or when there is no usable backup. Each further experiment on a live store risks more data. A WordPress maintenance team handles this routinely, including the part people skip: finding out on staging why the update failed. If the cause turns out to be old custom code that the new version exposed, the durable fix is to have it rewritten properly by a WordPress plugin developer.
Frequently asked questions
Can I roll back a WordPress update without a backup?
Often, yes. Previous versions of plugins and of WordPress itself can be downloaded and installed over the current ones. What you cannot undo without a backup is a change the update made to the database, so the method works for file-only updates and is risky after a data migration.
Does WordPress undo a failed update by itself?
In two cases. If a plugin or theme update fails while it is being installed, WordPress puts the previous version back from a temporary copy. If an automatic plugin update causes a fatal error on the home page, current versions revert that plugin. An update that installs cleanly and then breaks one feature is not detected.
Will rolling back a plugin delete its settings?
No. Replacing a plugin's files leaves its settings and data in the database untouched. The exception is the case covered above, where the newer version already converted that data into a format the older version does not understand.
Should I roll back or wait for the plugin author's fix?
If the site is down or losing orders, roll back now and report the bug afterwards. If the damage is cosmetic or limited to one minor feature, staying on the new version and waiting for a patch is often safer than downgrading, especially when the update included security fixes.
Add worldwincoder.com as a preferred source on Google, or open this article in your AI assistant to use it as a source.
