On April 9, 2026, WordPress 7.0 will be released. It's the biggest release in years, with real-time collaboration, a refreshed admin interface, new blocks and the first AI infrastructure in WordPress core. Sounds impressive — but what will you actually notice as a business owner with a company website?
In this article I walk through the changes that matter to you, what you can safely ignore, and what you should take care of before April 9.
First: why 7.0?
WordPress counts version numbers as decimals. After 6.9 comes 7.0 — just like version 4.0 came after 3.9. There is no special meaning behind the first digit changing. It's simply the next release.
What does make 7.0 special is its content. This is the starting point of Gutenberg Phase 3: collaboration. Since WordPress 5.0 introduced the block editor in 2018, this is the biggest shift in how the editor works. The WP Engine lawsuit also played a role: the legal conflict between Automattic and WP Engine significantly disrupted development in 2025. Only two releases shipped instead of the usual three. WordPress 7.0 marks the return to normal pace — with three releases planned for 2026.
Collaboration in the editor
The most notable new feature: you can work on the same page or post with multiple people simultaneously. Think Google Docs, but inside WordPress.
Technically it works via Yjs, an open-source framework for synchronizing changes. The default connection method is HTTP long polling — that sounds technical, but it simply means it works on virtually any hosting environment. No special server configuration needed. Hosting providers or plugins can add WebSocket support for faster synchronization, but that's optional.
By default, WordPress 7.0 supports two simultaneous users per post. That's a deliberate, conservative choice because of the load on cheaper hosting. The number can be adjusted via wp-config.php.
Notes: comments on blocks
Notes already existed in WordPress 6.9, but 7.0 makes them seriously useful. You can now place comments on specific text within a block (similar to how you select text in Google Docs and leave a comment). New capabilities: @mentions with notifications, a suggestion mode where you can propose edits without directly changing the content (accept or reject with one click), and threaded replies.
Notes are only visible in the editor — they never appear on your website. For business owners who collaborate with a copywriter, designer or VA, this is a significant improvement. No more emailing Word documents back and forth with comments in the margins.
Is this useful if you work alone?
Honestly: if you're the only one working on your site, you won't use the collaboration features directly. But if you have someone else write your content, or if your web developer helps with pages, the review process becomes much smoother.
The admin looks different
WordPress 7.0 gives the entire admin area a visual refresh. The old "Fresh" color scheme is replaced by a new default scheme with more consistent typography, buttons and forms. It's not a complete redesign — more of a fresh coat of paint — but the difference is noticeable.
Additionally, DataViews replaces the familiar list view for posts, pages and media. Instead of the old table, you can now filter, sort and group without page reloads, and switch between table, grid and list views. It feels more modern and faster. Also new: visual revisions, which let you compare inline between previous versions of your content within the editor. And smooth transitions between admin screens instead of full page reloads.
What you need to know: plugins that modify the post list in the admin (think extra columns or custom views) may have issues with this. If you use such plugins, test on a staging environment before updating.
New blocks: icons, breadcrumbs and more
WordPress 7.0 delivers several new blocks that are immediately useful.
The Icons block includes 80+ SVG icons you can place anywhere without code. Color, size and background are customizable. Previously you needed a separate plugin for that.
The Breadcrumbs block adds breadcrumb navigation — important for SEO and usability. Until now, that was only possible via plugins like Yoast or Rank Math. Now it's built into WordPress.
Also new: responsive visibility per block (show or hide blocks on desktop, tablet or mobile without CSS), an improved Grid block with responsive columns, and native lightbox support for gallery images.
Smarter media uploads
A subtle but valuable improvement: WordPress 7.0 processes images in your browser before they're uploaded to the server. Resizing, compression and thumbnail generation happen client-side. This makes uploading faster and more reliable — especially on shared hosting where server resources are limited.
WordPress uses MozJPEG compression for this, making JPEG files significantly smaller without visible quality loss. Modern formats like WebP and AVIF are also supported.
AI in WordPress — what it does and doesn't do
This is where most articles about WordPress 7.0 get it wrong, so let me be precise.
WordPress 7.0 introduces an AI Client and a Connectors page under Settings. You can enter API keys for OpenAI, Anthropic (Claude) or Google (Gemini). And then... nothing happens. Literally. No AI buttons appear in your editor, no text is automatically generated, your site doesn't change in any way.
The AI Client is infrastructure for plugin developers. The idea: you configure an API key once, and every plugin that offers AI features can use that key. Think of future plugins for automatic alt text on images, SEO meta descriptions, or content summaries. But those are future plugins — on April 9, nothing changes in your daily usage.
If you don't enter any API keys, this feature has zero impact on your site. No extra load, no extra code running, nothing.
Font Library for everyone
The Font Library — a management screen for fonts under Appearance > Fonts — was previously only available for block themes. In WordPress 7.0 it works for all themes, including classic themes. You can install Google Fonts, upload custom font files and manage your typography without plugins or code changes. A small thing, but if you've ever been frustrated by installing a custom font, this is welcome.
Technical requirements: check your PHP version
This is the most important practical point. WordPress 7.0 drops support for PHP 7.2 and 7.3. The new minimum version is PHP 7.4. Recommended is PHP 8.3 or higher.
What does that mean in practice? If your server runs PHP 7.2 or 7.3, you cannot update to WordPress 7.0. The update will be blocked. Your site stays on WordPress 6.9 and will still receive security updates, but no new features.
Most Dutch hosting providers already offer PHP 8.2 or higher. Antagonist, TransIP, STRATO and Mijndomein are well above the minimum requirement. Mijndomein is even phasing out PHP 8.2 in favor of 8.3/8.4. Check your own version to be safe via the WordPress dashboard: go to Tools > Site Health > Info > Server.
Additionally, MySQL 8.0 or MariaDB 10.6 is recommended. Older versions will probably still work, but are considered a security risk. No Dutch hosting provider publicly documents which MySQL/MariaDB version they run, so if in doubt: ask your provider.
Plugin compatibility: no definitive picture yet
At the time of writing (March 2026), major plugins like WooCommerce, Elementor, Yoast, Contact Form 7 and ACF have not yet issued official compatibility statements for WordPress 7.0. The official Field Guide is expected around March 19 with RC1, and plugin developers typically publish compatibility updates around that time.
The biggest risks are with plugins that modify admin list views (because of DataViews), plugins that heavily override admin CSS (because of the new color scheme), and block plugins that still use Block API version 2 (because of the iframed editor). Chances are your everyday plugins will keep working — but test on a staging environment.
What should you do before April 9?
You don't have to update on April 9. There's no rush — and for most business sites it's wiser to wait a week or two until plugin developers have released their compatibility updates. The update will simply be offered via Dashboard > Updates, as always.
What you can do now: check your PHP version via Tools > Site Health > Info > Server. Still running 7.2 or 7.3? Contact your hosting provider to upgrade to at least PHP 7.4, but preferably 8.2 or higher. Update all your plugins and themes to the latest version — that's wise regardless of WordPress 7.0. And make a full backup of your database and files before you change anything.
If your hosting provider offers a staging environment (most managed hosts do), test the update there first. Check that your admin still looks as expected, that your forms still work, and that your webshop (if you have one) functions normally. After updating: clear all caches — browser, server and any caching plugins.
Conclusion
WordPress 7.0 is a substantial release. The collaboration features and Notes make WordPress genuinely useful as an editorial platform for the first time. The new blocks (icons, breadcrumbs) and responsive visibility are immediately practical. The AI infrastructure is currently invisible to end users, but lays the groundwork for what's coming in plugins over the next few months.
The most important thing right now: check your PHP version and make sure you have a working backup. The rest will follow.