Quick answer: WordPress 7.1 “Mary Lou” was released on August 19, 2026. It adds responsive styling without custom CSS, a new media editor with proper cropping and flipping, in-browser image processing, support for AVIF and HEIC images, inline Notes with @mentions, and two new blocks: Tabs and Playlist. Yes, you should be on it, and specifically on the latest point release (7.1.3, released October 6, 2026, at the time of writing), because the point releases include security fixes. Back up first and test page builders and editor plugins, because the post editor now always runs in an iframe.
WordPress releases can feel like a long list of developer changes. This guide focuses on what you will notice as a site owner, what could break, and how to update safely. All details come from the official WordPress.org release announcement.
WordPress 7.1 at a glance
| Area | What changed | Who benefits |
|---|---|---|
| Design | Responsive styles in Global Styles and block settings | Anyone using a block theme |
| Buttons | Hover, focus and active styles without CSS | Site owners and designers |
| Media | New crop, rotate and flip editor; in-browser image processing | Everyone who uploads images |
| Formats | AVIF, HEIC and HDR gain maps supported | iPhone users and speed-focused sites |
| Blocks | New Tabs and Playlist blocks; custom icon collections | Content creators, podcasters, developers |
| Collaboration | Notes attached to text, with rich text and @mentions | Teams and agencies |
| Editor | Post editor always loads in an iframe; admin bar in every editor | Theme and plugin compatibility |
Responsive styles without code
The biggest design change is responsive styling. In the Site Editor you can now set different styles for desktop, tablet and mobile in Global Styles or on individual blocks. A preview shows how the design looks at each size. Previously you needed custom CSS, a page builder or a plugin to do this.
Block theme authors can also define their own mobile and tablet breakpoints in theme.json, so the editor’s responsive controls match the theme’s layout. This is a big step for people who prefer the block editor over Elementor or Divi. If you are new to blocks, start with our WordPress block editor guide.
Interactive button styles
Buttons can now have hover, focus and active styles set in the editor, either for one button or for every button on the site. This sounds small, but it was one of the most common reasons people added custom CSS. Clear focus styles also help keyboard users, which supports accessibility.
A proper media editor
The old inline crop tool has been replaced. Clicking Crop now opens a modal editor with:
- Freeform cropping and fixed aspect ratios
- Horizontal and vertical flipping
- Precise rotation and snap rotation
- Editing image metadata
Upload handling also improved. You now see progress indicators, and uploads retry automatically if your connection drops.
Image processing moves to the browser
This change matters most for people on cheaper hosting. WordPress 7.1 compresses images, resizes them and creates thumbnails in your browser before uploading, using a WebAssembly build of the libvips image library. Less work on the server means fewer upload failures caused by PHP memory limits and timeouts. If you have ever seen “the server cannot process the image”, this release should reduce it.
AVIF, HEIC and HDR support
WordPress 7.1 adds native support for AVIF, a modern format that is often smaller than JPEG and WebP, plus HEIC, the default photo format on iPhones, and HDR gain maps. There is also an opt-in conversion that turns animated GIFs into video files, which are usually much smaller. Smaller images help page speed; see how to speed up WordPress for the rest of the checklist.
New blocks: Tabs and Playlist
- Tabs lets you show related content in tabbed panels, useful for pricing plans, product specs or FAQs grouped by topic.
- Playlist groups several audio tracks, with an optional waveform for each. It suits podcasts, music and courses.
- Icon block collections let developers register custom icon sets that appear next to the built-in icons.
Notes for teams
Notes, the editorial comments feature, can now be attached to a specific piece of text instead of a whole block. Notes support bold, italic, code and links, and typing @ mentions a collaborator and notifies them. Several conversations can run on the same block. For agencies and content teams, this reduces the need for separate review tools.
What could break: the iframed post editor
The most important compatibility change is that the post editor now runs inside an iframe for every theme, as the Site Editor already did. Benefits: admin styles no longer leak into your content, and viewport units and media queries work properly in the editor.
The risk: older plugins that add scripts or styles to the editor in outdated ways may stop working in the editor. Before updating a business site, test on a staging site and check:
- Your page builder opens and saves pages.
- SEO plugin panels appear in the editor sidebar.
- Custom blocks from plugins still render correctly.
- Forms, galleries and sliders display as expected in the editor and on the front end.
If something fails after updating, our guide to a WordPress plugin not working walks through finding the culprit.
Developer highlights
- A public SVG Icon API with functions to register icon collections and icons.
- The Abilities API, introduced earlier, gains a filterable execution lifecycle and custom validation, which supports automation and AI-powered integrations.
- New design system foundations for admin interfaces, with semantic design tokens.
- theme.json supports responsive styles and pseudo-states such as hover and focus-visible.
- Speculative loading defaults can be set with constants or environment variables.
How to update safely
- Take a full backup of files and database. See our WordPress backup guide.
- Update plugins and themes first, so they are ready for the new version.
- Test on staging if the site makes money.
- Go to Dashboard → Updates and update to the latest 7.1.x release.
- Clear caches, then check your homepage, a post, a contact form and, for shops, a test checkout.
- If you see a critical error, follow our guide to there has been a critical error on this website.
What comes next: WordPress 7.2
WordPress 7.2 Beta 1 was released on October 20, 2026, and the final release is planned for December 8, 2026. The beta adds responsive controls to more blocks, text shadow settings, emoji reactions in Notes, an “On This Day” dashboard widget and a Secrets API for developers. Do not run betas on a live site; test them on staging. We cover security point releases in our WordPress security news hub.
FAQ
Is WordPress 7.1 stable enough for a business site?
Yes. It has had several point releases since August, including maintenance and security fixes. Use the latest 7.1.x version and test key plugins first.
Do I need a block theme to use the new features?
The responsive styling and breakpoint features are built for block themes and the Site Editor. The media editor, image processing, Notes and new blocks work with any theme.
Will WordPress 7.1 slow down my site?
No. In-browser image processing reduces server load, and better image formats make pages lighter. Slowdowns after an update usually come from a plugin or cache issue, not core.
Which PHP version does WordPress 7.1 need?
WordPress recommends PHP 8.3 or higher, and older versions down to 7.4 are still supported. Running a current PHP version is faster and more secure.
WordPressPrime.com is an independent guide and is not affiliated with the WordPress Foundation, WordPress.org or Automattic. Always back up your website before making changes, and check official sources for the latest details.
