How to Roll Back a WordPress Plugin or Theme Update

If a plugin or theme update just broke your WordPress site, you can roll it back to the previous version — usually within minutes — by reinstalling the older release from the WordPress.org archive, using a rollback plugin, restoring from a backup, or uploading the old files manually via FTP. The fastest method depends on how much access you still have to your site, and whether you kept a backup before updating.

Below is every method ranked from easiest to most involved. Work through them in order and stop as soon as your site is healthy again.

What "Rolling Back" Actually Means

When WordPress updates a plugin or theme, it replaces the files in wp-content/plugins/ or wp-content/themes/ with the new version. Rolling back means replacing those files again — this time with the previous version. Nothing in your database changes during a typical plugin or theme update, so rollbacks are usually safe and reversible. The exception is plugins that run database migrations on activation (some page builders and WooCommerce extensions do this), which is why a backup before any rollback attempt is non-negotiable.

Before You Touch Anything: Take a Backup

Even a broken site is a starting point. Before you change anything, snapshot what you have now. If your host offers one-click backups in the control panel (cPanel, Kinsta, WP Engine, etc.), use it. If Jetpack, UpdraftPlus, or another backup plugin was running before the update, verify you have a clean pre-update copy already stored. If you are completely locked out, proceed to the FTP or hosting file manager method below, but understand you are working without a safety net — move carefully.

Method 1: WP Rollback (Easiest — Admin Access Required)

WP Rollback is a free, well-maintained plugin in the official WordPress.org directory. It adds a "Rollback" link next to every plugin and theme that was installed from WordPress.org, and lets you choose any previous version from a dropdown.

1. In your WordPress admin, go to Plugins → Add New and search for WP Rollback. Install and activate it.
2. Go to Plugins → Installed Plugins. Next to the plugin that caused the problem you will see a new Rollback link — click it.
3. Choose the version you were on before the update. If you are unsure, check your update notification email or activity log; a reasonable default is one version behind the current release.
4. Click Rollback and confirm. WordPress will download and install the older version exactly as it would a normal update.
5. Test your site. If everything looks good, do not update that plugin again until the developer releases a patch or you have tested the new version on a staging copy.

WP Rollback works the same way for themes — find it under Appearance → Themes, open the theme detail panel, and look for the Rollback button.

Limitation: This only works for plugins and themes hosted on WordPress.org. Premium plugins from third-party marketplaces will not appear. For those, you need Method 3 or 4.

Method 2: Download and Reinstall the Old Version Manually

If WP Rollback is not an option, you can download any previous version of a WordPress.org plugin directly from the official repository and install it as a ZIP file.

1. On your desktop browser, go to https://wordpress.org/plugins/PLUGIN-SLUG/advanced/ — replace PLUGIN-SLUG with the plugin's URL slug (e.g., contact-form-7). Scroll down to find the Previous Versions dropdown and download the version you need as a ZIP file.
2. In your WordPress admin, go to Plugins → Add New → Upload Plugin.
3. Upload the ZIP you just downloaded. When WordPress warns you the plugin is already installed and asks whether to replace it, click Replace current with uploaded.
4. Activate the plugin and test your site.

For themes the path is https://wordpress.org/themes/THEME-SLUG/ — click the Development Log or use the Trac link in the sidebar to locate old ZIP archives.

Method 3: Restore from a Backup (Best Option for Premium Plugins or Total Lockouts)

If you have a full site backup taken just before the update — and you should, because the pre-update checklist everyone recommends insists on it — restoring it is the cleanest rollback possible. It brings back the exact file state you were in without guesswork about which version number you were on.

The restore process varies by backup provider:

• UpdraftPlus: Go to Settings → UpdraftPlus Backups → Existing Backups, find the pre-update snapshot, and click Restore. Select only Plugins or Themes if you only need to roll back that component — there is no need to restore the entire database if the update did not touch it.
• Jetpack VaultPress Backup: Log in to WordPress.com, open the Activity Log, find the event just before the update, and click Restore to this point.
• Host-level backups: Most managed hosts (WP Engine, Kinsta, SiteGround, Flywheel) let you restore to a point-in-time snapshot from the hosting dashboard. This is the fastest path when the admin is unreachable.

If a restore is available, prefer it over any manual file surgery — it is deterministic and leaves nothing half-replaced.

Method 4: Replace Files Manually via FTP or File Manager

Use this when the admin dashboard is inaccessible and no managed backup is available. You will need FTP credentials or access to your host's file manager.

1. Download the correct older version ZIP from WordPress.org (or from the premium plugin's account portal) to your local machine and unzip it.
2. Connect to your server via FTP (FileZilla is free and reliable) or open the file manager in cPanel/Plesk.
3. Navigate to wp-content/plugins/ (or wp-content/themes/).
4. Rename the existing plugin folder — for example, rename woocommerce to woocommerce-BROKEN. This deactivates the plugin immediately without deleting anything, which is your safety net.
5. Upload the unzipped older version folder to the same location. The folder name must match the original exactly (e.g., woocommerce).
6. Visit your site. The plugin is now deactivated; go to Plugins → Installed Plugins and reactivate it, or it may reactivate automatically depending on how it was deactivated.
7. Once confirmed working, delete the -BROKEN folder.

If you are stuck at a white screen after an update, the WordPress White Screen of Death fix guide covers the full diagnostic — renaming the plugin folder via FTP is often the same first step.

When the Rollback Itself Causes Problems

Occasionally rolling back a plugin that ran a database migration on update will leave the database in a newer schema than the old code expects. Symptoms include PHP errors mentioning missing columns or tables, or a broken admin after the rollback. In this case:

• Check the plugin's changelog for any mention of database changes in the version you rolled back from.
• Try deactivating the plugin entirely and running a database repair via wp-admin/maint/repair.php if WordPress prompts it.
• If the plugin is WooCommerce or another e-commerce tool, a full database restore from backup is safer than a file-only rollback.
• Contact the plugin author — many respond quickly in the WordPress.org support forum when a release is causing widespread issues, and a hotfix may already be published.

How to Prevent Needing a Rollback Next Time

The single most effective habit is testing updates on a staging environment before applying them to production. A staging site is a private copy of your live site where you can update freely and break things without consequence. If you do not have one set up, your host may offer it with one click — here is how to use staging properly.

Beyond staging:

• Enable automatic backups that run before each update, not just nightly. UpdraftPlus has an option to back up before updates; several managed hosts do this by default.
• Read changelogs. Major version bumps (e.g., 3.x → 4.0) carry more risk. Minor patches (3.2.1 → 3.2.2) are usually safe to apply immediately.
• Use a Care Plan that includes managed updates with monitoring. Mend's $99/month Care Plan covers managed updates, backups, security scanning, and uptime monitoring — updates are applied and watched, so a bad one gets caught before it becomes your emergency.

When to Call a Professional

If you have tried the steps above and the site is still broken — or you cannot access FTP, do not have a backup, and are watching a live e-commerce store return errors — this is the moment to stop tinkering and get expert help. Every minute of downtime costs real money and erodes customer trust.

Mend's engineers handle exactly this scenario, every day. The Emergency Rescue service ($299) gets a senior engineer on your site fast — most fixes are resolved the same day — with a backup-first workflow and a plain-English report of exactly what changed. If you are not sure of the scope yet, start with a free Diagnosis; it triages the problem and gives you a flat-price quote before any work begins, no credit card required. Every fix is backed by a "fixed, or your money back" guarantee.