WordPress 7.0 is set to launch on April 9, 2026, at WordCamp Asia, and it’s shaping up to be the most significant WordPress release in over a decade. Built-in AI infrastructure, real-time collaboration, a refreshed admin dashboard, new blocks, and updated server requirements. This update touches practically everything.
Whether you’re a site owner wondering how this will affect your website, or a theme/plugin developer planning your next move, this guide breaks down every major change in WordPress 7.0, why it matters, and how to prepare.
Why Is WordPress 7.0 Such a Big Deal?
A bit of context first. The original 2025 roadmap planned three major releases, but that didn’t happen. The ongoing WP Engine lawsuit diverted significant energy and resources from core development, and Automattic paused its WordPress contributions for a period. As a result, 2025 delivered only one major release, WordPress 6.8 in April, followed by WordPress 6.9 « Gene » in December as a stabilizing foundation.
That means WordPress 7.0 carries the accumulated weight of features that have been building up for over a year. This isn’t a typical point release; it’s a generational leap.
Release Timeline
Here’s the official schedule:
- Beta 1: February 19, 2026
- Release Candidate 1: March 19, 2026
- Official Release: April 9, 2026 (WordCamp Asia Contributor Day)
The rollout includes four beta versions and at least one release candidate, with stabilization phases throughout March. If you want to test early, you can try Beta 1 on a staging site starting mid-February.
AI Integration: WordPress Meets Artificial Intelligence
This is the headline feature of WordPress 7.0 and arguably the biggest architectural shift since Gutenberg. WordPress is introducing a complete AI infrastructure layer built on four interconnected components.
1. The Abilities API
First introduced in WordPress 6.9, the Abilities API is a standardized registry that lets plugins and themes describe what they can do in a machine-readable format. Instead of every plugin building its own custom REST endpoints, developers register capabilities once using a simple wp_register_ability() function, and that single registration works across PHP, REST API, JavaScript, and external tools.
Think of it as a universal menu that tells any system, including AI, exactly what your WordPress site can do.
2. The MCP Adapter
The MCP (Model Context Protocol) Adapter takes the abilities registered through the API and makes them accessible to AI tools like Claude Desktop, Claude Code, Cursor, and VS Code.
In practical terms, an AI assistant can connect to your WordPress site, discover its capabilities, and perform tasks, like drafting a report of all sales on your WooCommerce store or summarizing form submissions from the past month, while respecting your site’s permission system. Every action goes through proper authentication and capability checks, so you stay in control.
3. WP AI Client
The WP AI Client (v0.1.0) is a provider-agnostic abstraction layer. Plugin and theme developers build one AI integration against the WP AI Client, and it works with multiple AI providers, no vendor lock-in, no choosing between OpenAI vs. Anthropic vs. others.
4. PHP AI SDK and Experiments Plugin
Rounding out the toolkit, the PHP AI SDK gives developers a native PHP interface for AI interactions, while the Experiments Plugin serves as a testing ground where the community can try new AI features before they land in core.
Why This Matters for Site Owners
The AI layer won’t write your blog posts on its own. WordPress is deliberately playing it safe by focusing on infrastructure first. But the practical benefits are coming fast. Your SEO plugin could auto-analyze content quality and suggest improvements. Your e-commerce plugin could generate sales reports on demand through a simple AI prompt. Your forms plugin could summarize hundreds of submissions into actionable insights. These aren’t hypotheticals; they’re exactly the kind of integrations this infrastructure enables.
Why This Matters for Developers
This is a first-mover opportunity. Register your plugin’s abilities now using the Abilities API, and your product will be « AI-ready » on launch day. One registration replaces maintaining parallel REST endpoints, custom block interfaces, and separate API integrations, with less code and less maintenance. The MCP Adapter also opens a new distribution channel: your plugin’s functionality becomes accessible from AI-powered development tools like Claude Code and Cursor, putting it in front of developers and power users who may never browse the WordPress plugin directory.
Real-Time Collaboration: Google Docs-Style Editing
WordPress 7.0 brings true real-time collaboration to the content editor. Multiple team members can edit the same post simultaneously, with live cursors and instant updates, similar to what you’d experience in Google Docs.
Behind the scenes, WordPress offers three technical approaches to make this work:
- HTTP Long Polling with Autosave: The most compatible option. Works on virtually any WordPress installation, including budget shared hosting.
- WebRTC Peer-to-Peer: Browser-to-browser connections that bypass the server entirely. Fast and efficient.
- WebSockets: The fastest option, but requires hosting support for persistent connections. WordPress VIP has already tested this successfully with 45 customers.
Enhanced Notes System
Building on the Notes feature introduced in WordPress 6.9, version 7.0 adds upgrades that make editorial collaboration much more practical:
- Fragment Notes: Comment on specific text within a block, not just the block itself
- @Mentions: Tag team members directly for notifications
- Digest Notifications: Get consolidated activity summaries instead of endless individual alerts
- Multi-Block Notes: Span comments across entire sections
- Suggestions Mode: Propose edits without changing the original (like Google Docs « Suggesting » mode)
Why This Matters for Site Owners
If you run a multi-author blog, an agency, or any site with a content team, this could save you real money. No more juggling Google Docs or Notion for editorial reviews, then copy-pasting into WordPress. The entire review-edit-publish workflow can happen inside WordPress itself. New team members get onboarded faster, too, with one tool instead of three.
A word of caution: the collaboration experience depends on your hosting. Budget shared hosting may deliver a degraded experience since it typically doesn’t support WebSockets or persistent connections. If real-time collaboration is important to your workflow, it might be worth upgrading to a host that supports WebSocket connections.
Why This Matters for Developers
If your plugin or theme adds custom blocks with complex state or custom save logic, you need to test them against real-time co-editing. Blocks that assume a single active editor may conflict with simultaneous editing sessions. This should be a QA priority before WordPress 7.0 launches.
Admin Interface Redesign: The First Refresh in 12 Years
The WordPress admin dashboard is getting its first major visual update since WordPress 3.8 in December 2013. That’s over twelve years with essentially the same look.
This is an evolution, not a revolution; you’ll still recognize your dashboard. Here’s what’s changing:
- DataViews & DataForms: Modern UI components expanding across Posts, Pages, and form interfaces
- Unified Design System: Consistent typography, design tokens, and visual language throughout the admin
- Refreshed Tables and Widgets: Cleaner table layouts and modernized widget designs
- Standardized Form Elements: A cohesive look for all form inputs
Why This Matters for Site Owners
A cleaner admin means less visual friction in your daily workflow. Settings are easier to find, screens look consistent, and if you hand off site management to a client or new team member, they’ll find the admin more intuitive and less intimidating. It’s the kind of improvement you notice most when you don’t have to think about it.
Why This Matters for Developers
This one requires action. If your plugin or theme adds custom admin screens, custom tables, or custom form elements, you need to audit them against the new design system. Custom admin CSS may break or look out of place. Plugins using DataViews should be tested for compatibility. Review your admin-side code now, don’t wait for user complaints after the update.
New Blocks and Editor Improvements
WordPress 7.0 brings several meaningful changes to the block editor.
Always-Iframed Post Editor
The post editor will now consistently load inside an iframe, regardless of block API version. Previously, blocks using API v2 could trigger a non-iframe editor, creating inconsistent behavior.
For site owners: Your editing experience will be more consistent and less prone to visual glitches caused by plugin or theme CSS leaking into the editor.
For developers: This is critical. 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; review it now and update any blocks that directly manipulate the global document.
New and Updated Blocks
- Tabs Block: Brand new. Create tabbed content sections natively, no more plugin or shortcode dependency for something this basic.
- Responsive Grid Block: Better control over grid-based layouts across screen sizes.
- Breadcrumbs Block: Progressing toward stability. Once complete, this gives you breadcrumb navigation and an SEO benefit without needing Yoast or RankMath just for this feature.
- Pullquote Block: Reinstated after being removed. Content creators who relied on it can use it again.
- Navigation Block: Continued improvements and better overlay handling.
- Image Improvements: Aspect ratio controls now work at all alignment settings. Gallery captions get a background blur effect.
Viewport-Based Block Visibility
Building on block visibility from WordPress 6.9, version 7.0 adds controls for hiding blocks based on viewport size. Show or hide specific content on mobile vs. desktop -> no custom CSS, no third-party visibility plugins. This is a feature many site owners currently pay for through premium plugins, and now it’s in core for free.
For developers: If your theme includes its own responsive visibility system, it now overlaps with core functionality. Consider whether to deprecate your implementation or differentiate it.
Per-Block Custom CSS
Individual block instances can now have their own custom CSS through an « Additional CSS » box in the block sidebar. A .has-custom-css class automatically applies to styled blocks.
For developers: Test for CSS specificity conflicts with your theme styles. The new .has-custom-css class may interact with your existing selectors in unexpected ways.
Enhanced Command Palette
The Command Palette now works globally across the admin, not just inside the editor.
For developers: You can register your own commands using the new useCommands hook, a great way to surface key plugin features to power users who prefer keyboard shortcuts over menus.
Changes That Affect Themes Specifically
Two changes deserve special attention from WordPress theme developers and theme users:
Default Link Styles Removed from Core
WordPress 7.0 removes default link styles from core. If your theme relied on WordPress to provide base link styling, your links may appear unstyled after the update. Theme developers must now handle link styles themselves. If you’re a site owner, check that your theme developer has addressed this in a compatibility update before upgrading.
AI-Generated Images Permitted in Theme Directory
WordPress.org now allows AI-generated images in themes submitted to the theme directory. For theme developers, this lowers production costs, and you can use AI-generated photography and illustrations instead of commissioning or licensing stock images. For theme buyers, it means you’ll start seeing more diverse and unique visual designs across the theme marketplace.
Updated Technical Requirements
WordPress 7.0 comes with updated server requirements. Check these before updating.
PHP Version
| Status | Version |
|---|---|
| Minimum Supported | PHP 7.4.0 |
| Recommended | PHP 8.3 |
| Fully Compatible | PHP 8.0 – 8.3 |
| Beta Compatible | PHP 8.4 – 8.5 |
| Dropped | PHP 7.2 and 7.3 |
If your site is running PHP 7.2 or 7.3, you must upgrade before updating to WordPress 7.0. Contact your hosting provider to check your current PHP version; most hosts make this a one-click change in your control panel. If your host doesn’t support at least PHP 7.4, that’s a strong signal your hosting is severely outdated, and it may be time to switch providers entirely.
Database
MySQL 8.0+ or MariaDB 10.6+ is required.
How to Prepare Your Site for WordPress 7.0
For Site Owners
- Check your PHP version. Log in to your hosting control panel and verify you’re on PHP 7.4 or higher. Upgrade now, don’t wait until release day.
- Back up everything. Full database and file backups before any major update. Use a reliable backup plugin or your hosting provider’s backup feature.
- Set up a staging environment. Never test a major update on your live site. Create a staging copy and run the beta there first.
- Audit your plugins and theme. Check with developers for WordPress 7.0 compatibility statements. Pay special attention to plugins that modify the admin interface.
- Test your collaboration hosting. If real-time editing matters to your team, verify your host supports WebSocket connections for the best experience.
- Check your link styling. After updating on staging, make sure your links still display correctly; the default link styles are no longer provided by core.
For Theme and Plugin Developers
- Register abilities now. Use the Abilities API so your product is AI-agent compatible on day one.
- Test blocks in the iframed editor. Any block relying on global
documentaccess needs to be updated. Review the migration guide. - Audit admin CSS. Test your custom admin screens and styles against the new design system.
- Test real-time collaboration. Run your blocks through co-editing sessions to catch state conflicts.
- Handle link styles. If your theme relied on the core’s default link styling, add your own.
- Check CSS specificity. Test for conflicts with the new
.has-custom-cssclass and per-block custom CSS. - Explore the Command Palette. Register commands
useCommandsto give your users quick keyboard access to key features.
Looking Ahead: WordPress 7.1 and 7.2
WordPress 7.0 is just the beginning of the 2026 release cycle:
- WordPress 7.1 (August 19, 2026). Expected to focus on media workflows and granular permissions, timed with WordCamp US
- WordPress 7.2 (December 8-10, 2026). Collaboration refinements and the groundwork for Phase 4: multilingual support
The Bottom Line
WordPress 7.0 is not just another version bump. It’s a foundational shift: AI infrastructure, real-time collaboration, a modern admin experience, and meaningful new blocks, all while keeping the WordPress workflow you already know.
The best way to prepare? Start testing the beta on a staging environment, make sure your hosting meets the new requirements, and keep your themes and plugins up to date. If you’re using a ThemeREX theme, rest assured that we’re already working on full WordPress 7.0 compatibility, so you’ll be ready on day one.
Have questions about how WordPress 7.0 will affect your site? Drop a comment below or reach out to our support team. We’re here to help you make the transition as smooth as possible.
