WordPress is getting close to its next major release. WordPress 7.0 Release Candidate 4 is now available for testing, and the final release is currently scheduled for May 20, 2026. As always with release candidates, WordPress recommends testing this version on a staging, local, or test site — not on a production website.
At the same time, the Gutenberg project continues to move forward. Gutenberg 23.1, released on May 7, 2026, introduces new experiments for content management, a new Media Editor experience, and updates to the @wordpress/ui package.
For everyday WordPress users, this may sound technical. But for creators, bloggers, small business owners, theme users, and developers, these updates show where WordPress is heading: a more powerful editor, better content workflows, stronger design tools, and a more flexible block-based publishing experience.
WordPress 7.0 RC4 is for testing, not production
The most important thing to know is simple: WordPress 7.0 RC4 is not the final stable release.
A release candidate is one of the last stages before a major version becomes public. It is close to final, but it still needs testing from the community. WordPress specifically recommends evaluating RC4 on a test server or test site rather than installing it on production or mission-critical websites.
That means site owners should not rush to upgrade their live websites yet. If you run a business site, WooCommerce store, blog, or client website, wait for the final WordPress 7.0 release and test your theme and plugins before updating.
For developers and theme authors, however, now is the right time to test compatibility.
WordPress 7.0 is scheduled for May 20, 2026
According to the official WordPress release announcement, the final release of WordPress 7.0 is scheduled for May 20, 2026. The release date was updated after contributors extended the 7.0 cycle to finalize architectural details and improve stability.
This makes WordPress 7.0 one of the most important releases to watch in 2026. It is not only a version number update. It continues WordPress’s long-term move toward a block-first editing and site-building experience.
For users of modern WordPress themes, especially block-ready and editor-friendly themes, this release matters because many improvements are connected to the editing workflow.
What’s new in WordPress 7.0?
The official WordPress 7.0 Field Guide outlines many developer-focused changes, enhancements, and compatibility notes. It is especially useful for theme developers, plugin authors, and agencies preparing products for the new release.
For non-technical users, the bigger picture is easier to understand: WordPress 7.0 focuses on making the editor more capable, improving content workflows, and giving users more control over how content appears across different devices.
Here are some of the most interesting areas to watch.
Better block visibility by device
One of the most practical improvements coming with WordPress 7.0 is viewport-based block visibility.
This feature allows users to show or hide blocks depending on the device type, such as desktop, tablet, or mobile. In other words, a block can be visible on desktop but hidden on mobile, without affecting the layout for other viewports.
This is especially useful for creators and small businesses building landing pages, homepages, product sections, promotional banners, or editorial layouts.
For example, a site owner could show a wider visual section on desktop, then hide it on mobile and use a simpler mobile-friendly block instead.
Previously, many users relied on custom CSS, third-party page builders, or extra plugins for this type of control. Bringing this kind of flexibility closer to WordPress core makes the block editor more useful for real website building.
Editor improvements for modern publishing workflows
WordPress has been steadily improving the editor for years, and WordPress 7.0 continues that direction.
The Field Guide notes a wide range of editor-related updates, including improvements that matter to developers and site builders working with blocks, styles, layouts, and admin experiences.
For content creators, this means the WordPress editor is becoming less like a simple writing screen and more like a complete publishing environment.
That matters because many modern websites are no longer just blogs. A creator website may include articles, landing pages, newsletters, product pages, resource hubs, and sales pages. A small business site may need service pages, testimonials, comparison sections, and promotional blocks.
The more capable the editor becomes, the easier it is to build and update these pages without touching code.
Real-time collaboration will not ship in WordPress 7.0
One major feature that many people were watching is real-time collaboration. However, WordPress has confirmed that real-time collaboration will not ship in WordPress 7.0.
The decision was made because the current approach was not considered robust enough for core at this stage. The concerns included surface area, race conditions, server load, memory efficiency, and recurring bugs found during testing.
This is an important detail. Real-time collaboration is a big feature, and adding it to WordPress core too early could create problems for site owners, hosting providers, plugin developers, and theme authors.
For now, the safer choice is to keep improving and testing the feature outside the final 7.0 release.
Gutenberg 23.1 brings new content management experiments
While WordPress 7.0 prepares for release, Gutenberg continues to act as the testing ground for future editor features.
Gutenberg 23.1 introduces two notable experiments focused on managing content inside the editor: a Custom Taxonomies management screen and a new Media Editor.
The Custom Taxonomies screen is especially interesting for content-heavy websites. If developed further, it could make it easier for users to create and manage content structures directly from the WordPress interface.
For publishers, bloggers, documentation sites, directories, and resource-heavy websites, taxonomy management is important. Categories and tags are only the beginning. Many advanced content websites need more flexible ways to organize posts, products, guides, or resources.
A new Media Editor experience
Gutenberg 23.1 also introduces a new Media Editor experiment, designed to improve image editing within the WordPress media flow.
This matters because images are central to modern websites.
Whether you run a blog, WooCommerce store, portfolio, magazine, or creator website, you probably work with images every day. Better media handling can make publishing faster and reduce the need to jump between WordPress and external tools for simple edits.
For ThemeMuse users, this is especially relevant because clean visual presentation is a big part of modern theme design. Better media tools can make it easier to prepare featured images, product visuals, blog graphics, and homepage sections.
Updates to the WordPress UI package
Gutenberg 23.1 also updates the @wordpress/ui package with new primitives, including Drawer and Autocomplete. These are more developer-focused changes, but they matter for the broader WordPress ecosystem.
When WordPress provides better interface components, plugin and block developers can build more consistent experiences inside the dashboard and editor.
For users, this can eventually mean cleaner settings screens, better block controls, smoother side panels, and more polished editor extensions.
What should WordPress site owners do now?
If you manage a live WordPress website, the best approach is cautious and simple.
Do not install WordPress 7.0 RC4 on a live website. Use a staging site, local environment, or test installation if you want to explore what is coming. WordPress itself recommends testing RC releases away from production websites.
Before updating to WordPress 7.0 final, site owners should:
- Create a full backup.
- Update plugins and themes.
- Test the website on staging.
- Check key pages, forms, and checkout flows.
- Confirm that custom blocks and layouts still work.
- Update the production site only after testing.
This is especially important for WooCommerce stores, membership sites, learning platforms, and business websites where downtime can affect revenue.
What should theme and plugin developers check?
Theme and plugin developers should use this release candidate phase to test compatibility.
Important areas to check include:
- block editor behavior
- custom blocks
- editor styles
- theme.json settings
- layout and spacing controls
- block supports
- responsive visibility behavior
- admin UI screens
- media handling
- template parts and patterns
- plugin settings screens
If your product depends heavily on the block editor, WordPress 7.0 is an important release to test early.
What this means for ThemeMuse users
For ThemeMuse users, the direction is encouraging.
WordPress continues to improve the editor, design tools, content workflows, and media experience. This supports the kind of websites ThemeMuse themes are designed for: clean, flexible, content-friendly websites for creators, bloggers, small businesses, and online stores.
Themes like Techfest, Swimsy, and Lumira benefit from a stronger WordPress editing experience because users can build and manage better pages with less friction.
As WordPress continues to move toward a more flexible block-first workflow, choosing a clean and well-structured theme becomes even more important. A good theme should not fight the editor. It should give users a solid foundation and let WordPress handle content creation naturally.
Final thoughts
WordPress 7.0 is close, and RC4 gives developers and advanced users a chance to test before the final release. The official final release is currently scheduled for May 20, 2026, while Gutenberg 23.1 continues to introduce experimental improvements for content management, media editing, and developer UI tools.
For most site owners, the best move is to wait for the stable release and test carefully before updating. For developers and theme authors, now is the time to check compatibility.
The bigger story is clear: WordPress is becoming a more powerful publishing and site-building platform. With better block controls, stronger editor workflows, and continued Gutenberg improvements, the future of WordPress is increasingly focused on giving creators and site owners more control without requiring custom code.
For ThemeMuse users, that is good news. A clean WordPress theme, paired with a stronger editor, makes it easier to build websites that are fast, modern, and comfortable to manage over time.