Table of contents of the article:
WordPress 7.0 is expected on May 20, 2026, and promises to be one of the most exciting releases in recent years. Not so much because it introduces a single revolutionary change, but because it appears to mark a new milestone for the entire WordPress ecosystem: block editor, collaboration, administration, performance, API, user experience, and developer tools.
After years in which the Gutenberg project has profoundly changed the way we create content, build layouts and manage themes, WordPress 7.0 should represent another step towards a more modern, more collaborative, and more consistent platform. It's no longer just about "writing articles" or "managing pages," but about offering a complete environment for producing, reviewing, designing, and publishing digital content that's increasingly similar to an advanced editorial suite.
The May 20, 2026, release date comes after a delay compared to the initial schedule. This detail is significant: the delay doesn't appear to be related to marginal reasons, but rather to the need to consolidate certain architectural choices, particularly regarding real-time collaboration and the overall stability of the release. In other words, WordPress 7.0 isn't a version to be interpreted simply as "new features," but as a major release that seeks to lay a more solid foundation for what comes next.
An important release, but one to be read with caution.
When talking about WordPress 7.0, it's easy to fall into the temptation of imagining a completely new version, almost a break from the past. In reality, WordPress rarely does this. Its strength, but also its limitation, is the need to maintain compatibility with a huge ecosystem: themes, plugins, page builders, custom installations, e-commerce, membership, LMS, multisite, shared hosting, enterprise environments and very different stacks.
For this reason, it's more realistic to expect an evolutionary release than a sudden revolution. WordPress 7.0 should bring visible new features, but also many less visible changes: editor refinements, API improvements, performance optimizations, bug fixes, greater interface consistency, and a consolidation of features already introduced in previous versions.
This approach is consistent with the CMS's recent history. WordPress has already undergone a profound transformation with the introduction of the block editor, the Site Editor, block themes, global styles, and patterns. Version 7.0 shouldn't erase this legacy, but rather make it more mature, reliable, and usable even in more complex professional contexts.
Real-time collaboration: the most anticipated (and postponed) innovation
The most talked about feature in WordPress 7.0 is undoubtedly real-time collaboration in the block editor. The goal is to allow multiple users to work on the same content simultaneously, reducing editorial conflicts and bringing WordPress closer to the experience offered by modern collaborative tools.
For those working in editorial offices, agencies, marketing departments, or distributed teams, this could be a significant breakthrough. WordPress already manages revisions, automatic saving, and edit locks, but the workflow often remains rigid: if one user is editing content, another risks overwriting changes or having to wait. Real-time collaboration, on the other hand, aims to make this process more fluid.
Imagine an editorial office where an author writes the text, an editor works on the titles, an SEO specialist modifies the metadata and content structure, and a graphic designer works on the visual blocks. More advanced collaborative management could reduce downtime, duplication, and manual steps.
However, Matt has already officially communicated that this feature will not be part of branch 7.
However, it's also one of the most delicate aspects. Real-time collaboration is not easy to implement in a distributed CMS like WordPress, installed on very different hosting providers. We're not talking about a centralized SaaS service where the entire infrastructure is controlled by a single provider. WordPress must run on low-cost servers, VPS, clusters, containerized environments, managed hosting, multisite configurations, and installations with extremely heterogeneous plugins.
Precisely for this reason, it's reasonable to expect a feature carefully introduced in subsequent releases after version 7, likely with initial limitations, well-defined use cases, and a strong focus on stability. Rather than an immediate copy of Google Docs within WordPress, we should expect the first major step towards native editorial collaboration, destined to improve over time.
Gutenberg enters a more mature phase
WordPress 7.0 is part of the so-called Gutenberg Phase 3, which focuses on collaboration and editorial workflows. After an initial phase focused on the block editor and a subsequent phase focused on site customization, the project is moving toward tools for teamwork, content management, and task organization.
This shift in perspective is important. For years, Gutenberg was perceived primarily as a visual editor, often compared to page builders like Elementor, Divi, or Beaver Builder. In reality, the project is much broader: Gutenberg has gradually become the driving force behind WordPress' administrative and design experience.
With WordPress 7.0, we could see further integration between the editor, Site Editor, patterns, templates, global styles, and management tools. The goal appears to be a more seamless experience: less fragmentation between "content," "theme," "template," and "layout"; more continuity between writing, design, and publishing.
This doesn't mean all users will automatically be satisfied. Some of the community still prefers the classic approach, based on a traditional editor, custom fields, PHP themes, and more developer-friendly tools. However, it's clear that the WordPress project is now moving toward an increasingly block-based interface.
Administration improvements
Another key theme concerns the modernization of the admin area. The WordPress dashboard is familiar, stable, and recognizable, but it retains many legacy elements. For some users, it's simple and straightforward; for others, it seems dated, inconsistent with the Site Editor, and not always suited to modern workflows.
WordPress 7.0 could continue the work of streamlining the interface, particularly through more consistent components, more modern data views, and better organization of the administrative screens. In recent development cycles, there has been a lot of talk about DataViews, i.e., more advanced ways to visualize, filter, and manage information within the administration.
This may seem like a technical detail, but it isn't. Managing content, patterns, templates, pages, media, users, and settings becomes increasingly complex as WordPress is used as a structured CMS and not just a blogging platform. Having more organized, filterable, and consistent interfaces can greatly improve daily work.
For agencies and developers, a more modern dashboard could also mean less need to build custom interfaces for clients. For end users, however, it could translate into a smoother learning curve and greater operational clarity.
Templates, patterns and site management
Another area to consider is the management of templates, patterns, and reusable components. In recent years, WordPress has pushed heavily on patterns, which are reusable block compositions that allow for faster page and section building. This approach is particularly important for block themes and Full Site Editing.
With WordPress 7.0, we can expect further improvements in managing these elements. The goal is to make it easier to understand what's being modified: content, a template, a part of the theme, a synchronized pattern, or a local variant.
This point is crucial because one of the most frequent criticisms of the Site Editor concerns the confusion between different levels. A less experienced user might edit a template thinking they're changing a single page, or alter a synchronized pattern without realizing the overall effect.Any improvements in clarity, preview, organization, and change control would therefore be very welcome.
For professionals, the maturation of templates and patterns can open up interesting scenarios: more consistent design systems, internal component libraries, reusable layouts, more standardized publishing processes, and less dependence on external page builders.
Performance: an increasingly clear priority
Performance has become a key concern for WordPress, both for technical reasons and for SEO and user experience. A modern CMS must be flexible, but it cannot become unnecessarily heavy. Each new feature must also be evaluated in terms of its impact on loading, queries, memory, JavaScript, CSS, and resource consumption.
WordPress 7.0 should continue the optimization efforts seen in previous versions. Expect attention to editor loading, asset management, block performance, rendering, caching, and overhead reduction where possible.
This is particularly important because WordPress is often criticized for being slow, even when the real culprit is overloaded themes, poorly developed plugins, inadequate hosting, or unoptimized configurations. However, the core still needs to do its part.
In a context where Core Web Vitals, response times, mobile experience and resource optimization are increasingly important, every core improvement can have positive effects on millions of sitesHowever, it's important to be realistic: no WordPress release will automatically transform a slow site into a fast one. The quality of your hosting, server configuration, caching, theme, plugins, and images will continue to make a huge difference.
Safety and compatibility
Every major release brings with it compatibility questions. WordPress 7.0 will be no exception. Themes and plugins will need to be tested, especially those that interact deeply with the editor, REST API, user roles, saving, revisions, custom blocks, and administrative interfaces.
You don't necessarily have to be afraid of upgrading, but you shouldn't approach it casually either. On simple showcase sites, the upgrade may be relatively straightforward. On WooCommerce, membership sites, LMSs, editorial portals, multisites, Bedrock installations, or environments with a lot of customization, it's advisable to proceed with greater caution.
Before updating a production site, it is a good idea to check:
- main theme and plugin compatibility;
- how the editor and custom blocks work;
- cache behavior, CDN and frontend optimizations;
- any PHP errors in the logs;
- correct functioning of forms, checkout, reserved areas and automations;
- compatibility with the PHP version in use.
The point is not to postpone the update indefinitely, but to include it in a correct process: staging, backup, testing, monitoring and then release to production.
What changes for developers and agencies
For developers, WordPress 7.0 will likely be a release worth watching closely. The most interesting new features might not only be those visible to end users, but also those hidden in the APIs, JavaScript components, block management, data interfaces, and collaborative workflows.
Custom block developers will need to ensure compatibility and best practices. Theme developers will need to continue to address the growing importance of block themes, the theme.json file, global styles, and visual editing logic. Those working on editorial plugins, workflows, reviews, approvals, and user roles will need to carefully monitor the evolution of real-time collaboration.
For agencies, WordPress 7.0 could become an opportunity to rethink the way sites are delivered to clients.As the administrative interface and editing tools become more powerful, defining permissions, roles, guidelines, and preconfigured components becomes even more important. A client left completely free within an increasingly powerful editor can cause harm; a client guided by a well-designed system, on the other hand, can work better and more autonomously.
What changes for those who manage corporate websites
For businesses, publishers, and marketers, WordPress 7.0 should be viewed primarily from an operational perspective. The question isn't just "what new features are there?", but "do these features improve my work processes?"
Real-time collaboration can be useful if multiple people are working on the same content. Pattern improvements can be helpful if the site uses recurring layouts. A more modern dashboard can be helpful if there's a lot of content to organize. Performance optimizations can be helpful if the site is already technically well-managed, however, on May 8, 2026, Matt explicitly announced that this feature will not be released in version 7 but will be postponed.
Conversely, those who use WordPress with a very basic approach may not notice the change as much. A small showcase site with just a few pages, a classic editor, and sporadic updates may not see any radical changes in their day-to-day operations. This doesn't mean the update is useless, but the value of the release will depend heavily on the type of project.
Beware of plugins and page builders
One of the most delicate aspects concerns the relationship between WordPress 7.0 and the major page builders. Elementor, Divi, WPBakery, Bricks, Oxygen, and other tools have built parallel ecosystems, often with their own logic. The evolution of the core towards blocks, Site Editors, and increasingly advanced visual tools may reduce, at least in some cases, the need for external page builders.
However, don't expect an immediate replacement. Many page builders still offer advanced features, consolidated workflows, templates, widgets, and integrations that the core doesn't fully cover. WordPress 7.0 will likely continue its journey toward a stronger native experience, but coexistence with page builders will remain a reality for a long time to come.
The real question for those who develop or manage websites will be strategic: should we continue to rely on heavy, highly proprietary page builders, or should we start investing more in native blocks, theme.json, patterns, and block themes? WordPress 7.0 could make this question even more relevant.
How to prepare for the update
Preparing for WordPress 7.0 should begin before the final release, especially for those running large sites. It's not necessary to install release candidates in production, but it can be very helpful to test them in test environments.
A good approach is to clone the site to staging, update the core, theme, and plugins, enable debug logging, and test the main features. For example, for a WooCommerce e-commerce site, you should test the shopping cart, checkout, payments, transactional emails, customer area, coupons, shipping, and management integrations. For a publishing site, you should check the publishing workflow, editors, roles, revisions, taxonomies, internal search, and backend performance.
It's also a good idea to check your PHP version. Modern WordPress versions run best on up-to-date stacks, and continuing to use outdated PHP versions exposes you to security, performance, and compatibility issues. A major CMS update might be the right time to review your server environment as well.
Should I upgrade now?
The most prudent answer is: it depends on the type of site. For test sites, personal blogs, or non-critical projects, updating immediately may be acceptable, especially if you want to experiment. For corporate sites, WooCommerce, high-traffic portals, or mission-critical installations, it's wiser to wait a few days or weeks, monitoring for any bugs that emerge after the release.
This doesn't mean ignoring the update. It means managing it professionally. Major releases can introduce small compatibility issues that are quickly fixed in subsequent versions. Waiting for an initial minor corrective release, or at least for initial feedback from the community, may be a reasonable option for sensitive environments.
The worst thing, however, is blindly updating without backups, staging, or a rollback plan. WordPress is generally reliable, but every real site is a unique combination of theme, plugins, custom code, server, cache, and external services.
A release that looks to the future
WordPress 7.0 shouldn't be interpreted solely for what May 20, 2026, will bring, but for the direction it points. The project seeks to transform WordPress into an increasingly collaborative, modular, and visual platform, without completely losing compatibility with the past.
It's a huge challenge. On one side, there are users who want simplicity, stability, and continuity. On the other, there are professionals and companies demanding modern tools, collaboration, performance, better APIs, and an experience closer to the standards of contemporary SaaS platforms.
WordPress must bring these worlds together. It must continue to function on a small personal blog while remaining credible for complex publishing projects, e-commerce, public administrations, companies, and digital agencies.
Conclusion
WordPress 7.0, scheduled for release on May 20, 2026, promises to be a significant release not only for the features it will introduce, but also for the journey it represents. Real-time collaboration has been postponed and will therefore not be released in version 7. The consolidation of Gutenberg, improvements to administration, the evolution of templates and patterns, performance optimizations, and new opportunities for developers all point to a platform undergoing a profound transformation.
Don't expect instant miracles, though. WordPress 7.0 won't automatically make every site faster, it won't suddenly eliminate the need for plugins, and it won't solve all the complexities of the ecosystem. Instead, it will be a new piece in an evolutionary process that began years ago and is destined to continue.
For those managing professional websites, the advice is clear: follow the release, test it on staging, check compatibility and performance, and update methodically, not impulsively. For developers and agencies, however, WordPress 7.0 will be an opportunity to rethink workflows, tools, components, and development strategies.
The feeling is that this release shouldn't be judged solely on its release day, but in the months to come, when its innovations truly begin to filter into daily work processes. WordPress 7.0 may not be a noisy revolution, but it could represent one of the most important steps towards the future of the world's most used CMS.
