WordPress 7.1: 6 Ultimate New Features (Complete Guide)

WordPress 7.1 is the second major WordPress release of 2026, shipping August 19 on the final day of WordCamp US in Phoenix and adding no-code responsive design controls, threaded @mention notes, a redesigned image editor, and two new blocks. If you run a WordPress site, this release changes how you style pages, collaborate with your team, and manage media — without touching a line of custom CSS. Here is everything that changed, why it matters, and how to prepare for it before you update a live site.

What Is WordPress 7.1 and When Does It Release?

WordPress 7.1 is a scheduled feature release that arrives August 19, 2026, timed to the closing day of WordCamp US, which runs August 16–19 in Phoenix, Arizona. According to the official WordPress 7.1 Field Guide, the release bundles more than 310 Trac tickets, over 100 of which are enhancements and feature requests, plus more than 180 bug fixes.

Unlike WordPress 7.0, which launched in May 2026 and introduced the platform’s first deep AI and real-time collaboration principles, 7.1 is largely a “finish what we started” release. It polishes the editing experience rather than introducing one dramatic new feature, which is why most site owners will notice a collection of smaller day-to-day improvements instead of a single headline change.

Two release candidates and a third RC shipped in the two weeks before launch, according to the official WordPress 7.1 Release Candidate 1 announcement, which means the feature set was locked well ahead of the public release. Barring a critical last-minute bug, the August 19 date is not expected to slip.

What’s New in WordPress 7.1’s Responsive Styling Controls?

WordPress 7.1’s biggest practical upgrade is bringing per-device and per-state styling directly into the block editor. For the first time, you can set different padding, font size, or layout for tablets and phones, and style hover, focus, and active states, entirely through editor controls instead of custom CSS.

In practice, this means a button that looks perfect on desktop but overflows on mobile no longer needs a child theme or a custom CSS snippet. You select the tablet or phone breakpoint icon in the block toolbar and adjust that block’s settings for that view only, while the desktop version stays untouched. The same logic applies to interactive states: a link’s hover color, a button’s focus outline, or a card’s active-state shadow can all be set from the block sidebar, with a live preview as you adjust each one.

• Set separate padding, margin, and font size per breakpoint (desktop, tablet, phone)
• Style hover, focus, and active states without a plugin or custom CSS
• Preview each breakpoint and state directly inside the editor canvas
• Existing custom CSS keeps working exactly as before — nothing is forced to migrate

For site owners who’ve relied on a page builder or hand-written CSS just to fix mobile layouts, this closes a real gap. It won’t replace a dedicated builder for genuinely complex layouts, but it removes the most common reason non-developers used to reach for one in the first place — and it means fewer support tickets asking “why does this look broken on my phone?”

How Do WordPress 7.1’s Collaboration Notes Work?

WordPress 7.1’s Notes feature now supports @mentions: typing “@” inside a note opens a searchable list of collaborators so you can tag the right teammate directly, and they receive a notification. This turns Notes from a general scratchpad into an actual feedback and review tool for editorial teams, similar to how comments work in a shared document.

The second change is inline notes. Previously, a note attached to an entire block — so a 400-word section covered by one comment made it genuinely hard to tell which sentence the feedback referred to. In WordPress 7.1, you can select a specific sentence or phrase and leave a note on just that text, the same way you’d leave an inline comment in Google Docs or Microsoft Word.

• @mention a specific editor, author, or admin inside any note
• Highlight a sentence or phrase and attach feedback to just that text
• Mentioned users get a notification linking straight to the note
• Notes remain visible in the editor sidebar until resolved or deleted

For multi-author blogs and agencies managing client sites, this is one of the more quietly significant changes in the release. It reduces the number of feedback conversations that happen over Slack or email instead of inside the post itself, which means less context gets lost between “here’s what needs fixing” and the actual edit.

What Changed in the WordPress 7.1 Media Library and Image Editor?

Media handling gets three concrete upgrades in this release. First, a redesigned image editor makes cropping, rotating, and scaling images feel closer to a dedicated photo tool rather than a bare-bones popup — adjustments apply with a visible preview instead of a blind commit-and-check cycle.

Second, WordPress 7.1 adds native HEIC support, so photos straight off an iPhone no longer need a plugin or manual conversion before upload. This has been a recurring pain point for years — HEIC is Apple’s default photo format, but WordPress core has historically rejected it outright, forcing editors to convert files manually or install a third-party plugin just to publish a phone photo.

Third, and most useful for anyone on an unreliable connection, uploads now pause automatically if your connection drops and resume on their own once you’re back online, instead of failing outright and forcing a re-upload from scratch. Combined, these three changes shave real time off the editorial workflow for sites that publish images daily, and they matter even more for accessibility: a smoother upload flow makes it more likely editors actually fill in alt text before hitting publish, rather than rushing past it after a failed upload.

What New Blocks Does WordPress 7.1 Add?

WordPress 7.1 ships two new native blocks: a Tabs block for organizing content into switchable panels without a plugin, and a Playlist block for grouping multiple audio or video files into one playable list. Both were previously only available through third-party plugins or block libraries, which meant extra code on the page and one more dependency to keep updated.

The Tabs block is the more broadly useful of the two. A pricing page can show monthly versus annual plans in separate tabs, a documentation page can split installation instructions by operating system, and a product page can separate specs, reviews, and shipping details — all without loading a page-builder plugin just for that one section. The Playlist block is aimed squarely at podcasters and musicians who want a native way to present an episode archive or an album without embedding a third-party player.

The release also keeps the Classic block in the inserter rather than removing it as earlier proposed, which matters if your site still depends on classic-editor content or a page builder that hooks into it. And a smaller but noticeable change: the admin toolbar now stays visible while you scroll inside the editor, so you don’t lose access to Save, Preview, or Exit while working on a long page.

Both new blocks were built with keyboard navigation and screen readers in mind from the start, rather than bolted on afterward. Tab panels announce which panel is active, and the Playlist block exposes standard media controls instead of a custom player that assistive technology can’t parse. That matters beyond compliance — accessible markup is also easier for search engines to read, which feeds directly into on-page SEO regardless of which content management system you use.

How Does WordPress 7.1 Affect Page Builder Plugins?

WordPress 7.1 doesn’t disable or restrict Elementor, Divi, Beaver Builder, or similar plugins — those still work exactly as they did before, since page builders manage their own rendering layer largely independent of core. What changes is the calculus for sites that were only using a builder for basic responsive tweaks.

If your main reason for running a builder was “I need different spacing on mobile” or “I need to style a hover state,” the new native controls now cover that without the extra plugin weight. If you need drag-and-drop layout freedom, dynamic content conditions, or a large template library, a builder is still the better tool. Reviewing your current WordPress plugin stack for designers after this update is a reasonable way to check whether every plugin you’re running is still earning its keep — fewer active plugins generally means fewer conflicts on the next major core release, not just this one.

What Does WordPress 7.1 Mean for Developers and Theme Authors?

For developers, the most notable decision in WordPress 7.1 is what didn’t ship. The planned React 19 upgrade was deferred past this release and remains an experiment inside the Gutenberg plugin rather than landing in core, which means block development against React 18 APIs is safe for at least one more release cycle.

Real-time collaborative editing — the feature most anticipated after WordPress 7.0 laid its groundwork — was tested extensively during the 7.1 cycle but held back from the final release. Both decisions point to a deliberately conservative release: core contributors chose stability over shipping half-tested infrastructure, which is generally the right call for software that a plurality of the web depends on.

Block theme authors should specifically check how the new responsive and interactive-state controls interact with any custom block styles registered via theme.json, since a theme that already hardcodes breakpoint-specific CSS could end up with two competing sources of truth for the same style. Testing on a staging copy of a block theme before rolling out to production catches this quickly.

Plugin authors should run their full test suite against the release candidate branch before the stable tag, paying particular attention to anything that hooks into the media upload flow or the block inserter — those are the two areas that changed enough internally to matter for tightly coupled integrations. Tools and services that integrate through the standard WordPress REST API are unaffected either way, since this release doesn’t touch REST route registration.

WordPress 7.0 vs WordPress 7.1: What Actually Changed?

The table below compares the two most recent releases so you can see exactly what’s new rather than guessing from the changelog.

How Do You Update to WordPress 7.1 Safely?

Updating safely takes five steps, and skipping any of them is how sites end up with a broken layout right after a major release. Follow them in order rather than jumping straight to the update button in your dashboard.

1. Take a full backup of your files and database before updating anything, and confirm the backup actually restores before you rely on it.
2. Check your active theme and key plugins for a “tested up to 7.1” note in their changelog or the WordPress plugin directory.
3. Run the update on a staging copy of your site first, not production — most hosts offer one-click staging environments for exactly this purpose.
4. Test your homepage, a blog post, any custom page templates, and your checkout or contact form on staging.
5. Once staging looks correct, update production during low-traffic hours and clear any page cache or CDN cache immediately after.

Keep a rollback plan ready even after following every step above. Most hosts let you restore a backup in a few minutes, and knowing that in advance removes the pressure to “just fix it live” if something does look wrong after the update goes out.

If your site is already on shaky performance footing, this is also a good moment to work through a broader WordPress speed optimization checklist, since a fresh core update is one of the few times you’re already touching every part of the stack and can measure the before-and-after difference cleanly.

Will WordPress 7.1 Break My Plugins, Theme, or Site Speed?

For most sites, no. WordPress 7.1 deliberately avoids the kind of breaking changes that force plugin or theme rewrites. As covered above, the planned React 19 upgrade was pushed beyond this release, and real-time collaborative editing was not enabled in the final build. Both were held back specifically to avoid destabilizing existing sites.

The realistic risk is narrower: a theme or plugin that heavily customizes the image editor, the Notes UI, or the block inserter could see minor visual conflicts. Sites running a classic PHP theme are essentially unaffected, since none of 7.1’s headline changes touch the classic templating system at all.

WordPress still powers a large share of the web — recent W3Techs figures put it at roughly 41.5% of all websites as of July 2026 — which is exactly why core releases are tested this conservatively. A breaking change in WordPress core has an outsized ripple effect compared to almost any other software update on the internet, so the core team consistently favors stability over speed when the two are in tension.

Beyond the core update itself, most performance and ranking gains still come from fundamentals: solid on-page SEO fixes, a proper caching layer, and a theme that doesn’t load unused code on every page. WordPress 7.1 gives you better tools for the editing experience, but it doesn’t replace that groundwork.

WordPress 7.1 FAQ

When exactly does WordPress 7.1 release?

WordPress 7.1 is scheduled for August 19, 2026, the final day of WordCamp US in Phoenix. Release Candidates 1 through 3 shipped earlier in August with the feature set locked, so the date is not expected to slip.

Do I need to rewrite my custom CSS after WordPress 7.1?

No. Existing custom CSS keeps working exactly as before. The new responsive and interactive-state controls are optional editor tools — they give you a no-code alternative going forward, but nothing forces you to migrate existing styles.

Is real-time collaborative editing included in WordPress 7.1?

No. Real-time collaboration was tested heavily during the 7.1 development cycle but was held back from the final release. The @mention and inline notes features are the collaboration upgrade that actually shipped.

Will my plugins still work after updating to WordPress 7.1?

Most will, since this release avoids breaking API changes. Check each plugin’s “tested up to” version in the WordPress plugin directory, and always test on staging before updating a live production site.

What happened to the Classic block in WordPress 7.1?

It stays. WordPress 7.1 keeps the Classic block available in the block inserter instead of removing it, so sites still depending on classic-editor content are not affected by this specific release.

Does WordPress 7.1 add HEIC image support?

Yes. WordPress 7.1’s redesigned media library accepts HEIC files natively, so photos exported directly from an iPhone can be uploaded without converting them to JPEG first.