For a plugin hosted in the official WordPress.org directory, open its page, select Advanced View, choose an earlier release from the version selector near the bottom, and download the ZIP file. You can then install that ZIP from Plugins > Add New Plugin > Upload Plugin. Before replacing the current release, create a complete file and database backup, test the change on staging if possible, and plan how you will prevent an automatic update from immediately restoring the newest version.
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
WordPress plugins are distributed as release packages. Installing an earlier package replaces the code currently active on your site with code from a previous release. That can restore compatibility after a plugin update conflicts with your theme, WordPress core, PHP version, another plugin, or a custom integration. It can also help you identify which release introduced a regression.
As an Amazon Associate I earn from qualifying purchases.
A rollback is not a repair in itself. It changes the plugin files; it does not automatically undo database changes made by a newer release. A plugin may have run upgrade routines when you first updated it, and an older build may not understand the resulting data. Treat a downgrade as a controlled troubleshooting step, not as a permanent security strategy.
The download procedure below applies to plugins available at wordpress.org/plugins. A commercial or privately distributed plugin may use a vendor portal, license account, or a package that is not present in the directory, so the WordPress.org version selector will not provide its releases.
#1 Best Overall
Before you roll back: safety and compatibility checks
Make a complete backup
Take a backup of both the WordPress files and the database immediately before changing the plugin. The file backup should include wp-content and the rest of the site files; the database backup should include the tables used by WordPress and the plugin. Store the backup somewhere outside the server and confirm that you know how to restore it. A plugin rollback can leave the site inaccessible, and a files-only backup will not restore database content.
Use staging whenever you can
Perform the first downgrade on a staging copy rather than on the live site. Check the public pages, the WordPress administration area, forms, checkout or membership flows, scheduled tasks, and any integration that depends on the plugin. If the older release works on staging, repeat the same package and steps on production during a maintenance window.
Record the current state
- Write down the currently installed plugin version and the version you intend to test.
- Note the WordPress core version, PHP version, theme, and related plugins.
- Capture the symptom that prompted the rollback, including the page, action, and error message.
- Save configuration screenshots or export settings if the plugin offers an export function.
Understand the trade-off
Older releases can contain vulnerabilities or bugs that were fixed later. Developers may support only the current release, so an old version might receive no help for security or compatibility problems. Use the oldest release necessary to isolate the fault, then look for a maintained fix or a compatible replacement. Do not leave a vulnerable build exposed simply because it avoids a short-term error.
Method 1: download a previous release from WordPress.org
This is the direct method for directory plugins. The wording and placement of the selector can change; current references use either Development Version or Previous Versions. If you see a different label, look for the version history control in the plugin page’s advanced information area.
- Open the plugin’s directory page. Visit wordpress.org/plugins and search for the plugin, or enter its repository slug in the address bar. Confirm that the page is the exact plugin you use; similarly named plugins can have different slugs and release histories.
- Open Advanced View. In the page’s Information sidebar, select Advanced View. This view exposes release and development information that is not shown on the standard plugin landing page.
- Find the version selector. Scroll to the bottom of the advanced information. Look for a drop-down labeled Development Version or, on some layouts, Previous Versions. The selector may include the current release and earlier tagged releases.
- Choose the target release. Select the version immediately before the update that caused the problem, unless your compatibility testing identifies another release. Avoid choosing an arbitrary much older version: larger gaps can introduce additional incompatibilities and database differences.
- Download the ZIP. Click Download and save the package to your computer. Keep the original filename so you can distinguish it from other test builds, and record the version shown on the directory page.
- Verify the package before installation. Check that the download is a ZIP archive and that its filename or extracted folder identifies the intended plugin. Do not upload a ZIP from an untrusted mirror when the official directory has the release you need.
Install the downloaded ZIP through the WordPress dashboard
The dashboard route is usually the simplest way to replace a directory plugin when you have administrator access and the server accepts plugin uploads.
- Sign in to WordPress with an account that can manage plugins.
- Open Plugins > Add New Plugin.
- Click Upload Plugin.
- Use the file picker to select the older-release ZIP you downloaded.
- Click Install Now and wait for WordPress to unpack the archive.
- If WordPress reports that the plugin already exists, stop rather than creating two copies. Deactivate the current plugin, delete its existing installation, and run the upload again. Deleting the plugin files does not necessarily remove its database settings, but you should still have the backup described above.
- When installation completes, activate the plugin only after checking the displayed version and reviewing any warning on the result screen.
Do not leave both copies active under different folder names unless you are deliberately testing an isolated installation and understand how the plugin identifies itself. Two copies can load the same classes, create duplicate scheduled events, or overwrite shared settings.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →What to do if the dashboard refuses the upload
Upload limits or timeouts
A hosting limit can reject a ZIP even when the package is valid. The dashboard may show a maximum upload size, a timeout, or a generic HTTP error. If you cannot adjust the server limits, use the manual FTP method below. Do not repeatedly submit the same upload while an earlier request may still be running; check the Plugins screen first to avoid partial or duplicate installations.
“Destination folder already exists”
This message means that the plugin’s directory is still present. Deactivate and delete the installed plugin from the Plugins screen, then retry the ZIP upload. If the site cannot load the dashboard, use FTP or your host’s file manager to rename the existing folder before uploading, keeping the renamed copy until the new release has been tested.
“The package could not be installed”
Confirm that you selected the plugin ZIP itself, not a larger archive containing documentation or several files. Download the release again from the directory page if the archive is incomplete. A plugin from a third-party vendor may use a different package structure and cannot be assumed to install through the WordPress.org workflow.
White screen or fatal error after activation
If activation produces a fatal error, use the hosting control panel or FTP to rename the plugin’s folder temporarily. Renaming prevents WordPress from loading it, allowing you to regain access and restore the backup or test another release. Preserve the error message, the PHP version, and the plugin version; those details identify whether the older build is incompatible rather than merely misconfigured.
PC 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 & 11Crashes, 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 minuteMethod 2: install the older release with FTP
FTP is useful when the dashboard upload is blocked or the administration area is unavailable. You need FTP or SFTP credentials and a client or file manager that can transfer directories.
- Download the desired release ZIP from the plugin’s WordPress.org advanced view.
- Extract the ZIP on your computer. The result should be a plugin folder containing the plugin’s PHP files and subdirectories.
- Deactivate the current plugin in Plugins if the dashboard is available. If it is not available, do not delete files blindly; first make sure you have a full backup and identify the correct plugin folder.
- Connect to the site with FTP or SFTP and open
wp-content/plugins. - Rename the existing plugin folder as a temporary backup, or remove it only after confirming that your backup is restorable.
- Upload the extracted older-version folder into
wp-content/plugins. Keep the folder name expected by the plugin unless you have a specific reason to change it. - Return to the WordPress dashboard, open Plugins, verify the displayed version, and activate the plugin.
- Test the site before deleting the renamed folder. Once the rollback is confirmed and the backup is safe, remove obsolete files so they cannot be mistaken for an active installation.
FTP replaces files but does not run the dashboard’s installation screen. If the plugin requires an activation step, visit the Plugins screen after the upload. Never overwrite an active installation while visitors are submitting forms or completing transactions unless you have accepted the risk of a brief interruption.
Method 3: use a rollback plugin
WP Rollback is a third-party option that adds a rollback control to plugins hosted in the WordPress.org directory. After installing it, a Rollback link appears under eligible plugins on the Plugins screen. Choose the target release, confirm the prompts, and allow the tool to replace the installed files.
This method is convenient when you want WordPress to handle the download and replacement from the dashboard, but it has the same safety requirements as a manual downgrade. Take a full backup first, test on staging, and verify that the selected plugin is actually hosted in the directory. It cannot provide versions for a private or vendor-only plugin that has no WordPress.org repository entry.
After the rollback, check the plugin’s settings and run the same reproduction test that exposed the original problem. If the issue remains, the fault may be in another plugin, the theme, core, server configuration, or stored data rather than in the plugin release itself.
Choosing the right method
| Method | Access required | Best use | Main limitation |
|---|---|---|---|
| WordPress.org ZIP plus dashboard upload | Administrator access and a working Plugins screen | Controlled installation of a specific directory release | Can fail because of upload limits or an existing plugin folder |
| FTP or SFTP | Server file-transfer credentials | Dashboard upload errors or a locked administration area | Files are replaced manually, so folder selection and backups require extra care |
| WP Rollback | Administrator access and a directory-hosted plugin | Quick selection of an earlier or newer repository release | Does not cover plugins outside the WordPress.org directory |
Use the dashboard ZIP method when it works and you need a documented, repeatable package. Choose FTP when the administration interface or upload limits prevent that route. Choose WP Rollback when you prefer an in-dashboard selector and the plugin is eligible. For a third-party plugin, obtain the older package and vendor instructions from the developer instead of forcing a repository workflow.
Prevent WordPress from immediately updating the plugin
WordPress can automatically install a newer plugin release after you downgrade. On the Plugins screen, locate the rolled-back plugin and disable its automatic updates using the plugin’s automatic-update control. The exact control may be displayed as an automatic-updates toggle or link depending on the WordPress version and site configuration.
Check the setting again after the rollback and after any site-management operation that may reset plugin preferences. If a host-level management tool, deployment script, or maintenance plugin controls updates, disable the corresponding rule there as well. Keep a written note that the plugin is intentionally held back so a later administrator does not re-enable updates without testing.
Recommended Free Tools
Disabling automatic updates is a temporary safeguard, not a substitute for maintenance. Monitor the plugin’s release notes and your compatibility constraints, test newer versions on staging, and re-enable updates once a supported release resolves the original problem.
Test the site after the downgrade
Confirm the release and activation state
- Open Plugins and confirm that the intended version is displayed.
- Make sure only one copy of the plugin is active.
- Check that automatic updates are disabled for the rolled-back plugin while testing.
Repeat the failure scenario
Perform the exact action that failed before the rollback. A useful test includes the same user role, page, form data, browser path, and connected service. Record whether the symptom disappeared, changed, or remained identical. “It appears to work” is not enough if the affected feature runs only through a scheduled task or a less frequently visited workflow.
Check related functionality
- Visit representative front-end pages and the plugin’s administration screens.
- Submit forms, create or edit the content type managed by the plugin, and verify notifications or integrations.
- Review scheduled events, background queues, webhooks, and logs if the plugin uses them.
- Check PHP and WordPress error logs for new warnings after activation.
- Test on mobile and desktop if the original problem involved front-end scripts or styling.
Watch for data and migration problems
If the newer release changed database structures or settings, an older release may show missing options, failed queries, or partial data. Do not repeatedly switch versions on the live site while guessing. Restore the pre-change backup if data integrity is uncertain, then reproduce the sequence on staging and ask the plugin developer for a supported migration path.
Rank #4
Troubleshooting by symptom
The old version is not listed
Confirm that you are viewing the correct repository page and that the release is a published directory version. The selector may use a different label from the one shown in older instructions. If the release is not offered, it may have been removed, never published in the directory, or belong to a vendor distribution; obtain it from the developer rather than downloading an unverified copy.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The rollback succeeds, but the original bug remains
Test with other plugins temporarily disabled and a standard theme on staging to identify a conflict. Compare the behavior with the current release, the candidate older release, and a clean backup. If every version fails, investigate WordPress core, PHP, server rules, JavaScript errors, permissions, or external services instead of continuing to downgrade.
The site asks for a database upgrade
Do not approve an unfamiliar database conversion on production without a backup and a recovery plan. A database upgrade is often forward-looking; returning to an older plugin can require the newer schema. Check the plugin’s documentation or developer support for the supported sequence, and use staging to determine whether the older release can read the existing data.
The plugin disappears after FTP upload
Inspect the extracted folder. WordPress expects the plugin’s main file to be inside the directory directly under wp-content/plugins; an extra nested folder can prevent detection. Correct the folder layout, refresh the Plugins screen, and verify file permissions without making broad permission changes across the site.
Security and maintenance after a rollback
Record why the site is pinned to the older release, who approved it, and which newer versions were tested. Set a review date rather than leaving the exception indefinitely. At each review, read the plugin’s changelog, test the newest candidate on staging, and check whether the incompatibility has been fixed.
Free tools Windows power users keep installed
One-click scans. No signup required.
Limit exposure while an old version is active: keep WordPress core, the theme, and unrelated plugins maintained; use strong administrator authentication; monitor logs; and remove unused plugins. These steps do not make an outdated plugin safe, but they reduce unrelated attack and failure surfaces.
If the plugin handles payments, accounts, personal data, or site administration, treat the rollback as a higher-risk change. A short maintenance window and a tested restore point are preferable to silently running an unsupported release.
Best Value
When not to use this procedure
- The plugin is not hosted in the WordPress.org directory and you do not have a legitimate older package from its developer.
- You cannot make or verify a full file-and-database backup.
- The rollback would remove a security fix without a clear, time-limited testing purpose.
- The plugin has already performed a database migration that the older release cannot safely reverse.
- The site is in the middle of a critical transaction, import, update, or deployment.
In these cases, restore a known-good backup, use a staging copy, or obtain guidance from the plugin developer or a qualified WordPress administrator. Do not solve a production outage by installing an unknown ZIP from a search result.
A repeatable rollback checklist
- Identify the exact plugin, repository page, current version, and target version.
- Back up all WordPress files and the database; verify the restore path.
- Clone the site to staging and reproduce the problem.
- Download the target release from the plugin’s WordPress.org advanced view, or obtain a verified vendor package for a non-directory plugin.
- Disable the current plugin before replacing its files.
- Install through Plugins > Add New Plugin > Upload Plugin, use FTP/SFTP, or use WP Rollback for an eligible directory plugin.
- Confirm the version, activate only one copy, and disable automatic updates while testing.
- Repeat the failure scenario and test connected site functions.
- Review logs and data integrity, then either keep the temporary rollback with a review date or restore the backup and pursue another fix.
Key limitations to keep in mind
The WordPress.org selector is a release download facility, not a guarantee that every historical version remains compatible with your current site. Directory availability does not establish security support for an older build. A plugin’s own developer may support only the latest release, and a third-party plugin may have an entirely separate distribution system. The safest rollback is therefore the smallest, best-documented change that you can test, reverse, and replace with a supported update as soon as practical.
Frequently Asked Questions
Can I download an older version of any WordPress plugin from WordPress.org?
No. The version selector applies to plugins hosted in the WordPress.org directory. Plugins distributed only through a vendor or private account require an older package from that developer.
Should I deactivate and delete the current plugin first?
Yes, when replacing it through the dashboard, deactivate the current installation and delete its files if WordPress reports that the destination already exists. Keep a verified backup, and never run two copies unintentionally.
Will rolling back remove the plugin’s settings?
Replacing plugin files does not automatically remove database settings, but a newer release may have changed the stored data. Test on staging and restore your backup if the older release cannot safely read the database.
How do I stop the latest version from reinstalling?
Disable automatic updates for the plugin on the Plugins screen and check any host or deployment tool that manages updates. Re-enable updates after testing a supported release.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Quick 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.
