I have spent the better part of a decade telling clients that “new” does not always mean “better.” WordPress 7.0 RC3 is that argument in release-note form. Everyone was waiting on Real-Time Collaboration (RTC), and the core team pulled it from the 7.0 release anyway. That was the hard call and the correct one. What is left is a release aimed at not breaking your site.
The architectural pivot in WordPress 7.0 RC3
A third Release Candidate is normally minor bug fixes and polish. RC3 is a refactor in the name of stability. Matt Mullenweg led the decision to drop RTC, citing race conditions, memory efficiency and server load. Shipping a feature that spikes CPU usage on shared hosting is not a risk the community can carry.
If you have followed the debate on object caching vs real-time editing, you know the synchronization logic behind multi-user editing is hard to get right. Fuzz testing turned up recurring bugs that could lose data. Pushing the work to the 7.1 cycle is the pragmatic move.
How to test the RC3 milestone safely
I do not trust the “WordPress Beta Tester” plugin for a serious review. I want to see what is happening in the terminal. The cleanest way to evaluate WordPress 7.0 RC3 is WP-CLI. It sidesteps the transient problems you sometimes hit with dashboard updates and takes you straight to the binary.
# Standard way to jump to the latest RC
wp core update --version=7.0-RC3
# Verify your environment hasn't choked on the update
wp core verify-checksumsIf you would rather sandbox it without the server overhead, the WordPress Playground instance holds up well for testing basic block interactions and the now “hard frozen” translation strings.
Notes for plugin authors
If you built features on the proposed RTC APIs, you have to change course. WordPress 7.0 RC3 has stripped those endpoints. Read the official dev notes on the RTC removal and check that your plugin’s “Tested up to” value of 7.0 still holds under these changes. Nobody wants to be the dev shipping a broken hook because they assumed a beta API would reach production.
If this release cycle is eating your dev hours, I can take it on. I have been wrestling with WordPress since the 4.x days.
Where this leaves 7.0
The release is still scheduled for May 20, 2026. With the experimental piece gone, the 143+ issues fixed since RC2 are what this version is actually about. Earlier major releases felt rushed to me. This one does not.
By the tides of sea,
where wind moves gently through trees,
sprouts up RC3.
