WordPress 7.0 is here: what's new, what's faster, and how to prepare

WordPress 7.0 is the most significant release in years — a rebuilt block model, a faster rendering pipeline, and PHP 8.4 as the new baseline. Here's what actually changed, why it matters for performance, and how to get your site ready before you hit update.

What's new in 7.0

The headline of this release isn't a single feature — it's the foundation. The editor, the templating layer, and the runtime all moved forward together, and the result is a platform that feels noticeably quicker from the dashboard to the front end.

Three changes stand out: a redesigned block model that cuts re-render cost, a server-side rendering path that ships less JavaScript, and a move to PHP 8.4 with typed properties throughout core.

The new block model

Blocks are now resolved through a flattened tree that avoids the deep reconciliation passes that made complex pages sluggish in the editor. In practice, editing a long post with dozens of nested blocks no longer feels like it's fighting you.

• Interactivity API by default — front-end interactions hydrate selectively instead of loading everything up front.
• Block bindings are now first-class, so dynamic data from custom fields renders without a plugin shim.
• Style variations can be scoped per-block, making design systems far easier to maintain.

Performance gains

Because 7.0 ships less JavaScript and renders more on the server, Core Web Vitals improve almost everywhere — especially Largest Contentful Paint on content-heavy pages.

"7.0 is the first release where the editor feels as fast as the published site. The block model rewrite paid off."— Priya Tan, Senior Engineer

PHP 8.4 & the runtime

WordPress 7.0 sets PHP 8.4as the minimum supported version. If you're on 8.1 or below, this is the change most likely to need attention before upgrading. The payoff is real: property hooks, faster array functions, and a leaner opcode cache.

A typical theme's functions.phpwon't need changes, but older plugins that relied on dynamic properties will emit deprecations. You can surface them on staging before they ever reach production:

# clone production to staging, then scan for 8.4 issues
wp site clone --to=staging
wp eval 'echo PHP_VERSION;'   # 8.4.2
wp plugin list --update=available --format=table
wp php-compat scan --target=8.4

How to prepare

The upgrade itself is one click. The work is in verifying that your plugins, theme, and custom code are happy on the new runtime. We recommend testing on a staging copy first — never upgrade production blind.

Compatibility checklist

1. Clone production to a staging environment and upgrade there first.
2. Confirm every active plugin lists 7.0 compatibility (or has a recent update).
3. Run a PHP 8.4 compatibility scan and resolve any deprecations.
4. Check custom blocks render correctly under the new block model.
5. Run a visual regression pass, then push staging → production.

The verdict

WordPress 7.0 is a confident, foundational release. The block model rewrite and the move to PHP 8.4 set the platform up for the next several years, and the performance wins are immediate on day one. As long as you test on staging first, the upgrade path is smooth — and on managed hosting, it's effectively hands-off.

If you've been waiting for the right moment to modernize your stack, this is it.