Writen by Darko Kovacevic

Last updated: May 2026 | Estimated read time: 10-12 minutes

WordPress 7.0 is the most significant release since the block editor arrived in 2018. It ships on May 20, 2026 — and unlike routine point updates, this one changes how teams work inside WordPress at a fundamental level.

The headline WordPress 7.0 features are real-time collaboration (multiple people editing the same page at the same time), a native AI infrastructure layer, a redesigned admin dashboard, and a set of practical block editor upgrades.

There’s also a PHP minimum version change that you need to check before you hit “Update”.

This guide covers every major change in plain English — what it is, what it means for your site, and exactly what to do before you upgrade.

📦 TL;DR — Quick Summary

1. ✅ Release date: May 20, 2026
2. ✅ Headline feature: Real-time collaboration — multiple editors on the same post, live
3. ✅ Also ships: WP AI Client, DataViews admin redesign, new blocks, responsive block visibility
4. ✅ PHP minimum: 7.4 — check yours before upgrading
5. ✅ Key action: Test on a staging site first. Don’t update your live site on launch day.

What Is WordPress 7.0 and Why Does It Matter?

WordPress 7.0 isn’t a routine version bump. It’s the official completion of Gutenberg Phase 3 — the “Collaboration” phase of a multi-year project to transform WordPress from a solo writing tool into a platform built for teams.

To understand the scale, here’s the quick timeline. WordPress 5.0 (2018) introduced the block editor — Gutenberg Phase 1. WordPress 6.x (2022–2025) focused on Full Site Editing — Phase 2.

WordPress 7.0 closes Phase 3 by shipping real-time collaboration, AI infrastructure, and a wholesale admin redesign.

One honest note before we go further. The 2025 release cycle was disrupted by legal disputes between Automattic and WP Engine, which slowed contributor activity and compressed the schedule from three releases to two. The upside: the extra time went into polishing. WordPress 7.0 is better for the delay.

Real-Time Collaboration: Edit Together Like Google Docs

WordPress 7.0 lets multiple people edit the same post or page at the same time. You’ll see other editors’ cursors moving on the page, their changes appearing live, and their inline comments updating in real time — all without leaving your dashboard.

This is called Real-Time Collaboration, or RTC for short. It’s built on a technology called Yjs — a type of system (called a CRDT engine) that merges simultaneous edits from multiple users without conflicts. You don’t need to understand the technical details. What matters is that it works reliably even when two people edit the same paragraph at the same time.

WordPress 7.0 ships with a default “HTTP polling” sync method, which works on virtually every hosting setup. If your host supports WebSockets (a faster real-time connection type), they can enable that upgrade separately.

The Notes feature is part of this too. Notes — block-level inline comments introduced in WordPress 6.9 — now sync live between collaborators. You can add a comment on a specific block, and your colleague sees it appear immediately without refreshing. There’s also a new keyboard shortcut for adding notes inline.

One important limitation to know before you upgrade. If a plugin adds a classic meta box to your post editor — those older-style panels that appear below the main content area — collaboration mode disables automatically for that post. This is a temporary compatibility issue.

The fix is migrating those plugins to the newer sidebar component system, but most plugin authors haven’t done that yet. Test your key plugins before updating a team site.

WP AI Client: WordPress’s New AI Infrastructure Layer

WordPress 7.0 does not include a built-in AI writer. Let’s clear that up immediately, because most headlines are misleading on this point.

What it does include is the WP AI Client — a standardized PHP library that acts as a universal connector between WordPress and external AI services. Think of it like a power adapter.

Before 7.0, every plugin that wanted AI features had to build its own direct connection to OpenAI, Google Gemini, or Anthropic. After 7.0, they all plug into one shared socket — the WP AI Client — and the connection works the same way regardless of which AI provider you use.

This matters in a practical way. If you switch AI providers (say, from OpenAI to Anthropic), you won’t need to reconfigure every plugin individually.

You change the provider once in the new Connectors screen in your WordPress admin, and every plugin that uses the WP AI Client updates automatically.

The Connectors screen lets you connect your preferred AI service using official provider plugins. At launch, there are three official provider plugins in the WordPress Plugin Directory: OpenAI, Google, and Anthropic. Community-built providers for OpenRouter, Ollama, and Mistral are also already published.

The Abilities API is the JavaScript side of this system. It lets the block editor surface AI-powered actions in context — for example, a “Rewrite this paragraph” button that appears when you select text, powered by whatever AI provider you’ve connected.

Plugin developers build those features; WordPress provides the infrastructure.

The honest summary: 7.0 lays the foundation. The AI tools built on top of it will arrive in plugins over the coming months — not on day one.

DataViews: A Smarter, More Modern WordPress Dashboard

The WordPress admin dashboard is getting its biggest visual overhaul in years. The old list tables — those plain grey grids showing your posts, pages, and media — are being replaced by DataViews, a modern interface that looks and works more like a proper web app.

With DataViews, your content lists are sortable, filterable, and interactive in ways the old tables never were. You can switch between a table view and a card/grid view. Bulk actions are cleaner.

The whole thing responds faster. It’s the kind of update that’s hard to describe but immediately obvious the first time you use it.

DataForms is the companion feature. It lets you edit post fields — title, status, categories, custom fields — directly within the list view, without opening the full editor. For anyone who manages large amounts of content, this alone will save significant time.

The compatibility note you need to hear. Plugins that hook into the old WP List Tables UI may display incorrectly or break entirely after the update. If you rely on plugins that add custom columns, bulk actions, or filters to your posts or media screens, test them on a staging site before upgrading.

Most major plugin authors will push compatibility updates around the May 20 launch — wait a week or two if you’re unsure.

New WordPress 7.0 Blocks and Editor Improvements

WordPress 7.0 ships two brand-new core blocks and upgrades several existing ones. These are practical, everyday improvements — the kind that used to require installing a separate plugin.

Here’s what’s new:

Breadcrumbs block — Adds a navigation trail to any page (e.g., Home → Blog → Post Title) without a plugin. Essential for e-commerce and large content sites.

Icons block — Insert SVG icons directly in the editor from a built-in library. No more uploading icon images or installing an icon plugin for basic use cases.

Cover block (video background) — The Cover block — the full-width banner block — can now use an embedded video as its background. Previously, this required custom code or a page builder.

Grid block (now responsive) — The Grid block automatically adapts your column layouts to different screen sizes. It used to require manual breakpoint settings; now it handles that on its own.

Gallery block (lightbox support) — Visitors can now click a gallery image to open a full-screen lightbox and browse through the set without leaving the page. Built-in, no plugin needed.

Responsive block visibility — You can now show or hide any block based on screen size — desktop only, mobile only, tablet only — directly from the block settings panel. This used to require a plugin or custom CSS.

Pattern Spotlight mode — When editing a pattern (a reusable block layout), you can now isolate it with “Spotlight mode” to focus on just that section, and use “Isolated Editor mode” to edit synced patterns without accidentally changing the surrounding layout.

One more under-the-hood improvement worth mentioning: image resizing and compression now happen in the browser before upload, rather than on the server. Uploads will be faster, and server processing load drops — a quiet but meaningful performance win.

PHP 7.4 Is Now the Minimum: What That Means for Your Site

If your site runs on PHP 7.2 or 7.3, it won’t be fully supported after WordPress 7.0. This is the one technical requirement change you need to act on before upgrading.

PHP (Hypertext Preprocessor) is the programming language that powers WordPress behind the scenes. It runs on your hosting server — not in your browser — and your host controls which version you’re using.

WordPress 7.0 drops support for PHP 7.2 and 7.3, raises the minimum to PHP 7.4, and recommends PHP 8.2 or higher for best performance and security, source: WordPress 7.0 developer notes.

How to check your PHP version right now:

1. Log into your WordPress dashboard
2. Go to Tools → Site Health
3. Click the Info tab
4. Expand the Server section
5. Look for the PHP version field

If you’re on PHP 8.0 or higher, you’re fine — skip ahead. If you’re on 7.2 or 7.3, contact your host or update via your hosting control panel before upgrading to 7.0.

Most major managed hosts (Kinsta, WP Engine, SiteGround, Cloudways) have been running PHP 8.x as their default for years. This change is most likely to affect sites on older shared hosting accounts that haven’t been touched in a while.

The recommended version is PHP 8.2 or 8.3. Even if 7.4 meets the minimum, upgrading to 8.x will give you measurable speed improvements on top of the 7.0 features.

How to Upgrade to WordPress 7.0 Safely

Don’t update your live site on May 20. That’s the single most important piece of advice in this entire post. Major releases always surface unexpected plugin conflicts in the first few days. Wait at least one to two weeks for the ecosystem to catch up.

Here’s the safe upgrade path, in order:

Step 1 — Check your PHP version. See the section above. If you’re below PHP 7.4, update that first before anything else.

Step 2 — Back up your entire site. Files and database, both. Use a plugin like UpdraftPlus or your host’s built-in backup tool. Do this even if you have automatic backups running — create a manual backup dated the day before you upgrade.

Step 3 — Set up a staging site. A staging site is a private copy of your website used for testing — it’s not visible to the public or search engines. Most managed hosts (Kinsta, WP Engine, Flywheel) offer one-click staging. If yours doesn’t, use a local development tool like LocalWP.

Step 4 — Run the update on staging first. Push the 7.0 update on your staging site and test thoroughly. Check the editor, your admin dashboard, any forms, checkout pages if you run WooCommerce, and any plugins that add panels to the post editor.

Step 5 — Pay attention to these specifically. Plugins using add_meta_box() (classic meta boxes) will disable real-time collaboration on posts where they appear. Plugins that customize WP List Tables may display incorrectly with DataViews. Flag any issues before moving to your live site.

Step 6 — Update your live site only after staging is clean. Once you’ve confirmed everything works on staging, update your live site. Do it during a low-traffic window and have your backup ready to restore if something unexpected surfaces.

Step 7 — Monitor for 48 hours. Check your site’s front end, admin, forms, and any automated workflows (email, payments, membership) in the two days after updating. Most issues appear quickly.

WordPress 7.0 FAQs

WordPress 7.0 Features: The Verdict

WordPress 7.0 is a genuine platform shift. Real-time collaboration alone moves WordPress from a solo tool into territory that previously required Google Docs, Notion, or a stack of third-party plugins.

The WP AI Client lays the infrastructure that the ecosystem will build on for years. DataViews makes the admin feel like it belongs in 2026.

The three things to take away:

• Collaboration is real and ready for teams
• The AI features are a foundation, not a chatbot, and ready for teams
• Your PHP version needs to be 7.4 or higher before you upgrade

Check your staging environment, back up your site, and let the ecosystem settle for a week or two after May 20. The WordPress 7.0 features are worth having — just don’t rush the upgrade.