WordPress 7.0 is shaping up to be one of the more consequential recent releases and fully deserving of a major version. It is the first major WordPress release planned for 2026, which makes the direction of this cycle especially important.
What makes WordPress 7.0 remarkable is the pattern revealed when one looks at the changes. Core has spent this cycle pushing on collaboration, AI infrastructure, more flexible block controls, navigation improvements, and continued work around modern admin and editing interfaces such as DataViews and DataForm. That combination makes WordPress 7.0 feel less like a routine feature release and more like a release about foundations.
What stands out about WordPress 7.0
The best way to frame WordPress 7.0 is a workflow release with platform implications. It does not try to reinvent WordPress in one go. Instead, it strengthens the pieces that affect how modern teams actually use the CMS, from editorial collaboration to design control to future-facing AI integrations. Even the admin story should be read that way. There is ongoing modernization work in and around wp-admin, especially through DataViews and related interfaces, but the outcome is an evolution, not a wholesale redesign.
That matters because WordPress has often been criticized from two sides at once. On one hand, it may seem overly reliant on plugins for features that many site owners now anticipate as standard. Conversely, it may appear conservative when compared to newer tools that are built around collaboration, structured workflows, and AI-adjacent features. WordPress 7.0 does not solve every one of those tensions, but it moves the platform in a more coherent direction than a typical major release.
AI foundations arrive in Core
One of the biggest additions in WordPress is the new AI Client, a built-in, provider-agnostic PHP API that lets plugins send prompts to AI models and receive results through a consistent, WordPress-native layer. Instead of every plugin building its own connectors, credential logic, and provider handling from scratch, Core now offers a common abstraction. WordPress handles routing requests to a suitable model from a provider the site owner has already configured.
That distinction is important because it corrects the biggest misconception around this release. WordPress 7.0 is not shipping as a built-in AI writing assistant. Core is not suddenly turning the editor into a chatbot. What it is doing is much more strategic: creating the plumbing that plugins, themes, and future WordPress features can rely on when they need AI capabilities. In practical terms, that is a stronger long-term move than shipping a flashy assistant bolted onto the interface.
Alongside the AI Client, WordPress introduces the Connectors API, a framework for registering and managing connections to external services, with the initial focus on AI providers. Core describes it as the standard layer for provider discovery, API key management, and admin UI around those integrations. The first flagship provider plugins developed by the project are for Anthropic, Google, and OpenAI.
That is where the new Settings → Connectors screen becomes especially useful. Before this, AI-related WordPress setups often meant scattered API keys and separate configuration screens across multiple plugins. WordPress 7.0 centralizes that model. It does not eliminate plugin-level innovation, but it does create a cleaner administrative baseline for sites that want to work with AI in a more organized way. For WordPress agencies and product teams, that is exactly the kind of unglamorous infrastructure that pays off later.
WordPress 7.0 also improves revisions in a way that feels overdue. Gutenberg 22.6 added visual change tracking inside in-editor revisions. Added text was shown in green and underlined, removed text was shown in red with a strikethrough, and formatting or attribute changes were highlighted visually. Entire added or removed blocks are also marked, making revision review far easier than the old markup-heavy experience.
That change matters because revisions are not just a safety feature. They are a workflow tool. When teams can review what changed without fighting raw HTML or jumping to a separate mental model for comparison, approvals become faster and less error-prone. WordPress has had revisions for years, but WordPress 7.0 makes them more legible, more visual, and more credible for modern content operations.
Design and editor controls get more practical
Typography is the practical win in this release. Gutenberg 22 extended the Font Library and Global Styles support to classic and hybrid themes, not just block themes. WordPress testing materials for 7.0 also confirm that classic themes get a dedicated Appearance → Fonts page, which makes font management feel more like a native admin workflow instead of a feature reserved for block-theme users.
That may sound incremental, but it closes a real gap. A large number of production WordPress sites still run classic themes or hybrid setups. Giving those sites a cleaner path to upload, activate, and manage fonts directly in WordPress makes the platform more consistent and reduces the need for theme-specific workarounds or extra typography plugins. It is a small feature with outsized day-to-day value.
Navigation also gets a meaningful upgrade. WordPress 7.0 introduces customizable navigation overlays for mobile menus, replacing the old fixed overlay behavior with editable overlay template parts in a new navigation-overlay area. Site owners can build overlays from blocks and patterns in the Site Editor, and WordPress includes a dedicated Navigation Overlay Close block to make those overlays usable and styleable.
Mobile menus are often one of the last stubborn UI areas in a block theme that still feel rigid or semi-hardcoded. Navigation overlays make that space editable in a more native way. For block-theme users, this means more control over branding, layout, and conversion elements inside mobile navigation, not just minor cosmetic tweaks.
WordPress 7.0 also pushes more control down to the individual block level. The most obvious example is viewport-based block visibility, which allows blocks to be shown or hidden for desktop, tablet, or mobile. Core notes that these controls are available through the block toolbar, inspector, and command palette and that blocks hidden by the viewport still render in the DOM and are hidden via CSS.
The second major improvement is custom CSS for individual block instances. WordPress adds a Custom CSS field to the Advanced panel, which finally gives users a built-in way to style a single block instance without the old workaround of adding a class name and then writing separate global CSS. For more advanced users, that is a major quality-of-life improvement. For less technical users, it lowers the friction of one-off design adjustments inside Core itself.
Taken together, these design and editor changes point in the same direction: WordPress is trying to reduce the distance between “I need one small custom behavior” and “I need a plugin or custom dev work.” It doesn’t close the gap entirely, but it does narrow it where site owners feel it most.
New blocks arrive, existing blocks keep improving
WordPress 7.0 adds two especially notable blocks. The first is the new Breadcrumbs block, a block that can be placed once, such as in a header, and then automatically reflect the site’s navigation hierarchy. For sites that want clearer wayfinding and cleaner information architecture, having breadcrumbs as a native block is a meaningful addition.
The second is the new Icon block. Gutenberg 22.6 introduced it as an SVG icon block supported by an API for registering icons on the server side and a REST endpoint for searching and filtering icons. The initial library comes from the wordpress/icons package, and the architecture is deliberately extensible so that the icon ecosystem can grow over time.
Existing blocks also become better. Gutenberg 22.6 added lightbox navigation to the Gallery block, which means users can move between gallery images without closing the overlay. The versatile HTML block now has three tabs: HTML, CSS, and JavaScript. Keyboard navigation and screen reader announcements are included too, which is the kind of detail that makes the feature more mature instead of merely more decorative.
The Grid block is also moving toward more responsive behavior when columns are set, and Core planning materials for 7.0 explicitly listed heading levels as Heading block variations among the targeted improvements for the release.
In summary, the release is not only adding new pieces; it is also tightening up a lot of the block-level rough edges that accumulate over time. The headings selector was always one thing that required an update.
Impact for site owners, teams, and agencies
For site owners, WordPress 7.0 is a release about doing more inside Core with less friction. Typography, responsive visibility, mobile navigation overlays, breadcrumbs, and block-level CSS all move common site-building tasks closer to native WordPress workflows.
For editorial teams, the most important story is collaboration plus revisions. Real-time collaboration is still being handled carefully, but the direction is unmistakable, and visual revision diffing already makes WordPress more credible as a content production environment for multiple stakeholders.
For developers and agencies, the real strategic shift is the platform layer. The AI Client and Connectors API create a cleaner foundation for AI-enabled products, while DataViews, navigation overlays, and more granular block controls continue the broader effort to modernize how WordPress behaves under the hood and in the admin.
Editorial: Why the release of 7 feels bigger!
We have followed WordPress core development long enough to be skeptical of grand narratives around any single release. WordPress 7.0 still earns a stronger reaction than most because it feels less like a collection of unrelated enhancements and more like a release where several long-running threads finally start to align. AI is being treated as infrastructure. Collaboration is being treated as a core workflow problem. And more of the design and editing experience is being pushed back to native Core capabilities, instead of custom themes.
That doesn’t mean every promise is fulfilled. Real-time collaboration still has constraints. WordPress is still evolving its modern admin interfaces rather than replacing everything at once. And AI support in 7.0 is more architectural than end-user-facing. But that restraint is part of what makes this cycle more convincing. The project is making foundational decisions first, rather than chasing headlines with a thin layer of surface-level novelty.
Our final take on WordPress 7.0
WordPress 7.0 looks substantial for a simple reason: it improves the product in the areas where the platform needed clearer momentum most: AI foundations, editorial collaboration, block-level control, and native workflow improvements. It does make it one of the more coherent WordPress releases in recent memory and one that should matter to anyone building, managing, or scaling serious WordPress sites in 2026.
We are also once again proud to have two Devrixians who contributed to the development of this release – thank you Stanko Metodiev and Rolly Bueno for your hard work!
Team DevriX
This article is crafted by DevriX's seasoned marketing team, boasting over four decades of collective expertise in crafting sophisticated marketing funnels, devising comprehensive content frameworks and pillars, implementing engaging email campaigns, and creating impactful social media content designed for scalability.
Our marketing experts specialize in the complete spectrum of inbound marketing strategies. As an accredited HubSpot Agency Partner and a Semrush Partner, we engage in meticulous research, blending our extensive experience with the unique insights of our highly skilled team.
We set benchmarks in content creation by incorporating cutting-edge marketing trends, leveraging in-depth industry research, and utilizing state-of-the-art AI tools for data segmentation and captivating content hooks. Our proficiency extends across a diverse range of sectors, including working with SMEs, Fortune 1000 companies, global B2B brands, major publishing entities, WooCommerce platforms, business directories, and affiliate networks.
