WordPress 7.1, code-named “Mary Lou,” shipped to the public on August 19, 2026. Following the AI-led foundations of WordPress 7.0, this release is a quieter, more practical update for site owners and agencies: faster media handling, per-device responsive controls in Global Styles, a public SVG icon system, and plumbing that helps AI agents and external tools interact with a site safely. This guide covers what changed, why it matters, and what to check before you update.
Client-side media processing continues from 7.0
WordPress 7.1 extends the client-side media processing work that began in version 7.0. More image and video work now happens in the browser before the file reaches the server. For a media-heavy blog or portfolio, that means shorter wait times when adding assets and lower CPU and memory cost on the server during uploads. The practical upside is real on shared and mid-tier hosting: large batches of photos no longer queue up server-side encoding jobs that can stall slower plans. Our earlier breakdown of client-side media processing explains the performance budget angle in detail.
Responsive block styles and configurable viewports
Global Styles now support per-device styling, and individual blocks pick up responsive controls. Editors can tune appearance for desktop, tablet, and mobile from the same interface instead of writing custom CSS. This is one of the most useful day-to-day changes in 7.1 for agencies that manage many client layouts, because layout polish that used to require a child theme or a custom stylesheet can now happen in the editor. Configurable viewports let you preview those breakpoints while you build, which reduces the guesswork that produces mobile-only layout bugs.
A public SVG icon API, with sanitization
The Icons API is now public. New functions such as wp_register_icon_collection(), wp_register_icon(), and wp_get_icon() let plugins and themes register custom icon sets with server-side rendering and REST API endpoints. WordPress sanitizes SVGs against a strict allowlist. That detail matters for security: SVG has long been a file type that plugins accepted carelessly, which opened stored-XSS paths. A core sanitization allowlist lets developers get the flexibility of SVG icons without reopening that classic upload gap. Site owners should still audit any plugin that accepts raw SVG uploads outside this API.
The Abilities API becomes AI-agent ready
The Abilities API, introduced in WordPress 6.9 as a machine-readable registry of capabilities, gains a filterable execution lifecycle, custom validation, a unified public exposure flag, and client-compatible JSON Schema output. This is the plumbing that AI agents and external tools use to work with a site safely. As AI assistants increasingly read and act on WordPress content, a standardized, permission-aware capability registry is what lets them perform useful tasks without escalating privileges. For teams building AI workflows on top of WordPress, 7.1 is the release where that integration story gets concrete.
New design tools and an accessibility push
Core opts several blocks in for 7.1, including Group, Accordion, Pullquote, Post Content, and Quote. dimensions.minWidth applies as CSS min-width and picks up dimensionSizes presets from a theme. Text-shadow is now supported in Global Styles. On accessibility, the release ships a 46-ticket push that includes a shared, accessible tooltip mechanism replacing pointer-only title attributes across several screens, which helps keyboard and screen-reader users get the same context mouse users already had.
What is not in 7.1
Real-time collaboration did not land, though the Notes feature gained email notifications for mentions and shareable revision links. The “On This Day” dashboard widget was dropped, and the plan to hide the Classic block was reverted, so behavior is unchanged. The Guidelines and Knowledge merge proposal continues to evolve but is not a finished user-facing feature in this release. React 19 in core was punted to a future cycle, so plugin authors should not assume a newer React runtime in the editor yet.
What site owners should check before updating
The post editor now always runs in an iframe, regardless of which blocks are present. Blocks still on Block API v2 or lower should be updated to v3, and plugins that inject admin styles into the canvas need a compatibility check. If you maintain custom blocks or admin-screen customizations, run that check before rolling 7.1 across client sites.
- Take a tested backup and stage the update on a copy of the site first.
- Confirm your active theme and page builder support Block API v3.
- Check that security and caching plugins have a 7.1-compatible release.
- Review custom admin CSS, since the iframed editor changes how canvas styles load.
For a deeper look at the developer-facing changes, the WordPress 7.1 Field Guide remains the authoritative reference, and our WordCamp US 2026 coverage shows how the broader community is thinking about AI for WordPress teams. If you run multiple client sites, batch the update in waves and watch your error logs for Block API warnings rather than updating everything at once.
A maturing admin Design System
The wordpress/theme package introduces design tokens and a stable React ThemeProvider for consistent UI theming inside custom admin screens. Combined with the new tooltip and icon APIs, that gives plugin and theme authors a coherent, supported set of building blocks for admin interfaces instead of each project hand-rolling its own styles. For site owners, the benefit is indirect but real: admin screens from different plugins look and behave more consistently, which makes the backend easier to navigate and lowers the chance of conflicting custom CSS breaking an editor view after an update.
