WordPress 7.1 is scheduled for 19 August 2026, landing on the final day of WordCamp US. Beta 1 arrived on 15 July, so the feature set is now largely visible — and one change in particular will affect sites that still rely on the Classic block.
Read this as a beta summary, not a spec sheet. The core team states plainly that planned work "doesn't necessarily mean each will make it into the final release of WordPress 7.1." Everything below reflects the published roadmap as of late July 2026. Features get deferred late in a cycle — check the official release notes on 19 August before making decisions that depend on any single item.
WordPress 7.1 at a Glance
| Item | Detail |
|---|---|
| Release date | 19 August 2026 |
| Beta 1 | 15 July 2026 |
| Minimum PHP | 7.4 — unchanged from 7.0 |
| Recommended PHP | 8.3 or newer — unchanged |
| Biggest risk | Classic block removed from the inserter |
| Focus areas | AI tooling, collaboration, media, Site Editor styling |
If you are already running WordPress 7.0 on PHP 8.3, there is no server work to do before 7.1. The requirements did not move. See the PHP requirements guide if you are unsure what you are currently running.
The Change Most Likely to Affect You
Buried among the feature announcements is the item with the widest practical impact: the Classic block is being deprecated and removed from the inserter.
This does not delete your content. Posts that already contain a Classic block continue to render. What changes is that you can no longer add a new one from the block inserter, which matters if your editorial workflow still depends on it — and a surprising number of sites migrated from the Classic Editor by wrapping old content in Classic blocks and never revisiting it.
Before updating, search your content for Classic blocks. If writers routinely insert them, plan the workflow change before release day rather than discovering it when someone cannot do their job.
AI Features
WordPress 7.0 laid the AI groundwork; 7.1 extends it. The AI Client gains generation streaming (responses appear progressively rather than arriving all at once) and embeddings, which underpin semantic search and content-similarity features.
Connectors gain authentication via username and application password, making it easier to wire WordPress to external AI services without custom code. There is also a Guidelines feature for encoding editorial rules and brand voice, so AI-assisted output can follow a publication's house style.
Worth being clear: these are foundations for developers and plugin authors more than finished features for site owners. If you were expecting to open the editor on 19 August and find a polished AI writing assistant, adjust expectations.
Collaboration and Notes
Notes, introduced earlier, becomes considerably more useful. WordPress 7.1 is set to add notes on specific content within a block and across multiple blocks, rich text inside notes, notifications for replies and follows, and emoji reactions.
For editorial teams currently running review cycles through email or a separate tool, this is the release that makes in-WordPress feedback genuinely workable. Real-time collaborative editing is also being pursued, but strategic decisions there remain open — treat it as unconfirmed.
Site Editor and Admin Changes
- Responsive and pseudo-state styling for blocks — hover and focus states, plus breakpoint-specific styling, without writing CSS. Probably the most practically useful item in the release for people building sites.
- A dedicated Identity section in the Site Editor, consolidating site title, tagline, logo and icon.
- Reorganised command palette with recent and suggested commands.
- Admin colour scheme carried into the Site Editor, closing a long-standing inconsistency.
- Persistent admin bar across editors, so navigation no longer disappears when you enter an editing context.
New Blocks and Media Handling
Three new core blocks are planned: Playlist, Table of Contents, and Tabs. Each replaces a common reason for installing a plugin, which is worth noting if you currently run a block library for one feature.
Media gains client-side processing: HEIC image support (the default iPhone photo format, previously a recurring upload complaint), Ultra HDR, and GIF-to-video conversion, which can meaningfully reduce page weight on image-heavy sites. A new media editor modal adds freeform and aspect-ratio cropping.
On performance, speculative loading moves to "moderate" eagerness when caching is detected — a modest prefetching improvement rather than a headline change.
Should You Update on Day One?
For most production sites, no — and this is not specific to 7.1. Point releases like 7.1.1 typically follow within a few weeks and resolve issues that only surface at scale. Waiting costs you very little.
Update promptly if you are running a staging environment, developing plugins or themes, or genuinely need the collaboration features. Wait if you run WooCommerce at volume, depend on heavily customised page builders, or have editorial workflows built around the Classic block.
Either way, the sequence is the same: back up, test on staging, update plugins first, then update core. Our safe update guide covers the process, and the 7.1 rollback guide covers what to do if an update goes wrong.
How to Prepare Before 19 August
- Audit for Classic blocks. The one change with a real chance of disrupting a workflow. Find out now whether your editors use them.
- Confirm your PHP version. Requirements have not changed, but if you are still on 7.2 or 7.3 you are below the minimum for 7.0 as well and are overdue.
- Test on staging during beta. Beta 1 is already out. Testing now is how compatibility problems get reported while they can still be fixed.
- Check your critical plugins. Page builders, WooCommerce extensions, and anything touching the editor carry the most risk.
- Take a verified backup. Not just a scheduled one — confirm you can actually restore it.
Frequently Asked Questions
When is WordPress 7.1 released?
19 August 2026, coinciding with the final day of WordCamp US in Phoenix. Beta 1 was released on 15 July 2026, with betas and release candidates running through the intervening weeks.
Does WordPress 7.1 require a new PHP version?
No. The minimum remains PHP 7.4 and the recommendation remains PHP 8.3 or newer, unchanged from WordPress 7.0. If you are running 7.0 today, no server change is needed for 7.1.
Will WordPress 7.1 break the Classic block?
Existing content keeps rendering. What changes is that the Classic block is deprecated and removed from the inserter, so new ones cannot be added from the editor. If your team still inserts Classic blocks as part of their routine, that workflow needs revisiting before you update.
Should I wait for WordPress 7.1.1?
For most production sites, yes. A point release usually follows within weeks and fixes issues that only appear once a release meets millions of real configurations. The exceptions are staging environments, development sites, and teams who specifically need the new collaboration features.
Are all these features confirmed?
No, and the core team says so directly: planned work "doesn't necessarily mean each will make it into the final release." This article reflects the published roadmap during the beta period. Items are sometimes deferred late in a cycle, so verify against the official release notes on 19 August before relying on any specific feature.