Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Troubleshooting · Guide

How to Roll Back a Plugin Update

Short answer

Install WP Rollback, open Plugins > Installed Plugins, and click the Rollback link under the plugin. Pick the earlier version from the list and confirm to replace the current files with the old ones. Turn off auto-updates for that plugin so WordPress does not reinstall the broken version.

Key takeaways

  • A plugin rollback replaces files only, so settings stored in the database stay put.
  • WP Rollback works only for free plugins from the WordPress.org directory.
  • WP Rollback needs WordPress 6.5 or newer, PHP 7.4 or newer, and MySQL 5.0 or newer.
  • Since WordPress 6.3, a failed manual update rolls itself back, and since 6.6 a fatal error after an auto-update does too.
  • Turn off auto-updates for the plugin after a rollback, or the broken version returns.

What does rolling back a plugin update mean?

Rolling back a plugin update means replacing the current plugin files with the files of an earlier version.

The plugin keeps its settings, since settings live in the database and a rollback only swaps files. Your content, users, and other plugins stay exactly as they are.

A rollback is a short-term fix, not a permanent answer. The goal is to get the site working again while the plugin author fixes the bad release.

When should you roll back a plugin instead of fixing it?

Roll back when a site broke right after one plugin updated and nothing else changed.

Signs that point at a single plugin are a white screen after its update, a form or checkout that stopped working, or a feature that vanished the same day. If several things updated at once, check the debug log first to find which one failed.

Do not roll back when the problem is a hacked site, a server fault, or a theme conflict. Find the real cause first, since a rollback only helps when one plugin update broke the site.

Rolling back is also the wrong move when the old version has a known security flaw. In that case, keep the site on the new version and look for a different fix, such as turning off the broken feature.

How do you roll back a plugin with WP Rollback?

Install WP Rollback, open Plugins > Installed Plugins, click the Rollback link under the plugin, pick the earlier version, and confirm.

  1. Go to Plugins > Add New Plugin, search for WP Rollback, then install and activate it.
  2. Go to Plugins > Installed Plugins and find the plugin you want to roll back.
  3. Click the Rollback link below the plugin name.
  4. Pick the version you want from the list, then click Rollback.
  5. Read the warning, confirm that you have a backup, and click Rollback again.
  6. Click Activate Plugin when the old version is in place.

WP Rollback works only for plugins from the WordPress.org directory. The WPBeginner rollback guide notes that you cannot roll back third-party plugins that are not in the official plugin directory.

WP Rollback needs WordPress 6.5 or newer, PHP 7.4 or newer, and MySQL 5.0 or newer. Those minimums come from the WP Rollback plugin page.

The plugin page also warns you to test the rollback on a staging or development site first, and to take a backup before you roll back on a live site. Our staging site guide shows how to set up that safe copy.

How do you roll back a plugin by hand?

Download the older version as a ZIP from the plugin page on WordPress.org, then install it over the current version.

  1. Open the plugin page on WordPress.org and scroll to the bottom.
  2. Open Advanced View and find the version list, then download the ZIP of the version you want.
  3. Go to Plugins > Add New Plugin > Upload Plugin in your dashboard.
  4. Upload the ZIP and confirm the install when WordPress asks to replace the current version.
  5. Activate the plugin if WordPress leaves it inactive.

You can also do the same job from the command line. The WP-CLI command is wp plugin install plugin-name --version=2.4.1 --force, replacing the name and number with your plugin and version. That command comes from Simafri's WordPress rollback guide.

The manual route is the only option when WP Rollback cannot reach the plugin, for example when the plugin is premium or from another source. It also works when the dashboard is broken, as long as you can upload files by FTP instead.

What if the plugin is not from WordPress.org?

Premium and third-party plugins have no public version list, so you need the old ZIP from the vendor.

Check your downloads page on the vendor site first. Many vendors keep older releases there for licensed buyers. If the vendor has no archive, check whether you saved the old ZIP on your computer or in a backup.

WP Rollback Pro adds support for premium plugins you already have licensed and installed, including Elementor Pro, Gravity Forms, and WooCommerce extensions. That is stated on the WP Rollback plugin page.

Do not download a premium plugin ZIP from a random site. Those copies may carry malware or a changed version number, and they give you no vendor support.

Which rollback method should you use?

Pick the method that matches where the plugin came from and whether the dashboard still opens.

MethodWorks forNeeds
WP RollbackFree plugins from WordPress.orgDashboard access
Manual ZIP installAny plugin with a saved older ZIPDashboard access or FTP
WP-CLI install commandAny plugin from WordPress.orgSSH access and WP-CLI
Vendor downloadPremium pluginsA license and the vendor archive

WP Rollback is the fastest option for a free plugin, since it lists every released version in one place. The manual ZIP route is the fallback when the plugin is premium or the dashboard will not open.

What does WordPress roll back on its own?

Since WordPress 6.3, a manual plugin or theme update that fails partway through puts the old version back by itself.

The Make WordPress Core rollback post explains how it works: the old version moves to a wp-content/upgrade-temp-backup/ folder first, and if the update fails, the backup is restored to its original location. If the update succeeds, the backup is deleted.

Since WordPress 6.6, an automatic update that causes a fatal error also rolls back by itself. LetsKnowTech's rollback guide states that WordPress reinstalls the previous version when an auto-update of an active plugin causes a fatal error.

These safety nets only cover failed installs and fatal errors. An update that installs fine but breaks a layout, a form, or a checkout still has to be rolled back by hand.

How do you stop the broken version from coming back?

Turn off auto-updates for that plugin right after the rollback, or WordPress may install the broken version again.

  1. Go to Plugins > Installed Plugins.
  2. Find the plugin and click Disable auto-updates under its name.
  3. Leave it off until the author ships a fixed release.

WordPress runs its background updater twice a day, so an unguarded rollback can vanish overnight. LetsKnowTech's rollback guide warns that a single run of the background updater reinstalled the broken version on a test site. Our guide to plugin auto-updates explains the auto-update settings in full.

Check the plugin changelog on WordPress.org before you turn auto-updates back on. Look for a release note that names the bug you hit, then update and test it on staging first.

How do you check the rollback worked?

Open the Plugins page and confirm the version number, then test the feature that broke.

  • Check the version shown under the plugin name matches the version you picked.
  • Load the page or feature that broke and confirm it works again.
  • Open the site front page and one more key page to check nothing else broke.
  • Read debug.log for any new fatal error tied to the old version.

If the old version also fails, the plugin may not be the real cause. Read the debug log again and look for the first fatal error, since it names the file that actually failed.

If the rollback worked but the plugin is now far behind, plan the next step. Our plugin conflict fix guide can help when two plugins clash instead of one plugin failing alone.

What mistakes should you avoid?

Never roll back on a live site without a backup, since a bad rollback can break the site further.

  • Do not roll back to a version with a known security flaw just because it works.
  • Do not forget to turn off auto-updates for the plugin, or the broken version returns.
  • Do not roll back every plugin at once; roll back the one that changed right before the break.
  • Do not assume the rollback undid database changes, since it only replaces files.

A rollback may not reverse database changes or other side effects from the update. That warning comes from the Upsure plugin page, and it applies to every manual rollback too.

Keep a note of the version you rolled back to and the date. When the author ships a fix, that note tells you exactly which release to test next.

Frequently asked questions

Can I roll back a premium plugin with WP Rollback?

No. WP Rollback lists only plugins hosted in the WordPress.org directory. For a premium plugin, download the older ZIP from the vendor downloads page, or use WP Rollback Pro, which adds support for licensed premium plugins. Never use a premium ZIP from an unknown site.

Does rolling back a plugin undo its database changes?

A rollback replaces plugin files only, so settings stored in the database stay as they are. It does not undo changes the update made to database tables. If the update changed tables and the old files cannot read them, you may need a full backup restore instead.

How do I stop WordPress from updating the plugin again?

Go to Plugins > Installed Plugins and click Disable auto-updates under the plugin name. WordPress runs its background updater twice a day, so an unguarded rollback can be overwritten overnight. Turn auto-updates back on only after the author ships a fixed release.

How do I know the rollback worked?

Check the version shown under the plugin name on the Plugins page, then test the feature that broke. If the old version also fails, read debug.log for the first fatal error, since the plugin may not be the real cause.

Does WordPress roll back a failed update by itself?

WordPress 6.3 added automatic rollback for a manual update that fails partway through, and WordPress 6.6 added it for an auto-update that causes a fatal error. An update that installs fine but breaks a layout or a checkout still has to be rolled back by hand.

Can I roll back a plugin without installing WP Rollback?

Yes, if you still have the older ZIP. Go to Plugins > Add New Plugin > Upload Plugin, upload the ZIP, and confirm the install when WordPress asks to replace the current version. You can also do it over FTP by replacing the plugin folder.

Sources

  1. WP Rollback – Rollback Plugins and Themes WordPress.org
  2. Plugin Rollbacks WP Rollback Docs
  3. New in 6.3: Rollback for failed manual plugin and theme updates Make WordPress Core
  4. How to Rollback WordPress - Undo WordPress Updates WPBeginner
  5. WordPress update broke your site: how to roll back cleanly Simafri
  6. How to Roll Back WordPress: Core, Plugins and Themes LetsKnowTech

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test