iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
For a plugin hosted in the official WordPress.org directory, download an earlier release from the plugin’s Advanced View, then install its ZIP from Plugins > Add New Plugin > Upload Plugin. Before changing anything, back up the site, test the rollback on staging when possible, and prevent automatic updates from immediately replacing the older release.
First, confirm that this method applies
The WordPress.org download process works for plugins that are listed in the official directory at https://wordpress.org/plugins/. It does not provide historical packages for a plugin sold or distributed only through a developer’s own website, a private customer portal, or another marketplace. For those products, obtain the package from the original vendor and follow that vendor’s downgrade instructions.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →
An older plugin can restore compatibility after a WordPress core, theme, PHP, or plugin update, but it also removes fixes that may have been added in newer releases. Treat a rollback as a controlled troubleshooting step, not as a permanent security strategy. Developers may support only the current release, so an older version may receive no bug or security assistance.
Before downloading: make the rollback safe
Back up both files and the database
Create a complete backup of the WordPress files and database before replacing the plugin. The database can contain plugin settings, while the files include uploads, themes, custom code, and the plugin itself. A backup lets you restore the working state if the older release causes a fatal error, data problem, or layout failure.
#1 Best Overall
Use staging whenever possible
Perform the change on a staging copy first. Check the front end, the WordPress dashboard, forms, editors, scheduled tasks, checkout or membership flows, and any feature that depends on the plugin. If staging is unavailable, schedule the change for a low-traffic period and keep an administrator session open so you can recover quickly.
Record the current state
- Write down the installed plugin version and the version you intend to test.
- Note the WordPress, PHP, and active theme versions.
- Export or record important plugin settings if the plugin offers that option.
- Save the backup location and confirm that the backup can actually be restored.
Plan for automatic updates
After a rollback, disable automatic updates for that plugin. Otherwise WordPress may install the newest release again, making the downgrade appear to have failed. Re-enable updates only after you have selected a compatible version and confirmed that the original problem is resolved.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsMethod 1: download an older release from WordPress.org
- Open the plugin’s directory page. Go to https://wordpress.org/plugins/, search for the plugin, and open its listing. You can also enter the plugin’s directory slug in your browser if you already know it.
- Open Advanced View. In the listing’s Information sidebar, select Advanced View. The exact location or wording can change as the directory interface is updated.
- Find the historical-version selector. Scroll to the bottom of Advanced View and look for a drop-down that may be labeled Development Version or Previous Versions. WordPress.org pages have used both labels, so verify the live label on the page you are viewing.
- Choose the release. Select the version immediately before the current one if you are testing a simple regression. If that does not solve the problem, select the specific version known to work with your site. Check the version number carefully before downloading.
- Download the ZIP. Click Download and save the ZIP file to your computer. Do not extract or rename it if you plan to use the WordPress upload installer.
The downloaded archive is the plugin package. Keep it until the rollback has been verified; it is useful for repeating the installation on staging or restoring the same version after another update.
Install the ZIP from the WordPress dashboard
This is the simplest approach when you can sign in as an administrator and the hosting environment permits plugin uploads.
- Sign in to WordPress.
- Open Plugins > Add New Plugin.
- Click Upload Plugin.
- Choose the older plugin ZIP you downloaded from WordPress.org.
- Click Install Now and wait for the installation result.
If the current release is still installed, WordPress may report that the destination folder already exists or that the plugin is already present. Deactivate the current plugin, then delete it from the Plugins screen before uploading the older ZIP. Deleting the plugin files does not necessarily remove its settings, but a backup is still essential because plugin-specific uninstall behavior varies.
Another option is to place the older release in a differently named folder, but that can leave two copies of the same plugin and cause duplicate loading or confusing updates. Removing the active copy first is generally easier to understand and troubleshoot.
Activate and test
When installation finishes, open Plugins > Installed Plugins and activate the older release. Confirm that the displayed version is the one you selected. Test the feature that prompted the rollback, then check unrelated site functions for side effects. Keep the browser’s developer console and the WordPress error log available if the site behaves unexpectedly.
Install manually with FTP
Use FTP when the dashboard uploader is unavailable, the server rejects the ZIP, or you need direct control over the plugin directory.
- Download the historical ZIP using the WordPress.org steps above.
- Extract the ZIP on your computer. It should produce a plugin folder containing the plugin files.
- Connect to the site with your FTP client or hosting file manager.
- Open
wp-content/plugins. - Deactivate and remove or rename the existing copy of the plugin before uploading the older folder. Renaming is a useful emergency measure because it preserves the files for inspection, but the renamed folder must not remain as a second active copy.
- Upload the extracted older-version folder into
wp-content/plugins. - Return to Plugins > Installed Plugins, verify the version, and activate it.
FTP replaces files but does not automatically adjust plugin settings or database data. If the older release expects a different data structure, follow its activation notices and restore the backup if it cannot operate safely.
Use a rollback plugin instead
A rollback utility can download and install an earlier or newer release directly from the WordPress.org directory. After installing the WP Rollback plugin, a Rollback link appears beneath eligible plugins on the Plugins screen. Select that link, choose the target version, and follow the confirmation prompts.
This option is limited to plugins hosted in the WordPress.org directory. It does not create a historical package for a premium or private plugin, and it should still be preceded by a full backup and staging test. Disable automatic updates after the rollback so the selected release remains in place while you investigate.
Choose the right method
| Method | Best use | What you need | Important limitation |
|---|---|---|---|
| WordPress.org ZIP plus dashboard upload | You can access the administrator dashboard and want a visible, repeatable process | The plugin’s directory listing and downloaded ZIP | Existing copies may need to be deactivated and deleted first |
| Manual FTP upload | The dashboard uploader fails or direct file control is required | FTP or hosting file-manager access and an extracted ZIP | It replaces files but does not manage settings or database changes |
| WP Rollback | You want version selection from the Plugins screen | The rollback plugin and a directory-hosted plugin | Works only for plugins in the WordPress.org directory |
| Vendor-provided package | The plugin is private, premium, or absent from WordPress.org | A ZIP and instructions from the original developer | The WordPress.org historical-version selector does not apply |
What to do after the downgrade
Verify the version and the failing feature
Look at the plugin’s entry under Plugins > Installed Plugins and confirm the version number. Reproduce the original problem using the same workflow that exposed it. A rollback is useful only if it changes that behavior without introducing a more serious failure.
Rank #4
Check dependent components
Test the active theme and plugins that integrate with the downgraded plugin. Pay particular attention to forms, editor blocks, widgets, scheduled jobs, REST or API connections, and administrative screens. A plugin can appear active while a dependent feature is silently broken.
Keep the update decision explicit
Leave automatic updates disabled while the older release is under evaluation. Record why the rollback was made and which version worked. Once a compatible newer release is available, test it on staging, take a fresh backup, and update deliberately rather than allowing an unattended update to decide the timing.
Troubleshooting common problems
The old version will not install
- Confirm that the file is a complete ZIP downloaded from the plugin’s directory listing.
- Deactivate and delete the currently installed copy, then retry the upload.
- If the dashboard still fails, use FTP to remove or rename the existing plugin folder and upload the extracted older folder.
- Check available disk space and the hosting account’s upload limits.
The plugin is missing after FTP upload
Check that the folder is directly inside wp-content/plugins, not nested one level deeper such as wp-content/plugins/plugin-name/plugin-name. Then refresh the Installed Plugins screen. If WordPress reports a missing main plugin file, inspect the extracted folder and confirm that the ZIP was unpacked correctly.
The site shows a fatal error or a blank page
Use the backup to restore the previous plugin files, or rename the problematic folder through FTP so WordPress cannot load it. If you can reach the dashboard, deactivate the plugin. If not, use the hosting file manager or FTP, then review the server and WordPress error logs before trying another version.
Best Value
The latest version returns automatically
Automatic updates are still enabled, or an update-management service is enforcing them. Disable the plugin’s automatic-update control in the Plugins screen and check any hosting or maintenance system that performs scheduled updates. Recheck the installed version after the next update cycle.
The rollback does not fix the original issue
Test a different known-compatible release rather than stepping backward indefinitely. The cause may be WordPress core, the theme, PHP, another plugin, cached assets, or a configuration change rather than this plugin’s latest code. Use staging to isolate those variables and restore the backup if testing becomes uncertain.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →When not to stay on an older release
Move back to a maintained release as soon as compatibility is restored or the developer supplies a fix. Older packages can contain known security vulnerabilities, stability defects, or incompatibilities with newer WordPress and PHP versions. If the older version is required temporarily, restrict the rollback to staging or a monitored production window, document the exception, and schedule a review instead of treating the downgrade as finished work.
Quick Recap
Quick rollback checklist
- Is the plugin hosted in the WordPress.org directory?
- Have you created and verified a full file and database backup?
- Have you tested the target release on staging?
- Did you download the exact version you intend to install?
- Did you deactivate and remove or rename the current copy before replacing it?
- Did you verify the installed version and test the affected feature?
- Did you disable automatic updates for the rolled-back plugin?
- Have you recorded a plan to test and return to a maintained release?
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
