WordPress 7.1: What’s New and What It Means for Your Website

WordPress 7.1 arrived on August 19, 2026, with a group of changes focused on the everyday work of managing, designing, and extending a website. The release, named “Mary Lou” after jazz pianist and composer Mary Lou Williams, includes more direct responsive design controls, a more capable content review workflow, improved media processing, two new blocks, and several developer-facing APIs.

For organizations running custom themes, plugins, integrations, or complex publishing workflows, the update also introduces compatibility considerations. The post editor is now fully iframed, media processing has changed, and several APIs have expanded. A staging review remains an important part of the update process.

WordPress 7.1 Builds on the Foundation of WordPress 7.0

WordPress 7.0 introduced substantial changes to the administration experience and added platform-level foundations for AI integrations. WordPress 7.1 develops those systems while placing greater emphasis on the editor, collaboration, responsive design, and media management.

The update incorporates ten versions of the Gutenberg plugin into WordPress Core, from Gutenberg 22.7 through 23.6. That development span helps explain why the release contains a mix of visible editor features and deeper changes to APIs, interface components, block behavior, and administrative navigation.

The result is a release with practical value across several roles. Content teams gain a more precise review process. Designers and marketers can adjust more presentation details inside the editor. Developers receive additional tools for responsive styling, icons, automation, and administrative interfaces.

Responsive Styling Is Now Available in the Editor

Responsive design has traditionally required a combination of theme settings, custom CSS, and external development work. WordPress 7.1 moves more of that control into the Site Editor.

Editors can now apply different block styles for desktop, tablet, and mobile views. These changes can be configured through Global Styles, where they affect every instance of a block, or on an individual block within a specific page. The preview canvas can also be resized manually, allowing teams to inspect a layout between the standard device presets.

This is useful for adjustments such as reducing heading sizes on smaller screens, changing mobile spacing, or adapting the alignment of a content section for narrower viewports. Block themes can define their own mobile and tablet breakpoints in theme.json, giving development teams a way to align the editor with the responsive rules used by the theme.

WordPress 7.1 also adds visual controls for interactive states. Button blocks can receive separate styles for hover, focus, and active states at the global or individual-block level. The WordPress 7.1 Field Guide documents broader support for responsive variations, configurable viewports, interaction states, and text shadows within the Global Styles system.

These controls reduce the amount of CSS needed for routine presentation changes. They also introduce another layer of editorial responsibility. A local mobile override can affect one page, while a Global Styles change can alter buttons, typography, or spacing across the website. Teams should define who can make global design changes and include responsive checks in their publishing process.

Notes Become a More Complete Content Review System

Notes first appeared in WordPress 6.9 as a way to attach comments to blocks. WordPress 7.1 expands the feature into a more useful review system for content teams, agencies, and multi-author publications.

A note can now be attached to a selected sentence or phrase instead of the entire block. This gives editors a precise reference when requesting a correction or asking a question. Collaborators can be tagged with @mentions, and Notes support bold, italics, code, links, and emoji. Several discussion threads can remain active on the same block, while longer notes collapse to keep the interface manageable.

The expanded Notes workflow brings more editorial context into WordPress itself. A writer can see the passage under discussion, the feedback attached to it, and the colleague responsible for responding. This can reduce the need to copy comments between documents, project-management tools, and the CMS during final review.

Real-time co-editing isn’t part of the final WordPress 7.1 release. Multiple people can’t yet work in the same post with a Google Docs-style editing experience. Notes support structured feedback and asynchronous collaboration, while real-time collaborative editing remains under development.

Image Editing and Media Handling Receive Major Improvements

WordPress 7.1 replaces the previous inline cropping interface with a dedicated media editor. The new modal keeps the familiar Crop button and adds freeform cropping, aspect-ratio presets, horizontal and vertical flipping, precise rotation controls, and metadata editing in one workspace. It is available from both Image and Cover blocks.

The larger change happens during image processing. Compression, resizing, and thumbnail generation can now run in the user’s browser before the image reaches the server. WordPress uses a WebAssembly build of libvips for supported operations, reducing the server resources needed for large media uploads. This can help prevent PHP memory-limit errors and upload timeouts, especially on websites where editors frequently work with high-resolution images.

The release also adds support for formats produced by current phones and cameras, including HEIC, AVIF, and HDR gain maps. Upload progress is easier to follow, and interrupted uploads can retry when the connection returns. The WordPress 7.1 media changes also include a new Attached Images section in the inserter and easier access to media connected to the current post.

Media Library browsing changes as well. Infinite scrolling is enabled by default, although individual users can restore pagination through their profile settings. These improvements make the media workflow more resilient, but teams should still test existing image-optimization plugins, offload services, CDN integrations, and custom upload processes before deploying the update.

Tabs and Playlist Join the Core Block Library

WordPress 7.1 adds two blocks that previously required a plugin or custom implementation.

The Tabs block organizes related content into selectable panels. It can support product specifications, service details, comparison content, and other page sections where displaying every item at once would create an unnecessarily long layout. Existing tab components created by plugins do not convert automatically, so there is no immediate reason to rebuild functioning content. Teams can evaluate the Core block for new pages and compare its behavior, accessibility, styling options, and maintenance requirements with their current solution.

The Playlist block groups multiple audio files into a single player. Publishers can include track titles, artist information, cover artwork, and an optional waveform. The block is relevant to podcasts, educational resources, music libraries, event recordings, and other sites that publish collections of audio.

Several smaller block improvements accompany these additions. Background gradients can work with background images, Columns and Gallery blocks can transform into Grid layouts while retaining their content, and the Icon block receives a more structured selection experience. The public SVG Icon API also allows themes and plugins to register their own icon collections for use inside the editor.

The Admin and Editing Experience Is More Consistent

The WordPress admin bar now remains visible while users move between supported editor screens. It provides a consistent route between the front end, dashboard, Site Editor, and Block Editor. The change is small in isolation, but it removes a recurring navigation interruption for people who spend much of the day editing content or site templates.

The Command Palette also organizes commands into recent actions, relevant matches, and contextual suggestions. This gives editors faster access to Styles, Navigation, Templates, Patterns, and other frequently used areas.

Site identity settings are now grouped under a dedicated Design section. Editors can manage the site title, tagline, logo, and site icon from one screen instead of locating them across separate settings and templates.

The post editor now runs inside an iframe for all themes. This separates the editing canvas from the surrounding administration interface, preventing admin styles from leaking into page content. Viewport-relative units and media queries can target the canvas more predictably, which supports a closer relationship between responsive previews and front-end behavior.

For customized websites, this change requires attention. Plugins using older versions of the Block API, legacy meta boxes, or JavaScript and CSS that cross the editor document boundary may behave differently. The iframed editor guidance recommends that plugin developers review these integrations and update affected code.

WordPress Continues Building Its AI and Automation Infrastructure

WordPress 7.0 established the AI Client and Connectors API as common infrastructure for connecting plugins with external AI providers. WordPress 7.1 advances the surrounding developer framework through refinements to connectors and the Abilities API.

The Abilities API, introduced in WordPress 6.9, gives WordPress components a standardized way to describe actions that can be discovered and executed programmatically. Version 7.1 adds filtering, execution lifecycle hooks, stronger schema preparation, validation options, and a unified method for exposing abilities to external clients. These additions provide a clearer foundation for automation and AI-assisted tools built by plugin and platform developers.

This doesn’t place a general-purpose AI assistant inside every WordPress dashboard. It gives developers shared infrastructure for building integrations without creating a separate provider, credential, and action system for every plugin. The practical user-facing value will depend on how hosting companies, agencies, and plugin teams apply these APIs.

The release also expands DataViews and DataForm APIs, introduces a theming foundation for administrative interfaces, and makes the SVG Icon API public. Together, these changes help developers build extensions that behave more consistently with the rest of WordPress.

Accessibility and Performance Continue to Improve

WordPress 7.1 includes accessibility work across administration screens, list tables, navigation, setup flows, widgets, and editor interfaces. Shared functions for accessible tooltips give Core and plugin developers a consistent way to provide contextual information without relying on inaccessible title attributes or mouse-only interactions. Screen-reader labeling, focus behavior, contrast, and hierarchical information also receive updates.

The new Tabs and Playlist blocks were developed with keyboard and assistive-technology use in mind. Site teams still need to test the final implementation within their own themes because surrounding styles and custom code can affect front-end accessibility.

Performance improvements are most visible in the media workflow. Browser-based image processing reduces server work during uploads, while configurable speculative loading gives hosts and advanced site owners more control over page prefetching. Automatic media retries can also prevent interrupted connections from forcing editors to restart larger upload batches.

Wrap Up

WordPress 7.1 brings several common design, review, and media tasks closer to the core editing experience. Responsive controls reduce the need for minor CSS requests. Notes carry clearer editorial context. Browser-based media processing addresses a frequent source of upload failures. New blocks and APIs give site owners and developers additional options without forcing immediate changes to existing content.

The value of the release will depend on implementation. Global design controls require governance, new Core blocks need evaluation against existing components, and customized editor integrations need compatibility testing. A staged update allows teams to adopt the useful improvements while protecting the workflows their website already supports.

With all of that being said, we want to thank our DevriXian – Rolly Bueno, for his contribution on this update!