WordPress 7.1 “Mary Lou” was released on August 19, 2026, and the current version is 7.1.4, a security release from October 28, 2026 that fixes 22 vulnerabilities. 7.1 runs on PHP 7.4 or newer, WordPress.org recommends PHP 8.3 or newer, and the next major release, WordPress 7.2, is scheduled for December 8, 2026.
7.1 is the second major release of 2026. It was led by Anne McCarthy, shipped on the last day of WordCamp US, and is named for the jazz pianist and arranger Mary Lou Williams. The headline features are responsive and hover styling without CSS, two new blocks (Playlist and Tabs), a new media editor, richer Notes, and image processing that moves from your server into the browser.
Everything below is checked against the official WordPress 7.1 Field Guide, its developer notes, and the release posts on WordPress.org News. You can download WordPress from WordPress.org, though most sites are offered the update under Dashboard → Updates, and minor releases like 7.1.4 install automatically on sites with background updates enabled.
| WordPress 7.1 | Details |
|---|---|
| Release date | August 19, 2026 |
| Codename | “Mary Lou”, after Mary Lou Williams |
| Release lead | Anne McCarthy |
| Current version | 7.1.4 (October 28, 2026) |
| Minimum PHP | 7.4 |
| Recommended PHP | 8.3 or newer (7.1 is compatible up to PHP 8.5) |
| Recommended database | MySQL 8.0+ or MariaDB 10.11+ |
| Next major release | WordPress 7.2, scheduled for December 8, 2026 |

WordPress 7.1.x Point Releases
Four maintenance and security releases have followed 7.1 so far. Every one of them includes security fixes, so the only 7.1 build you should be running today is the latest one.
| Version | Released | Type | What it fixed |
|---|---|---|---|
| 7.1.1 | Sept 17, 2026 | Maintenance and security | 11 security fixes plus 17 Core and 19 Block Editor bug fixes. The security fixes include a stored XSS in wpautop(), an authenticated path traversal in the REST templates controller, a Contributor+ arbitrary post overwrite, and a bug that let any logged-in user reparent comments and notes. |
| 7.1.2 | Sept 22, 2026 | Security | One critical fix (CVE-2026-87902). Under certain server and theme conditions, an unauthenticated attacker could make page template resolution include a local PHP file outside the theme, which can lead to remote code execution. |
| 7.1.3 | Oct 6, 2026 | Maintenance and security | 7 security fixes and 4 bug fixes, including a stored XSS on the Comments screen via pending comments, a second-order SQL injection in WXR export, an XSS in Imgur embeds, and Authors being able to sticky posts. |
| 7.1.4 | Oct 28, 2026 | Security | 22 vulnerabilities, among them a weakness in the upgrade process that could allow remote code execution during the upgrade window, several stored XSS issues (Interactivity API, Categories, Playlist and image blocks, Customizer selective refresh), and Notes being readable by users who cannot edit the post. It also updates the bundled root certificates after the eMudhra revocation. |
7.1.2 arrived only five days after 7.1.1, because it patched a single critical issue. Each security fix was also backported to every branch still eligible for security updates (currently back to 4.7), so a site parked on 7.0 should be on 7.0.8, the release that matches 7.1.4. WordPress.org is clear that only the latest version is actively supported, so a backport is a safety net, not a reason to stay behind.
7.1.4 also carried WordPress 7.2 Beta 3, which is why the 7.2 testing posts jump straight from Beta 2 to Beta 4. If you are not sure which build a site is on, the WordPress version checker will tell you, and the full WordPress version history lists every release back to 0.7.
Client-Side Media Processing: The Real Headline
Until now, uploading a photo to WordPress meant handing it to your server. PHP passed the file to GD or Imagick, and your host spent CPU and memory generating every thumbnail size before the upload finished. That is why big photos hit memory errors, and why “increase your PHP memory limit” is such common advice.
In 7.1 that work moves into the browser. According to the client-side media processing dev note, the editor now compresses, resizes, rotates and converts images with wasm-vips, a WebAssembly build of the libvips library, running in a Web Worker. It generates every registered thumbnail size there too, then uploads each one through a new sideload REST endpoint. It is on by default in browsers that support it.
What this actually changes for you
- iPhone photos upload. HEIC files are decoded in the browser and uploaded as JPEG, with the original HEIC kept as a companion file, even on hosts with no server-side HEIC support.
- Your host stops doing the heavy image work. Sub-size generation leaves PHP, which is the work that most often trips memory limits and timeouts on shared hosting.
- Smaller files for visitors. The dev note says libvips output is better compressed than GD or Imagick, with JPEGs roughly 15% smaller.
- AVIF works without server support, and HDR photos with gain maps (UltraHDR) keep their HDR data in every generated size.
- Uploads survive a bad connection. Each sub-size is its own request, failed requests retry automatically, and uploads pause when you go offline.
- GIFs can become video. Opaque animated GIFs get a companion MP4 or WebM, and the editor offers to switch the block to a looping, muted “GIF” variation of the Video block. It is reversible, and transparent GIFs are left alone.
Which browsers get it
Support depends on the browser. The full pipeline needs SharedArrayBuffer, which WordPress unlocks with a Document-Isolation-Policy header that only Chromium browsers support. In practice:
| Browser | Client-side processing in 7.1 |
|---|---|
| Chrome, Edge (137+) and other Chromium browsers | Full support |
| Chrome on Android | From version 146 |
| Safari | Falls back to server-side, but in-browser HEIC decoding still works |
| Firefox | Falls back to server-side; GIFs upload unchanged |
The client also checks the device before it starts: more than 2 GB of memory, at least two CPU cores, a connection faster than 2G with no Save-Data header, and a Content Security Policy that allows blob: workers. The worker download is about 13 MB. If any check fails, WordPress uses the old server-side path, so nobody gets an error.
Two other details are easy to get wrong. Uploads actually send more bytes than before, because the browser uploads the original plus every sub-size; the saving is server CPU and memory, and smaller files when visitors load the images. And this is not a security boundary. The dev note says the server still validates every upload (MIME type, dimensions, capabilities), so treat it as a performance change rather than a hardening one.
Your existing settings still apply. The client reads big_image_size_threshold, image_editor_output_format, wp_editor_set_quality and the EXIF rotation filter from the server. If you have tuned large image scaling or your max upload size, those guides still apply. To turn the feature off entirely:
add_filter( 'wp_client_side_media_processing_enabled', '__return_false' );
The media library and editor caught up too
A new media editor modal replaces the old inline cropper, and the familiar Crop button still opens it. It brings freeform and aspect-ratio cropping, horizontal and vertical flipping, fine-grained rotation and metadata editing into one workflow. Uploads show a progress snackbar in the editor, Gallery blocks can pull in and sort media already attached to the post, and the inserter shows those images in a new Attached images section.

The Media Library grid now uses infinite scrolling by default instead of a “Load more” button. If you prefer the old pagination, each user can switch it back in their profile.

Responsive and Hover Styling Without CSS
Two long-requested features arrive together, and they matter most to people who build sites rather than plugins.
Responsive styling lets you set how a block looks at different screen sizes from inside the editor, both in Global Styles (every instance of a block) and on a single block. Set a smaller font size on mobile without opening a stylesheet. Block themes can also define their own mobile and tablet breakpoints in theme.json, which override the defaults used by responsive styles and block visibility.
Interactive state styling covers hover, focus, focus-visible and active states. In 7.1 it is limited to the Button and Navigation Link blocks, per the pseudo states dev note, so “make this button change color on hover” is now a setting. Theme authors can define the same states in theme.json with keys like :hover, even nested inside a responsive state.

Together these remove two of the most common reasons people still reach for custom CSS or a page builder. If you build client sites, this is the change most likely to shorten your build time. Site owners who would rather lock it down can hide the state controls with the blockStatesEditingEnabled editor setting.
New Blocks and Block Improvements
Two new Core blocks shipped. The Playlist block collects audio files into one player with an optional waveform, which covers podcast and music use cases that used to need a plugin. The Tabs block organizes content into clickable panels, another job that has meant a third-party block until now. For collapsible sections rather than tabs, the core Accordion block has been around since 6.9, and our roundup of WordPress accordion plugins compares it with the plugin options.

Several existing blocks improve too. Background gradients and background images no longer fight each other, a fix that covers Group, Verse, Accordion, Pullquote, Post Content and Quote. The Custom HTML block can now hold editable nested blocks inside its preview. The Image block gains a Mark as decorative toggle that hides ornamental images from screen readers. The Query Loop block can exclude the current post. And pasting a shortcode into the Embed block now produces a real Embed block instead of leaving the raw text behind.

New Design Tools
Three smaller additions each remove a reason to reach for custom CSS:
- A background gradient block support (
background.gradient) that combines with background images instead of being overridden by them. - A minimum width control in the dimensions panel, which stops an element collapsing on narrow screens without a media query.
- Text shadow support in Global Styles, so you can set it once per block type rather than per instance. WordPress 7.2 extends this with block-level controls and
theme.jsonpresets.
Individually these are small. Together with the responsive and interactive-state controls above, they continue the pattern of this release: things that used to need a stylesheet becoming settings.
A Real Icon System
WordPress 7.0 added a built-in SVG icon set and the Icon block. 7.1 turns that into a public API, according to the icon API dev note. Plugins and themes can register their own collections with wp_register_icon_collection(), add icons with wp_register_icon(), and render any icon in PHP with wp_get_icon(). Registered icons show up in the Icon block picker alongside the core set.
The REST side grows too. /wp/v2/icons (from 7.0) gains a collection field and filter, and a new read-only /wp/v2/icon-collections endpoint lists collections. One limit to know before you migrate an icon font: registered SVGs are sanitized down to <svg>, <path> and <polygon>, so icons built from circles, rects or groups need flattening to paths first.
Collaboration: Notes Grew Up, Real-Time Editing Did Not Arrive
Notes, the editorial commenting system, got most of the collaboration work this cycle. You can use inline formatting (bold, italic, code, links, emoji), tag colleagues with @mentions, leave a note on a text selection rather than a whole block, keep several conversations going on the same block, and collapse long notes to keep the margin readable. Mentions also send an email notification, and shareable revisions let you send someone a link to a specific revision.
What is not there is real-time collaboration. It was pulled from WordPress 7.0 twelve days before that release, and it is not in 7.1 either. The Field Guide says real-time collaborative editing “received extensive testing and feedback during the WordPress 7.1 cycle, but it is not enabled in the final release,” with work continuing on conflict handling and compatibility. The 7.2 beta announcements so far focus on Notes (emoji reactions, notes on the canvas, a minimized mode) and do not list real-time editing either.
The practical read: if you were waiting for Google Docs style co-editing, keep waiting. Notes plus shareable revisions cover the “get a second pair of eyes on this draft” case today.
Admin Quality-of-Life Changes
The admin bar now stays visible in the Site Editor and Block Editor (the beta posts called it the omnibar), except in Distraction Free mode. The “W” logo no longer doubles as a back button: a dedicated chevron takes you back, and your site icon, when set, opens the site menu. The command palette (Ctrl+K, or Cmd+K on Mac) groups results into Recent, matching and Suggestions, and the Site Editor finally respects your chosen admin color scheme.

Site title, tagline and icon move into a dedicated Identity section of the Site Editor. And you can finally change a comment’s parent from the Edit Comment screen with a new “In reply to” dropdown, scoped to the same post. That control had a security gap at launch, any logged-in user could reparent comments and notes, which 7.1.1 fixed.

What Developers Need to Know
The biggest structural change is the enforced iframed editor. In 7.0 the post editor was only iframed when every block in the post used Block API version 3 or higher. In 7.1 it is always iframed, regardless of theme type, block API versions, or legacy meta boxes. The iframe dev note says most blocks work unchanged; the breakage comes from code that reaches for the global document or window to touch the canvas. The fix is to get the canvas document from an element via ownerDocument and defaultView.
Beyond that, the Abilities API (introduced in WordPress 6.9) gains filtering in wp_get_abilities(), execution lifecycle hooks, a unified public exposure flag and client-compatible JSON Schema, which matters if you are building MCP or AI integrations on top of it. Block Bindings extend to List Item blocks. A new Design System ships semantic design tokens and a stable React ThemeProvider for admin interfaces. New wp_get_tooltip() and wp_get_toggletip() functions add accessible tooltips. And the Connectors screen accepts username and application password authentication alongside API keys.
The Field Guide counts 20 new hooks (19 filters and one action) and more than 310 Core Trac tickets. It also bumps jQuery UI from 1.13.3 to 1.14.2, which is the kind of dependency change that breaks a plugin quietly rather than loudly. The next section collects everything in the dev notes that can change behavior on a live site.
What Can Break When You Update to 7.1
Most sites running maintained plugins update to 7.1 without incident. The risk sits in a handful of specific changes, all documented in the Field Guide’s dev notes. If you maintain custom code, this is the checklist to run on a staging site first:
| Change in 7.1 | Who is affected | What to check |
|---|---|---|
| Post editor always iframed | Custom blocks and editor plugins that use the global document/window | Blocks that style or listen to the canvas; switch to ownerDocument and useRefEffect |
| Client-side image processing | Plugins hooked to wp_image_editors, image_memory_limit or image_make_intermediate_size | Those hooks no longer fire for browser-processed uploads. wp_generate_attachment_metadata now runs twice (create, then update), so make watermark or CDN code idempotent |
| Cross-origin isolation in the editor | Plugins loading external scripts, embeds or iframes in the block editor (Chromium only) | External scripts get crossorigin="anonymous"; browser-side fetch() of remote images can fail on CORS |
| Strict Content Security Policy | Security plugins or headers that set worker-src | Add blob: to worker-src, or uploads fall back to server-side processing |
| jQuery UI 1.14.2 | Plugins using jQuery UI widgets | $.fn._form, $.ui.ie, $.ui.safeActiveElement and $.ui.safeBlur are removed |
notify_post_author filter | Code that returns __return_true to force author emails | It now sends emails for comments in moderation, spam and trash too; check approval status in your callback |
| Persistent admin bar | Plugins that add admin bar nodes | Nodes now appear in the Site Editor; hide them with a $screen->is_block_editor() check if needed |
| Navigation font size | Themes that style has-*-font-size on navigation items | Font size no longer propagates to child items; a filter in the dev note restores the old classes |
| Block-level preset specificity | Themes with block-level presets in theme.json | Preset classes now use :where(), so custom CSS that relied on the higher specificity may lose |
| Data and deprecated APIs | Editor plugins | getEntityRecords() returns full collections for non-paginated entities; __experimentalCloneSanitizedBlock logs deprecations; @wordpress/nux is a no-op |
If an update does take a site down, the screen you will usually see is the WordPress critical error page, and recovery mode often gets you back in without SFTP. From there, finding the plugin conflict is a matter of disabling suspects one at a time.
What Did Not Make It
The Roadmap to 7.1 listed more than the release carried, and it warned that not everything would ship. The Field Guide has a whole section on what was deferred or changed direction.
The Classic block stays. It was going to be hidden from the block inserter in 7.1, a change merged in late June. On July 7 it was reverted: the Classic block stays in the inserter exactly as before, the wp_classic_block_supports_inserter filter was removed, and the companion Enable Classic Block plugin is being closed. The announcement said the approach “had things largely backward” and that the Classic block “should become obsolete by choice, not by force.” If you still use it, nothing changes and no migration is needed.
These were on the roadmap or in early betas and are not in 7.1:
- Real-time collaboration, tested through the cycle but not enabled, as covered above.
- The Table of Contents block, which was on the roadmap next to Playlist and Tabs.
- The React 19 upgrade, punted beyond 7.1 and still an experiment in the Gutenberg plugin.
- The “On This Day” dashboard widget, which was cut from 7.1 and now appears in the WordPress 7.2 betas.
- Guidelines, a system for encoding editorial rules and brand voice for AI tooling, which stays a merge proposal for now.
- Unicode email addresses, which moved to a community plugin for wider testing (announced with Beta 3).
Release Schedule and How to Test It
The 7.1 cycle ran to plan. Two of its pre-releases were folded into unplanned 7.0 security releases, which added steps without moving the final date:
| Date | Milestone |
|---|---|
| July 15 | Beta 1 (feature freeze) |
| July 17 | Beta 2, shipped as part of the 7.0.2 release |
| July 22 and 29 | Beta 3 and Beta 4 |
| August 5 | Release Candidate 1, the Field Guide, and the 7.1 branch |
| August 6 | Release Candidate 2, shipped as part of the 7.0.3 security release |
| August 12 | Release Candidate 3 |
| August 18 | Dry run and a 24-hour code freeze |
| August 19 | WordPress 7.1 final release |
The August 19 date never moved. With 7.1 final, there is no beta channel to bother with. Most sites are offered the update under Dashboard → Updates. If you prefer the command line, WP-CLI does it in one step:
wp core update
wp core update-db # run this after, especially on multisite
Test on a staging copy first if you maintain plugins or a heavily customized theme. WordPress Playground will also spin up a throwaway instance in the browser with nothing to install.
What Comes Next: WordPress 7.2
WordPress 7.2 is the final major release of 2026, led by Matt Mullenweg, and it ships with a new default theme called Ipsum. The official 7.2 schedule targets December 8, 2026:
| Date | 7.2 milestone |
|---|---|
| October 20 | Beta 1 |
| October 27 and 28 | Beta 2, then Beta 3 (shipped inside 7.1.4) |
| November 3 and 10 | Beta 4 and Beta 5 |
| November 17 | Release Candidate 1 and Field Guide |
| November 24, December 1 | Release Candidates 2 and 3 |
| December 8 | WordPress 7.2 final release |
The betas so far show 7.2 building directly on 7.1: responsive controls for more blocks (including Gallery columns and cropping), client-side media processing extended to the Media Library screen, block-level text shadow controls, emoji reactions on Notes, the “On This Day” widget, and a new Secrets API for storing credentials. Treat that list as provisional until the 7.2 Field Guide is out, since 7.1 showed how much can change between Beta 1 and release.
Should You Update Now?
Yes. Three months and four point releases in, 7.1 is the stable branch, and 7.1.1 through 7.1.4 have all been security releases. Staying on an older 7.1 build, or on 7.0 below 7.0.8, means running code with publicly documented vulnerabilities.
Two quick checks before you do. First, confirm your PHP version is at least 7.4, and ideally 8.3 or newer. Second, take a full backup you have actually tested restoring. If you run custom blocks or editor plugins, walk the “what can break” table above on staging first; everyone else can update from the dashboard.
Frequently Asked Questions
Is WordPress 7.1 stable?
Yes. 7.1 was released on August 19, 2026 and has had four maintenance and security updates since, the latest being 7.1.4 on October 28, 2026. It is the version WordPress.org serves today, and 7.1.4 is the build you should be on. The changes most likely to cause trouble are the always-iframed post editor and client-side image processing, which mostly affect custom blocks and media plugins.
What PHP version does WordPress 7.1 need?
WordPress 7.1 needs at least PHP 7.4 and MySQL 5.5.5, but WordPress.org recommends PHP 8.3 or newer with MySQL 8.0+ or MariaDB 10.11+. 7.1 is compatible with PHP 7.4 through 8.5. PHP 7.4 is long past end of life, so treat it as a floor, not a target.
When is WordPress 7.2 coming out?
WordPress 7.2 is scheduled for December 8, 2026, with Release Candidate 1 on November 17. It is the last major release of 2026 and ships with a new default theme, Ipsum.
What is the latest version of WordPress 7.1?
WordPress 7.1.4, released October 28, 2026. It is a security release covering 22 vulnerabilities. Sites with automatic background updates get it on their own; everyone else should update from Dashboard → Updates.
Does WordPress 7.1 include real-time collaboration?
No. It was tested throughout the 7.1 cycle but is not enabled in the final release, and it is not listed in the 7.2 betas so far either. Notes received the collaboration work instead, with @mentions, rich text, email notifications and shareable revisions.
Why is it called “Mary Lou”?
WordPress names each major release after a musician. 7.1 honors Mary Lou Williams, the jazz pianist, arranger and composer whose work ran through swing, bebop and sacred jazz. In the 1940s her Harlem apartment was a nightly workshop where Thelonious Monk, Dizzy Gillespie and Bud Powell traded ideas. WordPress 7.0 was “Armstrong”.
Wrapping Up
WordPress 7.1 is a less dramatic release than 7.0, and that is not a criticism. Where WordPress 7.0 “Armstrong” introduced an AI framework and a redesigned dashboard, 7.1 mostly finishes things: responsive and hover styling that should have been editor controls years ago, media handling that copes with what phones actually produce, and a pile of small admin fixes. The busy run of security releases since August is the real story of its first three months, so get on 7.1.4 and plan for 7.2 in December.
Last updated November 9, 2026, with 7.1.4 as the current release and the published 7.2 schedule. Not sure what you are running? The WordPress version checker will tell you in a couple of seconds.


