WordPress 7.1 Beta 4 is now available for testing alongside the Gutenberg 23.6 release, bringing another round of improvements ahead of the platform’s planned August launch. The update focuses heavily on stability, with more than 114 changes since Beta 3. For site owners, it is a useful preview—but not yet production-ready software.
Key takeaways
- WordPress 7.1 Beta 4 includes more than 114 updates and fixes.
- Changes cover 51 Editor issues and 63 Core issues.
- Gutenberg 23.6 arrives in the same development window.
- The final WordPress 7.1 release is scheduled for 19 August 2026.
- Testing should take place on a staging site, local installation or WordPress Playground.
Beta 4 is designed to make WordPress 7.1 more reliable before release. Anyone managing a business website should avoid installing it on a live or mission-critical site, particularly if there is no recent backup or rollback plan.
What WordPress 7.1 Beta 4 includes
The latest beta contains more than 114 updates since Beta 3, split between the Editor and Core. The release includes 51 Editor fixes and 63 Core fixes, showing that this phase of development is primarily about polishing existing functionality rather than introducing major new features.
Among the editor-focused improvements, notes should remain more reliably connected to the content they reference, while tagged people are displayed more clearly. These may appear to be small changes, but dependable editing tools can make a meaningful difference for teams publishing regularly.
Gutenberg 23.6 adds to the testing picture
The Gutenberg 23.6 release arrives alongside Beta 4, making this an important checkpoint for users who want to understand how WordPress’s editing experience is progressing. Gutenberg development feeds into the wider WordPress platform, so testing the two releases together can help identify issues before they affect the final product.
For agencies, freelancers and businesses with a WordPress care plan, this is also a good reminder to review staging workflows. Testing updates away from the live site makes it easier to check themes, plugins, forms and page layouts without putting visitors or customers at risk.
How to test safely
There are several ways to explore Beta 4 without manually replacing a production installation:
- Install the WordPress Beta Tester plugin and select the appropriate bleeding-edge beta stream.
- Download the Beta 4 package and use it on a dedicated test website.
- Run the supplied WP-CLI beta update command in a safe development environment.
- Open a WordPress Playground instance in a browser for quick, temporary testing.
Whichever method you choose, keep testing separate from your public website. A WordPress maintenance plan can help by providing controlled updates, backups and monitoring as new releases move from beta to stable.
What happens next
The planned final release date for WordPress 7.1 is 19 August 2026, with WordCamp US scheduled for 16–19 August. Further testing and bug reports will be important before then, particularly as more users try the software in different hosting, theme and plugin environments.
Site owners can use this period to audit compatibility, refresh backups and confirm who is responsible for update testing. Waiting for the stable release—and having a WordPress care plan ready to manage it—offers a safer route than experimenting directly on a business-critical website.
Sources
- WordPress.org blog: WordPress 7.1 Beta 4, Brand Spur.