How to Update WordPress Safely (Ready for WordPress 7.2)

Updating WordPress takes one click. Updating it without breaking anything takes about fifteen minutes of preparation, and that is the part most guides skip. With WordPress 7.2 planned for December 8, 2026 (Release Candidate 1 is due November 17), now is a good time to set up a routine you can repeat for every release.

This guide explains the difference between major and minor updates, the checklist to run before you update, three ways to update WordPress core, what to check afterwards, and how to recover if an update goes wrong.

Major vs minor WordPress updates#

• Minor releases (for example 7.1.3 to 7.1.4) fix bugs and security issues. WordPress installs them automatically by default, and they rarely change how your site works. Install them as soon as they are out.
• Major releases (for example 7.1 to 7.2) add features and change the editor, themes and APIs. They are where plugin and theme conflicts happen, so they deserve a backup, a staging test and a check afterwards.

At the time of writing, WordPress 7.1.4 is the current release.

Before you update: the checklist#

1. Back up files and database, and make sure the backup is stored off your server. Our WordPress backup guide explains how.
2. Check your PHP version under Tools > Site Health > Info > Server. Major WordPress releases raise the recommended PHP version over time; old PHP is a common cause of errors after an update.
3. Update plugins and themes first, so they are on versions that support the new WordPress release. Check each plugin's "Tested up to" version on WordPress.org for major releases.
4. Read the release notes on wordpress.org/news for anything that affects your theme, editor or key plugins.
5. Test on staging for major releases. Our WordPress staging site guide shows how.
6. Pick a quiet time and make sure someone can check the site right after.

How to update WordPress#

Option 1: from the dashboard (most sites)#

1. Go to Dashboard > Updates.
2. Click Update to version x.y.z.
3. Wait. WordPress shows a maintenance message to visitors for a few seconds while it updates.
4. If the release needs it, WordPress asks you to update the database. Click the button.

If the update stalls and your site shows "Briefly unavailable for scheduled maintenance", see our guide to WordPress stuck in maintenance mode.

Option 2: with WP-CLI#

On hosts with SSH access:

• wp core update
• wp core update-db
• wp core version (to confirm)

WP-CLI is faster for many sites and easy to script for agencies.

Option 3: manually (when the dashboard cannot)#

If file permissions or a broken admin block the dashboard update:

1. Download the latest WordPress from wordpress.org and unzip it.
2. Delete the wp-admin and wp-includes folders on your server.
3. Upload the new wp-admin and wp-includes, and the loose files in the root, overwriting the old ones.
4. Do not touch wp-content or wp-config.php.
5. Visit /wp-admin and run the database update if asked.

Should you turn on automatic updates for major releases?#

Minor and security releases are automatic by default, and you should keep them that way. For major releases, automatic updates are convenient but risky on business sites, because a conflict can appear overnight with nobody watching. A sensible rule: automatic major updates on simple sites with monitoring; manual, tested updates on stores and client sites. Our guide to WordPress automatic updates shows how to control each type.

After the update: what to check#

1. Clear every cache: caching plugin, host cache and CDN.
2. Open your key pages in a private window: home, top landing pages, pricing, contact, cart and checkout. Check on desktop and mobile.
3. Submit a form and, on a store, place a test order.
4. Open the editor and edit a post to make sure it loads.
5. Check Tools > Site Health for new warnings.

If something breaks after updating WordPress#

• White screen or "critical error": WordPress usually emails the admin a recovery link. Use it to log in and deactivate the plugin or theme involved. Our guides to the critical error and the white screen of death go step by step.
• A layout or feature broke: it is almost always a plugin or theme that is not ready for the new version. Update it, or roll it back; see how to roll back a WordPress plugin and how to find a plugin conflict.
• Need WordPress itself back on the old version: restore your backup. Downgrading core by hand is possible but risky after a database update.

Ready for WordPress 7.2#

For the December 8 release: update plugins and themes during the release candidate period, test 7.2 on staging once RC1 is out on November 17, and plan the live update for a quiet day after the release, not the minute it ships. If you run WooCommerce, avoid updating during your Black Friday week; see our WooCommerce update guide.

Know within minutes if an update changed your site#

Clicking Update is easy. Noticing that the checkout button lost its styling, or that a page now returns an error, is the hard part. The free MyKavo WordPress plugin records every core, plugin and theme update, including automatic ones at night:

• The culprit, named. On paid plans, from Starter, MyKavo checks your key pages right after each update and labels any change: "Appeared after: Updated WordPress 7.1.4 to 7.2".
• "Did it crash?" (free). About ten seconds after an update, the site checks its own home page and up to three monitored pages for server errors, the critical error page and PHP fatal errors.
• Snapshots and one-click rollback (free). A copy of each plugin and theme is saved right before it updates, so a plugin that breaks with the new release can be put back for seven days.
• Safe Update All (free). Update plugins one at a time with a check after each, and roll back automatically if one breaks the site.

Summary#

Install minor releases right away. For major releases, back up, check PHP, update plugins and themes first, test on staging, then update from Dashboard > Updates, WP-CLI or manually. Afterwards clear caches and check your key pages, forms and checkout. If something breaks, use the recovery email, roll back the plugin or theme involved, or restore your backup. For WordPress 7.2, test during the release candidate and update on a quiet day after December 8.