WordPress 7.1, named Mary Lou, shipped on 19 August 2026 during WordCamp US. Among the headline items was responsive styling: the ability to style blocks per viewport directly in the editor, rather than accepting one set of values and patching the rest with custom CSS.
For anyone who has built block theme sites, this closes a gap that has driven a lot of people toward page builders. It does not close all of it, and it is worth being precise about which parts.
What it actually does
You can now set style values that apply at specific viewport sizes from inside the block inspector. Padding that differs on mobile, a font size that steps down on tablet, spacing that collapses on small screens, all set visually rather than written by hand.
Before this, block theme builders had three options: accept fluid typography and hope, write custom CSS with media queries, or install a plugin. All three worked. None of them were something you could hand to a client.
The feature arrived alongside a related change worth knowing about. Applying local style changes globally is no longer all or nothing. The Apply globally option now opens a review step so you can choose which modified styles to promote and which to keep as local overrides, which prevents the familiar accident of changing one heading and restyling the whole site.
Where it still falls short of a builder
If you build in Elementor, this is not yet a reason to switch, and pretending otherwise would be dishonest.
- Breakpoints are fixed. You work with the viewport sizes WordPress defines rather than defining your own, which builders have allowed for years.
- Not every property is exposed. Coverage is broad but not complete, so some things still need CSS.
- The visual editing experience is still block first. Precise positioning remains easier in a builder.
What has changed is the direction and the pace. Native block editing keeps absorbing the reasons people reached for builders, and each release the gap narrows. Our Elementor versus Gutenberg comparison covers where that decision currently sits.
What else landed in 7.1
Responsive styling was not the only change worth planning around.
- A redesigned media editor and improved image processing, including fixes for long animated GIF uploads and correct handling of EXIF rotated images.
- Richer Notes with mentions and inline feedback, which makes editorial review inside WordPress genuinely workable for the first time.
- An SVG Icon API for registering icons and icon collections in core, ready for plugins to extend.
- An enforced iframed post editor for block themes, which is the change most likely to expose sloppy plugin CSS.
That last one deserves attention if you maintain plugins or a custom theme. Styles that leaked into the editor through the admin document will no longer apply once the editor is properly iframed. The full detail is in the WordPress Developer Blog and the 7.1 Field Guide.
Should you update
On a staging copy first, as with any major release. Test your block templates, any custom blocks, and anything that injects editor styles.
For a straightforward block theme site the upgrade is low risk and the responsive controls are an immediate quality of life improvement. For a site with custom blocks or heavy editor customisation, the iframed editor change is the one to test properly before going live. Our WordPress 7.1 overview covers what breaks and what to check.
Frequently asked questions
What is responsive styling in WordPress 7.1?
It is the ability to set style values that apply only at specific viewport sizes, directly from the block inspector. Padding, spacing and typography can now differ between mobile, tablet and desktop without writing custom CSS media queries or adding a plugin.
Can I set custom breakpoints in WordPress 7.1?
No. You work with the viewport sizes WordPress defines rather than defining your own. Custom breakpoints remain a page builder feature, and this is one of the clearer remaining gaps between native block editing and a builder like Elementor.
Does WordPress 7.1 replace the need for a page builder?
Not yet, though it narrows the gap. Native block editing now handles responsive styling, but fixed breakpoints, incomplete property coverage and a block first editing model mean precise layout work is still faster in a builder for most people.
What is the iframed editor change in WordPress 7.1?
Block themes now load the post editor inside an iframe rather than in the admin document. This improves style isolation but means CSS that previously leaked into the editor from a plugin or theme will no longer apply. It is the change most likely to cause visible breakage after updating.
Should I update to WordPress 7.1 immediately?
Test on a staging copy first, as with any major release. Simple block theme sites tend to update cleanly. Sites with custom blocks, editor style customisations or heavily extended editors should verify the iframed editor change before going live.