WordPress 7.1 is out: what to do before you press update

A new major version of WordPress, 7.1, was released on August 19, 2026, timed to coincide with WordCamp US. The headline changes are in how people work together on content, how styling is handled, and how media is managed.

If you run a small business site, the useful question is not what is in the release. It is when you should install it, and what you should have in place first. Major releases are where sites break, and the breakage almost never comes from WordPress itself. It comes from a plugin or theme that was written against the old behavior and has not caught up.

You are probably not being asked to act today

Minor WordPress releases (the security and maintenance ones) install themselves on most sites by default. Major releases like 7.1 usually do not. That difference is deliberate, and it is in your favor. It gives plugin and theme authors a few weeks to publish compatibility updates, and it gives you time to let other people find the sharp edges first.

Waiting two or three weeks after a major release costs you almost nothing. The new features are not urgent. Security fixes, when they come, are shipped as minor releases that reach you anyway.

One exception: if your site is running a WordPress version that is several years old, sitting still is the riskier choice. Old versions stop receiving security fixes, and the longer the gap, the more painful the eventual jump. That situation is worth raising with whoever maintains the site rather than solving on your own.

Have a backup you have actually seen

Before any major update, you want a full backup taken that day: files and database, stored somewhere that is not the same server as the website. A backup that only exists inside your hosting account is not much protection if the account itself is the problem.

The part people skip is confirming the backup exists. Open your backup plugin or your host’s backup panel and look at the date and time of the most recent one. If the newest entry is from four months ago, or the plugin is reporting errors it has been reporting for a while, you have a housekeeping job before you have an update job.

You do not need to know how to restore the backup yourself. You need to know that a restorable copy exists and who would perform the restore if it came to that.

What to check after the update

Give yourself fifteen minutes and walk the parts of the site that make you money. Load the homepage while logged out. Submit your own contact form and confirm the message arrives in the inbox. If you sell online, add something to the cart and get as far as the payment step. If you take bookings, make a test booking. Then open a couple of pages on your phone.

Because this release touches styling and media, pay particular attention to how pages look rather than only whether they load. Spacing, fonts, and image sizes are the sort of thing that shifts quietly and that nobody reports for weeks.

Also open the media library and check that images are still displaying and still uploading. A site that looks fine but silently refuses new uploads will not announce itself until the next time you add a product photo.

When it goes wrong, and when to stop

Most post-update problems are a plugin conflict, and most are fixable. But there is a line worth respecting: if the site is down, if checkout is broken, or if you are being told to edit files, stop and call the person or company responsible for maintaining the site. Attempting a database restore or file surgery while a live site is failing is how a recoverable morning becomes an expensive week.

If you have no one, most hosts offer some level of support, and many can restore a recent backup for you. Find out which category yours falls into before you need the answer.

The wider point about a release like 7.1 is that the collaboration and media changes reward sites that are already tidy: current plugins, a theme that is still maintained, backups that run. If you cannot say with confidence that those three things are true, that is the work in front of you, not the new version number.

Background reading: What’s New in WordPress 7.1? (Features & Screenshots)