WordPress 7.0 Is Out: An Agency's Take Two Weeks In

WordPress 7.0 shipped on April 9, 2026 — the biggest major version jump the project has had in years. After two weeks running it against staging copies of a handful of client sites, here's our read on what's genuinely useful, what's over-hyped, and what agencies should actually do about it this quarter.

What's in the release

The shortlist of features that will matter to most sites:

• Real-time collaborative editing — multiple users editing the same post or page simultaneously, with offline sync. HTTP polling by default, websocket providers available as plugins.
• Web Client AI API — a standardized Core interface for plugins and themes to access generative AI models from any provider. Providers stay external; Core provides the plumbing.
• Client-Side Abilities API — a browser-side registry that lets plugins expose "abilities" consistently (think: a structured way to register commands for the command palette, AI agents, and automation).
• Client-side media processing — image resizing and compression now happen in the browser before upload, reducing server load and enabling more advanced formats.
• Visual revisions — revision comparison now shows visual diffs, not just raw content differences.
• Responsive editing mode — blocks can be shown or hidden based on screen size without extra CSS.
• PHP-only block registration — server-side blocks without the JavaScript build step. Inspector controls auto-generate.
• New blocks: Breadcrumbs, Icons, and Heading level variations. Improved blocks: Navigation (simpler workflow, customizable mobile overlays), Cover (video backgrounds), Grid (responsive), Gallery (lightbox).
• Admin UI refresh — new default color scheme, smoother view transitions between screens.

Full feature list is in the WordPress 7.0 Beta 1 announcement and the dev notes.

Our take: the headline features

Web Client AI API is the real story. For years, every WordPress AI plugin has been a snowflake — each one bundling its own provider integration, its own credential storage, its own rate limiting. 7.0's Client AI API legitimizes AI features on Core. Providers stay external (good — no lock-in), but plugins can now share one interface for prompts, completions, and streaming. For agencies, this means AI-assisted writing, alt-text generation, content translation, and internal search can all plug into the same auth and logging layer. The plugin ecosystem will take 6–12 months to catch up, but the groundwork matters.

Real-time collaboration is what clients will ask about — and what most will rarely use. We ran it on a staging copy of a client's content site. It works. It's impressive. But the honest reality: most mid-market WordPress sites have one or two editors who work on different things at different times. The value curve of collaborative editing tracks team size, and most of our clients don't have the team size to notice. Enterprise and newsroom clients with multi-editor workflows will genuinely benefit. Everyone else — ignore for now and don't let the feature drive the upgrade timeline.

Client-side media processing will quietly save money. If your client's site takes a lot of uploads from marketing staff, the offloaded image processing is a real win. Shared hosts will thank you — you'll see less PHP memory consumed on large image uploads. This is the kind of invisible improvement that matters more than the flashy demos.

Admin UI refresh is cosmetic. The new color scheme is cleaner. View transitions feel nice. None of it justifies the upgrade on its own. If a client is on 6.x and asks "should we update for the new look," the answer is no — update for the security and performance improvements, and treat the UI refresh as a small bonus.

PHP-only block registration is a sleeper feature. If you build client-specific blocks, you can now skip the JavaScript build pipeline for simple dynamic blocks. Auto-generated inspector controls means less boilerplate. For agencies shipping 3–5 custom blocks per project, this cuts build complexity noticeably. We're already using it on one engagement this week.

What to actually do this quarter

Safe to upgrade now:

• Sites using the block editor, maintained themes, and a reasonable plugin count (under 20 active).
• Sites running PHP 8.1+ on managed WordPress hosts (Kinsta, WP Engine, Pantheon) — these platforms have already tested 7.0 compatibility across their fleets.

Wait to upgrade if:

• The site uses a heavily customized admin that depends on the old admin styles (7.0 rewrites several admin templates).
• Critical plugins haven't updated their "Tested up to" version yet. Check the plugin page; if it still says 6.9 or 6.8 three weeks after 7.0 shipped, the maintainer is likely inactive.
• The site uses the Classic Editor exclusively and you've been avoiding Gutenberg. 7.0 doesn't force the issue, but the investment in Classic-only workflows is clearly running out of road.

Don't wait, but handle with care:

• Sites with custom blocks built pre-7.0 — they'll likely still work, but block supports and design tools changed meaningfully. Budget a few hours of QA per custom block.

Our standard pre-upgrade checklist for client sites:

1. Clone production to a staging environment
2. Run the 7.0 upgrade on staging
3. Smoke-test: editor, preview, checkout (if WooCommerce), contact forms, navigation menu
4. Run axe accessibility audit before and after — block supports changes can subtly affect output
5. Diff the generated HTML on 3–5 representative pages to catch markup shifts
6. Run Lighthouse before and after — if performance regressed more than 5 points, investigate before promoting

For most sites this is a 2–3 hour engagement. For sites with custom blocks or heavy admin customization, budget a day.

The bigger picture

7.0 is the first release where the AI plumbing in Core stops feeling like plugin-land. That's a shift. Combined with Client-Side Abilities, we think the next 18 months of WordPress development will be defined by what the ecosystem builds on this foundation — not by what shipped today. It's a release worth upgrading to, not for what it does, but for what it enables.

Originally referenced: WordPress 7.0 Release Candidate 2 announcement on WordPress.org. Feature details drawn from the Beta 1 announcement and the 7.0 dev notes.

If you're running WordPress in production and want help planning your 7.0 upgrade — especially if you have custom blocks or complex content workflows — get in touch.