WordPress 7.0 Beta 5 is available for testing
Released , WordPress 7.0 Beta 5 is a pre-release build intended for testing and feedback, not production use.
This beta is still under active development. Install it only on a staging environment, disposable test site, or a local build so you can safely validate upgrades, theme compatibility, plugin behaviour, and editorial workflows without risking downtime.
Testing guidance for site owners and WordPress teams
Where Beta 5 should (and should not) run
Do not install Beta 5 on production or mission-critical websites. Treat it as a change-detection build for spotting regressions early, especially around administrative flows, editor tooling, and any custom integrations that rely on WP core behaviour.
Supported ways to test Beta 5
You can test via the WordPress Beta Tester plugin by selecting the “Bleeding edge” channel and “Beta/RC Only” stream, by direct download and manual installation of the Beta 5 zip, by running WP-CLI with wp core update --version=7.0-beta5, or by using WordPress Playground for browser-based testing with no setup.
What to test beyond the upgrade path
Upgrades matter, but feature testing matters just as much. Run real editorial journeys, check role-based access patterns, confirm admin bar behaviour, and validate that navigation and settings routes used by your team still behave as expected after the update.
How to report issues so they get fixed
When you hit a bug, log it in the Alpha/Beta area of the support forums or file it directly in WordPress Trac if you can provide clear reproduction steps. Before reporting, compare your findings with the current list of known bugs to avoid duplicate triage.
Release schedule checkpoint
The planned final release date for WordPress 7.0 remains . Beta and RC testing is where stability is won, so early validation of real sites and real workflows has a direct impact on the quality of the final release.
Beta 5 highlights: fixes, polish, and a new navigation tool
Over 101 updates and fixes since Beta 3
WordPress 7.0 Beta 5 includes more than 101 updates and fixes since Beta 3, with targeted bug-fix cycles continuing through the remaining betas. If you maintain bespoke plugins, complex themes, or multisite networks, this is the moment to validate assumptions and surface edge cases while changes are still cheap to land.
New feature: Command Palette shortcut in the Omnibar
Beta 5 adds a new Command Palette entry point for logged-in editors. A new field in the upper admin bar shows a ⌘K or Ctrl+K hint and unfurls the command palette when activated, aiming to speed up navigation and common actions from anywhere across the site.
For teams, this is worth testing with real roles and real permissions. Confirm what actions are discoverable, whether custom admin pages appear as expected, and how the palette behaves across editing screens, design tasks, and plugin management routes.
FAQ
Can I install WordPress 7.0 Beta 5 on a live site?
No. Beta 5 is not production-ready. Use a staging environment, a test server, local development, or WordPress Playground so failures do not affect visitors or revenue.
What is the quickest way to try Beta 5 without setting up hosting?
Use WordPress Playground. It runs in your browser, requires no installation, and is suited to fast checks of core behaviour and UI changes.
How do I update to Beta 5 using WP-CLI?
Run wp core update --version=7.0-beta5 on a non-production install, then test key journeys such as log-in, editing, publishing, media uploads, and plugin settings screens.
What is the Command Palette shortcut added in Beta 5?
Logged-in editors get a new admin bar field marked with ⌘K or Ctrl+K. Activating it opens the command palette, designed to streamline navigation and common actions from anywhere in the admin or front end while logged in.
When is WordPress 7.0 expected to ship?
The scheduled final release date is .
Where should I report bugs found in Beta 5?
Report issues in the Alpha/Beta area of the support forums, or file a reproducible report in WordPress Trac if you are comfortable doing so. Checking known bugs first helps triage move faster.
