What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
For a plugin hosted in the WordPress.org directory, open its plugin page, select Advanced View, choose an earlier release from the version selector at the bottom of that page, and download the ZIP file. Test the rollback on a staging copy first, back up the site, then install the ZIP through Plugins > Add New Plugin > Upload Plugin. You can also use the WP Rollback plugin or upload the unzipped folder over FTP.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
What downloading an older plugin version actually does
A rollback replaces the code currently running on your site with code from an earlier release. It is useful when a new plugin update introduces a fatal error, breaks a page-builder layout, changes an integration, or conflicts with your WordPress version or another extension. Downloading the ZIP is only one part of the job: the old files must be installed in place of the active copy, and the result must be tested before visitors rely on it.
As an Amazon Associate I earn from qualifying purchases.
This procedure applies to plugins whose releases are published in the WordPress.org plugin directory. A plugin purchased directly from a developer, supplied by an agency, or distributed from another marketplace may not appear in that directory. In those cases, use the vendor’s own archive or support instructions; the WordPress.org version selector and WP Rollback cannot retrieve a package that is not hosted there.
Prepare the site before choosing a release
Older code can contain bugs or vulnerabilities that were fixed later. Treat a rollback as a controlled troubleshooting change, not as a permanent security strategy. Complete these checks before changing the live site:
#1 Best Overall
- Make a full backup. Save both the WordPress files and the database, and confirm that the backup can be restored. A plugin can change database records as well as files, so a files-only copy may not be enough to reverse an unsuccessful test.
- Use staging whenever possible. Clone the site to a staging environment and perform the rollback there first. Check the front end, the WordPress dashboard, forms, checkout or membership flows, scheduled jobs, and any service that depends on the plugin.
- Record the present version. In Plugins > Installed Plugins, note the current version and the reason for reverting. Keeping that information makes it easier to return to the newer release or explain the change to a developer.
- Check the target release date and compatibility. An older version may predate your current WordPress or PHP environment. If the plugin’s release notes identify a required WordPress version, PHP version, add-on, or database migration, account for that before installing it.
- Plan for updates. WordPress may offer the latest update again after a rollback. Decide how you will monitor and re-enable updates rather than leaving an old version unattended.
Do not skip the backup because the change appears reversible. If the old release performs a database migration or leaves the site in a partially updated state, simply uploading the newer ZIP may not restore every setting.
Download an older release from WordPress.org
1. Open the plugin’s directory page
Go to the WordPress.org plugin directory and search for the plugin by name. You can also enter its directory slug in the address bar if you know it. Confirm that the page is the correct plugin by checking its name, author, description, and current release before downloading anything.
Free tools Windows power users keep installed
One-click scans. No signup required.
2. Open Advanced View
In the page’s Information sidebar, select Advanced View. The advanced page contains development and release information that is not shown in the normal plugin listing.
3. Select the required version
Scroll to the version selector at the bottom of the advanced page. Sources and current directory layouts use different wording for this control: it may be labelled Development Version or Previous Versions. The important test is the list of numbered releases, not the exact heading. Choose the version immediately before the problematic update if you are testing a simple one-step rollback; choose an older release only when compatibility or a known regression requires it.
Write down the exact version number you selected. Do not assume that “development” means “latest stable”; inspect the entries and choose a numbered release that matches your plan. If the version you need is not listed, the directory may not expose it, or the plugin may not be hosted there.
4. Download and preserve the ZIP
Click Download after selecting the release. Keep the ZIP unchanged and label it with the plugin name and version, such as plugin-name-2.4.1.zip, so it cannot be confused with the current package. Do not extract and recompress it before using the dashboard uploader; WordPress expects a valid plugin ZIP structure.
Install the downloaded ZIP in the dashboard
The dashboard uploader cannot safely install a second copy under the same plugin directory while the current copy is still present. Use this sequence on staging first and on production only after the backup is complete:
- Sign in with an account that can manage plugins.
- Open Plugins > Installed Plugins.
- Deactivate the plugin you intend to replace. If the plugin is causing a fatal error, use the host’s recovery tools or file access to disable it instead of repeatedly loading the broken dashboard.
- Delete the existing plugin from the Installed Plugins screen, unless you have a deliberate file-management plan to replace its folder. Before deleting, check the plugin’s documentation for settings or files that it says must be preserved.
- Go to Plugins > Add New Plugin > Upload Plugin.
- Select the older ZIP, click Install Now, and wait for the installation result. Do not close the browser while WordPress is unpacking the archive.
- Activate the installed release only after WordPress reports a successful installation. If activation fails, leave it deactivated and restore the backup or the previous package.
If you cannot delete the current copy, another option is to rename its plugin folder before uploading the older package. This is a file-management workaround, not a second active installation: ensure that only one copy is active, and remove the unused folder after you have confirmed which release works.
Use WP Rollback instead of downloading manually
WP Rollback is a third-party plugin that adds a rollback action to plugins and themes hosted in the WordPress.org directory. After installing it, open the Installed Plugins screen and use the Rollback link shown beneath an eligible plugin. Select the target version and follow the confirmation steps.
This method is convenient when you already know the version you want, but it does not expand the repository: it cannot roll back a commercial or private plugin that has no WordPress.org listing. Keep the same staging and backup precautions, because the rollback action still replaces active plugin files and may expose compatibility problems. Disable or review automatic updates afterward so the next routine update does not immediately reinstall the newest release.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Install the older version manually with FTP
FTP is useful when the WordPress dashboard is unavailable or when an administrator prefers direct file control. Download the selected ZIP first, then:
- Extract the ZIP on your computer. The result should be a folder containing the plugin’s main PHP file and supporting files.
- Connect to the site with an FTP client or the file manager supplied by your host.
- Open the WordPress directory, then
wp-content/plugins. - Rename the existing plugin folder as a temporary backup, or remove it only after your full site backup is verified.
- Upload the extracted older-version folder into
wp-content/plugins. Preserve the folder name expected by the plugin unless the plugin’s documentation says otherwise. - Return to Plugins > Installed Plugins, confirm that WordPress detects the plugin, and activate it.
Uploading the ZIP itself into wp-content/plugins will not install it; that directory needs the extracted plugin folder. Conversely, the dashboard’s Upload Plugin control expects the ZIP, so do not submit an already extracted folder there.
Rank #4
Why a rollback may fail
| Symptom | Likely cause | What to check |
|---|---|---|
| The version selector is missing | The plugin is not hosted in the directory, or the page layout has changed. | Confirm the plugin’s official directory listing and look for Advanced View. A vendor-distributed package needs its own archive. |
| “Installation failed” or an invalid ZIP message | The download is incomplete, the archive was altered, or the ZIP contains an extra folder level. | Download the release again, keep the original archive, and use the dashboard uploader with the unmodified ZIP. |
| “Destination folder already exists” | The current plugin folder is still present. | Deactivate and delete the current copy, or rename its folder before installing. Keep only one active copy. |
| The plugin installs but will not activate | The older release is incompatible with the site’s WordPress or PHP environment, or another extension is conflicting. | Read the activation error, compare the target release’s requirements, and test with related extensions disabled on staging. |
| The site shows a fatal error after activation | The rollback did not resolve the conflict, or the old code is incompatible with another component. | Use WordPress recovery mode or file access to deactivate the plugin, restore the backup, and test a different release on staging. |
| The newer version returns automatically | Automatic plugin updates remain enabled. | Review the plugin’s automatic-update setting in the Installed Plugins screen and monitor update notices while the older version is in use. |
Verify that the rollback solved the original problem
Do not stop when the plugin’s version number changes. Run a targeted test based on the failure that caused the rollback:
- Reproduce the original front-end page, form, editor action, or integration that failed.
- Open the relevant dashboard screens and save a harmless test setting.
- Check error logs and the browser console for new errors.
- Confirm that scheduled tasks, webhooks, email delivery, caching, and authentication still operate when those services are part of the plugin’s job.
- Test on more than one browser or user role when the issue affects visitors or administrators differently.
Keep the site on staging until the target workflow passes. If the old release fixes the symptom but breaks another workflow, the rollback is not a complete solution; restore the backup and isolate the conflicting component before trying another version.
Prevent WordPress from replacing the older release
After a successful rollback, open Plugins > Installed Plugins and review the automatic-update control for that plugin. Disable automatic updates for the rolled-back plugin while you investigate, then check the dashboard regularly for security releases and compatibility fixes. A rollback should have an owner and a review date; otherwise an old package can remain in production long after the original problem is forgotten.
When the developer publishes a fix, test the newer release on staging before re-enabling updates. Keep the backup from the rollback period until the replacement has been tested and the site has completed at least one normal maintenance cycle.
Best Value
When the plugin is not in the WordPress.org directory
The directory procedure cannot retrieve packages that are sold or distributed elsewhere. For a commercial, private, or agency-maintained plugin:
- Check the vendor account or download area for an archived ZIP and its release notes.
- Ask the developer which version supports your WordPress and PHP versions.
- Use the same dashboard upload or FTP process once you have a legitimate ZIP.
- Keep proof of the package’s origin and version so a future administrator can identify it.
Do not download an old commercial plugin from an unofficial mirror. An altered package can contain malicious code, and an unofficial copy may not include the vendor’s required license files or update channel.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesChoosing between the three rollback methods
| Method | Best for | Limitations |
|---|---|---|
| WordPress.org download plus dashboard upload | Administrators who want a saved ZIP and a visible, repeatable process. | Requires a directory-hosted plugin and access to the WordPress dashboard. |
| WP Rollback | A quick rollback of an eligible directory plugin or theme from the Installed Plugins screen. | Works only with items hosted in the WordPress.org directory and still requires backups and testing. |
| FTP upload | Sites whose dashboard is inaccessible or administrators who need direct file control. | Requires FTP or file-manager access and careful folder handling. |
How to return to the current release
Once the developer has addressed the problem, download the current release from the normal plugin page or use the standard update prompt. Back up the site again, test the update on staging, deactivate and replace the old package if the dashboard reports a folder conflict, then activate and retest the workflow that originally failed. Re-enable automatic updates only after you have decided that routine updates are safe for this plugin.
If the newer release requires a database upgrade, follow its migration instructions and retain a restorable backup. Never assume that moving forward and backward repeatedly is harmless; alternate versions can leave data or settings in a state that an older release does not understand.
Security and support implications
Older releases may lack fixes for security vulnerabilities, stability defects, and compatibility issues. Developers may support only the latest release, so troubleshooting help for a rollback can be limited. Use the oldest version necessary to confirm or avoid the problem, restrict access to the staging copy, and set a specific plan for replacing it.
For a production site, document the plugin name, exact version, rollback date, reason, backup location, test results, and person responsible for monitoring it. That record turns an emergency downgrade into a controlled maintenance decision and makes the eventual upgrade safer.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Quick Recap
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.
