On July 15, 2026, WordPress 7.1 Beta 1 ships. Betas will follow weekly through the end of the month, and the final release is locked for August 19 — timed to land at WordCamp US. If you build on WordPress, maintain a site, or write plugins, the window to test and break things is right now. Three days from today.

WordPress 7.0.1, the maintenance release, just dropped on July 9 with 13 Core tickets and 13 Gutenberg fixes. That means the 7.0 dust has settled and the 7.1 train is leaving the station. The WordPress Developer Blog published the July 2026 roundup two days ago, and the feature list is packed. Not the "minor tweaks and bug fixes" kind of packed. The "your plugin might break and your theme might need updates" kind of packed.

Responsive styling is finally real

The single most requested feature in the block editor's history is per-breakpoint styling, and 7.1 makes it testable in core. You will be able to set different font sizes, spacing, and layout properties for mobile, tablet, and desktop directly in the editor — no custom CSS hacks, no third-party block extensions. If you have been writing @media queries by hand to compensate for the editor's one-size-fits-all approach, this changes everything about your workflow.

The feature has been available in the Gutenberg plugin for a few releases, but landing it in core means it gets the stability pass and the API surface that theme developers can actually depend on. Test your themes now. If your block styles assume a single breakpoint, they will behave differently once responsive styling is active.

The AI Client gets streaming and embeddings

WordPress 7.0 shipped a built-in AI Client API, which was the first time core offered a standardized way for plugins to talk to AI providers. In 7.1, the API grows up. Streaming responses land in this release, which means plugins can deliver real-time AI output — think live content generation, streaming chat responses, and progressive block suggestions without the user staring at a spinner.

Embeddings support is also coming, which opens the door for semantic search, content recommendations, and context-aware AI features that understand what a site's content actually means rather than just matching keywords. If you are building anything AI-powered on WordPress, the 7.1 AI Client is the foundation you should be building on. Rolling your own provider integration is now the wrong move.

React 19 is coming — test your plugins

WordPress is migrating from React 18 to React 19 in the 7.1 cycle. This is not a behind-the-scenes swap. React 19 changes how concurrent rendering works, introduces new hooks, and deprecates patterns that many plugins rely on. The WordPress core team is explicitly asking plugin developers to test against the betas now.

If your plugin uses ReactDOM.render, findDOMNode, or the legacy context API, those will generate warnings in 7.1 and break in future releases. The components package is also dropping the 40px opt-in prop, which affects how admin UI elements size themselves. These are the kinds of changes that surface as "it works fine" during beta and then explode in production. Test early.

Block Bindings grow up

Block Bindings, the feature that lets blocks pull data from custom fields and other sources, expands significantly in 7.1. The biggest change: bindings now work on List Items and nested content. Previously, you could bind a paragraph or a heading to a custom field, but nested blocks inside groups and columns were stuck with static content. That limitation is gone.

For anyone building data-driven sites — directories, real estate listings, product catalogs — this is the feature that makes block bindings genuinely useful instead of a cool demo. Combined with the new extensibility surfaces for block variations, theme developers get significantly more control over how bound blocks render and behave.

Layout improvements and the admin bar

Two quality-of-life changes that will make daily editors happier: the admin bar returns to the post and site editors (it was removed in 7.0 and people were not quiet about it), and layout controls now support real fixed widths and auto-fit grids. The grid auto-fit behavior means blocks can adapt their column count based on available space without requiring explicit breakpoint rules, which pairs nicely with the new responsive styling features.

What to do this week

If you run a WordPress site, update to 7.0.1 if you have not already (it shipped July 9 and is bug-fix only). If you develop plugins or themes, spin up a WordPress Playground instance and test against the 7.1 beta starting Tuesday. The Playground integration means you can test without touching a production site — just open playground.wordpress.net and load the beta.

The final release drops August 19. That gives you roughly five weeks to find the edge cases before 43 percent of the web picks it up.

Sources: WordPress Developer Blog — What's new for developers (July 2026), WordPress 7.0.1 maintenance release