WordPress 7.1 Launches at WordCamp US: Here’s What’s New

WordPress 7.1 is shipping on August 19, 2026, the closing day of WordCamp US in Phoenix — the traditional venue for WordPress major releases. It is the second major release of the year, led by release coordinator Anne McCarthy, and it lands with a focused set of features that affect how site owners publish content, how editors collaborate, and how AI tools interact with WordPress sites. Here is a clear breakdown of every significant change and what it means if you run a WordPress site.

Note: this is a major release, not a minor maintenance update. WordPress 7.0.4, released on August 12 with a security patch, is separate. Version 7.1 is a feature release built on months of Gutenberg plugin iterations, and it changes how the editor looks and works for everyone.

Responsive styling and hover controls — now built into the editor

The most visible change for non-technical users is that responsive design controls and pseudo-state styling (hover, focus, active states) are now native Site Editor features rather than something you write custom CSS for. In WordPress 7.0 and earlier, making a button change colour on hover required either a page builder with its own control layer or hand-coded CSS in a child theme. In 7.1, you set it directly in the editor UI.

The same applies to breakpoints. You can define how a block looks on mobile, tablet and desktop from the editor panel without touching code. For content-heavy sites and landing pages, this removes a meaningful class of developer-only tasks. Designers and editors can now own those adjustments themselves.

Asynchronous collaboration via enhanced Notes

WordPress 7.1 significantly upgrades the collaborative editing experience. The Notes feature now supports suggestion mode (propose changes without immediately applying them, similar to “suggest edits” in Google Docs), rich text formatting in comment threads, and emoji reactions. Teams working asynchronously across time zones gain a proper review loop without leaving the editor.

This matters most for organisations running multi-author editorial operations on WordPress — news sites, brand blogs, agency-managed sites. Traditionally these teams layered on third-party plugins or worked outside WordPress entirely for review cycles. Version 7.1 makes that workflow first-class. It is a meaningful catch-up with hosted editorial platforms that have offered inline suggestions for years.

New core blocks: Tabs and Playlist

Two new blocks ship in core: Tabs and Playlist. The Tabs block gives editors a native way to organise layered content — specifications, FAQs, step-by-step instructions — without a plugin. The Playlist block handles audio and video collections. Both cover common patterns that previously required third-party solutions, and having them in core means they are maintained, accessible, and compatible with any block theme.

For site owners who relied on specific page builder blocks or plugins for these patterns, it is worth testing the native versions. Core blocks benefit from guaranteed future compatibility and typically perform better on Core Web Vitals because they ship less JavaScript than plugin alternatives.

Native media organisation and a new media editor modal

The Media Library gets a new editor modal in 7.1, adding an in-context editing experience where you can crop, adjust and annotate images without leaving the page you are building. Previously, media editing required navigating away to the Media Library or opening a separate tool. The native media organisation improvements also include better folder-like grouping, making it easier to manage large asset collections inside WordPress without plugins like Real Media Library.

Classic theme migration assistance

WordPress 7.1 ships an automated migration assistant to help sites running classic PHP-templated themes move to block themes without starting from scratch. The tool analyses your existing theme structure and generates a starter block theme that preserves your visual design as closely as possible. This lowers the barrier for the large share of the WordPress install base still running classic themes — many of which date to the pre-Gutenberg era and have accumulated significant customisation.

The migration is a starting point, not a complete conversion. Complex child themes with heavy custom PHP will still need developer review. But for straightforward classic themes, the assistant can cut migration time significantly. If your site is running a theme built before 2020, this is a feature worth evaluating when planning your next update.

AI knowledge management: wp_knowledge and the Guidelines feature

Perhaps the most forward-looking addition in 7.1 is the wp_knowledge custom post type — a native place to store structured site knowledge that AI tools and content agents can read. It ships with three built-in knowledge types: guidelines, memories, and notes. You can also register your own types via a filter. Think of it as a machine-readable brief about your site: who your audience is, what tone you write in, what topics are off-limits.

Paired with this is the new Guidelines feature, which gives site administrators controls over how AI clients built on WordPress’s AI layer can interact with the site. You can restrict certain AI-assisted actions or set permissions by user role. For sites with strict editorial policies or regulated content, this is meaningful governance infrastructure, not just a novelty.

The AI Client itself gains two capabilities in 7.1: streaming responses (faster first word, better perceived performance for long-form generation) and embeddings support for semantic and vector search inside the WordPress admin. The practical implication: future AI-assisted search within large site archives will use meaning-based matching rather than keyword matching alone.

What got deferred: React 19

The most discussed deferral in the run-up to 7.1 was React 19. The upgrade will not ship in WordPress core with this release — it continues as an experiment in the Gutenberg plugin. The core team flagged increased risk of compatibility issues with older plugins and custom blocks when running under enforced iframe mode, and opted to give the ecosystem more time to adapt.

If you read our breakdown of Next.js 16 and React 19, you will know that React 19 brings meaningful performance improvements through the new compiler and Server Components. WordPress site owners will get those benefits eventually, but 7.1 is not the release for it. For most sites, this is a non-issue right now — it becomes relevant once the ecosystem upgrade lands, likely in a 2027 major release.

Block supports and developer improvements

For developers, WordPress 7.1 expands the Abilities API introduced in 7.0, which provides a consistent pattern for registering and checking feature capabilities across blocks and themes. Two new block supports and one new Global Styles property also ship — including a gradient support improvement that resolves a long-standing workaround theme authors have used for years. Extended Unicode support for email addresses closes an internationalisation gap that affected non-Latin address formats.

Should you update to WordPress 7.1?

For most production sites, the answer is yes — but with standard precautions. WordPress major releases are thoroughly tested through beta and release candidate phases (RC1 shipped with 145 fixes; RC2 followed). That said, the enforced iframe mode for block themes in 7.1 does introduce some compatibility risk with older plugins and custom blocks. Before updating:

• Test on a staging copy of your site first, not directly in production.
• Check your key plugins against the 7.1 compatibility notes in the official developer field guide.
• Back up your database and files before applying the update.
• If you run a classic theme and custom PHP templates, treat this as a minor project, not a one-click update.

Sites that use only maintained themes and up-to-date plugins from reputable developers should update with low risk. Sites with bespoke code — custom post types, complex child themes, heavily modified admin panels — benefit from a developer review before the update goes live. You can read the full update cost and scope in our guide to website development and maintenance costs.

If maintaining WordPress updates yourself feels like more than you can handle, working with a dedicated web development team that handles CMS updates, compatibility checks, and ongoing security patching is the cleaner option for business-critical sites.

What this release means for content and SEO teams

The SEO implications of 7.1 are mostly indirect but positive. The new native blocks (Tabs, Playlist) mean less plugin JavaScript on the page, which typically benefits page speed. The responsive controls in the editor make it easier to get mobile layouts right without developer cycles, which matters for Core Web Vitals. The AI knowledge layer and Guidelines feature do not directly affect search rankings today, but they position WordPress-based sites to integrate cleanly with AI search optimisation workflows as these tools evolve.

For editorial teams, the async collaboration improvements in Notes are the day-to-day win. If your content review cycle currently involves Slack threads, Google Doc comments and WordPress drafts all running in parallel, 7.1 gives you better tools to consolidate that flow inside the CMS.

Frequently asked questions

When is WordPress 7.1 released?

WordPress 7.1 is scheduled for release on August 19, 2026, on the final day of WordCamp US in Phoenix, Arizona. It is the second major release of 2026 and available from the official WordPress news channel.

Does WordPress 7.1 include React 19?

No. The React 19 upgrade has been deferred beyond WordPress 7.1 and continues as an experiment in the Gutenberg plugin. It will ship in a future major release once the broader plugin ecosystem has had time to adapt to the compatibility changes it requires.

What is the wp_knowledge post type in WordPress 7.1?

It is a new native post type that stores structured site knowledge — guidelines, memories, notes — in a machine-readable format. AI tools and content agents that integrate with WordPress can read this data to understand your site’s editorial context, tone, and rules. You can register custom knowledge types via a filter.

Is it safe to update to WordPress 7.1 immediately?

For most sites running current themes and maintained plugins, yes — after testing on staging first. Sites with older custom themes or bespoke PHP code should have a developer review compatibility before updating, particularly because of the enforced iframe mode change for block themes.

Will the old responsive and hover CSS I wrote break in WordPress 7.1?

Existing custom CSS should not break — the new editor controls add native options without removing the ability to write your own styles. However, you may find you no longer need some custom CSS once the built-in responsive and pseudo-state controls handle those cases natively.