WordPress 7.1: What Changed for Business Sites and Should You Update?

WordPress 7.1, released on 19 August 2026, is the current major version of WordPress, and most business sites should be on it by now, ideally on the latest maintenance release (7.1.4 at the time of writing). It adds responsive styling without code, a new image editor, better team notes and faster image uploads. The main risk is not WordPress itself but older plugins that hook into the post editor, so test on a staging copy before you update a site that earns money.

This article is for business owners, marketing teams and agencies who run WordPress sites and need to decide when and how to update. It covers what is new, what changed under the hood, the PHP version you need, and when it is worth handing the update to a developer.

#What WordPress 7.1 is and when it came out

WordPress 7.1 is the second major release of 2026. The official release post (opens in a new tab) names it "Mary Lou" after the jazz pianist Mary Lou Williams and credits more than 800 contributors. It followed WordPress 7.0, which came out on 20 May 2026.

Since then, the 7.1 branch has had four maintenance releases. The WordPress releases page (opens in a new tab) lists 7.1.4 on 28 October 2026, released together with 7.0.8 for sites still on the 7.0 branch. Maintenance releases fix bugs and security issues without adding features, and most sites receive them automatically.

WordPress 7.1 released

19 Aug 2026

Latest maintenance release, 7.1.4

28 Oct 2026

Scheduled date for WordPress 7.2

8 Dec 2026

The next major version is already close. The WordPress 7.2 Beta 5 post (opens in a new tab) gives 8 December 2026 as the scheduled final release date. If your site is still on 6.x or 7.0, you will soon be two major versions behind, which makes each later update bigger and riskier.

#What is new for editors and site owners

The changes in 7.1 make everyday editing faster, especially for teams that manage their own pages. None of them require you to change how your site works, but some are useful enough to plan for.

#Responsive styling without code

Responsive styles are the most useful change for business sites. Before 7.1, making a block look different on a phone usually meant custom CSS or a page builder. Now editors can set it from Global Styles or a block's own settings and preview the page at different screen widths while editing.

For a business, this means fewer small developer jobs for mobile fixes. It also means a block theme can now do more of what people previously bought a page builder for. If you are weighing that question, my comparison of Elementor, Gutenberg and Avada covers the trade-offs.

#Better collaboration through notes

Notes now support formatting, links and @mentions that notify colleagues, and a note can be attached to a specific piece of text. For agencies and in-house teams, this moves review comments out of email and screenshots and into the page itself.

#Faster, lighter image uploads

WordPress 7.1 processes images in the browser before upload. The release post says compression, resizing and thumbnail creation now run in the browser using a WebAssembly build of the libvips image library, which reduces server load and the memory and timeout errors that cheap hosting often throws on large uploads. It also adds native support for AVIF and HEIC images, which matters if your team uploads photos straight from an iPhone.

#What changed for plugins and themes

The changes that can affect a working site are in the WordPress 7.1 Field Guide (opens in a new tab), the developer notes published before each release. For a business owner, four of them are worth knowing about.

1. The post editor always runs in an iframe. The field guide says 7.1 completes the move to an iframe-based post editor, including on sites that register old-style meta boxes. An iframe keeps the editing area separate from the rest of the admin screen. Plugins that add boxes or scripts to the editor and reach across that boundary may stop working properly.
2. jQuery UI was updated to 1.14.2. Older plugins that depend on jQuery UI for date pickers, sliders or drag-and-drop in the admin should be tested.
3. The Media Library scrolls endlessly by default. It loads more items as you scroll instead of showing pages. Each user can switch back to pages. Plugins that change the media grid should be checked.
4. The admin bar stays visible in editors. Plugins that add items to the toolbar may behave differently on editor screens.

The planned change to hide the Classic block from the block inserter was reverted, so sites that still rely on the Classic block keep it in 7.1.

Developers also got new tools in 7.1, including responsive breakpoints in theme.json, a public SVG Icon API and an extended Abilities API for automation and AI tools. These do not change your site on their own, but they show where WordPress is heading: more design control in the block editor and more ways for other software to work with a site safely.

#Minimum PHP version and hosting

WordPress needs PHP 7.4 or newer. The minimum was raised from 7.2.24 to 7.4 in WordPress 7.0, as announced in the core team's post on dropping support for PHP 7.2 and 7.3 (opens in a new tab). That post says sites still on PHP 7.2 or 7.3 remain on the 6.9 branch and do not receive newer versions.

The minimum is not the target. The WordPress requirements page (opens in a new tab) recommends PHP 8.3 or greater and MySQL 8.0 or MariaDB 10.11 or greater, and warns that older versions may leave a site open to security threats. The hosting team's compatibility page for 7.1 (opens in a new tab) goes further and suggests PHP 8.4 or 8.5 for new installations.

PHP 8.2 stops getting security fixes on 31 December 2026, so many sites need a PHP change in the next few weeks anyway. I cover that move in detail in PHP 8.2 end of life for WordPress and WooCommerce sites.

#Should you update to WordPress 7.1 now?

Yes, for most sites, with testing first. 7.1 has been out since August and has had four maintenance releases, so the early bugs have been fixed. Staying on an older major version means you miss security improvements, and some plugins now expect a recent WordPress: WooCommerce, for example, now requires WordPress 7.0 or newer on its plugin page.

There are three cases where waiting a short time is sensible:

• A plugin you depend on is not marked as tested with 7.1. Ask the vendor or test it on staging first.
• Your site runs on PHP older than 7.4. The PHP upgrade has to come first, and that is a project of its own.
• You are in a busy sales period. Update after the peak, not during it, unless the release fixes a security issue.

#What a safe update looks like

A safe WordPress update is a short routine, not a single click. The official update guide (opens in a new tab) says to back up first and to check that plugins and themes are compatible with the version you are installing. For a business site, I would add a staging test and a check of the pages that earn money.

1. Take a full backup of files and database, stored away from the server, and make sure you know how to restore it.
2. Update on a staging copy first. This is a private copy of your site where breaking things costs nothing.
3. Test what matters to the business: the home page, main service pages, contact and quote forms, checkout if you sell online, logins, and the editor screens your team uses.
4. Update the live site at a quiet time, then repeat the key checks.
5. Watch for a day or two. Check form submissions and orders still arrive, and look at the error log if your host provides one.

My website maintenance checklist puts this routine into a monthly schedule.

#Do it yourself or hire help?

A small brochure site with a few well-known plugins can usually be updated by its owner, as long as there is a working backup. A developer is the better investment when the site makes money every day, when it has custom code or plugins that have not been updated in a long time, or when it is still on an old PHP version.

What a professional adds here is the testing, not the click. That means a staging copy, a list of the pages and forms to check, a clear rollback if something fails, and fixing conflicts rather than just switching plugins off. That is what website maintenance and support covers. If an update has already caused errors, plugin conflict fixes find the plugin at fault, and emergency WordPress fixes cover a site that is down right now.

#Where to start

Log in and check three things: your WordPress version under Dashboard, your PHP version under Tools and Site Health, and whether any plugin shows that it has not been tested with your WordPress version. If you are on PHP 7.4 or newer and your plugins are current, plan the 7.1 update this month with a backup and a staging test. If not, sort out PHP and the old plugins first, because WordPress 7.2 arrives in December.