WordPress 7.0: what is known, what is speculation, what to do now

A note up front: at the time of writing (April 2026), WordPress 7.0 is on the public roadmap but has not shipped. Specific feature lists, schema changes, and migration timelines circulating online, including in posts that brand themselves as the “complete guide”, are part forecast, part wishlist. Treat anything definitive about 7.0 as speculation until it lands in a release candidate published on the official Make WordPress blog and tagged in the core trac.

What we do know from public Make WordPress posts: Phase 3 work on collaborative editing is in progress, deeper integration between the Block Editor and AI providers is being discussed in core meetings, and the Site Editor templating model is being refined. What we do not know yet: which AI features (if any) will land in core versus stay as plugins, the final PHP minimum, or the exact ship date.

If you are planning work that will overlap with the 7.0 cycle, the honest move is to track make.wordpress.org/core and core trac tickets directly, rather than relying on third-party predictions. This post is one of those third-party predictions; read it accordingly.

Learn more about professional WordPress development at WPPoland.

#WordPress 7.0 release date

WordPress 7.0 RC1 was released on March 19, 2026. The final general availability release is scheduled for April 9, 2026. This follows the standard WordPress release cycle: Beta 1 in late February, followed by three beta releases, then release candidates, then the final stable version.

If you are planning an upgrade, the safest window is two to four weeks after the final release, once the initial patch cycle catches compatibility issues reported by early adopters.

#WordPress 7.0 roadmap

WordPress 7.0 sits at the end of Phase 3 of the Gutenberg project’s four-phase plan:

Phase 4 will bring native multilingual capabilities, which means WordPress will finally handle content translation at the core level instead of relying on plugins like WPML or Polylang. For agencies managing multilingual sites today, this is the feature to watch on the post-7.0 roadmap.

#AI in WordPress today, and where 7.0 might go

The honest version of “AI features in WordPress 7.0” starts with what already works in 6.x, because that is what real sites are running.

Available today, in production WordPress:

• Yoast and Rank Math both ship AI-assisted writing helpers (titles, meta descriptions, internal link suggestions) built on third-party model APIs.
• Jetpack AI Assistant offers in-editor generation, summarization, and translation. Quality varies by language and prompt.
• Standalone content generation plugins exist across a wide quality range; useful for drafts, dangerous when wired straight to publish without human review.
• Automattic and contributor teams are running Phase 3 experiments, including collaborative editing and editor-side AI calls, in the Gutenberg plugin ahead of any merge into core.

A pragmatic architecture for adding AI to a WordPress site today, which will likely survive whatever 7.0 ships:

• Expose a small REST API endpoint per provider (OpenAI, Anthropic, Google, or a self-hosted model). Keep provider-specific code behind one interface so swapping models is a config change, not a rewrite.
• Run anything slower than a few seconds through Action Scheduler, not a synchronous request. This is the same pattern WooCommerce uses; it scales.
• Store API keys as wp-config.php constants or via a managed secret store loaded at boot. Never put live keys in plugin options or .env files committed to a repo.
• Cache responses keyed on a hash of the prompt plus model version. AI calls are expensive and frequently repeated.

Failure modes worth designing against from day one:

• API key leakage through plugin auto-updates or backups that include wp-content dumps.
• Rate-limit failures during traffic spikes, which silently degrade the editor experience if there is no fallback.
• Hallucinated facts, citations, or product specs published without a human review step. The cost of one bad page in search is higher than the cost of any review workflow.

If 7.0 introduces a core abilities or connectors layer, the same boundaries apply: the API surface changes, the failure modes do not. For ethics and editorial framing, see the AI content ethics guide for publishers.

#What’s actually known about 7.0 right now

Strip out the marketing framing and the picture is narrower than most “complete guide” posts suggest.

Confirmed in public Make WordPress discussion:

• Phase 3 of the Gutenberg roadmap is the working theme, with collaboration and editorial workflow as the two areas that have seen the most public proposals and PRs.
• AI integration is being prototyped in the Gutenberg plugin and discussed in core meetings, but the boundary between “ships in core” and “stays a plugin” is unsettled.
• The Site Editor and pattern system are being iterated on, with refinements to template editing and block locking landing in 6.x point releases first.

Not confirmed, despite frequent claims:

• A specific shipping date for 7.0. Release schedules slip; treat any single date as a target, not a commitment.
• A definitive AI feature list in core. Several proposals exist, including provider-agnostic abilities and a connectors UI, but proposals are not releases.
• The PHP minimum bump and exact deprecations. These are decided late in the cycle.

For agencies and product teams shipping in 2026, the practical takeaway is simpler than any feature list: build on WordPress 6.x using forward-compatible patterns (block themes, theme.json, the REST API, Action Scheduler for background work) so that whatever 7.0 ultimately ships, the migration is incremental rather than a rewrite.

#What’s New in WordPress 7.0

WordPress 7.0 introduces dozens of new features and improvements across the entire platform. The most transformative changes center around three core areas: AI integration through the Abilities API, real-time collaborative editing, and a comprehensive admin interface redesign. These features work together to create a more intelligent, connected, and user-friendly WordPress experience.

#Key Feature Highlights

The Abilities API stands out as the most innovative addition, providing developers with standardized methods for integrating AI services directly into WordPress workflows. This API handles authentication, rate limiting, content sanitization, and context management - eliminating the need for each plugin developer to build these complex systems independently.

#Real-Time Collaboration Features

WordPress 7.0 finally delivers on the long-promised real-time collaboration capabilities, transforming the block editor into a true multi-user environment. This feature allows content teams to work together on posts and pages simultaneously, seeing each other’s changes in real-time without conflicts or version control issues.

#How Real-Time Collaboration Works

The collaboration system uses WebSocket connections to maintain persistent communication between users editing the same content. When a user makes changes, operational transformation algorithms ensure that concurrent edits merge directly without data loss. Each collaborator receives a unique color-coded cursor and presence indicator, making it easy to see who is working on which section.

Key collaboration features include:

• Presence Indicators: See who is currently viewing or editing content
• Colored Cursors: Track exactly where other users are working
• Inline Comments: Add contextual feedback without leaving the editor
• Activity Feed: View recent changes and who made them
• Conflict Resolution: Intelligent merging when users edit the same block

#Collaborative Workflows

The real-time collaboration feature integrates deeply with WordPress’s existing user role and permission system. Administrators can configure which user roles can collaborate, set up approval workflows, and define who has final publishing authority. This makes WordPress 7.0 suitable for enterprise editorial teams, newsrooms, and marketing departments that require structured content approval processes.

For agencies and developers, the collaboration system exposes JavaScript APIs that allow custom implementations. You can build specialized collaboration features tailored to specific client needs, such as custom notification systems, advanced approval workflows, or integration with external project management tools.

#AI Integration & Abilities API

The Abilities API represents WordPress’s formal entry into the AI-powered content management era. This comprehensive framework provides developers with tools to integrate AI services natively into WordPress, creating intelligent content workflows that were previously impossible or required complex third-party integrations.

#Understanding the Abilities API Architecture

The Abilities API operates on a provider-agnostic model, meaning it can work with any AI service that implements the standard interface. Whether you’re using OpenAI’s GPT models, Anthropic’s Claude, Google’s Gemini, or a self-hosted LLM, the API provides consistent methods for content generation, analysis, and modification.

Core components of the Abilities API include:

// Registering an AI ability
add_filter( 'wp_abilities_register', function( $abilities ) {
    $abilities['content_generation'] = [
        'provider' => 'openai',
        'capability' => 'edit_posts',
        'endpoint' => 'https://api.openai.com/v1/chat/completions',
        'rate_limit' => 100, // requests per hour
    ];
    return $abilities;
} );

// Using an AI ability in your code
$response = wp_abilities()->request( 'content_generation', [
    'prompt' => 'Generate a blog introduction about WordPress 7.0',
    'max_tokens' => 150,
    'temperature' => 0.7,
] );

#Built-In AI Features

WordPress 7.0 ships with several AI-powered features enabled by default when API keys are configured:

1. Smart Content Suggestions: AI analyzes your content and suggests improvements for readability, SEO, and engagement
2. Auto-Alt Text Generation: Automatically generates descriptive alt text for uploaded images
3. Content Summarization: Create excerpts and summaries with one click
4. Translation Assistance: AI-powered translation suggestions for multilingual sites
5. Code Generation: Generate custom CSS, template parts, and block patterns from natural language descriptions

#The New “Connectors” Page

One of the most practical additions in the current beta cycle is the dedicated “Connectors” screen. This allows users to instantly connect WordPress with popular AI services, ranging from OpenAI to Anthropic, without the need for multiple third-party plugins. This out-of-the-box solution ensures that LLM integration becomes an integral part of the core system configuration.

#Privacy and Security Considerations

The Abilities API includes robust privacy controls that ensure sensitive data isn’t sent to AI providers unintentionally. Site administrators can configure which content types can be processed by AI, set up data anonymization pipelines, and audit all AI requests through comprehensive logging. This is particularly important for businesses handling sensitive customer data or operating in regulated industries.

#Admin Interface Redesign

WordPress 7.0 introduces the most significant admin interface update since WordPress 3.0. The new design replaces the aging PHP-based admin screens with a modern React-based single-page application architecture, delivering faster load times, smoother interactions, and a more cohesive user experience.

#Design Philosophy

The redesign follows a “content-first” philosophy that minimizes distractions and puts the focus on creating and managing content. The classic WordPress admin menu has been reimagined as a collapsible sidebar that can be hidden to maximize screen real estate. Dashboard widgets are now modular blocks that users can rearrange, resize, or remove based on their preferences.

Key improvements include:

• Instant Navigation: No more full page reloads when switching between admin sections
• Contextual Toolbars: Relevant actions appear based on the current context
• Dark Mode: Native dark mode support for reduced eye strain
• Keyboard Shortcuts: Comprehensive keyboard navigation for power users
• Mobile-First: Fully responsive design that works directly on tablets and phones

It is worth noting that while the admin refresh is already substantial, it remains a work-in-progress during the current beta cycle. The core team still has room to refine details before the planned April release.

#Customization and Extensibility

Developers can extend the new admin interface using familiar WordPress hooks and filters, along with new React-based APIs. Custom admin pages can now be built as React components that integrate with the core interface. The REST API powers all admin interactions, making it easier than ever to build headless or decoupled WordPress applications.

#PHP 7.4 Requirements & Benefits

WordPress 7.0 raises the minimum PHP requirement from 5.6 to 7.4, a change that reflects the reality of modern web hosting while delivering substantial performance and security benefits. This requirement ensures that all WordPress sites can take advantage of modern PHP features and receive security updates from the PHP project.

#Why PHP 7.4?

PHP 7.4, released in November 2019, introduced numerous features that WordPress 7.0 leverages for improved performance:

• Preloading: OPcache preloading reduces startup time by 30-50%
• Typed Properties: Improved code reliability and IDE support
• Null Coalescing Assignment Operator: Cleaner, more maintainable code
• Spread Operator in Arrays: Better performance for array operations
• FFI (Foreign Function Interface): Potential for high-performance extensions

#Performance Improvements

Sites upgrading to WordPress 7.0 with PHP 7.4 typically see:

#Checking Your PHP Version

Before upgrading to WordPress 7.0, verify your PHP version through the WordPress admin dashboard under Tools > Site Health > Info > Server. If your server runs an older PHP version, contact your hosting provider to upgrade. Most reputable hosts already support PHP 7.4 or higher, often through simple control panel settings.

#How to Prepare Your Site

Preparing for WordPress 7.0 requires careful planning to ensure a smooth transition. Follow this comprehensive checklist to minimize downtime and prevent issues.

#Pre-Migration Checklist

1. Audit PHP Compatibility

   • Check current PHP version in Site Health
   • Contact hosting provider if upgrade needed
   • Test PHP 7.4 on staging environment

2. Inventory Your Extensions

   • List all active plugins and themes
   • Check WordPress.org for 7.0 compatibility badges
   • Contact developers for unverified extensions
   • Identify alternatives for incompatible plugins

3. Review Custom Code

   • Search for deprecated functions in custom themes/plugins
   • Update code using WordPress 7.0 coding standards
   • Test custom post types and taxonomies

4. Backup Everything

   • Database backup via phpMyAdmin or WP-CLI
   • File backup including wp-content directory
   • Test backup restoration procedure

5. Set Up Staging Environment

   • Clone production site to staging
   • Perform test upgrade on staging first
   • Verify all critical functionality

#How to prepare without guessing the migration

Writing a step-by-step “how to migrate to 7.0” guide before 7.0 has shipped is dishonest. The version-specific commands, the database upgrade routine, the new admin settings: none of it is final. Anyone publishing exact migration steps today is filling in blanks with assumptions.

What you can do now is reduce future migration cost regardless of what 7.0 looks like. The work is unglamorous and pays back on every release, not just this one.

Audit the parts of the stack most likely to break on a major upgrade:

• Themes still using functions.php template tags in place of block themes. Convert to block themes or plan the lift.
• Custom Gutenberg blocks built against early @wordpress/scripts versions. Pin and test against the latest stable.
• Page builders with their own rendering layer. These are the most common cause of “we cannot upgrade” debt.
• Custom REST endpoints without versioning. Add /v1/ namespacing now so a future bump is non-breaking.

Set up the boring infrastructure that lets you upgrade quickly when 7.0 does ship:

• A staging environment that mirrors production PHP version, plugin set, and content volume. Database parity matters more than people expect.
• Automated backups with a tested restore path. An untested backup is theatre.
• Plugin and theme updates running on a regular cadence, not deferred until the next major. Sites stuck on 6.0 are stuck because nobody updated 6.1 through 6.8.
• A short list of plugin authors you trust, with email contacts. When 7.0 ships, you will want to know within a week which of your plugins are tested against it.

When 7.0 actually reaches RC on the official release calendar, the upgrade path is the same one that has worked for every major WordPress release: run it on staging first, watch the error log, wait two to four weeks past general availability before touching production for client sites, and read the official field guide post on Make WordPress before assuming any third-party guide (this one included) reflects what actually shipped.

#Troubleshooting Common Issues

Despite thorough preparation, issues may arise during or after migration. Here are solutions to common WordPress 7.0 problems.

#PHP 7.4 Compatibility Issues

White Screen of Death

• Check PHP error logs for fatal errors
• Identify incompatible plugins by deactivating all and reactivating one by one
• Update or replace plugins using deprecated PHP functions

Deprecated Function Warnings

• Install Query Monitor plugin to identify deprecated calls
• Update custom code replacing deprecated functions
• Suppress warnings in production using error_reporting settings

#AI Integration Problems

Abilities API Not Responding

• Verify API keys are correctly configured
• Check rate limits haven’t been exceeded
• Ensure firewall allows connections to AI provider endpoints

Slow AI Response Times

• Implement caching for AI-generated content
• Use local AI models for sensitive data
• Configure fallback providers

#Real-Time Collaboration Issues

WebSocket Connection Failures

• Verify hosting supports WebSocket connections
• Check firewall isn’t blocking port 443 for secure WebSockets
• Test with caching plugins disabled

Editing Conflicts

• Ensure all users have unique sessions
• Clear browser cache and cookies
• Check for plugin conflicts with heartbeat API

#What to do until 7.0 actually ships

Until WordPress 7.0 reaches a tagged release on wordpress.org, the most useful thing any team can do is ignore the prediction posts (this one included) and watch the primary sources: the Make WordPress core blog, Gutenberg release notes, and the trac milestone for 7.0.

For an existing project shipping in 2026, build on a current 6.x release using block themes, theme.json, and the REST API. Treat AI as an integration layer behind your own endpoints, not a feature you wait on core to provide. When 7.0 lands, the migration becomes a question of which of your custom integrations can be replaced by a core API, not a rewrite.

If you want help auditing a stack for upgrade readiness, our WordPress development team does that work for production sites every release cycle.