Troubleshooting · Guide
How to Roll Back a WordPress Core Update
Short answer
Roll back WordPress core with the WP Downgrade plugin, a manual file swap over FTP, or the WP-CLI command wp core update --version=X --force. Back up first, pick the last release on the previous branch, and turn off major auto-updates until the conflict is fixed. A core rollback replaces files only, so it does not undo database changes.
Key takeaways
- A core rollback is a short-term fix; plan to move back to the latest version once the conflict is solved.
- WP Downgrade makes WordPress treat the version you pick as the latest one, so you install it like a normal update.
- A manual rollback deletes only wp-admin and wp-includes, never wp-config.php or wp-content.
- A core rollback replaces files only and does not undo database schema changes.
- WordPress 7.1.5, released November 18, 2026, fixes 20 security issues, and only the latest version is actively supported.
When should you roll back a WordPress core update?
Roll back core only when a WordPress update itself broke the site and no plugin or theme fix solves it.
A core rollback is the last resort, not the first step. The Nexcess upgrading and downgrading guide puts it plainly: downgrading is a short-term fix, so plan to move back to the latest version once the problem is solved.
Check the plugin and theme first. Most breakage after a core update comes from a plugin that is not ready for the new version, and rolling back that plugin is safer than rolling back all of WordPress.
Roll back core when the dashboard or front page fails on a clean install, when the error points at a core file, or when the update itself was interrupted and left core files half replaced.
Our fix guide for a site broken after an update walks through the checks that tell you whether core or a plugin is at fault.
What should you do before you roll back core?
Take a full backup of files and database, note your current version, and check which version you are going back to.
Our guide to backing up WordPress covers the full backup, including where to store it so a server fault cannot take both the site and the backup.
Open Dashboard > Updates and write down the version you run now. Our guide to checking your WordPress version shows where the number sits if you are not sure.
WordPress 7.1.5 is the current release as of November 2026, a security release from November 18, 2026 that fixes 20 issues. That date and count come from the WordPress 7.1.5 release page.
Pick the last release on the previous branch, not just any older number. The WordPress 7.1.5 release page lists fixed releases for older branches, including 7.0.9, 6.9.12, and 6.8.13, and notes that only the most recent version is actively supported.
Check that your plugins and theme support the version you are moving to. The Nexcess upgrading and downgrading guide says to look at the “Requires at least” and “Tested up to” fields on each plugin page on WordPress.org.
Also check your PHP version. WordPress 7.1 needs PHP 7.4 or newer, according to SmartWP's WordPress versions table, so going back to an old core version does not help if PHP is the real problem.
Which core rollback method should you use?
Pick the method that matches your access level and whether the dashboard still opens.
| Method | Needs | Best when |
|---|---|---|
| WP Downgrade plugin | Dashboard access | You can still log in to wp-admin |
| Manual FTP swap | FTP or file manager access | The dashboard will not load |
| WP-CLI commands | SSH access and WP-CLI | You manage the server by command line |
| Full backup restore | A backup from before the update | The update changed the database too |
The plugin route is the simplest when the dashboard works. The backup restore is the safest when the database changed, since it is the only method that puts the old database back.
How do you roll back core with WP Downgrade?
Install WP Downgrade, type the target version in its settings, save, and run the update from Dashboard > Updates.
- Go to Plugins > Add New Plugin, search for WP Downgrade, then install and activate it.
- Go to Settings > WP Downgrade and enter the exact version number you want, such as 7.0.9.
- Click Save Changes.
- Go to Dashboard > Updates and click the button to install that version.
- If you see “Database Update Required”, click Update WordPress Database.
The Nexcess upgrading and downgrading guide lists these exact steps and notes that WordPress then installs the older release like a normal update.
WP Downgrade works by making WordPress treat the version you choose as the latest one. The WP Downgrade plugin page explains that the release you specify is downloaded from WordPress.org and installed as any regular update would be.
While a version number is saved in the plugin, WordPress stays on that version. That detail comes from the Nexcess upgrading and downgrading guide, so remember to clear the setting when you are ready to update again.
How do you roll back core by hand over FTP?
Download the older release, delete the wp-admin and wp-includes folders, and upload the old core files without touching wp-content or wp-config.php.
- Download the version you need from the WordPress Release Archive and unzip it on your computer.
- Take a screenshot of your Plugins page so you know which plugins were active, then deactivate them all.
- On your server, delete the
wp-adminandwp-includesfolders. Do not touchwp-config.phpor thewp-contentfolder. - Upload everything inside the unzipped
wordpressfolder except itswp-contentfolder. - Log in to wp-admin and click Update WordPress Database if WordPress asks.
The Nexcess upgrading and downgrading guide gives these steps and warns that downgrading only replaces core files, so it does not revert database schema changes made by newer versions.
The WordPress Release Archive lists every recorded release with ZIP and tar.gz downloads. The release archive shows 7.1.5 from November 18, 2026 as the latest release, with older branches such as 7.0.9 listed below it.
Use the manual route when the dashboard will not load or the plugin route fails. It needs FTP or file manager access, and it takes longer than the plugin route on a slow connection.
How do you roll back core with WP-CLI?
Run two commands from your WordPress folder: one to install the older version, and one to update the database.
wp core update --version=7.0.9 --force
wp core update-db
The Nexcess upgrading and downgrading guide lists this exact pair of commands, with the version number swapped for your target release.
Check the version first with wp core version, which prints the release your site runs now. That command comes from BlogVault's downgrade guide.
WP-CLI is the fastest route when you have SSH access, since it skips the browser entirely. It still does not revert database schema changes, so the same warning applies as with the other methods.
What does a core rollback not undo?
A core rollback replaces files only, so it leaves database changes, content edits, and plugin data exactly as they are.
A major core update can change the database structure, and going back to older files does not undo that change. Kinsta's downgrade guide makes the same point: a rollback does not reverse database schema changes from the newer version.
That is why a full backup restore is safer than a file-only rollback when the update changed the database. A backup taken before the update holds both the old files and the old database, so it returns the whole site to a known state.
If the site works after the file rollback, do not assume the database is fine. Open the dashboard, visit Tools > Site Health, and check for database errors before you call the job done.
How do you stop WordPress from updating again right away?
Turn off automatic updates for major releases until the conflict is fixed, or WordPress will install the newer version again.
WordPress installs minor maintenance and security releases automatically by default, such as 6.8.1 to 6.8.2. That default comes from the Nexcess upgrading and downgrading guide.
On the Updates screen, click "Switch to automatic updates for maintenance and security releases only" to stop major updates while still receiving security fixes. BlogVault's downgrade guide warns that with major auto-updates on, the site can update itself back to the latest version within 12 hours.
Set a date to revisit the update. Rolling back core leaves the site on a release that no longer gets full support, so the fix is only safe for a short time.
How do you check the rollback worked?
Open Dashboard > Updates and confirm the version number, then load the site and test the feature that broke.
- Confirm the version shown matches the version you picked.
- Load the home page and two key pages, and check that menus and images show up.
- Log in to wp-admin and confirm the dashboard loads without errors.
- Test the feature that broke after the update, such as the editor or a checkout step.
- Read debug.log for any new fatal error tied to core files.
If the site still fails on the old version, the core update was probably not the cause. Read the debug log for the first fatal error and look for the plugin or theme file it names.
WordPress 7.2 is planned for December 8, 2026, according to the WordPress 7.1.5 release announcement. If you rolled back to 7.0.9, plan to move forward again before that release lands.
Before you update again, test the new version on a staging copy. Our staging site guide shows how to set one up.
What mistakes should you avoid?
Never roll back core without a backup, and never treat an old version as a permanent home.
- Do not roll back more than one branch, since older branches stop receiving security fixes.
- Do not forget to turn off major auto-updates, or the site updates itself again.
- Do not delete wp-content or wp-config.php during a manual rollback; only wp-admin and wp-includes go.
- Do not skip the database update prompt, since the old files may need the older schema steps.
The WordPress 7.1.5 release page reminds readers that only the most recent version is actively supported, and that sites on WordPress 4.6 or earlier get no security updates at all.
Keep a note of the version you rolled back to, the date, and the reason. When the plugin author or the next core release fixes the conflict, that note tells you exactly what to test before updating again.
Frequently asked questions
Is a backup restore safer than a core rollback?
A full backup restore is safer when the update changed the database, since it is the only method that puts the old database back. A file-only rollback leaves database schema changes in place, which can cause errors even on the old files.
Will WordPress update itself again after I roll back?
Yes. WordPress installs minor maintenance and security releases automatically by default, and major updates can follow if they are enabled. Switch to automatic updates for maintenance and security releases only, and revisit the major update once the conflict is fixed.
How do I confirm the rollback worked?
Open Dashboard > Updates and check the version shown there. Then load the home page, log in to wp-admin, and test the feature that broke. If the site still fails on the old version, the core update was probably not the cause.
How long is it safe to stay on the older version?
Only the most recent version is actively supported, and older branches receive security fixes only as a courtesy. Sites on WordPress 4.6 or earlier get no security updates at all, so staying on an old version is a short-term fix, not a plan.
Which folders do I delete in a manual core rollback?
Delete only the wp-admin and wp-includes folders, then upload the old release files except its wp-content folder. Never delete wp-config.php or wp-content, since they hold your settings, themes, plugins, and uploads.
Which older version should I roll back to?
Use the last release on the previous branch, such as 7.0.9 if you came from 7.1.5. The WordPress Release Archive lists every release, and the version page for the current release lists the fixed release for each older branch.
Sources
- Upgrading and Downgrading WordPress Nexcess Docs
- Version 7.1.5 WordPress.org
- WordPress 7.1.5 Release WordPress.org
- Release Archive WordPress.org
- WP Downgrade | Specific Core Version WordPress.org
- How to Downgrade Your WordPress Site Kinsta
- How to Downgrade WordPress Safely BlogVault
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.
Thanks — we review requests within 3 business days.
