WordPress · Recovery
How to Roll Back a Plugin Update
A plugin updated overnight. Your site broke. Here's how to restore the previous version without losing your settings — three methods, from easiest to most technical.
Quick reassurance: Your plugin settings live in the database, not the plugin files. Rolling back the files doesn't touch your settings. The site content, options, and database are unaffected.
WP Rollback plugin (easiest)
If you can still access wp-admin, this is the fastest method. It adds a "Rollback" link next to every plugin.
- Go to Plugins → Add New
- Search for WP Rollback
- Install and activate it
- Go to Plugins → Installed Plugins
- Find the plugin that broke, click Rollback
- Select the previous version from the dropdown
- Click Rollback — the plugin is replaced
Pro tip: WP Rollback also works for themes. Same flow, different menu. It's one of the most-used recovery plugins in the WordPress ecosystem for a reason.
Limitation: Only works for free plugins hosted on wordpress.org. Premium plugins aren't in the WP Rollback index.
Manual download and upload
Works for free AND premium plugins. Slightly more steps but no dependency on a third-party plugin.
- Go to the plugin's page on
wordpress.org/plugins/[plugin-slug]/ - Scroll to the bottom and click Advanced View
- Scroll further to Previous Versions
- Download the ZIP of the version you want
- In wp-admin: Plugins → Add New → Upload Plugin
- Upload the ZIP
- When prompted, click Replace current with uploaded
Important: Don't deactivate the plugin first. Uploading over the active plugin preserves your settings and immediately rolls back. Deactivating risks some plugins deregistering their data in edge cases.
For premium plugins: Check your account dashboard on the vendor's site. Most have a "Downloads" or "Versions" section. If they don't offer previous versions, contact their support.
WP-CLI (fastest if you have SSH)
The fastest method when you have shell access. One command does it.
# List plugins with current versions
wp plugin list
# Roll back to a specific version
wp plugin install plugin-slug --version=1.2.3 --force
# Example: roll back WooCommerce
wp plugin install woocommerce --version=8.4.0 --force
# Disable auto-updates for this plugin
wp plugin auto-updates disable plugin-slug
# Confirm the version
wp plugin get plugin-slug --field=versionPro tip: The --force flag is required to overwrite an already-installed plugin. Without it, WP-CLI skips because the plugin exists.
If wp-admin is inaccessible
You can't log in to install WP Rollback or use the uploader. Recover via file access first, then roll back.
Step 1 — restore access:
- Connect via SFTP or hosting file manager
- Navigate to
wp-content/plugins/ - Rename
[plugin-slug]to[plugin-slug]-broken - Visit your site — it should load now
- Log into wp-admin
Step 2 — roll back:
- Download the previous version from wordpress.org (or your vendor)
- Upload it via SFTP to
wp-content/plugins/[plugin-slug]/ - Or extract locally and upload the folder
- Delete the
[plugin-slug]-brokenfolder once the new one is in place - Reactivate the plugin in wp-admin
Careful: When uploading via SFTP, the folder name must match the original plugin's folder name exactly, or WordPress won't recognize it as the same plugin.
After you roll back — the follow-up steps
Rolling back solves the immediate problem. These steps prevent it recurring.
- Disable auto-updates for the rolled-back plugin. Otherwise it'll update again tonight and break the site again. (See below.)
- Check the plugin's support forum. Search for reports of the same issue. If 10 other users report it, a fix is likely coming within a week.
- Subscribe to the plugin's changelog. wordpress.org shows the changelog on the plugin page. Check it weekly for a version that fixes your issue.
- Consider a replacement. If the plugin updates slowly and breaks often, that's a signal to find a better-maintained alternative.
- Document what broke. Keep a log of past plugin updates that broke things. It makes future decisions easier.
🔒 How to disable auto-updates
Two ways. Pick based on how many plugins you want to protect.
Per plugin (in wp-admin):
- Go to Plugins → Installed Plugins
- Find the plugin
- Click Disable auto-updates next to it
Site-wide (in wp-config.php):
// Add this anywhere in wp-config.php before "That's all, stop editing!"
define('AUTOMATIC_UPDATER_DISABLED', true);Keep security updates on, disable only plugin updates:
// In wp-config.php
add_filter('auto_update_plugin', '__return_false');Recommended balance: Keep core security updates automatic. Disable auto-updates for critical plugins (WooCommerce, membership, payment gateways). Update those manually after testing on staging.
❓ Frequently asked questions
Will rolling back a WordPress plugin lose my settings?
No. Plugin settings are stored in the database, not the plugin files. Rolling back the files doesn't touch wp_options. The only risk is if the newer version changed the database schema — in that case, some settings may not be readable by the older version.
Where do I find previous versions of a plugin?
On the plugin's wordpress.org page, click 'Advanced View' at the bottom, then scroll to 'Previous Versions'. Download the version you want as a ZIP.
Does WP Rollback work for premium plugins?
WP Rollback only supports plugins hosted on wordpress.org. For premium plugins, download the previous version from your account dashboard on the vendor's site and upload it manually.
How do I disable auto-updates for WordPress plugins?
In wp-admin, go to Plugins → Installed Plugins. Click 'Disable auto-updates' next to the specific plugin. Or site-wide: add define('AUTOMATIC_UPDATER_DISABLED', true); to wp-config.php.
What if the plugin developer released a hotfix?
Update to the fix instead of rolling back. Check the plugin's changelog to confirm the fix addresses your issue. If no fix is available yet, roll back and disable auto-updates until one is released.