How to Roll Back a Plugin or Theme Update in WordPress

If a plugin or theme update just broke your site, you can roll back to the previous version by restoring a backup, using a dedicated rollback plugin, or manually replacing the files via FTP — most methods take under ten minutes. The fastest and safest path depends on what access you still have to your dashboard and whether a recent backup exists. Here is every method ranked from easiest to most involved, with exact steps for each.

What You Are Actually Seeing

Bad updates tend to produce a recognisable set of symptoms immediately after you click Update:

• A white screen or White Screen of Death on the front end or admin.
• A "There has been a critical error on this website" message.
• Broken layout — missing widgets, collapsed navigation, garbled CSS.
• A specific feature (checkout, contact form, slider) that stops working entirely.
• A 500 error triggered only on certain pages.

If at least one of those followed an update you ran today or yesterday, a rollback is exactly the right next step. Don't start disabling random plugins yet — that diagnosis step comes only if you cannot identify which update caused the problem.

Before You Do Anything Else: Confirm the Culprit

Check Dashboard → Updates history, or your host's activity log, to confirm which plugin or theme was updated most recently. If you updated several things at once, deactivate them one by one (newest first) to isolate the offender before rolling anything back — that saves you restoring an entire backup unnecessarily.

Also check whether your host auto-updated anything overnight. Many managed hosts (WP Engine, Kinsta, SiteGround, Flywheel) run automatic plugin updates by default. Their control panels usually log exactly what changed and when.

Method 1 — Restore a Host or Plugin Backup (Safest, Fastest)

If your host keeps daily snapshots — and most managed hosts do — this is the cleanest rollback. It returns every file and the database to a known-good state in a few clicks.

1. Log in to your hosting control panel (cPanel, MyKinsta, WP Engine User Portal, etc.).
2. Find the Backups or Restore section. Look for the most recent snapshot taken before the update.
3. Restore to a staging environment first if your host offers it — confirm the site works, then push to production.
4. If no staging is available, restore directly and immediately test key pages and any user-facing forms.

The trade-off: a full restore also rolls back any content or orders created after the snapshot. If your store processed purchases in the last 24 hours, a targeted file-only rollback (Methods 2–4) is safer for the database.

Method 2 — Use WP Rollback (Dashboard Still Works)

WP Rollback is a free plugin in the official WordPress.org repository that adds a Rollback link next to every plugin and theme on the respective list pages. It pulls the older package directly from WordPress.org.

1. Go to Plugins → Add New, search for WP Rollback, install and activate it.
2. Go to Plugins → Installed Plugins. Next to the problem plugin you will now see a Rollback link alongside Deactivate and Delete.
3. Click it, choose the version you were running before the update (check your site notes or the plugin's changelog to confirm), and click Rollback.
4. WordPress replaces the plugin files and returns you to the plugin list. Test immediately.
5. For themes, go to Appearance → Themes, click the theme, and the same Rollback option appears.

Important limitation: WP Rollback only works for plugins and themes hosted on WordPress.org. Premium plugins from third-party marketplaces (Envato, individual vendor sites) are not in the repository — use Method 3 or 4 for those.

Once rolled back, go to Plugins → Installed Plugins, click Disable auto-updates for that plugin, and hold off updating again until the developer releases a patch or you have confirmed compatibility on a staging site.

Method 3 — Download and Re-upload the Old Version Manually

This works for both free and premium plugins when you have the old package.

For free WordPress.org plugins

1. Visit https://wordpress.org/plugins/PLUGIN-SLUG/advanced/ (replace PLUGIN-SLUG with the plugin's folder name).
2. Scroll to Previous Versions, choose the version you need from the dropdown, and download the zip.

For premium plugins and themes

1. Log in to the vendor's account portal (ThemeForest, Elementor, WooCommerce.com, etc.).
2. Check whether the vendor keeps version history in your purchase downloads. Many do. Download the prior release zip.
3. If the vendor does not provide old versions, check whether you have the zip saved locally from a previous manual update — developers who update carefully keep these.

Re-uploading the zip

1. If your dashboard loads: go to Plugins → Add New → Upload Plugin, upload the old zip, and click Replace current with uploaded.
2. If the dashboard is inaccessible: connect via FTP/SFTP, navigate to wp-content/plugins/ (or wp-content/themes/), rename the broken folder (e.g. my-plugin-broken), then upload and extract the old zip to the same location with the original folder name.

Always back up the current (broken) files before overwriting them, in case you need to send them to the developer as a bug report.

Method 4 — Temporarily Deactivate While You Wait for a Patch

If you cannot find an older version and a restore would destroy recent orders or content, deactivating the offending plugin is a legitimate short-term fix. It removes the functionality but stops the breakage.

1. Dashboard accessible: Plugins → Installed Plugins → Deactivate.
2. Dashboard inaccessible: Connect via FTP/SFTP, rename the plugin's folder inside wp-content/plugins/ (add -disabled to the name). WordPress will auto-deactivate it the moment the folder name no longer matches. Rename it back to re-enable.

For a broken theme that prevents admin access, connect via FTP and rename the active theme's folder. WordPress will fall back to the most recently active default theme (Twenty Twenty-Four or similar), which at least restores dashboard access.

How to Prevent This Next Time

Rolling back is a rescue operation — the goal is to make it unnecessary. A few habits eliminate most update emergencies:

• Take a backup immediately before every update. Many backup plugins (UpdraftPlus, BlogVault, Jetpack VaultPress Backup) can be configured to auto-backup before updates run.
• Use a staging environment. Most managed hosts provide one. Test updates on staging, then push to live. This is the single biggest risk-reducer available.
• Disable automatic updates for complex plugins. WooCommerce, page builders, and security plugins are the highest-risk candidates. Review their release notes before updating manually.
• Update one item at a time. Batch updates make it impossible to pinpoint the culprit quickly.
• Monitor the developer's changelog. Most major version bumps (2.x → 3.x) signal breaking changes — they deserve extra caution.

If you want all of this handled automatically with a safety net in place, Mend's Care Plan covers managed updates, automated backups, and uptime monitoring for $99/month — so you are not the one watching for breakage.

For more on building a sustainable update routine, see WordPress Maintenance Checklist: What to Do and When.

When a Rollback Is Not Enough

Sometimes the update triggered a deeper problem: a database migration that partially ran, a corrupted options table, or a conflict between the rolled-back version and another plugin that also updated. Signs this is happening:

• The site still breaks after the rollback.
• Settings inside the plugin are missing or reset.
• New errors appear that were not present before the update at all.
• WooCommerce orders or custom post types are behaving inconsistently.

At that point you are dealing with a multi-layer problem that needs database-level investigation — and that is where a quick DIY fix can make things worse if the wrong table rows get modified. This is also when having a pre-update backup becomes critical.

If you are stuck after trying the steps above, Mend's Quick Fix ($129, same-day) is designed exactly for this scenario — a senior engineer diagnoses the root cause, makes the fix safely on a backed-up copy, and sends you a plain-English report of what changed and why. Not sure of the scope yet? Start with a free Diagnosis — no card required.

For context on what a bad update can look like at the server level, What Plugins Actually Do to Your Server (Not Just Speed) explains why some updates cause breakage that goes well beyond a missing stylesheet.