WordPress 7.1 Beta 1 landed today, 15 July 2026, and the final release is locked in for 19 August at WordCamp US in Phoenix. If your team builds on WordPress — whether you maintain client sites, ship plugins, or run a headless stack — this is the release cycle where several long-deferred changes finally arrive. Some of them will break things.
Here is what matters, what to test now, and what you can safely ignore.
TL;DR
- WordPress 7.1 Beta 1 drops 15 July 2026, with the final release scheduled for 19 August at WordCamp US in Phoenix.
- React 19 replaces React 18 under the hood — any plugin using compiled JSX, @wordpress/element, or editor internals needs immediate compatibility testing.
- Responsive block styling arrives in core, letting editors control per-viewport layouts without custom CSS or media queries.
- The new Guidelines feature gives site owners structured editorial rules that plug directly into AI content tooling.
- The Classic block and TinyMCE are deprecated — teams still relying on Classic Editor workflows need a migration plan before August.
- Real-time collaboration (RTC) has been deferred again and will not ship in 7.1.
React 19: The Change That Will Break Plugins
This is the headline. WordPress 7.1 upgrades from React 18 to React 19, and the compatibility implications are significant.
React 19 removes several legacy APIs that WordPress plugins have relied on for years. The react-dom/test-utils package is gone. ReactDOM.render is fully removed in favour of createRoot. String refs no longer work. If your plugin ships compiled JSX or touches editor internals, these are not theoretical concerns — they are build-breaking changes.
The Gutenberg team has been proactive here. Since Gutenberg 23.4, there has been an experimental gutenberg-react-19 flag that swaps the React 18 bundles for React 19 at runtime. Enable it under the Experiments screen and watch your browser console. Compatibility polyfills will log warnings wherever your code hits a removed API.
Our advice: do not wait for Beta 2. Set up a staging environment today, enable the flag, and run your entire plugin and theme stack against it. The plugins that break in August will be the ones whose teams assumed someone else would catch the issue.
At REPTILEHAUS, we have been running React 19 compatibility audits for client WordPress builds since the flag shipped. If your plugin portfolio is large, this kind of systematic testing is not optional — it is the difference between a smooth upgrade and a support fire.
Responsive Block Styling: The End of Viewport Hacks
For years, making WordPress blocks responsive meant writing custom CSS, adding media queries manually, or relying on third-party plugins that bolted viewport controls onto the block editor. WordPress 7.1 makes this native.
Editors can now define how any block appears at different screen sizes directly in the editor. Gutenberg 23.5 replaces the old fixed desktop/tablet/mobile preview toggle with a unified, freely resizable device preview — drag the edge of the canvas and see your layout adapt in real time.
Alongside viewport-level control, pseudo-state styling for hover, focus, and active states ships for both Global Styles and individual blocks. This is a meaningful step towards eliminating the gap between what designers specify and what content editors can actually implement without touching code.
For agencies and development teams, this changes the conversation with clients. Responsive behaviour that previously required developer intervention can now be handled by content teams directly. That is a win for everyone — editors move faster, developers focus on higher-value work.
Guidelines: AI-Ready Editorial Governance
The Guidelines feature, which has been shipping as an experiment since Gutenberg 22.7 in March, is slated for WordPress core in 7.1. On the surface, it is straightforward: site owners get a structured place to define editorial rules, brand voice, tone, and content standards.
The interesting part is what sits underneath. Guidelines are designed to plug directly into AI content tooling. When an AI assistant generates or edits content within WordPress, it can reference the site’s Guidelines to stay on-brand and within editorial boundaries. The feature supports import and export between sites, making it practical for agencies managing multiple properties.
This is WordPress acknowledging what every development team already knows: AI is writing content on WordPress sites right now, and there is no governance layer for it. Guidelines is a first attempt at solving that problem at the platform level.
If your team builds AI-powered content workflows — and if you are not, your competitors are — this is infrastructure worth paying attention to. It is also an area where custom integration work will be needed to connect Guidelines with specific AI tools and workflows. That is exactly the kind of AI integration work our team specialises in.
Classic Block Deprecation: The Migration You Cannot Postpone
WordPress 7.1 formally deprecates the Classic block and lazy-loads TinyMCE to improve performance. This has been coming for years, but deprecation in core means the clock is now ticking.
If your sites or client sites still rely on Classic Editor workflows — and a surprising number of enterprise WordPress installations do — you need a migration plan. The Classic block will not vanish overnight, but deprecation means it stops receiving bug fixes, security patches slow down, and eventually it gets removed entirely.
The practical impact is straightforward: audit your sites for Classic block usage, identify content that needs converting to native blocks, and plan the migration. For large sites with thousands of posts using Classic blocks, this is a non-trivial project that benefits from automation and tooling rather than manual conversion.
Notes, Collaboration, and What Did Not Ship
WordPress 7.1 brings improvements to the Notes feature, including suggestion mode and emoji reactions, making asynchronous editorial feedback richer. These are welcome quality-of-life improvements for editorial teams.
The elephant in the room is real-time collaboration (RTC). It was cut from WordPress 7.0, and it has been deferred again for 7.1. The release is framed around collaboration, but the flagship collaboration feature — multiple editors working on the same post simultaneously, Google Docs-style — remains unresolved.
This is not surprising. RTC in a system as extensible and plugin-dependent as WordPress is an extraordinarily difficult engineering challenge. But it does mean that teams waiting for native real-time co-editing need to continue relying on third-party solutions or workflow-based approaches for now.
What Your Team Should Do This Week
Beta 1 is here. The final release is five weeks away. Here is a practical checklist:
- Spin up a staging environment with WordPress 7.1 Beta 1 today. Do not test on production.
- Enable the React 19 flag in Gutenberg Experiments and test every plugin and custom theme in your stack. Watch the console for deprecation warnings.
- Audit Classic block usage across your sites. If you have significant Classic block content, start planning the migration now.
- Test responsive styling with your existing themes. Verify that per-viewport block controls work as expected with your custom blocks and design systems.
- Review the Guidelines feature if your editorial workflow involves AI-generated content. Consider how structured editorial rules could integrate with your existing tooling.
- Update your deployment pipeline to include WordPress 7.1 beta testing as a gate before the August release.
The Bigger Picture
WordPress 7.1 is not a revolution. It is a release that finally delivers on several promises that have been in the pipeline for multiple cycles — particularly React 19 and responsive styling. The AI-adjacent Guidelines feature signals where WordPress is heading, even if the implementation is still early.
For development teams and agencies, the React 19 upgrade is the item that demands immediate attention. Everything else can be adopted incrementally. But the teams that start testing today will be the ones offering smooth upgrades in August, while everyone else scrambles.
If your team needs help with WordPress 7.1 compatibility testing, React 19 migration, or building AI-powered editorial workflows on the new Guidelines framework, get in touch. This is what we do.
📷 Photo by Souvik Banerjee on Unsplash
