WordPress 7.1 Beta 1 Just Landed, and the Final Release Has a Date

The WordPress 7.1 update moved from planning into real testing this week. Beta 1 shipped on July 15, 2026, weekly betas follow through the rest of the month, and the WordPress team has locked in a final release date of August 19, 2026, timed to launch during WordCamp US. If you run a WordPress site, or your agency builds on WordPress for you, this is the window where the changes are still easy to test and cheap to fix.

What the WordPress 7.1 update changes for site owners

Most of what’s landing in 7.1 sits under the hood, but a few changes will show up the moment you open the editor. The biggest one is responsive styling. You’ll be able to set different styles for desktop, tablet, and mobile directly inside the block editor, and the old fixed device-preview toggle is being replaced with a single resizable preview window. If you’ve ever had to hand a developer a list of “this looks fine on desktop but breaks on mobile” fixes, this closes a real gap.

The admin bar is also coming back to the post and site editors by default, replacing the WordPress logo corner with a plain back button. It’s a small change, but if your theme or a plugin adds custom UI near the editor header, it’s worth a look before the final release.

WordPress is also bringing back infinite scrolling in the Media Library, a feature that was removed back in WordPress 5.8. If you manage a site with a large image library, you’ll notice browsing feels faster and less like flipping through pages.

One decision worth knowing about: the Classic block was originally scheduled to disappear from the block inserter in 7.1. WordPress reversed that call. The Classic block stays, and the team is instead focused on making the block editor good enough that people choose it instead of being pushed into it.

Why the WordPress 7.1 update matters even if you never touch the code

You don’t need to write PHP to feel the effects of a WordPress core release. Themes and plugins get tested against new versions constantly, and 7.1 carries a few changes that touch how sites render. The default control size across the editor’s interface components is becoming a fixed 40 pixels, all 330 icons in the WordPress icon library now inherit color instead of using a fixed fill, and speculative loading (which preloads pages you’re likely to click next) is shifting from a conservative default to a moderate one when your host has caching set up. None of this breaks a well-maintained site, but it’s exactly the kind of change that trips up an old, neglected theme.

This is the real argument for treating a WordPress update like routine maintenance rather than an annual chore. A site built on clean, well-structured markup tends to sail through core updates without drama, while a site patched together with outdated plugins is where compatibility issues actually show up. The same logic applies to performance. As WordPress detailed in its own July developer roundup, the 7.1 cycle also lays groundwork for a faster, libvips-based image editor in core, which fits a pattern we’ve written about before: how a site’s underlying build quality decides its speed and search ranking, not just its design.

What to do before August 19

You don’t need to install a beta on your live site. What’s worth doing now is simpler: check that your theme and major plugins are actively maintained, back up your site before any update, and if you or your agency maintain custom code, test it against the Gutenberg plugin’s experimental React 19 flag, since that’s the clearest early signal of what changes when WordPress eventually makes that jump. Developer tooling shifts like this tend to arrive in waves. It’s the same reason we’ve been tracking changes like GitHub Copilot’s move to usage-based billing, since the tools your developer relies on shape how fast and how safely your site gets updated.

If your site runs on a page builder or a heavily customized theme, ask whoever maintains it whether they’ve checked compatibility with 7.1 betas. A quick staging-site test now avoids a scramble on release day.

Frequently Asked Questions

When does WordPress 7.1 officially release?

WordPress 7.1 is scheduled for final release on August 19, 2026, to coincide with WordCamp US. Beta releases continue weekly until then, followed by a release candidate on August 5.

Will the WordPress 7.1 update break my website?

Not if your theme and plugins are actively maintained. Most of the risk sits with older, unsupported themes or custom code that relies on deprecated components. Testing on a staging site before updating is the safest approach.

Is the Classic block being removed in WordPress 7.1?

No. WordPress reversed an earlier plan to hide the Classic block from the inserter. It remains available, and the team is focused on making the block editor a better default choice instead.

The bottom line on the WordPress 7.1 update

The WordPress 7.1 update brings genuine, visible improvements, easier responsive editing, a faster Media Library, and a more consistent editor interface, alongside under-the-hood changes that mostly matter if your site is running outdated code. You have about a month before the final release lands. Use it to confirm your site is in good shape, not to worry about a beta you’ll never need to touch directly.