The announcements for WordPress 7.0 Beta 1 lead with the visual refresh, which is the least interesting part of it. I have been wrestling with the editor since the 4.x days, and this release reads differently: the real changes are in how WordPress syncs data, how it talks to AI providers, and where media gets processed. The direction is collaborative editing with a lot more work happening in the browser.
Real-time collaboration in core
Plugins have been trying at real-time collaboration for years. Core now ships it with a standardized sync provider, defaulting to HTTP polling because that works on ordinary shared hosting. Websocket support is where it gets interesting. Alongside the multiplayer editing there are stabilized notes and data syncing that survives going offline. Anyone who has lost 500 words to a timed-out session or a flickering Wi-Fi connection knows why that part is worth having.
The WP AI Client and the Abilities API
AI in WordPress has been mostly noise so far, and 7.0 puts some structure under it. The WP AI Client is a provider-agnostic layer, so plugin developers can code against a core interface instead of each writing their own wrapper around OpenAI or Anthropic. It hooks into the Abilities API from 6.9, which is what lets a model take an action inside WordPress instead of only producing text. That means fewer duplicate API wrappers in your codebase and a smaller security surface to worry about.
PHP-only blocks and browser-side media processing
If you dislike context-switching between PHP and React, WordPress 7.0 Beta 1 lets you register a block in PHP alone, with the inspector controls generated for you. Writing a custom dynamic block gets a lot less ceremonial. Client-side media processing is the other one to read up on: the browser resizes and compresses an image before the file reaches your server, which takes the CPU cost of a bulk upload off the web server.
How to test WordPress 7.0 Beta 1 safely
Do not run WordPress 7.0 Beta 1 on a production site. Something will break. The final release is not due until April 9, 2026, so there is time to work through it properly. The quickest route in is WP-CLI, faster than fiddling with a plugin and with more control over the update itself.
# Update your local dev site to Beta 1
wp core update --version=7.0-beta1If you would rather not set up a local environment at all, WordPress Playground needs no configuration and will show you how your current theme handles the new dashboard styles and view transitions.
If beta testing this release is eating your dev hours, I can take it on. I have been wrestling with WordPress since the 4.x days.
What to do before 7.0 ships
There is a lot in here. New Icons and Breadcrumbs blocks, the Client Side Abilities API, and an editor that behaves more like an application than a page. Two things are worth doing early: revisit your block registration logic, and run your media workflows against the beta. Moving processing into the browser changes where the bottleneck sits, and finding out in 2026 that your custom upload filters are deprecated is a bad way to spend a release week.
Props to the core contributors and reviewers who put the original release post together. Seven-oh lands soon.
