WordPress 7.1 "Mary Lou", released on August 19, 2026, adds per-device styling, a new media editor, Tabs and Playlist blocks and in-browser processing for iPhone HEIC photos. Yes, you should update. Install 7.1.3, the October 6 security release, and only after a backup and a test on a staging copy.
Clicking Update takes seconds. Your PHP version and any plugins that add panels under the post editor decide how much testing you need. WordPress runs 39.6% of all websites, according to W3Techs data from October 24, 2026, so plenty of site owners face this choice in the same few weeks.
On this page
- WordPress 7.1 features at a glance
- Responsive styling without writing CSS
- Phone photos and image processing in the browser
- Tabs, Playlist and Notes for editors
- What WordPress 7.0 added if you skipped it
- What can break when you update to WordPress 7.1
- What PHP version does WordPress 7.1 need?
- WordPress 7.1 release date and the patches since
- How to check plugin compatibility before you update
- How to update to WordPress 7.1 safely
- Should I update WordPress now or wait?
- When a WordPress 7.1 update turns into a rebuild
WordPress 7.1 features at a glance
More than 800 contributors, over 170 of them first-timers, shipped more than 1,500 improvements and fixes, according to the official WordPress 7.1 release post. The name honors jazz pianist and composer Mary Lou Williams.
| Feature | What changes | Who notices first |
|---|---|---|
| Responsive styling | Font size, color, spacing and layout per device, with no CSS | Anyone who edits pages |
| Media editor | One modal to crop, flip, rotate and edit image metadata | Editors who prepare images |
| Browser image processing | Chrome and Edge resize, compress and convert HEIC before upload | Teams uploading phone photos |
| Tabs block | Tabbed panels without a page builder | Sites with pricing or spec pages |
| Playlist block | Several audio tracks in one player, optional waveform | Podcasts and course sites |
| Notes | Rich text, @mentions and notes pinned to a phrase | Teams reviewing drafts |
| Admin bar | Stays on screen in every editor | Everyone who logs in |
| Button states | Separate hover, focus and active styles | Designers and theme builders |
Responsive styling without writing CSS
Responsive styling lets you set typography, color, background, border, spacing and layout separately for tablet and mobile. It works on one block, or on 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.
By default, Mobile means up to 480px wide and Tablet runs from there to 782px. Theme authors can move both breakpoints in theme.json, so the previews match the theme's real layout.
Take 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's a setting on the block, saved with the page.
A site that needs a locked design can turn this off with the responsiveEditingEnabled setting. Styles you already saved keep rendering exactly as before.
Phone photos and image processing in the 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. An iPhone HEIC photo goes up as a web-ready JPEG, and WordPress keeps the original HEIC beside it.
AVIF uploads work even when your host's PHP image editor can't read AVIF, and HDR photos keep their gain maps in every image size. The developer note on client-side media processing says libvips makes JPEGs about 15% smaller than GD or Imagick, the server-side libraries WordPress used before. Lighter images help Largest Contentful Paint, one of the Core Web Vitals Google uses to measure page experience.
Browser processing needs Chrome or Edge 137 or newer, or Chrome 146 on Android. Firefox and Safari fall back to the server, so an editor uploading from Safari on a Mac gets the old behavior. HEIC support then depends on your host.
The Media Library grid also scrolls continuously by default now, with a per-user option to go back to pages.
Tabs, Playlist and Notes for editors
Tabs splits related content into panels instead of one long scroll. Pricing tiers and product specs used to need a page builder or a tabs plugin for this. Every plugin is one more thing to update and one more thing that can break, so a built-in block takes one dependency off your list.
Playlist puts several audio tracks in one player, with an optional waveform. It's for podcasters and course creators who host audio on their own site.
Notes, the comments editors leave on drafts, now take formatting and links, and an @mention alerts the colleague you name.
Two expected changes missed the final release. Real-time collaborative editing isn't switched on in 7.1. WordPress developers also reverted a plan to hide the Classic block from the inserter, so older posts built with it keep their editing tool.
What WordPress 7.0 added if you skipped it
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 one shared way to build automation tools. A new Settings > Connectors screen links your site to AI providers, with Anthropic, Google and OpenAI as the featured three.
Check where those credentials live before anyone pastes a key in. The Connectors API developer note says API keys stored in the database aren't encrypted, only masked on screen. WordPress checks an environment variable first, then a PHP constant, then the database. An environment variable keeps the key out of the database and every database backup.
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. Skip 7.0 and you get both releases in one update, so plan 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. Trouble comes from old-style meta boxes, plugins built on jQuery UI and servers still on PHP 7.2 or 7.3, which can't install it at all.
The WordPress 7.1 Field Guide for developers says the post editor now always loads inside an iframe, including on sites that register legacy meta boxes. In 7.0, one older block in a post could switch the iframe off. Plugin code that reaches from the admin page into the editor canvas now targets the wrong document.
SEO panels and custom field boxes under the editor are the ones to click through on a test copy.
The release also moves jQuery UI from 1.13.3 to 1.14.2, which drops Internet Explorer support and removes four old helper functions. jQuery UI supplies widgets such as date pickers and drag-and-drop sorting. Open every plugin screen that uses them once after the update, before a customer finds the problem.
What PHP version does WordPress 7.1 need?
WordPress 7.1 needs PHP 7.4 or newer, the minimum that 7.0 raised from 7.2.24. Sites still on PHP 7.2 or 7.3 stay on the 6.9 branch, so they can't move to 7.x until PHP moves first.
WordPress.org recommends PHP 8.3 or newer. The WordPress 7.1 server compatibility page in the hosting handbook suggests 8.4 or 8.5 for new installs. It lists PHP 7.4 through 8.1 as end-of-life versions kept only for backward compatibility, and PHP 8.2 joins them on December 31, 2026.
The database needs a look too. MySQL 8.0 reached end of life on April 30, 2026, and the handbook says it should no longer be used. Its picks for new installs are MySQL 8.4 or MariaDB 10.11, 11.4 or 11.8.
Updating WordPress doesn't touch PHP, because PHP runs on the server. The steps for cPanel, Plesk and a VPS are in the guide on how to update your PHP version. If custom code breaks on a newer PHP, a fixed-price PHP 7.4 to 8.4 upgrade covers the code changes.
WordPress 7.1 release date and the patches since
Three security releases followed the August 19 launch within seven weeks. The first, 7.1.1, arrived on September 17 with 11 security fixes. Five days later, 7.1.2 closed a critical-severity flaw in page-template handling that, under certain conditions, let an attacker with no account run code on the server.
Then the WordPress 7.1.3 security release shipped on October 6 with seven more security fixes and four bug fixes. As of October 25, 2026, it's the version to install.
Two of the 7.1.1 fixes involved a logged-in account at Contributor level or above: an arbitrary post overwrite and the leak of draft post slugs. Sites with guest writers or forgotten agency logins carry more of that risk, so delete unused accounts before you update. Another fix covered a stored cross-site scripting flaw that an anonymous visitor could plant in a comment, once someone approved it.
Security fixes reach older branches back to 4.7, but the project says only the newest version gets active support. WordPress 7.2 Beta 1 came out on October 20, 2026, with the final release due on December 8. Moving to 7.1 now keeps that next jump small.
How to check plugin compatibility before you update
Open each plugin's page in the WordPress.org directory and read its "Tested up to" version. A plugin not tested with the last three major releases carries a warning that it may no longer be maintained.
Then read the changelog of every plugin that adds something to the post editor or the checkout. Look for a line that mentions 7.1, the iframe editor or jQuery UI. Paid plugins sold outside the directory post those notes on the vendor's site.
Your backup plugin is part of the risk too. UpdraftPlus shipped versions 1.26.13 and 2.26.13 after attackers used stolen UpdraftCentral keys to push backdoor plugins to connected sites on October 18 and 19, 2026. The UpdraftPlus breach report lists what to look for on your own site.
How to update to WordPress 7.1 safely
This order puts the low-cost checks before the expensive mistakes, and it's the same for a five-page brochure site and a busy store.
- Take a full backup of the files and the database, and store it off the server. WordPress's own update guide puts the backup before anything else.
- Check your PHP version under Tools > Site Health > Info. Below 7.4, upgrade PHP before you touch WordPress.
- Update plugins and themes, and delete the ones you no longer use.
- Copy the site to staging, or to a local install if your host has no staging tool. Run the WordPress update to 7.1.3 on the copy.
- Test the pages that earn money: checkout, booking and contact forms, the post editor with its SEO panel, and an image upload from a phone.
- Update the live site from Dashboard > Updates in your lowest-traffic hour, then clear any page cache.
- Place a real test order or send a form on the live site within the hour.
If a "failed update" message stays on screen, the official fix is to delete the .maintenance file from your 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 I update WordPress now or wait?
Update to 7.1.3 now if you run a brochure 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 with panels under the editor. Fix PHP first if you're below 7.4, because no 7.x release will install without it.
Waiting a week or two is fair when a plugin you depend on hasn't shipped its 7.1 compatibility release. That wait costs less than a rollback. Waiting for months doesn't hold up, since each skipped release piles more editor changes into one bigger jump.
Compare two sites. A clinic with eight plugins and one booking form can test 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 call with whoever built that checkout. Same release, different homework.
When a WordPress 7.1 update turns into a rebuild
Some sites can't take the update cleanly. The checkout may depend on a plugin whose developer stopped shipping updates, or custom theme code may fail on any PHP newer than 7.3. Patching each problem in turn can cost more than starting again on a current setup.
Before you decide, make a one-page list: your PHP version, every plugin with its "Tested up to" value, and the pages that bring in money. That list shows whether the job is a WordPress 7.1 update, a PHP upgrade or a rebuild.
Send that list to the WordPress website design and development team for a repair-or-rebuild answer within one business day.
Frequently asked questions
WordPress 7.1 "Mary Lou" came out on August 19, 2026. Three security releases have followed: 7.1.1 on September 17, 7.1.2 on September 22 and 7.1.3 on October 6, 2026. The release takes its name from jazz pianist and composer Mary Lou Williams.
Yes, for a site with maintained plugins and PHP 7.4 or newer, as long as you back up and test on a staging copy first. Install 7.1.3 rather than the original 7.1 build, because it carries every security fix released since August 2026.
PHP 7.4 is the minimum, set when WordPress 7.0 came out, and WordPress.org recommends PHP 8.3 or newer. Hosts still running PHP 7.2 or 7.3 keep a site on the 6.9 branch, so ask yours to move PHP up before you update WordPress.
Most maintained plugins keep working, but two changes can trip up older ones. The post editor now always loads in an iframe, even with legacy meta boxes, and jQuery UI moved to 1.14.2. Try plugins that add editor panels, date pickers or drag-and-drop screens on a staging copy first.
Only minor and security releases, on most sites. WordPress has installed those in the background since version 3.7, so a site already on 7.1 may have picked up 7.1.3 by itself. A major release such as 7.1 still needs someone to click Update Now under Dashboard > Updates.