WordPress 7.0: Everything That’s Changing (And How to Get Ready Before April)

If you’ve been running WordPress sites for any length of time, you’ve probably gotten used to a certain rhythm—a new version drops, you update, maybe a plugin breaks, life goes on. But WordPress 7.0? This one’s different. It’s not a polish-and-patch release. It’s the kind of update that makes you rethink how you use the platform entirely.

After a turbulent 2025 that saw legal battles, paused contributions, and only one major release, the WordPress project has been quietly stacking features like a coiled spring. Now that spring is about to snap forward. WordPress 7.0 lands on April 9, 2026, and it brings real-time collaboration, a built-in AI infrastructure layer, a refreshed admin dashboard, and enough under-the-hood changes to keep developers busy for months .

Here’s the thing—whether you’re a solo blogger, an agency juggling thirty client sites, or a developer building custom themes, this release touches your workflow. So let’s break down what’s actually coming, what it means for you, and how to avoid the “I should’ve tested that on staging first” panic.

Why WordPress 7.0 Matters More Than a Typical Version Bump

A little context goes a long way here. The original 2025 roadmap called for three major releases. That didn’t happen. The WP Engine lawsuit drained energy and resources from core development, and Automattic temporarily paused its WordPress contributions. The result? One major release in all of 2025—WordPress 6.8 in April—followed by WordPress 6.9 “Gene” in December, which served mostly as a stabilizer to clear technical debt .

So WordPress 7.0 isn’t just carrying one release’s worth of ambition. It’s carrying over a year’s worth of accumulated features, architectural decisions, and pent-up momentum. This is the official beginning of Phase 3 of the Gutenberg project—the collaboration phase—and it represents the biggest structural shift since the block editor itself landed back in 2018 .

You know what it reminds me of? It’s like when a city finally finishes a highway expansion after years of orange cones and detours. The construction was frustrating, sure. But the road on the other side is genuinely better.

Real-Time Collaboration: Google Docs, But Inside Your Dashboard

For years, WordPress has been a solo instrument. One person edits a post at a time. If someone else opens the same post, they get that slightly passive-aggressive “someone is already editing this” warning. Want to collaborate? You end up in Google Docs drafting content, then copy-pasting it into WordPress. It’s clunky. Everyone knows it.

WordPress 7.0 changes the game. Multiple users can now edit the same post simultaneously, with live cursors showing where each person is working. When a collaborator finishes typing in a block and pauses—or moves to another block—their changes push to all connected users instantly, no page reload required. A brief highlight animation shows which block just updated .

Behind the scenes, WordPress offers three technical approaches to make this happen. HTTP Long Polling with Autosave is the most compatible option and works on virtually any hosting setup, including budget shared hosting. WebRTC Peer-to-Peer creates browser-to-browser connections that bypass the server entirely—fast and efficient. And WebSockets deliver the fastest experience but require hosting that supports persistent connections .

Here’s a side note worth flagging: your hosting matters more than ever with this feature. Budget shared hosting will technically work, but the experience might feel sluggish compared to a host that supports WebSockets. WordPress VIP has already tested a WebSocket-based implementation with around 45 customers, proving the tech works at scale . If real-time collaboration is central to your workflow, this might be the nudge to evaluate your hosting setup.

A practical reality check: Gutenberg Lead Developer Riad Benguella has noted that the real-time features may ship as “experimental” or limited to specific environments, since many PHP hosting providers still don’t support WebSocket servers . It’s coming—but it might not be flawless everywhere on day one.

The Notes System That Replaces Your Slack-and-Screenshot Feedback Loop

WordPress 6.9 introduced “Notes”—a basic commenting system inside the editor. It was a start. WordPress 7.0 turns it into something genuinely useful for teams .

Fragment Notes let you select specific text within a paragraph and leave a comment on just that selection. Not the whole block—just the sentence or phrase you’re talking about. If you’ve ever used Google Docs’ commenting, this will feel immediately familiar.

@Mentions work exactly how you’d expect. Tag a teammate in a note, and they get notified via email or their dashboard. No more switching to Slack to say “hey, check paragraph three” .

Suggestions Mode is where it gets really interesting. Reviewers can propose specific edits tied to content within a block, and authors accept or reject them with a click—just like Google Docs’ “Suggesting” mode .

There’s also Multi-Block Notes for leaving feedback that spans entire sections, and a new Dashboard Widget showing recent notes across your site. For agencies, this is quietly massive. The entire review-edit-publish workflow can happen inside WordPress itself, which means fewer tools, fewer handoffs, and fewer places for feedback to get lost .

AI Infrastructure: The Abilities API and What It Actually Does

Let’s be clear about something: WordPress 7.0 is not adding an AI writing assistant to your editor. It’s doing something arguably more important—it’s building the plumbing that lets AI work with WordPress in a standardized, secure way .

The centerpiece is the Abilities API. Think of it as a universal menu that tells any system—including AI—exactly what your WordPress site can do. Developers register capabilities once using a simple wp_register_ability() function, and that single registration works across PHP, REST API, JavaScript, and external tools .

Sitting on top of that is the MCP Adapter (Model Context Protocol). This takes the abilities your site exposes and makes them accessible to AI tools like Claude, ChatGPT, Cursor, and others. An AI assistant can connect to your WordPress site, discover its capabilities, and perform tasks—like drafting a report of all WooCommerce sales or summarizing form submissions—while respecting your site’s permission system .

Then there’s the WP AI Client, a provider-agnostic abstraction layer. You build one AI integration against it, and it works with multiple AI providers. No vendor lock-in, no choosing between OpenAI versus Anthropic versus Google .

Why should you care? Because the ecosystem is about to get interesting. Your SEO plugin could auto-analyze content quality. Your e-commerce plugin could generate sales reports from a natural language prompt. Your forms plugin could summarize hundreds of submissions into actionable insights. These aren’t theoretical—they’re the exact use cases this infrastructure enables .

For developers, honestly, this is a first-mover opportunity. Register your plugin’s abilities now, and your product becomes “AI-ready” on launch day.

The Admin Redesign WordPress Hasn’t Had Since 2013

Here’s a fun fact: the WordPress admin dashboard has looked essentially the same since WordPress 3.8 dropped in December 2013. That’s over twelve years of the same visual language. It was overdue .

WordPress 7.0 begins modernizing the admin through a system called DataViews. Instead of the traditional WP List Tables (those old-school database-style tables for posts, pages, and media), DataViews introduces a flexible, app-like interface. You can filter, group, and sort content without page refreshes. Switch between table, grid, or list views. Save persistent views that remember your preferences .

It feels fast, fluid, and—this is the key part—much more like a modern SaaS application than a 2005-era database screen.

The refresh also includes a unified design system rolling out across the admin: consistent typography, design tokens for colors and spacing, refreshed admin tables, modernized dashboard widgets, and standardized form elements .

There’s also a dedicated Fonts screen at Appearance > Fonts, where you can manage installed fonts and upload new ones from a single location .

One thing worth mentioning—and this trips up a lot of people—any plugin that modifies the Posts, Pages, or Media list views has a higher-than-usual chance of compatibility issues with this release. The DataViews overhaul is deep. Test early .

New Blocks and Editor Upgrades Worth Knowing About

WordPress 7.0 ships several new native blocks that reduce your dependency on third-party plugins:

The Tabs Block is already merged and lets you create horizontal or vertical tabbed interfaces natively. No more shortcodes or plugin gymnastics for something this basic .

A Breadcrumbs Block is progressing toward stability, giving you breadcrumb navigation (and an SEO benefit) without needing a full-featured SEO plugin just for that one feature .

Blocks still in progress include a Slider Block for carousels, a Dialog Block for modal popups, a Playlist Block for podcasters and musicians, an Icon Block, and a Table of Contents Block that auto-generates from your heading structure . Not all of these are guaranteed to land in core by April—some may stay in the Gutenberg plugin—but they signal where things are heading.

The Pullquote Block also makes its return after being removed previously, which is welcome news for content-heavy sites .

Beyond new blocks, the editor itself gets several meaningful upgrades. Heading levels (H1–H6) are now proper Block Variations, meaning you can insert “Heading 2” directly from the block inserter with its own icon and default attributes . There’s also per-block custom CSS—individual block instances can have their own CSS through an “Additional CSS” box in the sidebar . And the Command Palette now works globally across the admin, not just inside the editor .

Responsive Editing Without Touching CSS

This one’s been a long time coming. WordPress 7.0 adds block visibility controls based on screen size. You can show or hide specific blocks on mobile, tablet, or desktop—directly from the editor, no custom CSS or child themes required .

It’s the kind of feature many site owners currently pay for through premium page builders or visibility plugins, and now it’s in core. For agencies that used to manage responsive content differences with CSS hacks or third-party tools, this simplifies things considerably .

Future releases are expected to build on this with responsive style editing (changing styles per breakpoint) and customizable breakpoints . But even the foundation shipping in 7.0 is a meaningful step forward.

Technical Shifts: PHP Requirements, Editor Iframing, and React 19

If you maintain sites or build plugins and themes, pay close attention here.

PHP 7.2 and 7.3 support is officially dropped. The minimum supported PHP version rises to 7.4.0, with PHP 8.3 recommended for best performance. If your site runs PHP 7.2 or 7.3, it’ll stay on the WordPress 6.9 branch—you’ll get security updates, but no new features until you upgrade PHP . Usage of those older versions has dropped below 4% of monitored WordPress installations, so the project felt comfortable making this move .

On the database side, MySQL 8.0+ or MariaDB 10.6+ is now required .

The post editor will now consistently load inside an iframe, regardless of block API version. This creates a sandboxed environment where site styles don’t leak into the editor (and vice versa), making WYSIWYG significantly more accurate. The flip side? Blocks that rely on global document access or assume they share the DOM with the admin page will break. WordPress has published a migration guide, and developers should review it now .

WordPress 7.0 also upgrades to React 19, bringing performance improvements and new features to the block editor’s underlying framework .

And one more thing that caught my eye: default link styles have been removed from core. If your theme relied on WordPress to provide base link styling, your links may appear unstyled after the update. Theme developers need to handle link styles themselves now .

No New Default Theme—And That’s Intentional

Breaking with tradition, WordPress 7.0 won’t ship with a “Twenty Twenty-Six” theme. The project is moving away from the one-new-theme-per-version model. Instead, the focus is on making existing block themes like Twenty Twenty-Five more powerful through the Site Editor and Phase 3 tools .

The message is clear: with the current generation of block themes and the Site Editor, you don’t need a brand-new theme every year—you can evolve what you already have.

On a related note, WordPress.org now permits AI-generated images in themes submitted to the theme directory. For theme developers, this lowers production costs; for theme buyers, it means more diverse visual designs across the marketplace .

How to Prepare Your Site Before April 9

The testing window between Beta 1 (February 19) and launch (April 9) is roughly seven weeks. That sounds like a lot until you factor in client work, plugin vendor response times, and the occasional “everything is on fire” Monday. Start now.

Check your PHP version first. Log into your hosting control panel and confirm you’re on at least PHP 7.4. Ideally, bump to PHP 8.2 or 8.3. Don’t wait until April—do this now and test thoroughly .

Audit your admin-facing plugins. Anything that modifies the Posts, Pages, or Media list views is the most likely to conflict with the DataViews overhaul. Custom admin CSS may also break or look out of place against the new design system .

Set up a staging environment. Never test a major update on your live site. Clone your production setup, upgrade the staging copy to the 7.0 beta, and run through your critical functionality .

Try out the Notes feature with your team. Spin up a sandbox site and experiment with inline commenting. See how it could replace your current feedback loops before you commit to it in production .

Watch for the Field Guide. The official Field Guide publishes on March 19 alongside Release Candidate 1. Read the Dev Notes for deprecated functions and breaking changes .

If you’re a developer, register your plugin’s abilities with the Abilities API now. Test your blocks in the iframed editor. Audit your admin CSS. Run your blocks through co-editing sessions to catch state conflicts. And if your theme relied on core’s default link styling, add your own .

What Comes After 7.0

WordPress is returning to a three-release cadence in 2026 after the 2025 slowdown. WordPress 7.1 is tentatively scheduled for August 19, 2026, expected to focus on media workflows and granular permissions—timed with WordCamp US. WordPress 7.2 is planned for December 8–10, 2026, bringing collaboration refinements and the groundwork for Phase 4: multilingual support .

That last bit—multilingual support baked into core—has been on the WordPress wishlist for… well, basically forever. If Phase 3 is any indication, it’ll be worth the wait.

Here’s What I’m Actually Doing

Look, I’ve been through enough major WordPress releases to know the drill. Usually, it’s a quick backup, a click of the “Update” button, and back to work. But honestly? WordPress 7.0 feels different.

This isn’t just a fresh coat of paint. The shift to DataViews and the new admin architecture is the kind of deep structural change that breaks things—mostly the old, dusty plugins we all forgot we were using. The collaboration features are genuinely exciting (I’m personally thrilled to stop copy-pasting from Google Docs), but they add a layer of complexity to the hosting environment we haven’t had to worry about before.

Here is my plan for wplukic.com and my client sites come April:

1. I am not updating on day one. I’ll let the early adopters find the edge cases with the new React 19 implementation.
2. Staging is non-negotiable. I’m spinning up a clone specifically to test the new admin interfaces. If you have custom dashboards or heavy backend customizations, this is where you’ll feel the pain.
3. I’m auditing my “Zombie Plugins.” Any plugin that hasn’t been updated in six months is getting replaced before April. The compatibility risk is just too high this time.

WordPress is finally growing up into the application platform we always knew it could be. It’s going to be powerful, but the transition period might be a little bumpy. Grab a coffee, fire up a staging site, and let’s get ready.