What is new in WordPress 7.1 and should you update your website?

WordPress 7.1 "Mary Lou", released on August 19, 2026, adds responsive styling in the Site Editor, a new media editor, Tabs and Playlist blocks, and native support for AVIF, HEIC and HDR images. Yes, you should update, but go straight to 7.1.3, the security release from October 6, 2026, and only after a backup and a test on a copy of your site.

The update button takes one click. The real work is knowing what that click changes on a site that takes orders, books appointments or collects leads, and what happens if one plugin isn't ready. With WordPress running 39.6% of all websites, according to W3Techs data from October 2026, a lot of business owners face the same decision this month.

The new features are worth having. The risk sits in old plugins and old server software rather than in anything this release adds.

What WordPress 7.1 changes on your website

Most of what changed in 7.1 shows up in the screens you use every week. More than 800 contributors, over 170 of them first-timers, shipped more than 1,500 improvements and fixes, according to the official release announcement.

• Responsive styling, so a block can have its own font size, colour, spacing and layout on tablet and mobile without custom CSS.
• A media editor that opens in a modal and replaces the old inline cropping tool.
• Native AVIF, HEIC and HDR gain map support, with resizing and compression moved into the browser where it can run.
• Two new blocks, Tabs and Playlist.
• Notes that take rich text and mentions, for feedback on drafts.
• An admin bar that now stays on screen as you move across every editor.

The release is named after Mary Lou Williams, the jazz pianist, arranger and composer. There is no single headline feature, and that suits a business site: an editor who used to file a ticket to fix a heading on mobile can now do it alone in the editor.

Responsive styling without writing CSS

Responsive styling lets you set typography, colour, background, border, dimensions, spacing and layout separately for tablet and mobile, either on a single block or for every block of one type through Global Styles. Switch the editor preview to Tablet or Mobile, make the change, and it applies only at that screen size. The default style still covers everything else.

Out of the box, Mobile means screens up to 480px wide and Tablet covers 480px to 782px. Theme authors can move those breakpoints in theme.json with px, em or rem values, so the editor previews match the theme's actual layout.

Think of a services page whose hero headline wraps onto five lines on a phone. Before 7.1, the fix was a media query in a custom CSS box that only a developer would touch. Now it is a setting on the block, saved with the page rather than tucked away in a stylesheet. A site that needs a locked design can switch responsive editing off with the responsiveEditingEnabled setting, and any styles already saved keep working.

AVIF, HEIC and HDR photos, processed in your browser

Version 7.1 can resize, compress and convert images in the browser before they upload, using wasm-vips, a WebAssembly build of the libvips image library. iPhone HEIC photos become web-ready JPEGs with the original kept alongside, AVIF works even when the host can't read it, and HDR gain maps survive in every generated image size.

Compression improves too. The developer note on client-side media processing says libvips produces JPEGs about 15% smaller than GD or Imagick, the server-side libraries WordPress has used until now. Across a catalogue of a few hundred product photos, that adds up to lighter pages without anyone touching an export setting.

One detail decides whether you see any of this: browser processing needs Chrome 137 or Edge 137 and newer. Firefox and Safari fall back to server-side processing with no visible change, so an editor uploading from Safari on a Mac gets the old behaviour, and HEIC or AVIF handling then depends on what your host's image library supports.

The new media editor replaces the old inline cropping tool with one modal for freeform and fixed aspect-ratio cropping, horizontal and vertical flips, precise rotation and metadata editing. The Media Library grid also scrolls continuously by default now, with a per-user option to go back to pages.

Tabs, Playlist and better Notes for editors

Two blocks are new in 7.1. Tabs splits related content into tabbed panels instead of one long scroll, and Playlist groups several audio tracks in one player with an optional waveform. Notes, the comments editors leave on a draft, now take rich text and mentions, so feedback reaches the right person without a separate email thread.

Tabs is the block most business sites will use. Pricing tiers, product specifications and service comparisons have needed a page builder or a tabs plugin until now. Every plugin is one more thing to update and one more thing that can break, so a built-in block takes one dependency off the list.

Playlist serves a smaller group: podcasters, musicians and course creators who host audio on their own site. The waveform gives listeners a sense of each track before they press play.

The AI Client and Connectors that arrived in 7.0

WordPress 7.0 "Armstrong", released on May 20, 2026, added an AI Client that lets WordPress talk to generative AI models. Paired with the Abilities API, it gives plugins a shared way to build automation and content tools. A new Settings > Connectors screen links the site to AI providers, with Anthropic, Google and OpenAI featured from day one.

Plugins that register with the AI Client get a connector card on that screen automatically. Check where those credentials end up before anyone pastes them in. The Connectors API developer note states that API keys stored in the database are masked in the interface but not encrypted. Credentials are read from environment variables first, then PHP constants, then the database, so ask your host or developer to set them as environment variables and leave the admin field empty.

The same release redesigned the dashboard and added a Command Palette on Ctrl+K (⌘K on a Mac), a font management page and custom CSS per block. It also raised the minimum PHP version to 7.4. Sites that skipped 7.0 get both releases in one update, so budget testing time for both.

What can break when you update to WordPress 7.1

For a site on maintained plugins and a current PHP version, this is a routine update. Problems come from a short list: plugins that add old-style meta boxes under the post editor, plugins built on jQuery UI, and servers still running PHP 7.2 or 7.3, which WordPress dropped in 7.0. Those are the places to look before you click.

The 7.1 Field Guide for developers confirms the post editor now always loads inside an iframe, including on sites that register legacy meta boxes. Plugins whose scripts or styles reach from the admin page into the editor content may stop behaving as expected. SEO panels, custom field boxes and product or booking settings under the editor are the ones to click through on a test copy.

Version 7.1 also moves jQuery UI to 1.14.2. Older plugins use it for date pickers, sortable lists and drag-and-drop settings screens, so open those screens once after the update, before a customer finds the problem.

On the server, 7.0 raised the minimum PHP version from 7.2.24 to 7.4, and WordPress now recommends PHP 8.3 or newer. MySQL 8.0 reached end of life on April 30, 2026, and the WordPress hosting handbook advises moving those sites to MySQL 8.4 LTS. Ask your host which versions you run. It takes one support message.

Why 7.1.3 matters more than the feature list

Three security releases followed 7.1 within seven weeks. The first, 7.1.1, arrived on September 17, 2026 with fixes for 11 vulnerabilities. Five days later, 7.1.2 closed an unauthenticated path traversal flaw in page-template handling that could, under some conditions, lead to remote code execution. Then 7.1.3, on October 6, fixed seven more. As of October 21, 2026, 7.1.3 is the version to install.

Several of the 7.1.1 fixes need a logged-in account at Contributor level or above, such as an arbitrary post overwrite and the disclosure of draft post slugs. Sites with many authors, guest writers or forgotten agency logins carry more of that exposure, so deleting unused accounts belongs on the update checklist. One fix covered a stored cross-site scripting flaw that an anonymous visitor could trigger through an approved comment.

Security fixes are backported to older branches, currently as far back as 4.7, but the project says only the most recent version is actively supported. Minor and security releases install themselves in the background on most sites, a behaviour in place since WordPress 3.7. Major releases such as 7.1 still wait for someone to click Update Now.

How to update to WordPress 7.1 safely

Back up first, check PHP, update plugins, test on a staging copy, then update the live site at a quiet hour and clear the cache. That order puts the cheap checks before the expensive mistakes, and it works the same for a five-page brochure site and a busy store.

1. Take a full backup of the files and the database, and store it off the server. The official WordPress update guide lists this before anything else.
2. Check your PHP version in the hosting panel or under Tools > Site Health > Info. Below 7.4, upgrade PHP before you touch WordPress.
3. Bring plugins and themes up to date, and delete the ones you no longer use.
4. Copy the site to staging, or to a local install if your host has no staging tool, and update the copy to 7.1.3.
5. Test the pages that earn money: checkout, contact and booking forms, the post editor with your SEO and custom field panels, and an image upload straight from a phone.
6. Update the live site from Dashboard > Updates during your lowest-traffic hour, then clear any page cache so visitors see the new version.
7. Submit a real test order or form on the live site within the hour.

If a "failed update" message gets stuck on screen, the official fix is to delete the .maintenance file from the WordPress folder over FTP. When something breaks after a successful update, restore the backup first and debug on the staging copy, not on a live checkout.

Should you update now or wait?

Update to 7.1.3 now if you run a brochure, blog or lead-generation site on a short list of maintained plugins. Test on staging first if you run a store, a membership site or plugins that put boxes under the post editor. Fix PHP first if you are below 7.4, because the 7.x releases need it.

The case for updating now: the security fixes, per-device styling, HEIC uploads from phones and a built-in Tabs block, plus a smaller jump next time. The case for waiting a week or two: a plugin you depend on may ship a 7.1 compatibility release, and waiting for it costs less than a rollback.

Waiting is fair for a store in the middle of its busiest season. Waiting indefinitely is not. Each skipped release adds editor changes and security patches to test in one larger jump, and the site drifts further from the version the WordPress project actively supports.

Picture two sites. A clinic with eight plugins and one booking form can update on staging in the morning, book a test appointment and go live after lunch. A store with 45 plugins and a custom checkout field needs a day of testing and a conversation with whoever built that checkout. Same release, different homework.

If your site has fallen far enough behind that a rebuild looks cheaper than another round of fixes, email Techno Mantraa at info@technomantraa.com for a custom quote.