The second Release Candidate (“RC2”) for WordPress 7.0 is ready for download and testing!
This version of the WordPress software is under development.** Please do not install, run, or test this version of WordPress on production or mission-critical websites.** Instead, it’s recommended that you evaluate RC2 on a test server and site.
Reaching this phase of the release cycle is an important milestone. While release candidates are considered ready for release, testing remains crucial to ensure that everything in WordPress 7.0 is the best it can be.
You can test WordPress 7.0 RC2 in four ways:
PluginInstall and activate the WordPress Beta Tester plugin on a WordPress install. (Select the “Bleeding edge” channel and “Beta/RC Only” stream.)Direct DownloadDownload the RC2 version (zip) and install it on a WordPress website.Command LineUse this WP-CLI command:
wp core update --version=7.0-RC2WordPress PlaygroundUse the WordPress Playground instance to test the software directly in your browser. No setup required – just click and go!
The scheduled final release date for WordPress 7.0 is April 9, 2026. The full release schedule can be found here. Your help testing Beta and RC versions is vital to making this release as stable and powerful as possible. Thank you to everyone who helps with testing!
Please continue checking the Make WordPress Core blog for 7.0-related posts in the coming weeks for more information.
What’s new in WordPress 7.0? Check out the Beta 1 announcement and 7.0 Developer Notes for details and highlights. For technical information related to issues addressed since RC1, you can browse the following links:
GitHub commits since March 24, 2026
Closed Trac tickets since March 24, 2026
WordPress is open source software made possible by a passionate community of people collaborating on and contributing to its development. The resources below outline various ways you can help the world’s most popular open source web platform, regardless of your technical expertise.
Testing for issues is crucial to the development of any software. It’s also a meaningful way for anyone to contribute.
Your help testing the WordPress 7.0 RC1 version is key to ensuring that the final release is the best it can be. While testing the upgrade process is essential, trying out new features is equally important. This detailed guide will walk you through testing features in WordPress 7.0. For those new to testing, follow this general testing guide for more details on getting set up.
What else to test:
If you encounter an issue, please report it to the Alpha/Beta area of the support forums or directly to WordPress Trac if you are comfortable writing a reproducible bug report. You can also check your issue against a list of known bugs.
Curious about testing releases in general? Follow along with the testing initiatives in Make Core and join the #core-test channel on Making WordPress Slack.
Web hosts provide vital infrastructure for supporting WordPress and its users. Testing on hosting systems helps inform the development process while ensuring that WordPress and hosting platforms are fully compatible, free of errors, optimized for the best possible user experience, and that updates roll out to customer sites without issue.
Want to test WordPress on your hosting system? Get started with configuring distributed hosting tests here.
For plugin and theme authors, your products play an integral role in extending the functionality and value of WordPress for all users.
Thanks for continuing to test your themes and plugins with the WordPress 7.0 beta releases. If you haven’t yet, make sure to conclude your testing and update the “Tested up to” version in your plugin’s readme file to 7.0.
If you find compatibility issues, please post detailed information to the support forum.
Do you speak a language other than English? ¿Español? Français? Русский? 日本語? हिन्दी? বাংলা? मराठी? ಕನ್ನಡ? You can help translate WordPress into more than 100 languages. This release milestone (RC2) also marks the hard string freeze point of the 7.0 release cycle.
At first just a dream,
RC2 flows like a stream
with seven-oh gleam.
*Props to @amykamala *@annezazu for proofreading and review.
The first Release Candidate (“RC1”) for WordPress 7.0 is ready for download and testing!
This version of the WordPress software is still under development. Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, it’s recommended to evaluate RC1 on a test server and site.
WordPress 7.0 RC1 can be tested using any of the following methods:
PluginInstall and activate the WordPress Beta Tester plugin on a WordPress install. (Select the “Bleeding edge” channel and “Beta/RC Only” stream.)Direct DownloadDownload the RC1 version (zip) and install it on a WordPress website.Command LineUse this WP-CLI command:
wp core update --version=7.0-RC1WordPress PlaygroundUse the WordPress Playground instance to test the software directly in your browser. No setup required – just click and go!
The scheduled final release date for WordPress 7.0 is April 9, 2026. The full release schedule can be found here. Your help testing Beta and RC versions is vital to making this release as stable and powerful as possible. Thank you to everyone who helps with testing!
Please continue checking the Make WordPress Core blog for 7.0-related posts in the coming weeks for more information.
What’s new in WordPress 7.0? Check out the Beta 1 announcement and WordPress 7.0 Developer Notes for details and highlights.
RC1 contains more than 134 updates and fixes since the Beta 5 release. You can browse the technical details for all issues addressed since Beta 5 using these links:
GitHub commits since March 12, 2026
Closed Trac tickets since March 12, 2026
The release squad in conjunction with project leadership identified additional features that were not ready for beta 1 but are included in RC1 as supporting requirements for flagship features of the release.
AI Connectors Screen – A new admin screen for connecting AI providers to your site and an API for registering additional ones.
The Command Palette is now available via a ⌘K or Ctrl+K shortcut in the admin bar.
Want to look deeper into the details and technical notes for this release? These tickets and pull requests are just some of the latest updates:
#GB-76700: Client Side Media as plugin only
#GB-76722: Add support for non-AI providers on Connector’s Screen
#GB-76736: New activation hook to enable RTC by default
#64904: WP_ALLOW_COLLABORATION constant for RTC
#GB-76643: Real Time Collaboration is opt-in by default
#GB-76460: Toggle to turn RTC session notifications on/off
#62046: Update PHP AI Client package to 1.3.1
#GB-76550: Revisions: Show changed block attributes in sidebar
#62067: Single config option to disable all LLM related features
#63697: OPCache added to Site Health > Info > Server
The final release is on track for April 9, 2026. As always, a successful release depends on your confirmation during testing. So please download and test!
WordPress is open source software made possible by a passionate community of people collaborating on and contributing to its development. The resources below outline various ways you can help the world’s most popular open source web platform, regardless of your technical expertise.
Testing for issues is crucial to the development of any software. It’s also a meaningful way for anyone to contribute. Your help testing the WordPress 7.0 RC1 version is key to ensuring that the final release is the best it can be. While testing the upgrade process is essential, trying out new features is equally important. This detailed guide will walk you through testing features in WordPress 7.0.
What to test:
If you encounter an issue, please report it to the Alpha/Beta area of the support forums or directly to Trac if you are comfortable writing a reproducible bug report. You can also check your issue against a list of known bugs.
Hosting systems provide vital infrastructure for supporting WordPress and its users. Testing on hosting infrastructure ensures that WordPress and hosting systems are fully compatible, free of errors, optimized for the best possible user experience, and that updates roll out to customer sites without issue. Thank you to all web hosts who test WordPress!
Want to set up testing on your hosting system? Get started with configuring distributed hosting tests here.
For plugin and theme authors, your products play an integral role in extending the functionality and value of WordPress for all users.
Thanks for continuing to test your themes and plugins with the WordPress 7.0 beta releases. With RC1, you’ll want to conclude your testing and update the “Tested up to” version in your plugin’s readme file to 7.0. If you find compatibility issues, please post detailed information to the support forum.
Curious about testing releases in general? Follow along with the testing initiatives and join the #core-test channel on Making WordPress Slack.
Do you speak a language other than English? ¿Español? Français? Русский? 日本語? हिन्दी? বাংলা? मराठी? ಕನ್ನಡ? You can help translate WordPress into more than 100 languages. This release milestone (RC1) marks the hard string freeze point of the 7.0 release cycle. However, strings will not be available for translation until RC2 later this week.
RC1 arrives
with momentum, sped up time
and jazz on the mind.
Props to @4thhubbard, @desrosj, @jeffpaul, @chaion07, @audrasjb, @jorbin for collaboration and review.
WordPress 7.0 Beta 5 is ready for download and testing!
This version of the WordPress software is still under development. Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, it’s recommended to test Beta 5 on a test server and site.WordPress 7.0 Beta 5 can be tested using any of the following methods:
PluginInstall and activate the WordPress Beta Tester plugin on a WordPress install. (Select the “Bleeding edge” channel and “Beta/RC Only” stream.)Direct DownloadDownload the Beta 5 version (zip) and install it on a WordPress website.Command LineUse this WP-CLI command:
wp core update --version=7.0-beta5WordPress PlaygroundUse the WordPress Playground instance to test the software directly in your browser. No setup is required – just click and go!
The scheduled final release date for WordPress 7.0 is still April 9, 2026. The full release schedule can be found here. Your help testing Beta and RC versions is vital to making this release as stable and powerful as possible. Thank you to everyone who helps with testing!
Please continue checking the Make WordPress Core blog for 7.0-related posts in the coming weeks for more information. What’s new in WordPress 7.0? Check out the Beta 1, Beta 2, Beta 3 and Beta 4 announcements for details and highlights.
Your help testing the WordPress 7.0 Beta 5 version is key to ensuring everything in the release is the best it can be. While testing the upgrade process is essential, trying out new features is equally important. This detailed guide will walk you through testing features in WordPress 7.0.
If you encounter an issue, please report it to the Alpha/Beta area of the support forums or directly to WordPress Trac if you are comfortable writing a reproducible bug report. You can also check your issue against a list of known bugs.Curious about testing releases in general? Follow along with the testing initiatives in Make Core and join the #core-test channel on Making WordPress Slack.
WordPress 7.0 Beta 5 contains more than 101 updates and fixes since the Beta 3 release.
Each beta cycle focuses on bug fixes, and more are on the way with your help through testing. You can browse the technical details for all issues addressed since Beta 3 using these links:
GitHub commits since March 5, 2026
Closed Trac tickets since March 5, 2026
Issues addressed since Beta 4:
GitHub commits since March 10, 2026
Closed Trac tickets since March 10, 2026
WordPress 7.0 Beta 5 contains a new feature!
Instantly access all the tools you need with a single click using the new Command Palette shortcut in the Omnibar! In 7.0 Beta 5, logged-in editors will see a field with a ⌘K or Ctrl+K symbol in the upper admin bar that unfurls the command palette when clicked. The new command palette entry point streamlines navigation and customization, giving you full control from anywhere on your site – whether you’re editing, designing or just browsing plugins.
A smooth melody
Beta 5 plays on its strings.
Seven brings good things.
Props to @amykamala, @annezazu and @4thhubbard for proofreading and review.
WordPress 6.9.2 and WordPress 6.9.3 were released yesterday, addressing 10 security issues and a bug that affected template file loading on a limited number of sites.
The WordPress Security Team has discovered that not all of the security fixes were fully applied, therefore 6.9.4 has been released containing the necessary additional fixes.
Because this is a security release,** it is recommended that you update your sites immediately**.
You can download WordPress 6.9.4 from WordPress.org, or visit your WordPress Dashboard, click “Updates”, and then click “Update Now”. If you have sites that support automatic background updates, the update process will begin automatically.
For more information on WordPress 6.9.4, please visit the version page on the HelpHub site.
The security team would like to thank the contributors who reported and investigated this issue, in particular Thomas Kräftner for his responsible disclosure. The security issues that are resolved in 6.9.4 are:
A PclZip path traversal issue reported independently by Francesco Carlucci and kaminuma
An authorization bypass on the Notes feature reported by kaminuma
An XXE in the external getID3 library reported by Youssef Achtatal
WordPress 6.9.2 was released earlier today and addressed 10 security issues.
A few users have subsequently reported an issue where the front end of their site was appearing blank after updating to 6.9.2. The issue has been narrowed down to some themes using an unusual approach to loading template files via “stringable objects” instead of primitive strings for file paths.
Although this is is not an officially supported approach to loading template files in WordPress (the template_include filter only accepts a string), it nevertheless caused some sites to break. As a result, the Security Team has decided to address this in a fast follow 6.9.3 release.
As always,** it is recommended that you update your sites to the latest version of WordPress immediately.** This ensures your site is protected by all available security fixes in 6.9.2 and that you will not be affected by the bug fixed in 6.9.3.
Many thanks to those who reported the issue, assisted in narrowing down the problem, and helped with the fix, in particular Jos Klever who assisted throughout the process.
You can download WordPress 6.9.3 from WordPress.org, or visit your WordPress Dashboard, click “Updates”, and then click “Update Now”. If you have sites that support automatic background updates, the update process will begin shortly. You don’t have to do a thing!
For more information on WordPress 6.9.3, please visit the version page on the HelpHub site.
The next major release of WordPress will be version 7.0, which is planned for April 9, 2026. The Security Team has decided to package a new beta release (7.0 beta 4) to keep everyone protected from the patched vulnerabilities, including the dedicated members of the community focusing their time and effort on testing the upcoming release.
This will be an additional beta release in the 7.0 release cycle. The schedule will remain the same going forward, but with five total beta releases instead of the previously planned four. The next 7.0 beta release is still scheduled for Thursday, March 12th.
This beta version of the WordPress software is still under development. Please do not install, run, or test WordPress 7.0 beta versions on production or mission-critical websites. Instead, you should evaluate Beta 4 on a test server and site.
PluginInstall and activate the WordPress Beta Tester plugin on a WordPress install. (Select the “Bleeding edge” channel and “Beta/RC Only” stream.)Direct DownloadDownload the Beta 4 version (zip) and install it on a WordPress website.Command LineUse this WP-CLI command:
wp core update --version=7.0-beta4WordPress PlaygroundUse the WordPress Playground instance to test the software directly in your browser. No setup is required – just click and go!
WordPress 7.0 Beta 4 contains the ten security patches shipped in WordPress 6.9.2, and more than 49 updates and fixes since the Beta 3 release, including 14 in the Editor and 35 in Core.
Each beta cycle focuses on bug fixes. More are on the way, thanks to your help with testing. You can browse the technical details for all issues addressed since Beta 3 at these links:
GitHub commits for 7.0 since March 5, 2026
Closed Trac tickets for 7.0 since March 5, 2026
As always, a successful release depends on your confirmation during testing. So please download and test!
Props @peterwilson, @desrosj, @marybaum, @amykamala for peer reviewing.
This is a security release that features several fixes.
Because this is a security release,** it is recommended that you update your sites immediately**.
You can download WordPress 6.9.2 from WordPress.org, or visit your WordPress Dashboard, click “Updates”, and then click “Update Now”. If you have sites that support automatic background updates, the update process will begin automatically.
For more information on WordPress 6.9.2, please visit the version page on the HelpHub site.
The security team would like to thank the following people for responsibly reporting vulnerabilities, and allowing them to be fixed in this release:
A Blind SSRF issue reported by sibwtf, and subsequently by several other researchers while the fix was being worked on
A PoP-chain weakness in the HTML API and Block Registry reported by Phat RiO
A regex DoS weakness in numeric character references reported by Dennis Snell of the WordPress Security Team
A stored XSS in nav menus reported by Phill Savage
An AJAX query-attachments authorization bypass reported by Vitaly Simonovich
A stored XSS via the data-wp-bind directive reported by kaminuma
An XSS that allows overridding client-side templates in the admin area reported by Asaf Mozes
A PclZip path traversal issue reported independently by Francesco Carlucci and kaminuma
An authorization bypass on the Notes feature reported by kaminuma
An XXE in the external getID3 library reported by Youssef Achtatal
The WordPress security team have worked with the maintainer of the external getID3 library, James Heinrich, to coordinate a fix to getID3. A new version of getID3 is available here.
As a courtesy, these fixes are being backported, where necessary, to all branches eligible to receive security fixes (currently through 4.7). As a reminder, only the most recent version of WordPress is actively supported. The backports are in progress and will ship as they become ready.
This release was led by John Blackbourn. In addition to the security researchers mentioned above, WordPress 6.9.2 would not have been possible without the contributions of the following people: Dennis Snell, Alex Concha, Jon Surrell, Isabel Brison, Peter Wilson, Jonathan Desrosiers, Jb Audras, Luis Herranz, Aaron Jorbin, Weston Ruter, and Dominik Schilling.
WordPress 7.0 Beta 3 is available for download and testing!
This beta version of the WordPress software is still under development. Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, you should evaluate Beta 3 on a test server and site.WordPress 7.0 Beta 3 can be tested using any of the following methods:
PluginInstall and activate the WordPress Beta Tester plugin on a WordPress install. (Select the “Bleeding edge” channel and “Beta/RC Only” stream.)Direct DownloadDownload the Beta 3 version (zip) and install it on a WordPress website.Command LineUse this WP-CLI command:
wp core update --version=7.0-beta3WordPress PlaygroundUse the WordPress Playground instance to test the software directly in your browser. No setup is required – just click and go!
The scheduled final release date for WordPress 7.0 is April 9, 2026. The full release schedule can be found here. Your help testing Beta and RC versions is vital to making this release as stable and powerful as possible. Please continue checking the Make WordPress Core blog for 7.0-related posts in the coming weeks for more information. Thank you to everyone who is contributing with testing!
Catch up on what’s new in WordPress 7.0: Read the Beta 2 announcement for details and highlights.
Your help testing the WordPress 7.0 Beta 3 version is key to ensuring everything in the release is the best it can be. While testing the upgrade process is essential, trying out new features is equally important. This detailed guide will walk you through testing features in WordPress 7.0.
If you encounter an issue, please report it to the Alpha/Beta area of the support forums or directly to WordPress Trac if you are comfortable writing a reproducible bug report. You can also check your issue against a list of known bugs.Curious about testing releases in general? Follow along with the testing initiatives in Make Core and join the #core-test channel on Making WordPress Slack.
WordPress 7.0 Beta 3 contains more than 148 updates and fixes since the Beta 2 release, including 70 in the Editor and 78 in Core.
Each beta cycle focuses on bug fixes, and more are on the way with your help through testing. You can browse the technical details for all issues addressed since Beta 2 using these links:
GitHub commits for 7.0 since February 26, 2026
Closed Trac tickets for 7.0 since February 26, 2026
Tapping into the power of AI is even easier in Beta 3! The WP AI Client Connectors screen now dynamically registers providers from the WP AI Client registry, in addition to the 3 default providers, giving users more flexibility and command over AI integrations.
Through sun set and rise,
Beta 3 takes off and flies.
Seven soon arrives.
Props to @annezazu, @jeffpaul, @chaion07,* @audrasjb and @valentingrenier for proofreading and review.*
WordPress 7.0 Beta 2 is now ready for testing!
This beta version of the WordPress software is under development. Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, you should evaluate Beta 2 on a test server and site. You can test WordPress 7.0 Beta 2 in any of the following ways:
PluginInstall and activate the WordPress Beta Tester plugin on a WordPress install. (Select the “Bleeding edge” channel and “Beta/RC Only” stream.)Direct DownloadDownload the Beta 2 version (zip) and install it on a WordPress website.Command LineUse this WP-CLI command:
wp core update --version=7.0-beta2WordPress PlaygroundUse the WordPress Playground instance to test the software directly in your browser. No setup required – just click and go!
The scheduled final release date for WordPress 7.0 is April 9, 2026. The full release schedule can be found here. Your help testing Beta and RC versions is vital to making this release as stable and powerful as possible. Make sure to check the Make WordPress Core blog for 7.0-related posts in the coming weeks for more information. Thank you to everyone who contributes by testing!
Catch up on what’s new in WordPress 7.0: Read the Beta 1 announcement for details and highlights.
Your help testing WordPress 7.0 Beta 2 is key to ensuring everything in the release is the best it can be. While testing the upgrade process is essential, trying out new features is equally important. This guide on what to test in WordPress 7.0 will walk you through testing features in WordPress 7.0.
If you encounter an issue, please report it to the Alpha/Beta area of the support forums or directly to WordPress Trac if you are comfortable writing a reproducible bug report. You can also check your issue against a list of known bugs. Curious about testing releases in general? Follow along with the testing initiatives in Make Core and join the #core-test channel on Making WordPress Slack.
WordPress 7.0 Beta 2 contains more than 70 updates and fixes across the Editor and Core since the Beta 1 release.
Each beta cycle focuses on bug fixes; and more are on the way with your help through testing. You can browse the technical details for all issues addressed since Beta 1 using these links:
GitHub commits for 7.0 since February 20, 2026
Closed Trac tickets for 7.0 since February 20, 2026
Beta 2 also contains a new feature!
AI provider management is more intuitive in 7.0 Beta 2 with a new Connectors UI dashboard page. WordPress users can now manage external AI connections in a central place in wp-admin, under Settings > Connectors. The new UI enables users to add, delete, and update external connections. It is powered by an extensible, route-based architecture that allows plugins and themes to hook into the page and expand its functionality. The new Connectors page builds on PHP-based script and menu infrastructure, and adds route components powered by @wordpress/components and @wordpress/admin-ui. A new connections-wp-admin-init hook and registration APIs allow plugins to integrate cleanly. This makes managing external connections easier while giving developers a clearer path to extend the experience.
New, and fresh as dew
Crafted and refined for you:
Beta 2 breaks through.
Props to @4thhubbard, @annezazu, @audrasjb, @mukesh27, and @chaion07 for collaboration, proofreading and review.
WordPress 7.0 Beta 1 is ready for download and testing! This beta release is intended for testing and development only. Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, use a test environment or local site to explore the new features.
You can test WordPress 7.0 Beta 1 in any of the following ways:
PluginInstall and activate the WordPress Beta Tester plugin on a WordPress install. (Select the “Bleeding edge” channel and “Beta/RC Only” stream.)Direct DownloadDownload the Beta 1 version (zip) and install it on a WordPress website.Command LineUse this WP-CLI command: wp core update --version=7.0-beta1WordPress PlaygroundUse a 7.0 Beta 1 WordPress Playground instance to test the software directly in your browser. No setup required – just click and go!
The scheduled final release date for WordPress 7.0 is April 9, 2026. The full release schedule can be found here. Your help testing Beta and RC versions is vital to making this release as stable and powerful as possible. Thank you to everyone who contributes by testing!
Testing for issues is a critical part of developing any software, and it’s a meaningful way for anyone to contribute – whether or not you have experience. Details on what to test in WordPress 7.0 are available here.
If you encounter an issue, please share it in the Alpha/Beta area of the support forums. If you are comfortable submitting a reproducible bug report, you can do so via WordPress Trac. You can also check your issue against this list of known bugs.
Curious about testing releases in general and how to get started? Follow along with the testing initiatives in Make Core and join the #core-test channel on Making WordPress Slack. WordPress 7.0 will include new features that were previously only available in the Gutenberg plugin. Learn more about Gutenberg updates since WordPress 6.9 in the What’s New in Gutenberg posts for versions 22.0, 22.1, 22.2, 22.3, 22.4, 22.5 & 22.6.
WordPress 7.0 boasts numerous upgrades in the editing and admin experience, delivering enhanced real time collaboration, refined customizability, new dashboard styles, and an expanded developer toolbox for people who create, design, and build with WordPress every day.
Working as a team just got easier with the ability for multiple users to edit together in real time, while visual revisions allow a visual comparison between page versions, adding agility to the creation and review process. Working with patterns has been simplified, making layout updates and content changes more intuitive, while view transitions smoothly move you from screen to screen as you click.
New and improved blocks and design features in 7.0 make sites more customizable, with video embed backgrounds in the Cover block, a responsive-enabled Grid block, and new Icons, Breadcrumbs and Heading blocks. An updated Navigation block makes menu changes easier and more reliable in fewer steps. Responsive, mobile-friendly controls in 7.0 allow you to hide or reveal blocks based on screen size, while client-side media handling speeds up media processing. The Font Library screen for managing installed fonts is now enabled for all themes, so site editors are always able to browse, install, and organize fonts.
For developers, it’s now easier to build modern experiences while staying aligned with Core principles. The new WP AI Client in WordPress 7.0 brings a layer into Core that allows leveraging of AI models from any provider within the WordPress framework. This means plugins and themes can tap into any AI model to expound on its endless options. 7.0 offers even more versatility with the Client Side Abilities API that introduces a standardized way to register and run “abilities” in the browser, supporting richer, more consistent workflows. Additionally, 7.0 introduces PHP-only block registration with auto-generated inspector controls, adding a new dimension to block creation, while Block Bindings updates for pattern overrides expands support to custom dynamic blocks, giving block creators more options.
Needless to say, this release offers a wide range of flexibility to creators, teams and developers, while bringing a visual refresh to the admin experience you know and love with a fresh default style.
Building on the momentum started in WordPress 6.9, the ability for teams to create and edit together is more refined and robust in 7.0. With this version of WordPress multiple users can edit and collaborate on the same post or page in real time, with data syncing and stabilized notes for smoother teamwork and a more streamlined editing and review process.
Real Time Collaboration: Teams can now edit posts and pages together live from multiple locations, with offline editing and data syncing enabled, and a new default HTTP polling sync provider with options for plugins or hosts to include websocket support. With this collaborative content creation workflow, teams can brainstorm more effectively and boost productivity. For the beta period, real-time collaboration is opt-in in order to get broader feedback and testing.
Notes: 7.0 introduces real time syncing of notes that helps facilitate collaboration, a keyboard shortcut for new notes, and a series of quality-focused fixes that bring more stability to the Notes feature.
WordPress 7.0 gives the wp-admin experience a boost with a fresh default color scheme, and a cleaner, more modern looking dashboard, while keeping the interface familiar. The upgraded dashboard enhances the editing experience with new visual revision comparisons, and smooth transitioning between screens.
Visual Revisions: Working with revisions is even better in 7.0 with the added ability to make visual comparisons to revision versions within the editor.
View transitions: Cross-document view transitions in the dashboard offer visual continuity with seamless movement from screen to screen.
Creators have more flexibility in 7.0 with new tools for content and design, enhanced editing controls, and attention to mobile friendliness.
Responsive Editing Mode: Block visibility is now more responsive and mobile-friendly, with the ability for blocks to be displayed or hidden based on screen size.
Pattern Editing and contentOnly interactivity: WordPress 7.0 introduces pattern-level editing modes, a tree view for buttons and list blocks, and the ability to opt out of the default content only mode. The new Spotlight mode helps you isolate content in patterns and notes, while the Isolated Editor mode can be used for editing symbols and reusable pieces like synced patterns, template parts, or navigation.
Block supports and design tools: 7.0 includes text line indent support, text column support, aspect ratios for wide and full images, dimension width and height support, and dimension presets, tools and controls.
7.0 delivers a series of new and improved blocks and block features, a streamlined navigation workflow, and more versatile design options like video embeds as section backgrounds.
Navigation Block: Navigation workflow is now more intuitive and clear, with improved editing and presentation. 7.0 introduces customizable navigation overlays as template parts, including mobile version overlays that can be hidden or revealed based on custom breakpoint settings.
Heading Block: Heading levels are now available as block variations, giving more control over page hierarchy and design.
New blocks: 7.0 makes building pages more diverse with new Breadcrumbs and Icons blocks.
Cover block embedded videos: Video embeds can now be used as a background in the cover block, opening up opportunities for sleeker and more creative designs.
The Grid block is now responsive-enabled allowing grid-based layouts to adapt more smoothly across screen sizes.
The Gallery block now has lightbox support that lets the user click through and view each gallery image.
Working with WordPress on the backend is now more robust for developers, with new and enhanced API features that support flexibility and lay a foundation for future advancements. The Client Side Abilities API provides a client-side registry for WordPress capabilities that allows you to tap into new and innovative website options. WordPress 7.0 offers even more by introducing the Web Client AI API to Core, enabling access to generative AI models in one central interface.
Web Client AI API: The new AI client and API acts as a command center for accessing and communicating with generative AI models, with providers remaining external to WordPress Core, and Abilities API integration.
Abilities and Workflows API: With the new client side abilities package users have access to new and hybrid abilities, filter and search functionality for abilities, and an improved command palette and UI.
Blocks and patterns created on the server: WordPress 7.0 boasts the ability for PHP-only blocks and patterns to be generated server-side and auto-registered with the Block API.
DataForm: Introducing a new details layout, new controls (combobox, adaptiveSelect), and updated trigger for panel layout (dedicated edit button). Additionally, the initial iteration for validation is complete: all controls have support, and all layouts display error messages.
DataViews: DataViews has a new activity layout, and a foundation has been laid to be able to register 3rd party types in future releases.
CodeMirror update: CodeMirror has been updated to version 5.65.40, aiding more flexible extensibility and library options.
WordPress 7.0 introduces Client-side media processing, leveraging the browser’s capabilities to handle tasks, like image resizing and compression, for smoother image processing. This enables the use of more advanced image formats and compression techniques, and reduces demand on the web server; providing a more efficient media handling process for both new and existing content, and supporting smoother media workflows.
With so many options and enhancements in WordPress 7.0 Beta 1, this is still only the beginning. You can expect future releases to be even better.
As sun kisses moon,
Beta 1 ignites in bloom…
Seven-oh lands soon.
Props to @ellatrix, @jeffpaul, @annezazu, @chaion07, @zunaid321, @audrasjb, @mukesh27, @ankit-k-gupta, @oandregal, @westonruter, @karmatosed, @bph for reviewing and collaborating on this post!
WordPress 6.9.1 is now available!
This minor release includes fixes for 49 bugs throughout Core and the Block Editor, addressing issues affecting multiple areas of WordPress including the block editor, mail, and classic themes. For a full list of bug fixes, please refer to the release candidate announcement.
WordPress 6.9.1 is a short-cycle maintenance release. The next major version of WordPress will be 7.0; it is scheduled for release on 9 April 2026 at WordCamp Asia.
If you have sites that support automatic background updates, the update process will begin automatically.
You can download WordPress 6.9.1 from WordPress.org, or visit your WordPress Dashboard, click “Updates”, and then click “Update Now”. For more information on this release, please visit the HelpHub site.
This release was led by Aaron Jorbin and Aki Hamano.
WordPress 6.9.1 would not have been possible without the contributions of the following people. Their asynchronous coordination to deliver maintenance fixes into a stable release is a testament to the power and capability of the WordPress community.
Aaron Jorbin, Aaron Robertshaw, acmoifr, Adam Silverstein, Adil Öztaşer, Aki Hamano, Alexander Bigga, amanandhishoe, Andrew Serong, Bernie Reiter, brumack, David Arenas, David Baumwald, Deepak Gupta, Deepak Prajapati, Dennis Snell, digitalblanket, Ella Van Durpe, Fabian Kaegy, George Mamadashvili, Hit Bhalodia, iflairwebtechnologies, Isabel Brison, Jaydeep Das, Jb Audras, Jeff Golenski, Jeffrey Paul, jhtjards, Joe Dolson, John Blackbourn, Jon Surrell, Jonathan Desrosiers, Jorge Costa, Justin Tadlock, Karthick, Kirtikumar Solanki, Lena Morita, luisherranz, Madhavi Shah, Manuel Camargo, Maud Royer, Mehraz Morshed, Monarobase, mrwweb, Mukesh Panchal, Muryam Sultana, mydesign78, Narendra Sishodiya, Nik Tsekouras, Ninos, Noruzzaman, Olga Gleckler, Ophelia Rose, Ov3rfly, Ozgur Sar, Paragon Initiative Enterprises, Pascal Birchler, Pavel Vybíral, Peter Wilson, pmbs, Presskopp, r1k0, ramonopoly, Riad Benguella, Ricardo S., Rolly Bueno, Sarah Norris, Scott Reilly, Sergey Biryukov, Shazzad Hossain Khan, siliconforks, Soyeb Salar, spielers, Stephen Bernhardt, studio_m, Takashi Irie, Takashi Kitajima, threadi, Tobias Bäthge, Tomoki Shimomura, Umesh Singh, Vania, Weston Ruter, WFMattR, wolf45, zoe20
To get involved in WordPress core development, head over to Trac, pick a ticket, and join the conversation in the #core channel. Need help? Check out the Core Contributor Handbook.
Props to @audrasjb, @davidbaumwald, @westonruter, @jeffpaul, @presskopp for proofreading.
Good news, everyone! WordPress 7.0 has a new release date: May 20th, 2026! Thank you all for your flexibility in these recent weeks while W…