WordPress 7.1: What to Check on Your Theme and in the Editor
Responsive block styles, editor compatibility, and a few everyday changes worth checking before updating your site.
WordPress 7.1, named Mary Lou, arrived on August 19, 2026. The official version record confirms the release. If you maintain a small business site, start with the pages you edit every week: a service page, a recent article, and the homepage.
This is a reading of the release documentation with suggested checks for your own site. We have not tested every theme or plugin against 7.1.
A closer look at the mobile layout
7.1 adds phone and tablet style overrides for supported blocks, both individually and through Global Styles. Themes can configure the viewport boundaries. The base styling still applies wherever no override is set. See the responsive styles developer note.
Take a homepage heading that looks comfortable on a laptop but fills most of a phone screen. That is a useful place to try the new controls. Adjust one property, save, and open the actual page on a phone. Check the next section too: reducing the heading size may leave a large gap if the surrounding padding stays the same.
Keep a copy of your existing CSS while testing. Removing all the old mobile rules at once would make it much harder to tell which change affected the page.
Check the writing screen, even when the public page looks fine
The block-based post editor now always uses an iframe. Older custom blocks need checking because code that accesses the outer page's document may miss the editing canvas. WordPress explains the change in its iframe compatibility note.
On a staging copy, open an older article that uses your usual plugin blocks. Edit the text, replace an image, save the draft, and reopen it. If a control disappears or stops responding, record the block name and plugin version. A screenshot of the public page alone will not show that kind of problem.
For a site with a custom theme, send those steps to whoever maintains it. A reproducible editing problem is easier to investigate than a report that the update “broke the design.”
Two smaller changes you may notice first
The media grid now loads more files as you scroll, with a per-user setting to opt out. The media library note explains the preference.
The toolbar also stays available across supported editing screens. If a plugin adds its own toolbar shortcut, include that shortcut in your checks. Details are in the toolbar update.
What about editing together?
Real-time collaborative editing is not enabled in the final 7.1 release. The Classic block also remains available after a proposal to hide it was reversed. Both decisions appear in the 7.1 Field Guide.
If shared editing was your reason to update, keep that distinction in mind when planning the team's workflow.
Before updating production, back up the database and files and confirm how you would restore them. Test a form submission and, for a shop, a checkout in the payment provider's test mode. Check the release archive for the current stable maintenance version when you schedule the work.
Keep the theme and hosting unchanged during this update if possible. You can borrow the page selection from our theme-switch checklist, then add the editing tasks above to it.