The WordPress ecosystem in 2026 has reached a pivotal moment of balance. Following the ambitious foundational plumbing introduced earlier in the year by WordPress 7.0 — which focused on the centralized Connectors API and the DataViews admin framework — the open-source community officially released WordPress 7.1 on August 19, 2026.
While early roadmaps hinted at deeper AI feature rollouts, the final release of WordPress 7.1 represents a deliberate, developer-approved shift: it is fundamentally a styling, media, and design-centric release. Most experimental AI features — vector embeddings, streaming generation, and the proposed Guidelines system — slipped to future releases, allowing the core team to focus on resolving long-standing creator pain points.
Book a free, no-obligation strategy call and we'll map out your next move.
From native per-device responsive styling that eliminates the need for custom CSS media queries, to a browser-driven client-side image processing engine with native iPhone HEIC support, WordPress 7.1 delivers immediate, tangible workflow upgrades. The release cycle also addressed community stability head-on by formally reversing the proposed removal of the Classic block.
Visual Styling: Responsive Controls and Pseudo-States Without CSS
For over a decade, customizing how a WordPress block behaves on mobile versus desktop required custom CSS media queries or a third-party layout plugin. WordPress 7.1 removes that friction with native per-device responsive styling built directly into the block settings sidebar.
Fluid Font Overrides — specify exact font sizes for mobile screens directly in the UI, rather than relying solely on automated fluid typography clamps.
Flexbox Direction Shifts — Group and Row container blocks switch from a horizontal row on desktop to a stacked column on mobile with a single setting.
Unified Resizable Canvas — the editor replaces rigid, fixed preview toggles with a freely resizable device preview, so you can test non-standard screen widths dynamically.
Theme.json Breakpoint Presets — theme authors define custom breakpoints in theme.json, so the editor preview widths mirror the production front end accurately.
Interactive Pseudo-States (Hover, Focus, Active)
Alongside responsive controls, 7.1 adds visual pseudo-state styling. A new "State" selector inside block settings lets you customize how elements look on hover, focus, and active states: button hover and focus colors without writing a stylesheet, a native text-shadow control in Global Styles for headings and hero banners, and layered semi-transparent gradients over background images on Group and Cover blocks.
The Classic Block Reversal: A Win for Backward Compatibility
One of the most consequential stories of this release cycle wasn't a new feature at all. Earlier in 7.1 development, core contributors proposed deprecating and eventually removing the Classic block to accelerate full site editing adoption. Enterprise publishers, agencies, and long-standing site owners pushed back hard, citing the millions of legacy posts still built on TinyMCE formatting.
On July 7, 2026, the core team formally reversed the deprecation plan. The Classic block remains fully accessible in the inserter, the underlying TinyMCE integration continues to receive maintenance, and publishers managing large archival databases can update to 7.1 without forced block conversions or migration scripts.
New Native Core Blocks (And What Got Punted)
What Shipped
The Tabs block organizes dense content into interactive, clickable panels instead of long vertical scrolling. It's built in three layers: an outer container managing horizontal versus vertical orientation, a tab list controlling active-state indicators and keyboard focus rings, and flexible tab panels that host any nested block — columns, galleries, forms, or patterns.
The Audio Playlist block gets an overhaul for podcasters, educators, and musicians: an interactive waveform visualizer for scrubbing through tracks visually, paired with automated ID3 tag parsing that pulls artist, title, and cover art directly from the uploaded file.
What Got Punted to 7.2
The Table of Contents block did not ship in 7.1. During late-stage beta testing, the core team ran into accessibility inconsistencies around heading-level nesting and dynamic DOM rendering on complex single-page templates, and pushed the block to WordPress 7.2 rather than merge it half-finished. If you're currently relying on a plugin for a table of contents, keep it installed — there's no native replacement yet.
The Client-Side Media Revolution: Browser-Driven Processing & HEIC
This is arguably the release's most consequential change, even though it's the quietest. Historically, image resizing, orientation correction, and thumbnail generation were handled server-side via PHP libraries (Imagick or GD) after a raw file was uploaded. In WordPress 7.1, that processing moves to the browser — dimension checks and initial compression happen client-side using WebAssembly and Canvas APIs before the file ever reaches your server.
Native iPhone HEIC support — iOS users upload .heic photos directly without a conversion plugin; the browser converts and optimizes into web-ready formats before transfer.
Resilient upload queue — a dropped connection pauses and safely resumes the upload rather than corrupting the file.