General

Upgrading and Downgrading WordPress

This article explains how to update WordPress to the latest version and how to go back to an earlier version if an update causes a compatibility problem with your plugins or theme. Whichever you’re doing, take a full backup of your site first. Downgrading is a short-term fix, so plan to move back to the latest version once the problem is solved.

Overview

Keep WordPress up to date, and only downgrade as a short-term fix when an update breaks something on your site. This article covers both, plus what to check before and after. Updating is sometimes called upgrading; they mean the same thing.

Note

If your site is hosted with Nexcess, see WordPress Upgrade and Downgrade in our hosting docs for options specific to your hosting plan.

Which one do you need?

Your situationWhat to do
A new WordPress version is availableUpdate WordPress
A plugin says it needs a newer version of WordPressUpdate WordPress
Something broke right after a WordPress updateRestore your backup, or downgrade WordPress, then report the problem
Something broke right after a plugin or theme updateRoll back that plugin or theme, not WordPress. See Accessing and Installing Older Plugin Versions
You’re not sure what caused the problemRun a conflict test first. See Testing Conflicts With Themes and Other Plugins

Before you start

A few minutes of preparation makes any problem easy to undo. Do these steps whether you’re updating or downgrading.

  1. Write down your current WordPress version. Go to Dashboard > Updates, or Tools > Site Health > Info and open the WordPress section. If you need to downgrade later, this is usually the version to go back to.
  2. Back up your whole site, including the database and all files. Your host may already take daily backups, so check that a recent one exists. If not, make one now and keep a copy somewhere other than your server.
  3. Check that your plugins and theme support the version you’re moving to. On each plugin’s WordPress.org page, look for the minimum WordPress version (Requires at least) and the newest version it’s been tested with (Tested up to). For our plugins, see Version Compatibility.
  4. Check your PHP version. Newer WordPress versions can need a newer PHP version. You’ll find yours under Tools > Site Health > Info > Server. See PHP Requirements.
  5. Test on a staging site if you can, so you see the result before your live site changes. See Testing Updates in a Staging Environment.
  6. Pick a quiet time. Your site can be unavailable for a minute or two. Avoid updating during peak traffic, active checkout windows, or scheduled campaign launches.
  7. Make sure you can reach your site’s files through FTP, SFTP or your host’s file manager, in case you get locked out of the dashboard.

Updating WordPress

Most sites update in one click from the dashboard. Use that unless it fails.

Update from the dashboard

  1. Complete the checks in Before you start.
  2. Update your plugins and theme first, so they’re ready for the new version. If a plugin update says it needs the newer WordPress, leave it until WordPress is updated.
  3. Go to Dashboard > Updates.
  4. Click Update to version followed by the version number. Keep the page open until it finishes. Visitors see a short maintenance message while it runs.
  5. If you see Database Update Required, click Update WordPress Database.
  6. Run the checks in After you update or downgrade.

If you’re several versions behind

Major versions are the first two numbers, like 6.8 or 6.9. If you’re more than two major versions behind, WordPress recommends updating one major version at a time, especially on large sites. The methods in Downgrading WordPress below let you install a specific version, so you can use them to step up too. Take a fresh backup between steps.

Automatic updates

WordPress installs minor maintenance and security releases automatically by default (e.g., 6.8.1 to 6.8.2). Major version updates (e.g., 6.8 to 6.9) require manual confirmation or opting in, though some managed hosts may configure major auto-updates for you.

Other ways to update

  • Your host’s tools. If your hosting control panel has a WordPress manager, you can usually update from there. Nexcess customers can follow WordPress Upgrade and Downgrade.
  • WP-CLI, if you’re comfortable with the command line: run wp core update, then wp core update-db.
  • Manually, if the dashboard update keeps failing: follow Option 3: Downgrade manually below, using the latest version from WordPress.org instead of an older one.

Downgrading WordPress

Downgrade only to fix a specific problem, and update again as soon as the problem is fixed.

Warning

Downgrading only replaces core files—it does not revert database schema changes made by newer versions. If an update altered your database structure, restoring a full backup is the only way to return to the prior state.

Which version should you go back to?

Go back to the version you were on before the update, the one you wrote down in Before you start. If you don’t know it, pick the newest release of the previous major version. For example, if 6.9.0 caused the problem, try the latest 6.8 release. All versions are listed in the WordPress Release Archive. Don’t go below the minimum version your plugins and theme need.

Option 1: Restore your backup

If you have a backup from just before the update, restoring it is the cleanest fix. It puts your files and your database back exactly as they were. Use your host’s restore tool or your backup plugin.

Restoring also removes any activity logged since the backup was taken, including orders, transactions, new content, and form submissions. Export or record recent entries first.

Option 2: Use the WP Downgrade plugin

The free WP Downgrade | Specific Core Version plugin makes WordPress treat the version you choose as the latest one, so you install it like a normal update. It’s a third-party plugin, not one of ours.

  1. Go to Plugins > Add New Plugin, search for WP Downgrade, then install and activate it.
  2. Go to Settings > WP Downgrade, enter the exact version number you want, such as 6.8.3, and save.
  3. Go to Dashboard > Updates and click the button to install that version.
  4. If you see Database Update Required, click Update WordPress Database.

While a version number is saved in the plugin, WordPress stays on that version. When you’re ready to update again, clear the version number or deactivate the plugin, then update as normal.

Option 3: Downgrade manually

Use this if you can’t reach your dashboard, or the plugin doesn’t work on your site. You’ll need access to your site’s files through FTP, SFTP or your host’s file manager.

  1. Download the version you need from the WordPress Release Archive and unzip it on your computer.
  2. Take a screenshot of your Plugins page so you know which plugins were active, then deactivate them all.
  3. On your server, delete the wp-admin and wp-includes folders. Don’t touch wp-config.php or the wp-content folder.
  4. Upload everything inside the unzipped wordpress folder except its wp-content folder. When asked, overwrite the existing files.
  5. Log in to your dashboard. If you see Database Update Required, click Update WordPress Database.
  6. Reactivate your plugins one at a time, checking your site after each one.

For more detail, see Upgrading WordPress in the WordPress documentation.

Option 4: Use WP-CLI

If you’re comfortable with the command line, run this from your WordPress folder, replacing the version number:

wp core update --version=6.8.3 --force
wp core update-db

After you downgrade

  • Stop WordPress updating itself straight back. If Dashboard > Updates shows automatic updates for all new versions, switch to maintenance and security releases only. If your host manages updates, ask them to pause WordPress core updates.
  • Report the problem to the plugin or theme developer so it can be fixed. Include your system information; see Sharing Your System Information.
  • Update again once a fix is released, and turn automatic updates back on.

After you update or downgrade

Spend five minutes checking your site so you catch problems before your visitors do.

Quick checklist

  • Go to Dashboard > Updates and confirm it shows the version you expected.
  • Clear your caching plugin, server cache, CDN and browser cache. See How to Clear Your Site and Browser Cache Properly.
  • Visit your home page, a standard post, and a core landing page to verify the layout.
  • In the dashboard, edit an existing post or page to verify the editor loads properly.
  • If your site uses e-commerce, forms, or user logins, complete a test transaction or submission.
  • Check the Plugins page for any plugin that was deactivated or shows a version notice.
  • Check Tools > Site Health for new warnings.

Common problems

What you seeWhat to do
“Briefly unavailable for scheduled maintenance” for more than a few minutesUsing your file manager or FTP, delete the .maintenance file in your site’s main folder.
“There has been a critical error on this website” or a blank pageCheck the site admin’s inbox for an email titled “Your Site is Experiencing a Technical Issue”. It has a link that lets you log in and deactivate the plugin or theme causing the error. No email? Rename the wp-content/plugins folder to turn off all plugins, then rename it back and reactivate them one at a time.
The update fails with “could not copy files” or “Download failed”This is usually file permissions or disk space on your server. Contact your host, or use the manual method.
“Database Update Required” keeps coming backClick Update WordPress Database again. If it repeats, clear your object cache or ask your host to.
A plugin says it needs a newer WordPress version, or has been deactivatedYou’ve gone below that plugin’s minimum version. Update WordPress, or install an older version of the plugin. See Accessing and Installing Older Plugin Versions.
Pages or the calendar look broken or unstyledClear every cache again, including your CDN. Then run a conflict test. See Testing Conflicts With Themes and Other Plugins.

To see the error behind a problem, turn on WordPress’s debug log. See Debugging in WordPress.

Frequently asked questions

Will I lose my content, settings, or database records?

No. Your content and settings live in the database and the wp-content folder, and none of the update or downgrade methods replace them. The exception is restoring a backup, which brings back everything as it was at backup time.

The problem started after a plugin update. Do I need to downgrade WordPress?

No. Roll back that one plugin instead. See Accessing and Installing Older Plugin Versions.

I downgraded and the problem is still there. What now?

The WordPress update probably wasn’t the cause. Update WordPress again, then run a conflict test to find the plugin or theme involved.

How long can I stay on an older version?

As short a time as possible. Keep automatic minor updates on so you still get security fixes for that version.

Getting help

If you’re stuck, contact our support team. See the Software Support Policy and Contacting Support. To help us help you faster, include:

  • The WordPress version before and after the change
  • The method you used
  • Any error message, word for word, or a screenshot
  • Your system information. See Sharing Your System Information

Filed under FAQ
Last updated: November 2, 2026
Was this page helpful?
Thanks for the feedback!