WordPress 7.0 ships on April 9, 2026, and it is the most significant release since the block editor arrived in WordPress 5.0 back in 2018. That is not an opinion. It is a structural statement about what this release actually does.
WordPress 7.0 marks the official start of Phase 3 of the Gutenberg project. If Phase 1 was the block editor and Phase 2 was full site editing, Phase 3 is collaboration. The platform is moving from a tool where one person edits to a system where teams work together in real time, with AI integration baked into the foundation and a completely refreshed admin interface that should have been updated years ago.
At KrishaWeb, we have been building on WordPress since 2007 and have been actively tracking 7.0 through its beta and release candidate cycle. We attended WordCamp Asia 2026 in Mumbai, where WordPress 7.0 shipped live on Contributor Day. This guide covers every major change, what it means in practice, and what you need to do before and after updating.
WordPress 7.0 release date: April 9, 2026. Released live at WordCamp Asia, Jio World Convention Centre, Mumbai.
Test before updating; DataViews API changes affect some plugins
2026 release cadence
7.0 (April), 7.1 (August), 7.2 (December)
Significant since
WordPress 5.0 — the block editor release in 2018
Feature 1: Real-Time Collaborative Editing
This is the headline feature of WordPress 7.0 and the one that changes the most about how editorial teams work inside the platform.
Multiple users can now edit the same post or page simultaneously. Changes sync in real time. Conflicts are resolved automatically using CRDT (Conflict-free Replicated Data Type) technology, the same underlying mechanism that tools like Figma and Notion use. The platform stores sync data persistently using a dedicated internal post type called wp_sync_storage, so offline edits get merged when users reconnect.
The default sync provider uses HTTP polling, which means it works on every WordPress hosting environment, including shared hosting; no special server configuration is required. For environments that support WebSockets, faster sync is available. Developers can also plug in custom transport layers via the sync providers filter.
At launch, real-time collaboration is limited to two simultaneous collaborators per post. This limit is configurable via wp-config.php constants, and hosts can add their own provider or adjust the defaults. One important constraint: real-time collaboration is disabled for posts that have classic meta boxes present. If your site relies on classic meta boxes, those posts will not support collaborative editing until the meta boxes are migrated to registered post meta with show_in_rest enabled.
Notes, suggestions, and mentions
Built on the Notes system introduced in 6.9, WordPress 7.0 expands this into a full editorial feedback suite. Editors can leave notes on specific blocks or text fragments. A suggestion mode lets reviewers propose changes without directly editing the content. @mentions trigger email and dashboard notifications so the right person sees feedback without checking back manually.
If your editorial team currently cycles through Google Docs for drafts, comment threads for feedback, and then a final paste into WordPress, this is the feature that collapses that workflow into one place.
Revision history gets a visual overhaul
Revisions now use color-coded block overlays: green for added blocks, red for removed blocks, and yellow for modified blocks. A timeline slider lets editors scrub through version history in a read-only review mode. For businesses in compliance-heavy industries where content audit trails have legal significance, this built-in visual history is a material improvement over the plain-text revision diffs in older versions.
Feature 2: The WP AI Client — A Provider-Agnostic AI Layer in Core
This is the feature we have been watching most closely at KrishaWeb, and it is important to understand what it actually is before getting excited or dismissive about it.
WordPress 7.0 does not ship with a specific AI tool. It ships with infrastructure: a standardized AI integration layer called the WP AI Client, built on the php-ai-client package, that allows any plugin or theme to connect to AI services through a consistent, governed interface. No single vendor is locked in. Administrators manage everything from a single screen at Settings > Connectors.
OpenAI, Google AI, and Anthropic ship as default provider plugins. Additional providers can be registered through the connections-wp-admin-init hook. The API keys, the provider choice, and which capabilities to activate and where: all of that stays under the administrator’s control.
Before WordPress 7.0, AI in WordPress meant installing a plugin that had its own API key management, its own UI, its own integration approach, and its own data handling. Multiply that by every AI feature a site needed, and you had a fragmented, hard-to-govern stack.
The AI Connectors framework gives organizations a single layer to manage. You choose the provider. You control the API keys. You decide which AI capabilities are active and on which parts of the site. Plugins built on this infrastructure inherit that governance automatically.
For marketing and content teams, immediate practical applications include generating SEO meta descriptions, producing alt text for images at scale, and AI-assisted drafting directly inside the editor. For developers, the more interesting opportunity is building custom workflows on top of a stable, versioned API rather than a plugin-specific integration that might change with the next update.
What this is not
The AI layer in WordPress 7.0 is deliberately early-stage infrastructure. It does not ship with a built-in writing assistant or an AI autopublishing feature. It is the foundation that makes those things possible and governed, not the things themselves. The roadmap it enables, personalized content delivery, intelligent editorial assistance, and automated accessibility improvements are significantly larger than what ships on April 9.
Feature 3: The Admin Refresh — First Major UI Update Since 2013
WordPress 3.8 shipped in December 2013 and introduced the last significant visual update to the wp-admin. That was 12 years ago. WordPress 7.0 changes that.
The admin interface gets a visual and functional overhaul in 7.0, and two specific changes are going to affect every WordPress user every day.
Command Palette now lives across the entire admin
Previously, the Command Palette (the keyboard-driven search and action bar you trigger with Cmd+K or Ctrl+K) only worked inside the block editor. In WordPress 7.0, it lives in the Omnibar across the entire admin. Press Cmd+K from any screen, including settings pages, the media library, the plugins list, and jump directly to a draft, a specific post, a settings panel, or any admin screen.
For developers and site managers who work across large WordPress installations with hundreds of posts, this is the kind of keyboard-driven navigation that makes wp-admin feel like a modern application rather than a 2013 dashboard.
DataViews replaces legacy WP List Tables
The WP_List_Table class has been powering the Posts, Pages, and Media list views since the early days of WordPress. DataViews replaces it progressively, starting with Posts, Pages, and Media in 7.0. The new interface is filterable, sortable, and app-like. It includes a new activity layout and lays the groundwork for registering third-party content types in future releases.
For most users, this is a welcome modernization. For developers, there is an important compatibility note: the groupByField string property in the DataViews API has been replaced by a groupBy object that accepts field, direction, and showLabel properties. Any plugin that customizes the Posts, Pages, or Media list views needs to be tested against this change before updating production.
Compatibility check required: Plugins that hook into WP List Tables for Posts, Pages, or Media will need testing before updating to WordPress 7.0.
Feature 4: New Blocks and Editor Improvements
WordPress 7.0 ships a set of editor improvements that matter for both content teams and developers. Here is what is new.
New blocks: Breadcrumbs and Icons
The Breadcrumbs block auto-generates navigation paths from the current URL structure. It supports customization through two PHP filters: block_core_breadcrumbs_items for modifying the breadcrumb items and block_core_breadcrumbs_post_type_settings for post-type-level configuration.
The Icons block gives editors access to a REST-accessible icon library available at /wp/v2/icons. Themes and plugins can extend this library. It is a cleaner approach than the fragmented icon plugin ecosystem that has existed for years.
Viewport-based block visibility
Blocks can now be shown or hidden by device type through a stable core feature. After several releases in experimental status, this lands as a first-class editor capability in 7.0. For eCommerce teams building device-specific calls to action and for editorial teams that want different layouts on mobile and desktop, this removes the need for separate templates or third-party visibility plugins.
Per-instance custom CSS
Individual block instances can now receive custom CSS through the Advanced panel in the block editor. This is a significant addition for theme developers and site builders who need precise control without dropping into child theme CSS files for minor adjustments. Each block instance gets its own scoped styles, which keeps the global stylesheet clean.
Cover block video backgrounds, responsive Grid, Gallery lightbox
The Cover block gains video embed backgrounds in 7.0, removing the need for custom code or third-party blocks to achieve this common design pattern. The Grid block becomes responsive by default. The Gallery block gets lightbox navigation built in. The Navigation block supports customizable overlays with mobile-specific breakpoints.
Client-side media processing
Image resizing and compression now happen in the browser before upload, using native browser capabilities. The processor supports AVIF, WebP, and MozJPEG output formats. The practical effect is that images are optimized before they hit the server, cutting upload times and reducing the load on hosting infrastructure. For teams uploading large volumes of images, such as photography sites or product catalog managers, this is a meaningful workflow improvement.
Font Library available for all themes
The Font Library, which manages installed fonts, is now enabled for all themes in WordPress 7.0. Previously, it required block theme support. Site editors can now browse, install, and organize fonts regardless of which theme is active, which removes a long-standing inconsistency in the editor experience.
What Developers Need to Do Before and After Updating
WordPress 7.0 has genuine breaking changes. Here is the complete checklist, written from practical experience of building on WordPress for 17+ years.
1. Check your PHP version first
WordPress 7.0 drops support for PHP 7.2 and 7.3. The minimum is now PHP 7.4. If your server is running PHP 7.2 or 7.3, the WordPress 7.0 update will not apply, and your site will remain on the 6.9 branch for security updates only.
PHP 8.3+ is the recommended version. WordPress 7.0 introduces beta support for PHP 8.5, which is particularly relevant for the DataViews interface performance. If you are managing client sites, audit PHP versions across all of them before the update rolls out.
Any plugin that adds classic meta boxes to a post editing screen will disable real-time collaboration for that post type. This is not a bug. It is a deliberate architectural constraint. Classic meta boxes are a legacy pattern that predates the block editor data layer and cannot be synchronized safely in real-time sessions.
If you want collaborative editing available on your posts, migrate those meta boxes to registered post meta with show_in_rest: true. If migration is not feasible before 7.0, collaboration simply will not be available for those post types, which is fine as a transitional state.
3. Test DataViews compatibility for custom admin plugins
If any of your installed plugins customize the Posts, Pages, or Media list views by hooking into WP_List_Table or modifying groupByField in the DataViews API, test those plugins in a staging environment before updating. The groupByField string has been replaced by a groupBy object. Plugins that do not account for this change will break on 7.0.
4. The Interactivity API gains watch()
WordPress 7.0 adds a watch() primitive to the Interactivity API. It allows subscribing to reactive state changes at the store level, independent of DOM updates. This is useful for analytics instrumentation, side-effect tracking, and client-side navigation monitoring. If you are building interactive blocks with the Interactivity API, this is worth adding to your development patterns.
5. Block API v3 is becoming the reference model
Blocks that rely on global document queries or .wp-admin selectors should begin migration planning now. The iframed editor enforcement, currently punted to WordPress 7.1, means any block that reaches outside its iframe context for DOM access will break in the next major release. The time to fix this is during 7.0, not under pressure at 7.1.
6. The always-iframed post editor lands in 7.1
It was originally planned for 7.0 but was deferred. The Gutenberg plugin will still iframe the post editor blocks in the meantime. If you are maintaining blocks that depend on parent document access, start the migration now. 7.1 is scheduled for August 2026, which gives roughly four months.
The 2026 WordPress Release Roadmap
WordPress is returning to a three-release annual cadence in 2026 after shipping two major releases in 2025. Each version is anchored to a flagship community event.
Version
Release Date
Event
Theme
WordPress 7.0
April 9, 2026
WordCamp Asia, Mumbai
Phase 3 — Collaboration kickoff, AI infrastructure
Collaboration expansion, early multilingual native support
WordPress 7.0 is the opening chapter of a year-long collaboration arc. The features shipping in April are foundations, not finished products. The roadmap through 7.1 and 7.2 builds on this base toward a platform where multilingual content, deeper AI workflows, and mature real-time collaboration are standard capabilities.
How to Update to WordPress 7.0 Safely
For simple sites with few plugins, updating to WordPress 7.0 is straightforward through the dashboard. For complex sites with custom themes, many plugins, or custom admin functionality, treat this like any major release: test first.
Back up the site completely, including the database and all files.
Update PHP to 7.4 minimum on your server. PHP 8.3+ is recommended.
Spin up a staging environment that mirrors your production site exactly.
Update WordPress to 7.0 on staging first.
Test all custom plugins and themes, paying specific attention to anything that hooks into WP List Tables, uses classic meta boxes, or has custom DataViews modifications.
Check collaborative editing on any post types you plan to use it for.
Run through the block editor and verify all custom blocks render correctly.
Review the Settings > Connectors screen to understand the new AI provider configuration.
Once staging passes, update production with maintenance mode enabled.
Monitor error logs for the first 48 hours post-update.
We have been working on WordPress development since 2008 and have shipped hundreds of production sites for clients across professional services, SaaS, eCommerce, and media. When a major release like 7.0 lands, our team has already been through the betas and release candidates. We know where the compatibility risks are and what the new capabilities make possible.
WordPress 7.0 compatibility audits
Before you update a complex WordPress installation to 7.0, we can audit your theme, plugins, and custom code for the specific compatibility risks this release introduces: DataViews API changes, classic meta box conflicts with collaborative editing, Block API v3 alignment, and PHP version requirements. We identify what needs to change before the update, not after something breaks.
Collaborative editing implementation
Real-time collaboration in WordPress 7.0 is not a setting you flip on. Getting it working cleanly on a site with custom post types, editorial workflows, and existing meta box dependencies requires deliberate migration work. Our team can plan and execute that migration so your editorial team benefits from co-editing without disrupting the workflows they depend on.
AI integration on the WP AI Client framework
The AI Connectors framework in WordPress 7.0 is the foundation for building AI-powered content workflows directly inside WordPress. We help clients define which AI capabilities make sense for their specific use case, configure the provider connections, and build the workflows on top of that infrastructure. Whether that is bulk meta description generation, AI-assisted content review, or automated alt-text processing, we scope and implement it against the core framework rather than fragile plugin-level integrations.
Custom block development for WordPress 7
The Block API v3 transition, the iframed editor coming in 7.1, and the expanded Interactivity API all change the development baseline for custom blocks. If you have custom blocks that were built against earlier API versions, we can audit them, migrate the ones that need updating, and build new blocks to the 7.0 standard from the ground up.
Managed WordPress 7.0 updates for client sites
If you manage multiple WordPress sites and need a structured update process for 7.0 across all of them, including pre-update audits, staging environment testing, PHP version upgrades, and post-update monitoring, we run that process. One point of contact. Documented results. No surprises.
WordPress 7.0 releases April 9, 2026—the most architecturally significant release since the block editor in 2018.
Phase 3 of Gutenberg is now live. WordPress is moving from a single-user editing tool to a collaborative publishing platform.
Real-time collaboration uses CRDT sync with HTTP polling by default, supporting all hosting environments. Two simultaneous collaborators per post at launch, configurable.
The WP AI Client is not an AI feature. It is the infrastructure layer that governs how all AI features connect to WordPress going forward.
DataViews replaces WP List Tables for Posts, Pages, and Media. The groupByField to groupBy API change is a breaking change for affected plugins.
PHP 7.4 is the new minimum. PHP 7.2 and 7.3 sites will not receive the 7.0 update.
Classic meta boxes disable real-time collaboration for the posts that have them. Migration to registered post meta with show_in_rest is required.
The iframed post editor was deferred to 7.1 (August 2026). Start Block API v3 migration now.• WordPress 7.1 and 7.2 follow in August and December 2026, deepening the collaboration and multilingual foundations laid by 7.0.
Conclusion
WordPress 7.0 is the beginning of something, not the completion of it. Real-time collaboration, the WP AI Client, and the refreshed admin are foundations. The features they enable across WordPress 7.1 and 7.2 and beyond are what this release is really about.
For the teams who update carefully, understand the compatibility requirements, and start building on the new infrastructure, WordPress 7.0 is an opportunity to get ahead of where the platform is going. For the teams who delay without a plan, the gap between their WordPress installations and the current state of the platform will widen quickly this year.
At KrishaWeb, we have been tracking this release through every beta cycle and contributed to it at WordCamp Asia 2026. If you want help planning your 7.0 update, building on the new features, or understanding what this release means for your specific WordPress setup, our team is ready to help.
WordPress 7.0 is released on April 9, 2026. It was launched live during Contributor Day at WordCamp Asia 2026 in Mumbai, India, making it the first major WordPress release to ship at a WordCamp.
What is the most important new feature in WordPress 7.0?
Real-time collaborative editing is the headline feature. Multiple users can now edit the same post simultaneously, with automatic conflict resolution using CRDT technology. For content teams, this removes the dependency on external tools like Google Docs for collaborative drafting. The WP AI Client is equally significant architecturally, as it establishes the governed infrastructure layer for all future AI integrations in the WordPress ecosystem.
Will my current plugins work with WordPress 7.0?
Most plugins will work without changes. The plugins most likely to need updates are those that hook into WP List Tables for Posts, Pages, or Media (because of the DataViews API change), those that add classic meta boxes to post types (because those will disable collaborative editing), and those that use the groupByField DataViews property (because it has been renamed to a groupBy object). Test on staging before updating production.
Do I need a special host to use real-time collaboration?
No. The default sync provider uses HTTP polling, which works on all hosting environments, including shared hosting. Faster WebSocket-based sync is available on hosts that support it, but it is not required for the feature to function.
What PHP version do I need for WordPress 7.0?
PHP 7.4 is the minimum. PHP 8.3+ is recommended by the core team for the best performance, particularly with the DataViews admin interface. WordPress 7.0 also introduces beta support for PHP 8.5. Sites running PHP 7.2 or 7.3 will not receive the 7.0 update and will remain on the 6.9 security maintenance branch.
Is WordPress 7.0 ready for production sites?
Yes, as of the final release on April 9, 2026. The release went through five beta cycles and two release candidates with over 134 updates and fixes in the RC cycle alone. As with any major release, test on staging first, particularly if your site has custom plugins or custom admin functionality. For sites with simple setups and well-maintained plugins, the update is straightforward.
Praful Patel
Lead – CMS Development
A Full-Stack Developer and Technical Project Manager with expertise spanning WordPress, WooCommerce, Headless WordPress, Next.js, React, and AI Automation, I deliver end-to-end web solutions that combine technical depth with practical, business-focused thinking.
KrishaLabs
KrishaStudio
KrishaStore
