WordPress 7.0: What’s new, what changes, and how to prepare

Key takeaways

• WordPress 7.0 launches April 9, 2026, marking the official start of Gutenberg Phase 3.
• The DataViews admin overhaul is the highest-risk compatibility change in this release.
• The minimum PHP version rises to 7.4.
• Major WordPress releases are not the same as minor updates; don’t let auto-updates handle this one without testing first.

WordPress 7.0 is not a routine update.

It’s the formal launch of Phase 3 of the Gutenberg project, the most significant shift in how WordPress works since the block editor itself. The focus is collaboration: bringing the feedback loops, editorial workflows, and team communication that most agencies and content teams currently handle in Slack, Google Docs, and Trello directly into the CMS. 

For developers, it also brings real technical changes that require preparation. The latest April 9 release date has been postponed for a few weeks, but that gives you more time to prepare.

Let’s talk about what’s new, what is at risk, and exactly what to do before you update.

What is WordPress 7.0?

WordPress 7.0 is the official launch of Gutenberg Phase 3, and its core theme is workflows. The release moves WordPress away from the single-editor model it has operated on since launch and toward a shared, real-time environment where writers, editors, designers, and clients can work together inside the platform.

As of publication, the April 9, 2026, release date has been postponed “3-4 weeks.” After the slower pace of 2025, WordPress is also returning to a three-release cadence: version 7.1 was tentatively scheduled for August 19, 2026, and version 7.2 is expected around December 8-10, 2026. We’ll see if those dates change with the delay of 7.0.

WordPress 7.0 release schedule

The testing window is open now. Here is the full timeline:

The Field Guide—Automattic’s official documentation of deprecated functions and breaking changes—published on March 19 alongside RC 1. Read it before you update anything in production.

What’s new in WordPress 7.0

1. Enhanced notes and asynchronous collaboration

For anyone who has managed a client content approval process, this feature solves a real problem.

WordPress 7.0 expands the basic block-level commenting introduced in 6.9 into a full inline communication system. Users can leave notes on specific blocks or text fragments directly inside the editor. Teammates receive email or dashboard notifications automatically, and @ mentions route feedback to the right person without leaving the CMS.

• The old workflow: take a screenshot, paste it into an email or Slack thread, wait for a response, try to figure out which paragraph the feedback refers to, and repeat. 
• The new workflow: the conversation lives exactly where the content lives.

For agencies managing client approvals across multiple sites, this change alone removes an entire layer of back-and-forth from the production process.

2. Real-time co-editing

The headline feature of Phase 3 is real-time co-editing: multiple users working on the same post simultaneously, with live cursor visibility and instant block updates for all connected editors.

• When two or more users open the same post, the editor signals that collaboration is active. 
• When one editor finishes working in a block and moves on, those changes push to all other connected users instantly, no page reload required. 
• A brief highlight animation marks the block that just changed. 

Writers working on different sections of a long post can do so in parallel without stepping on each other’s work.

One important caveat: performant real-time collaboration relies on WebSocket servers, and many shared PHP hosting environments do not support them. WordPress 7.0 may ship this feature as experimental or limit it to environments that meet the technical requirements. 

If real-time co-editing matters to your workflow, verify that your WordPress hosting environment supports WebSockets before planning around it.

3. DataViews: the admin overhaul

The WordPress admin dashboard has looked essentially the same for over a decade. WordPress 7.0 changes that.

DataViews replaces the traditional WP List Tables on the Posts, Pages, and Media screens with a modern, app-like interface. Users get inline filtering without page reloads, multiple layout options (table, grid, or list), and persistent view preferences that remember how you like to work.

This is also the highest-risk compatibility change in 7.0. Any plugin that hooks into or modifies the existing Posts, Pages, or Media list views may break. This is not a minor styling conflict: it’s a structural replacement. Audit your plugins before you upgrade. The next section covers exactly which plugin categories are at risk.

4. Responsive editing mode

WordPress 7.0 gives content editors direct control over which blocks appear on desktop, tablet, or mobile, from inside the editor, with no CSS or plugins required.

Before this, showing a condensed call-to-action on mobile and a full banner on desktop required a plugin, custom CSS classes, or a child theme workaround. Now, an editor with no coding knowledge can handle it directly. 

For agencies, this means fewer support requests about mobile layout and more editorial control handed back to clients.

5. Pattern editing: Spotlight and Isolated Editor Mode

Editing a synced pattern previously required leaving your current post, opening the pattern separately in another screen, making changes, and navigating back. For non-technical users, this was disorienting enough that mistakes were common.

WordPress 7.0 introduces two modes that fix this. 

• Isolated Editor Mode lets users edit synced patterns inline, in context, without losing their place. 
• Spotlight Mode dims everything else in the editor and focuses the view on a single pattern or note, useful when a page is complex and concentration on one section matters.

For sites with global elements like announcement banners, CTAs, or footer blocks built as synced patterns, editors can now update them without accidentally navigating away.

6. Block design tools

WordPress 7.0 ships a set of design controls natively that previously pushed developers toward page builders like Elementor or Divi:

• Text line indent: Add paragraph indentation without writing CSS
• Text column support: Flow a single paragraph across multiple columns, newspaper-style, without a plugin
• Aspect ratio controls: Lock wide or full-width images to a specific ratio so they never appear stretched
• Dimension presets: Pre-defined spacing values that keep layout consistent across the whole site

These aren’t flashy features. They’re the practical controls that kept WordPress-native development frustrating for years. Their arrival in core reduces plugin dependency for theme developers and site builders.

7. The Abilities API and AI client

WordPress 7.0 is not adding an AI writer, but it is building the infrastructure that allows AI to work reliably within the CMS.

The new Abilities API acts as a standardized bridge between WordPress and external AI services. Instead of requiring custom integrations for each AI model, plugin developers can register their capabilities once and expose them to any AI client that understands the Model Context Protocol (MCP). This means tools like Claude and ChatGPT can discover what a specific WordPress site can do, request permission to act, and execute tasks within defined boundaries.

Practical applications include AI-generated alt text for images, SEO improvement suggestions, and content workflow automation. This is infrastructure work, maybe not a feature you will click on day one, but it matters for anyone building AI-powered tools on WordPress.

8. New native blocks: breadcrumbs, icons, and more

WordPress 7.0 adds two native blocks that have long required plugin dependencies:

• Breadcrumbs block: Adds hierarchical navigation trails (Home > Category > Post) to any template without a plugin, integrating cleanly with the Site Editor
• Icons block: Inserts scalable icons directly into content or layouts

Several existing blocks also get meaningful upgrades:

• The Gallery block gains a lightbox mode so clicking an image opens an overlay rather than a new page. 
• The Grid block adds responsive layout support. 
• The Cover block now supports embedded video backgrounds without requiring a direct file URL. 

Each of these eliminates a common plugin dependency that agencies often carry across every client site.

9. Heading block as block variations

Heading levels H1 through H6 now register as proper Block Variations. Users can insert “Heading 2” directly from the block inserter with its own icon, style, and default attributes.

This is a small change with a meaningful impact on editorial speed. Writers who are not thinking about block mechanics can search for what they need and insert it cleanly. Theme developers can define distinct default styles per heading level, making design systems more consistent from the start.

10. PHP-only block registration

WordPress 7.0 lets developers register blocks using only PHP, with no React, no Node.js, and no build toolchain required.

Previously, creating a custom block meant setting up a JavaScript build environment with Node, npm, and React. That barrier kept many experienced PHP developers out of block development entirely. 

PHP-only block registration removes it. WordPress generates the editor controls automatically. The result is lighter, faster plugin development for blocks that do not need complex client-side interactivity.

11. No new default theme

WordPress 7.0 will not ship a “Twenty Twenty-Six” theme. The project has moved away from the tradition of bundling a new theme with every major release. Instead, the focus is on making existing block themes, particularly Twenty Twenty-Five, more capable through the Site Editor and Phase 3 tools. 

The message from the core team: you do not need a new theme; you need a better editor.

WordPress 7.0 vs. 6.x: what actually changed

The technical changes that require action

Testing on staging is the right call. Here is what to actually look at when you get there.

PHP 7.4 is the new minimum — act before the update

Sites running PHP 7.2 or 7.3 need to upgrade before updating. Not after. Not the same week. Now.

The reason is straightforward: the collaboration features, AI libraries, and performance tools in WordPress 7.0 depend on capabilities that older PHP versions do not support. Many third-party AI SDKs already require PHP 7.4 or higher. The core team is not raising the minimum version as a formality.

PHP 8.2 or 8.3 is the recommended target, not just the minimum. Newer PHP versions deliver real performance improvements and stronger security, not just compatibility.

To check your current PHP version: 

1. Log in to your hosting control panel or run php -v in your terminal. 
2. Run the PHP upgrade in your staging environment and test critical functionality.
3. Promote to production after confirming nothing breaks.

The DataViews migration will break some plugins

Not every plugin will break, but some will. The ones at highest risk are the ones most agencies and developers use every day.

The safest approach is to update all plugins to their latest versions on staging first, then upgrade WordPress to the 7.0 RC. Visit every admin screen you use regularly before touching production.

Editor iframing changes how your styles render

WordPress 7.0 moves toward full iframing of the editor canvas. This creates a sandboxed editing environment that makes the WYSIWYG experience significantly more accurate. What you see in the editor now matches what visitors see on the front end.

The tradeoff: custom admin stylesheets and editor CSS overrides may conflict with the new design tokens introduced in 7.0. Test your theme’s editor styles in the new environment. If your site uses custom editor styling, budget time to review and adjust it before launch.

How to prepare: a pre-launch checklist

Do not let auto-updates handle a major release. 

WordPress auto-updates are appropriate for minor security patches and maintenance releases. A version 7.0 release touches the admin interface, the editor architecture, the PHP layer, and plugin compatibility simultaneously. It needs a staged, deliberate process.

1. Check your PHP version — upgrade to 8.2 or 8.3 now if you are below 7.4; do not wait.
2. Audit plugins that touch admin list views — Posts, Pages, and Media screens are all affected by DataViews
3. Clone your production site to a staging environment — never test a major update on a live site
4. Install the WordPress 7.0 Beta or RC on staging — run through every critical workflow: publish a post, upload media, manage users, process a form submission
5. Use visual comparison testing — check for layout regressions before they reach production; Liquid Web’s Managed WordPress includes a Visual Inspector that creates a staging site, runs the update, and shows a before/after comparison so you can see exactly what changed before committing
6. Test your editor styles — the iframed editor may render custom stylesheets differently than before
7. Walk your team through the Notes workflow in a sandbox — the collaboration features are new enough that a dry run before launch saves confusion later
8. Read the WordPress 7.0 Field Guide — it published March 19 on the Make WordPress Core blog and contains the complete list of deprecated functions and breaking changes
9. Plan your upgrade window — waiting one to two weeks after the launch gives the community time to surface compatibility issues and plugin vendors time to push updates

What WordPress 7.0 means for agencies

For agencies managing multiple client sites, WordPress 7.0 changes more than the editor.

• The Notes system removes a process problem that has existed for years. Client feedback no longer lives in a separate email thread or Slack channel that someone has to cross-reference with the CMS. It lives on the block the feedback is about. That alone reduces the back-and-forth in content approval cycles and makes client communication faster to act on.
• DataViews makes managing large content libraries across many sites faster and more consistent. The app-like interface, persistent views, and inline filtering add up to real time savings when you are working across dozens of properties.

The risk, though, scales with the number of sites. Testing one site before a major upgrade is manageable. Testing 20 requires a repeatable process, consistent environments, and tooling that makes staging and visual comparison fast. 

Liquid Web agency customers are running 50 or more sites on infrastructure built for exactly that kind of scale: predictable, standardized environments where spinning up a staging clone and running a pre-launch check is a routine part of the workflow, not a scramble.

Learn more about our agency hosting and get in touch if you need some help navigating the update.

WordPress 7.0 FAQs

Getting started with WordPress 7.0

WordPress 7.0 is a meaningful release, and the preparation work is real. Check your PHP version, audit your plugins, clone your site to staging, and give yourself enough time to test before updating. The teams that update without incident will be the ones that treated this as a planned process rather than a one-click event.

If you are managing this across multiple client sites, the process needs to be repeatable. That means consistent environments, fast staging, and tooling that surfaces compatibility issues before they become client calls at 2 a.m.

Liquid Web’s Managed WordPress hosting includes automatic updates for core and plugins, Visual Inspector for pre-update comparison testing, and infrastructure built for agencies running sites that cannot afford to go down. Move your sites without the headache: our team handles the migration.

Learn more about our WordPress hosting options: