WordPress 7.0 is not a routine update. It marks the official start of Gutenberg Phase 3 – the long-awaited era of collaboration. For the first time, WordPress is moving beyond its single-editor origins toward a shared, real-time platform where writers, editors, designers, and clients can work together directly inside the CMS.
This is also a comeback moment. After a turbulent 2025 that saw the WP Engine vs. Automattic lawsuit, paused core contributions, and only one major release (WordPress 6.9), the WordPress project is back with its most ambitious release in years. The scope of change touches everything: how teams edit content together, how AI integrates with the platform, how the admin dashboard looks and feels, and what developers can build natively without third-party plugins.
This guide covers every major feature, the real-time status of the release, practical preparation steps, and what comes next – all from the perspective of people who build WordPress tools every day.
1. Real-Time Collaboration – The Headline Feature
The feature that defines WordPress 7.0 is real-time collaboration (RTC). For the first time, multiple users can co-edit the same post or page simultaneously, with changes appearing live. No more editor lock screens. No more overwriting your colleague’s work. No more drafting content in Google Docs and pasting it into WordPress.
How It Works Under the Hood
The collaboration system uses a CRDT-based (Conflict-free Replicated Data Type) approach for conflict resolution. Sync data is stored persistently via post meta on a dedicated internal post type called wp_sync_storage. The transport layer uses HTTP polling rather than WebSockets – a deliberate architectural decision to ensure the feature works on every hosting environment, from budget shared hosting to enterprise infrastructure.
The default client-side limit is two simultaneous collaborators per post, though hosts and developers can adjust this. Collaboration is opt-in through the Writing settings screen, so it won’t activate on your site unless you explicitly enable it.
The Challenges That Shaped This Feature
Real-time collaboration is the most technically ambitious feature WordPress has ever attempted. During testing, the community identified several concerns that shaped how it shipped:
• The initial approach of storing sync data in postmeta raised performance concerns. The team is evaluating dedicated database tables optimized for the high-frequency writes that real-time editing generates.
• On shared hosting, even a single post with two collaborators can generate approximately 480 HTTP requests per minute, a significant load for budget hosting plans.
• Based on community feedback, RTC was moved to off-by-default (opt-in) for the Release Candidate phase, ensuring site owners consciously choose to enable it.
The Positive Side: It Works on Modern Setups
WordPress VIP’s early testing with production sites showed that RTC works seamlessly on sites built for modern WordPress. Teams using the block editor with native blocks reported smooth experiences. Stress tests, including adding dozens of blocks simultaneously, copying large amounts of content in parallel, and having entire teams edit together, showed the feature held up remarkably well.
Visual Revisions also arrive in 7.0, allowing a side-by-side visual comparison of page versions before reverting. No more scanning code diffs, you can see exactly what changed between drafts.
2. The Native AI Infrastructure – WordPress Becomes AI-Ready
WordPress 7.0 is not adding an AI chatbot or content writer. It’s doing something more strategic: building a standardized AI infrastructure layer directly into the core that any plugin, theme, or external service can connect to.
The Four Components
WP AI Client – A provider-agnostic API that lets plugins and themes communicate with any AI model (OpenAI, Anthropic Claude, Google Gemini) through a single, consistent interface. No AI provider is bundled by default.
Settings to Connectors – A new centralized screen in wp-admin where site owners register AI provider API keys. Connect once, and every compatible plugin benefits.
Abilities API + MCP – A standardized bridge that lets AI services discover what your WordPress site can do, request permission to act, and execute tasks within defined boundaries. This works with the Model Context Protocol, enabling AI assistants to manage content through natural language commands.
AI Experiments Screen – Found under Settings, this lets users opt in to AI-powered features such as excerpt generation, alt text creation, image generation, and content summarization.
| WHAT THIS MEANS FOR SMACKCODERS USERS: WP Ultimate CSV Importer already supports AI content generation via ChatGPT, Gemini, and Claude during imports. WordPress 7.0’s native Connectors API means future versions of our plugin can leverage a centralized API key setup, eliminating the need for separate configuration and simplifying your workflow even further. |
Production security note: API keys entered through the Connectors UI are masked visually but not encrypted in the database. For production environments, load credentials through environment variables or PHP constants. The system checks in priority order: environment variable, then PHP constant, then database.
3. Admin Dashboard Overhaul – DataViews Changes Everything
The WordPress admin interface hasn’t had a meaningful visual update since 2013. WordPress 7.0 changes that with DataViews – a modern, React-based replacement for the traditional admin list tables that have been the backbone of content management for over a decade.
| Before (WordPress 6.x) | After (WordPress 7.0) |
| Static server-rendered list tables | Dynamic React-based DataViews |
| Full page reload for every filter | Instant client-side filtering and sorting |
| Single table layout only | Grid, list, and table layout options |
| Limited bulk editing | Advanced bulk operations |
| Generic form elements | Unified design system with tokens |
| No font management screen | Dedicated Appearance → Fonts screen |
Beyond DataViews, the admin refresh includes animated page transitions, smooth dropdown interactions, unified form elements, and a consistent design token system for colors, spacing, and typography. The Font Library is now universally accessible at Appearance to Fonts across all themes, including classic PHP-based themes.
4. New Blocks and Design Controls That Fill Real Gaps
WordPress 7.0 introduces blocks that address genuine gaps site owners have been filling with third-party plugins for years:
Breadcrumbs Block – Native breadcrumb navigation that works with custom post types, archives, and query loops out of the box. No plugin needed.
Icons Block – A built-in icon system directly in core, reducing reliance on icon font plugins or custom SVG workarounds.
Responsive Grid Block – Set maximum columns and let layouts adjust across devices. Responsive visibility controls let you show or hide specific blocks per screen size (desktop, tablet, mobile).
Cover Block Upgrade – Video embed backgrounds for hero sections without custom code.
Navigation Block – Significantly upgraded with built-in mobile menu design, flexible submenus, customizable overlay behavior, and mobile layout preview in the sidebar.
Pattern Editing – Simplified substantially. Patterns now default to Content-Only editing mode, presenting clean fields grouped with block icons. Pattern overrides work with custom dynamic blocks through the expanded Block Bindings API.
5. Developer Toolbox – What’s Under the Hood
PHP-Only Block Registration
Blocks can now be registered and rendered entirely via PHP – no JavaScript and no build pipeline required. WordPress auto-generates inspector controls for common attribute types. This lowers the barrier for theme developers shipping custom blocks.
React 19 Upgrade
The block editor upgrades to React 19, bringing performance improvements and new capabilities. This is a potentially breaking change – custom block developers should test their plugins thoroughly.
Enforced Iframed Editor
The post editor now runs inside an iframe by default, isolating theme styles from editor styles. This significantly reduces the visual conflicts and “this block is broken” recovery prompts that have frustrated developers. Full enforcement is on a gradual rollout in 7.0, with complete enforcement planned for 7.1.
DataViews and DataForm API
Developers can use DataViews and DataForm components to build custom admin interfaces with standardized layouts, validation, and new controls like combobox and adaptive select. This replaces the need for one-off custom React admin tables.
Client-Side Image Processing
Uploaded images are now processed directly in the browser before reaching the server. This saves server resources, speeds up uploads, and adds support for modern image formats without requiring server-side library support.
Metabox Compatibility Note
Real-time collaboration disables itself when classic meta boxes are present. Plugins that rely on legacy metaboxes should be audited for RTC compatibility.
6. The PHP 7.4 Requirement – Check This First
| ACTION REQUIREDWordPress 7.0 raises the minimum PHP version from 7.2 to 7.4. If your hosting environment is running PHP 7.2 or 7.3, the update will not install. Check your PHP version now through your hosting control panel or WordPress dashboard under Tools → Site Health → Info → Server. |
While PHP 7.4 is the floor, the WordPress core team recommends PHP 8.3 or later for optimal performance and security. For the AI Client and real-time collaboration features specifically, PHP 8.2+ is recommended for full functionality.
7. How to Prepare Your Site – 7-Step Checklist
A major release like 7.0 demands more preparation than a minor security patch. Here’s your step-by-step checklist:
1. Verify Your PHP Version – Log into your hosting control panel. Confirm PHP 7.4 or higher. Upgrade to PHP 8.3 if available.
2. Create a Full Backup – Back up your entire site database, files, media, and configuration. Use a reliable backup plugin or your host’s snapshot tool.
3. Set Up a Staging Environment – Clone your production site to a staging environment. Never test a major release on your live site.
4. Audit Your Plugins and Theme – Update all plugins to their latest versions. Flag any plugin that modifies admin list views (Posts, Pages, Media); these carry the highest DataViews compatibility risk.
5. Test on Staging Run the update on staging. Walk through critical user journeys: publishing, editing, WooCommerce checkout, contact forms, CSV imports/exports, and any custom functionality.
6. Check Hosting for Collaboration If you plan to use real-time collaboration, confirm your hosting supports additional concurrent connections. HTTP polling works universally, but performance varies.
7. Plan Your Update Window – Wait 1–2 weeks after release before updating production. This gives the community time to surface issues and plugin vendors time to push compatibility updates.
| PRO TIPBookmark this checklist. It’s the single most important thing you can do before WordPress 7.0 hits your dashboard update screen. |
8. What WordPress 7.0 Means for Smackcoders Plugin Users
If you’re using Smackcoders plugins, here’s what you need to know about WordPress 7.0 compatibility:
WP Ultimate CSV Importer Pro
Our team is actively testing CSV Importer against the WordPress 7.0 Release Candidates. The plugin’s core import/export functionality works through WordPress’s data layer, not through admin list tables directly, which reduces the DataViews compatibility risk. However, we recommend updating to the latest version of CSV Importer before upgrading to WordPress 7.0 and testing on a staging site first.
The new WP AI Client in 7.0 is also exciting for CSV Importer users. Our plugin already supports AI content generation during imports via ChatGPT, Gemini, and Claude. As WordPress’s native AI infrastructure matures, expect tighter integration with the Connectors API in future releases.
WP Ultimate Exporter
Export functionality operates independently of the admin interface changes, so DataViews should not affect exports. Test your standard export workflows on staging as a precaution.
WP Leads Builder for CRM
CRM integrations work through form data capture and API calls, which are not directly impacted by 7.0’s editor or admin changes. Ensure your CRM plugin is updated, and test lead capture flows on staging.
Woo to Shopify Sync
Inventory sync operates at the API and database level. No direct impact expected from 7.0’s changes, but always verify sync operations on a staging environment before upgrading production.
| STAY UPDATED We’ll publish a dedicated compatibility report for all Smackcoders plugins once WordPress 7.0 reaches its final release. Follow our blog for the latest updates. |
9. What’s Coming After 7.0 – The Roadmap
WordPress is returning to a three-release cadence in 2026 after 2025’s slowdown. Here’s what’s on the horizon:
WordPress 7.1 – August 2026: Deeper collaboration workflows, the always-iframed post editor (deferred from 7.0), the Tabs block, Core Abilities for post management, and further DataViews extensibility.
WordPress 7.2 – December 2026: Expanded collaboration features and the first steps toward native multilingualism in WordPress core, a capability the community has requested for years.
Connectors API Growth: Scoped to expand beyond AI providers to support additional authentication methods and service types in future releases.
The trajectory is clear: WordPress is evolving from a content management system into a collaborative content platform. Each 2026 release builds on the foundation that 7.0 establishes.
Frequently Asked Questions
Q1: Will my existing plugins break after updating to 7.0?
Most plugins will continue to work. The highest risk is with plugins that modify the Posts, Pages, or Media list views (due to DataViews) and custom block plugins (due to React 19). Update all plugins to their latest versions and test on a staging site first.
Q2: Is WordPress 7.0 adding an AI writer to my site?
No. WordPress 7.0 builds AI infrastructure (WP AI Client, Abilities API, Connectors), not an AI writer. No AI calls are made unless you configure an API provider and explicitly opt into specific features.
Q3: Should I enable automatic updates for WordPress 7.0?
No. Major releases should always be tested manually on a staging site first. Automatic updates are best reserved for minor security releases.
Q4: What PHP version do I need for WordPress 7.0?
Minimum PHP 7.4. Recommended PHP 8.3+ for best performance. PHP 8.2+ recommended for AI Client and real-time collaboration features.
Q5: Is there a new default theme with 7.0?
No. There is no “Twenty Twenty-Six” theme. The focus is on making existing block themes more powerful through the Site Editor and Phase 3 tools.
Q6: Will WP Ultimate CSV Importer work with WordPress 7.0?
We are actively testing compatibility with the latest Release Candidates. Our plugin’s core functionality works through WordPress’s data layer, minimizing DataViews impact. Update to the latest version and test on staging before upgrading production.
