What’s new in WordPress 7.1 and how can you take advantage of it without breaking your website? The short answer is: don’t enable everything on your live website right away. Back up your site, create a staging environment, check your theme and plugins, then test each group of features according to its level of risk.
WordPress 7.1 “Mary Lou” was released on August 19, 2026, focusing on responsive design, collaboration in the editor, media workflows, and interface customization. The codename honors jazz pianist and composer Mary Lou Williams (according to WordPress.org).
If you regularly manage websites across multiple browsers, also see the WordPress browser testing tool to add a testing step after the update.
What new WordPress 7.1 features are worth trying first?
The three groups of changes most relevant to site owners are responsive styling controls, WordPress media editor and WordPress Notes. Each group addresses a different problem, so each requires a different testing approach.
| Feature | Practical value | Risks to check | Who should try it first |
|---|---|---|---|
| Responsive styling controls | Set display styles for Tablet and Mobile in the editor | Breakpoints, legacy CSS, and conflicts with themes or builders | Websites using block themes |
| WordPress media editor | Crop, rotate, flip, adjust proportions, and edit metadata in a separate window | Original images, file permissions, thumbnails, and image optimization plugins | Websites that publish many images |
| WordPress Notes | Comment directly on content, with clearer feedback and collaboration | User permissions, notifications, and approval workflows | Teams with multiple editors |
| Improved media handling | More resilient uploads and support for additional browser-side processing workflows | Browser, file size, hosting, and CDN | Websites with large videos or images |
| Interaction states | Customize hover, focus, focus-visible, and active states for some blocks | Accessibility, contrast, and theme CSS | Websites that need optimized button interfaces |
Responsive styling lets you set style values for Tablet and Mobile viewports in Global Styles or on individual blocks. WordPress generates CSS using media queries for these values; breakpoints can be configured at the theme level through theme.json (according to WordPress.org).
The new media editor moves image cropping into a separate modal, supporting freeform cropping, aspect ratios, rotation by small increments or preset angles, image flipping, and metadata editing. This is more convenient, but you should still keep a copy of the original images before making bulk edits.
Notes has been expanded for collaboration: comments attached to content or blocks, rich-text replies, notifications, emoji reactions, and the ability to apply suggestions. However, this feature is only useful when the team agrees on who can comment, who can edit, and who has publishing permissions (according to WordPress.org).
WordPress 7.1 update checklist to avoid breaking your website
1. Prepare backups and staging
- Record the current versions of WordPress, the theme, plugins, PHP, and server configuration.
- Create full backups of the database, the
wp-contentand necessary configuration files. - Create a staging environment with data that closely resembles the live website. Don’t test only on a blank site.
- Make sure you have a recovery plan: a downloaded backup or a snapshot from your hosting provider.
Before updating, open key conversion pages such as the homepage, landing pages, cart, contact forms, and posts with many images. Capture screenshots of their appearance to compare after the upgrade.
2. Check the theme, plugins, and editor
On staging, update the theme and plugins according to the provider’s compatibility documentation, either before or after upgrading WordPress as they recommend. Pay particular attention to page builder, caching, image optimization, membership, e-commerce, and custom block plugins.
Then create a test draft containing a heading, paragraph, button, image, gallery, video, table, and form. If the website uses a block theme, open the Site Editor and check Global Styles. If it uses a classic theme, don’t expect all the new responsive controls to appear fully.
3. Test responsive styling controls in a controlled manner
- Choose a less important block, such as a content group on staging.
- Set a clear change on Mobile, such as reducing the font size or spacing.
- Preview it on Desktop, Tablet, and Mobile in the editor.
- Open the page in an incognito browser and test it further on a real device.
- Recheck fragile elements such as menus, tables, CTA buttons, and image columns.
Avoid setting too many breakpoints or editing Global Styles and individual blocks at the same time. When an issue occurs, first remove the change from the individual block, then check theme.json and custom CSS. If your editorial workflow does not want users to make viewport-specific changes themselves, WordPress 7.1 has a setting responsiveEditingEnabled to disable the responsive editing interface; this does not remove saved responsive styles (according to WordPress.org).
4. Test the media editor and Notes
For the media editor, try JPEG, PNG, WebP, and large images in turn. After cropping or rotating an image, check it in the Media Library, older posts, the image sitemap, and thumbnail versions. Do not directly edit the website’s only copy of an image unless you are sure the host can restore the file.
For Notes, create three test roles: writer, editor, and approver. Attach a note to a paragraph, reply to it, mention a colleague if the workflow supports it, and then check who receives notifications. Standardize conventions such as “Feedback,” “Needs revision,” and “Resolved” to prevent Notes from becoming a discussion channel without a conclusion.
If the website has multiple users, you should also review AI agent permissions management and logging to establish clear approval rules for new automated or collaborative workflows.
How to check results and handle common issues
After updating staging, use the acceptance checklist below before deploying to production:
- Display: check the homepage, posts, category pages, menu, footer, and 404 template on wide screens, tablets, and phones.
- Functionality: submit forms, log in, search, process payments, upload images, and interact with dynamic content.
- Performance: clear the cache according to the proper procedure and then check again; do not draw conclusions from a single load while the cache is still stabilizing.
- SEO: check titles, canonical tags, structured data, featured images, and indexability.
- Accessibility: use the keyboard to navigate menus, buttons, and modals; check focus, form labels, and contrast.
Some common issues have relatively clear solutions:
- Mobile layout overflows: disable the responsive change you just created, check for fixed widths in the block or old CSS, and then try each property again one at a time.
- Edited image does not appear: check write permissions for the uploads directory, regenerate thumbnails, and temporarily disable image optimization plugins to identify conflicts.
- Editor has JavaScript errors: open the Console, disable plugins related to blocks or builders one at a time, and then compare compatible versions.
- Notes generate too many notifications: limit followers, agree on mention rules, and move resolved notes to a completed status.
- Media Library’s infinite scrolling is difficult to use: check the option in the user profile or configure an appropriate filter; WordPress 7.1 changes the default behavior to infinite scroll, so accessibility must also be evaluated (according to WordPress.org).
Deploy to production only after staging has passed functional checks and you have a fresh backup taken immediately before the update. Then monitor error logs, forms, orders, and high-traffic pages for at least one operating cycle appropriate for the website.
For websites that depend heavily on search, combine post-update checks with how to interpret AI Overviews and AI Mode data to detect changes in visibility and traffic from Google early.
Reference source
