WordPress 7.1 Is Out. Here's What Site Owners Should Actually Do.

WordPress 7.1, code-named Mary Lou, shipped on 19 August 2026. Most write-ups treat it like a feature catalogue. If you run a live site, that is the wrong document.

You do not need every new block on day one. You need a clean update, a working media library, and a theme that does not fall over when someone opens the editor on a phone.

This is the owner version.

What 7.1 actually changed for people who ship sites

Four things matter more than the rest.

Responsive styling is now a first-class editor control. You can set different typography, spacing, colour, and layout per viewport without a page builder or a custom CSS file. Themes can define breakpoint widths in theme.json. If your theme already fought the editor with extra CSS, this is the release that makes that fight expensive.

Hover, focus, and active states can be styled in the editor. Buttons and links no longer need a one-off stylesheet for the obvious interaction states. That does not retire designers. It does retire a class of “just install this plugin” fixes.

Uploads moved toward the browser. 7.1 processes and resizes more image work on the client, including better handling of phone formats such as HEIC. The server receives files that are already closer to the sizes you asked for. If your host was choking on large camera rolls, test this before you celebrate.

Notes got more useful for teams. Rich text, @mentions, and notes on a selection make asynchronous editing less of a comment thread taped to the sidebar. Real-time co-editing did not ship. Do not plan a live pair-edit workflow around 7.1.

There are also a native Tabs block, a Playlist block, and a Table of Contents block. Useful. Not the reason you should rush production.

For the longer arc of the platform, start with what WordPress actually is in 2026.

Do this week — in this order

1. Take a real backup, then clone. Update the clone first. Not the live site. If you are on WordPress.com versus a host you control, the path is different — see WordPress.com vs self-hosted.
2. Update WordPress, then themes, then plugins — never the other way around on a tired stack. Read the plugin changelog for “7.1” or “tested up to.” Anything that injects its own editor CSS is the first suspect.
3. Upload one iPhone photo and one large desktop PNG. Confirm thumbnails, crop, and the new inline cropper. Client-side media is the quietest breaking change in this release.
4. Open the site editor on desktop and on a phone-width preview. Check headings, buttons, and any block that used custom CSS for breakpoints. Responsive styling can fight old theme CSS.
5. Click every primary button. Hover and focus states now live in the editor. If a theme or builder already painted those states, you may get double styles.
6. Walk one editorial page that uses headings. If you add the new Table of Contents block, confirm it tracks the heading structure you actually published, not the draft you meant to publish.
7. If more than one person edits the site, try Notes on a single paragraph. Mentions and selection notes are the collaboration win. Do not wait for real-time sync. It is not here.

What you should not do

• Do not rebuild a working Elementor or other builder site “because core can do tabs now.” 7.1 does not convert those pages. A rebuild has a cost. Tabs do not pay it back by themselves.
• Do not dump ten new blocks onto the homepage on update day. Tabs, playlists, and a table of contents are for pages that already needed that shape.
• Do not assume the site got faster because the version number went up. If the homepage still feels heavy, look at the plugin stack first: WordPress isn't slow. Your plugin stack is.
• Do not skip PHP and host constraints. 7.0 already set the floor at PHP 7.4. If your host is still below that conversation, the release notes will not save you.

How to think about the new styling controls

Use them where you used to write the same three media queries by hand.

Leave them alone where a mature theme already owns spacing and type. Fighting two styling systems in one week is how sites get “updated” and then look unfinished.

If you are choosing tools for a new site, this release weakens the case for a builder that exists only to do hover states and mobile type. It does not weaken the case for a builder that is doing forms, WooCommerce templates, or a design system you already paid for.

The media change in plain language

Old WordPress asked the server to decode, resize, and store every size. That worked until phones started sending huge HEIC files into cheap shared hosting.

7.1 moves more of that work into the browser. Good for hosts. Good for editors on a decent laptop. Test it on the worst phone your client still uses. If an upload fails, you will find out on the staging site, not in a support thread.

Collaboration without the myth

Notes are better. Mentions are better. Suggestion-style feedback is closer to how teams already work in documents.

Real-time collaboration was on the roadmap and did not land. If your process needs two people in the same canvas at once, keep using the tool you already trust for that. Do not invent a 7.1 ritual around a feature that missed the train.

A sane definition of “done”

You are done with 7.1 when:

• staging matches production plugins and theme
• a phone image uploads and crops
• the homepage, one inner page, and checkout or contact still work
• no editor warning is sitting on a template you ship every week

You are not done because a changelog looked impressive.

If you are still deciding whether this platform is worth the hours, read Is WordPress still worth learning in 2026?

If you need the official line

Get WordPress from WordPress.org when you are installing or moving a self-hosted site. Official release notes live on Make WordPress Core.

If this checklist saved you an evening of guessing, you can support the writing on Ko-fi.

Update on a copy. Test the boring paths. Then ship.