Sometimes the cleanest fix for a broken update is to go back one step: reinstall the previous version of the plugin, keep everything else as it is, and retry the update once the conflict is understood. Done carefully, a rollback takes minutes.
If you’re not yet sure which plugin caused the problem, start with our guide to a site broken after an update.
Before you roll back
- Take a backup of the current state, so you can undo the rollback too.
- Note the version numbers: the one you have now and the one you want to go back to.
- Read the changelog. If the new version fixed a security issue, a rollback should be short-lived.
- Check for database changes. Some updates migrate data; the old version may not read it correctly afterwards.
Option 1: WP-CLI
If you have command-line access, WP-CLI can reinstall a specific version of any plugin hosted on WordPress.org:
# Check the installed version
$ wp plugin get plugin-slug --field=version
# Reinstall a specific earlier version
$ wp plugin install plugin-slug --version=1.2.3 --forceOption 2: a rollback plugin
Tools such as WP Rollback add a “Rollback” link next to plugins from WordPress.org and let you pick an earlier version from the dashboard. Handy when you don’t have command-line access — but it adds another plugin to maintain, so remove it once you’re done if you don’t need it regularly.
Option 3: manual reinstall
For premium plugins, or when the other options aren’t available:
- Download the previous version from the vendor’s account area (or take the plugin folder from a backup).
- Via SFTP or your host’s file manager, rename the current plugin folder, for example to
plugin-name-new. - Upload the previous version to
wp-content/plugins/. - Check the plugin is active and working, then delete the renamed folder.
After the rollback
- Check the page or feature that was broken, plus your key pages and main form.
- Look at the error log for any new warnings.
- Record why you rolled back, and which version you’re on.
- Watch for a fixed release, then test it on a staging site before updating live.
What WordPress does on its own
Recent versions of WordPress include some rollback protection: if a plugin update fails partway, the previous version is restored, and automatic plugin updates that cause a fatal error can be rolled back. That’s a valuable safety net, but it only catches crashes. A broken layout, a checkout that misbehaves or a form that stops sending still need a person to notice — which is why a careful update routine matters.
Frequently asked questions
Can WordPress roll back plugin updates automatically?
Recent WordPress versions can restore the previous version when a plugin update fails, and can roll back automatic plugin updates that trigger a fatal error. They won’t detect a broken layout or form, so a manual rollback is still sometimes needed.
Is it safe to install an older plugin version?
Usually, as a temporary measure. Check the changelog first: if the newer version fixed a security issue, plan to update again as soon as the conflict is resolved.
Will rolling back a plugin delete my data?
Reinstalling the plugin files normally keeps its settings and data, which live in the database. The exception is when an update changed the database structure — then the older version may not work correctly with the updated data.
How do I roll back a premium plugin?
Premium plugins aren’t on WordPress.org, so tools that fetch old versions from there won’t work. Use a previous version from the vendor’s account area, or restore the plugin folder from a backup.
