WordPress 7.1 entered its beta phase on July 15, 2026, and Gutenberg 23.4 arrived alongside it with an experimental toggle for testing React 19, an official call for testing on responsive styling, and a sweeping wave of deprecations across the @wordpress/components package. The final release lands on August 19, 2026, at WordCamp US – which means now is the time to get your plugins and themes ready.
The beta cycle is in full swing
The WordPress core team shipped the first 7.1 beta right on schedule on July 15, 2026, with weekly betas following through the rest of the month. The final release is set for August 19, 2026, timed to coincide with WordCamp US. For site owners and agencies, that means one thing: the testing window is open now, not after the stable release ships. If you run a site with custom plugins, custom blocks, or a Full Site Editing theme, spinning up a staging environment with the current beta should be on this week’s to-do list.
React 19 is no longer a question of “if”
The headline change for developers is the experimental gutenberg-react-19 flag that Gutenberg 23.4 adds under the Experiments screen. Enabling it swaps the React 18 bundles for React 19 at runtime – simulating exactly what every published plugin will face once WordPress core makes the actual jump. If your plugin or theme ships compiled JSX, relies on the @wordpress/element package, or touches editor internals directly, it’s worth flipping the switch now and watching the browser console for errors. Bugs caught months ahead of the real transition are far cheaper to fix than regressions discovered on a client’s production site.
Responsive styling without writing a single media query
Responsive style states have been quietly moving through the developer roundups for months, but only on July 3, 2026 did the work receive an official “Call for Testing” status. The goal is to let editors change a block’s appearance per breakpoint directly inside the editor, with no need to write custom CSS media queries. For agencies and freelancers who currently spend hours fine-tuning mobile layouts through add-on stylesheets, this could shave real hours off future projects. The block inspector’s “Apply globally” option also gains a review step: authors can now choose exactly which local style tweaks should be pushed site-wide and which should remain a one-off exception on a single block.
A deprecation wave – audit your plugins now
This month’s developer roundup also flags a broad deprecation wave across the @wordpress/components package. If your team maintains custom blocks, admin panels, or editor extensions, it’s worth working through the Gutenberg 23.4 and 23.5 changelogs to confirm you’re not relying on components slated for removal. Leaving that check until the last minute usually means scrambling to patch regressions right before 7.1 ships, with no room left for calm testing.
What to do about it now
The recommended approach is straightforward: spin up a staging copy of your site, install the current beta, enable the React 19 experimental flag, and walk through both key admin workflows and the block-based frontend. The earlier you catch a plugin or theme conflict, the smoother the real upgrade will go after August 19. It’s equally important to give clients a heads-up that a larger core update is coming and to schedule a maintenance window with them in advance.
Why this matters for online stores and business sites too
For store owners and business site operators, this update might not seem relevant at first glance, but it is. Most premium themes and plugins sold on marketplaces like ThemeForest or the WooCommerce Marketplace are themselves built on the @wordpress/components and @wordpress/element packages, so the deprecation wave will eventually surface even on sites where no custom code was ever written. Responsive styling without custom CSS could also mean faster seasonal or campaign-driven layout changes to product pages, without paying a developer for every small media-query tweak. It’s worth checking with your theme vendor whether, and when, they plan to test compatibility with WordPress 7.1 and React 19.
Conclusion
WordPress 7.1 isn’t a revolution on its own, but it’s laying the groundwork for architectural changes that will deepen in the releases that follow. Teams that skip testing React 19 compatibility and responsive styling now risk unpleasant surprises once summer ends. Need help auditing your site’s compatibility ahead of WordPress 7.1? Get in touch – we’ll help you set up a staging environment and walk through it together.
