WordPress 7.0: All new features, release info and what’s changing now

A new major release is here: WordPress 7.0 was officially released on May 20, 2026. With this release, the CMS continues its evolution from version 6.9 and introduces numerous improvements to the editor, performance, and developer tools.

With this release, WordPress continues its transformation into a modern, block-based publishing platform, with a stronger focus on design systems and more efficient content workflows.

In this post, we’ll break down the most important new features in WordPress 7.0 and explain what they mean for agencies, developers, and website owners. You’ll learn what features the new version includes and how to best prepare your website for the update.

The Release Schedule for WordPress 7.0

A major release like WordPress 7.0 goes through a multi-stage development process to ensure maximum stability and security. The version was released on schedule on May 20, 2026.

The WordPress 7.0 roadmap at a glance:

1. Beta phase (February 19 to March 12, 2026): During this phase, the first versions were made available for public testing. The focus here was on gathering feedback from the community to identify fundamental bugs in the new features—particularly the originally planned real-time collaboration—at an early stage.
2. Release Candidate Phase (March 19 to May 19, 2026): Following the beta versions, the first release candidates (RC1 & RC2) were launched on March 19. Due to necessary technical improvements to database stability, this phase was extended in April. The final stabilization versions followed in May (RC3 on May 8 and RC4 on May 14). From this point on, no new features were added; only critical bugs were fixed.
3. Final Release (May 20, 2026): Following the successful completion of the final tests, the final version of WordPress 7.0 was officially released. The update is available worldwide directly through the WordPress dashboard.

The WordPress Core Team regularly publishes up-to-date information on the development status and discussions about new features in the official WordPress Development Blog.

The most important new features in WordPress 7.0

The upcoming update builds on the developments from WordPress 6.9 and bundles several initiatives to make WordPress fit for the future. Here are five key features you should know about.

1. Further development of the Site Editor

Full Site Editing (FSE) was further expanded in WordPress 7.0 and includes several new features and refinements. The goal of these changes is to make the Site Editor more stable, flexible, and user-friendly.

The improvements include, among others:

• More stable workflow: Working with block themes and global styles becomes more reliable and intuitive.
• Improved template management: Nested blocks, synchronised patterns and templates can now be edited directly in the editor – without having to switch pages to the template area. The creation and management of templates and reusable layout areas such as headers or footers is now clearer.
• New layout options: Extended block functions and layout tools enable more precise designs without additional page builder plugins.
• New blocks and block functions: New core blocks such as icon or breadcrumb blocks and extended block variations (e.g. for headings) are intended to make typical design functions available directly in the WordPress core.
• Text Indent: Paragraphs can now be indented. The first paragraph is excluded, all subsequent paragraphs are automatically indented.
• Text Columns: The paragraph block now supports native multi-columns without any additional plugins.
• Aspect ratios: Defined aspect ratios now also apply to wide and full alignment for image blocks.
• Dimension presets: Width, height and spacing can be defined as predefined presets and reused consistently.

Functions such as block variations, pattern editing and instance-specific CSS per block are also being continuously expanded. This means that layouts and design systems can increasingly be defined directly in the editor without additional theme code.

2. Modernisation of the WordPress admin area

In addition to improvements in the editor, the WordPress project is also working on a gradual modernisation of the admin dashboard in order to adapt it step by step to the new look and UX of the FSE.

This update includes, among other things:

• Revised UI components: New interface elements such as dropdowns, tooltips and panels ensure more standardised operation.
• Modernised adjustments to colours, typography and interactions are intended to make the backend clearer and more intuitive.
• Smoother navigation: Improved loading times and smooth transition animations when switching between pages or opening dropdowns
• Client image processing: Uploaded images are now processed directly in the browser instead of on the server. This saves resources and provides support for modern image formats.

Expert opinion from Dominic Vogl: The new WordPress backend may not seem like a revolution at first glance, but it simply feels much fresher and more fluid than before. Animated page transitions everywhere, smooth dropdown openings and small interaction details: it’s precisely these little things that make a noticeable difference for me. It simply makes working in the WordPress dashboard a bit more fun again. – Dominic Vogl, Web Dev, Raidboxes

3. New possibilities for AI integration

Artificial intelligence is playing an increasingly important role in the WordPress ecosystem. Instead of integrating ready-made AI features directly into the core, the community is primarily working on technical foundations that enable better integration of AI tools.

This is done in WordPress 7.0 with the new WP AI Client, which provides a basis for initial features with WordPress’ own AI Experiments plugin, among other things, and shows what will be possible with this new interface. In addition, connectors have already been implemented with which API keys from OpenAI, Anthropic and Google can be used for text and image generation, for example.

In the future, we will certainly see a large number of other plugins here that will use this native interface to bring interesting AI features into WordPress. Please tell us about your experiences.

Possible use cases for the connector are

• Automated text creation
• Content analysis
• SEO optimisation
• Personalised content

4. New opportunities for developers

WordPress 7.0 also brings some technical improvements for developers. The focus is on better supporting modern development standards and further simplifying work with blocks and APIs.

The most important developments include

• Improved block registration: For pragmatic and lean blocks and block patterns, these can also be registered and used completely on the server side and with PHP from 7.0 (e.g. to create pure WP query output).
• Advanced APIs: Enhancements to the REST API and new UI components facilitate the development of modern plugins and themes.
• Updated developer tools: Improvements in the code editor, such as an updated CodeMirror version, ensure better development workflows.
• Native PHP blocks: In future, blocks can be registered and rendered completely via PHP – without JavaScript or React overhead, as is the case with regular Gutenberg blocks.

WordPress is also undergoing further technical development. This includes continuous core optimisations and possible adaptations to more modern PHP versions in order to improve security and performance in the long term.

Expert opinion by Dominic Vogl: For me, PHP-only blocks are one of the most exciting features in WordPress 7.0. Finally, I can build simple, server-side rendered blocks completely in PHP, without wp-scripts, without a build pipeline, without a single line of JavaScript. Especially for lean custom blocks that only need PHP logic anyway, this is a welcome extension. Less overhead, faster development, cleaner code. – Dominic Vogl, Web Dev, Raidboxes

5. further performance improvements

Performance remains a key issue in WordPress development. WordPress 7.0 also comes with optimisations that can have a direct impact on loading times and user experience.

These include, among others:

• Optimised block rendering: Improvements in block rendering reduce the overhead when rendering complex layouts.
• Improved database queries: Optimisations in the core can reduce the server response time (TTFB).
• Enhanced lazy loading: resources such as images or media are loaded even more efficiently.

These improvements have a positive effect on important key figures such as core web vitals, loading time and SEO.

CANCELED: First Steps Toward Real-Time Collaboration in the Editor

One of the most exciting developments in the WordPress ecosystem was the planned introduction of collaborative editing features directly within the editor. On May 8, 2026, it was announced on the official WordPress Developer Blog that the feature had been removed from version 7.0 because too many bugs and performance issues had arisen during the testing phase.

However, this doesn’t mean the feature is dead. Work on it will continue, and it will be released in a future version. In the future, changes made by team members will be visible in real time as block content is synchronized, and multiple users who want to edit the same page will no longer block each other.

The plan was to limit real-time collaboration in WordPress 7.0 to two concurrent users per post to minimize server load (especially on smaller hosting packages). For agencies and larger editorial teams, however, this limit can be flexibly adjusted via wp-config.php. Technically, the sync is based on the new CRDT architecture, which prevents write conflicts without bloating the database.

---

What does WordPress 7.0 mean for agencies and developers?

The update brings both opportunities and challenges for professional users.

For agencies

Advantages:

• Fewer dependencies: A more powerful site editor and new core blocks reduce the need for extra costs for external page builder plugins in many projects.
• More modern websites: Better performance and a more powerful editor make it easier to build fast and low-maintenance customer projects.

Preparation/Challenges:

• Testing first: Never deploy an update directly to production; always test it first in a staging environment or create a clone of your WordPress installation to test the update there.
• Plugin compatibility: Check all plugins for compatibility with 7.0 before the update goes live (especially for customised extensions).
• Theme Check: Test older or heavily customised themes specifically for conflicts with new editor and block functions.
• Complex setups: WooCommerce shops, membership sites and similar installations require particularly careful testing.
• Ensure rollback: Make sure that your host offers a rollback option in case of an emergency.

For developers

Advantages:

• WP AI Client: WordPress 7.0 brings a provider-agnostic AI interface directly into the core. Plugins and themes can now address various external AI models via a standardised API without having to build their own integrations.
• PHP-Only Block Registration: Blocks can now be registered and rendered entirely via PHP – without JavaScript or a build pipeline. WordPress generates Inspector controls for common attribute types automatically.
• Block Bindings API: Pattern overrides now work with any custom blocks, no longer just with core blocks. This makes the connection of dynamic data sources to blocks much more flexible.
• DataViews & DataForm API: New layouts, controls (combobox, adaptiveSelect) and complete validation with error messages make the DataViews/DataForm components a fully-fledged framework for your own admin interfaces.
• Client-side Abilities API: The Abilities API introduced in 6.9 gets a client-side extension – with improved filtering, querying and integration into the Command Palette for more flexible UI capabilities in plugins.

Breaking Change:

• iframed Post Editor: As of WordPress 7.0, the editor only checks the blocks actually inserted in the post. If all of them use Block API v3+, iFrame mode is activated. Full enforcement does not yet take place in 7.0. This is only planned for WordPress 7.1. If you operate your own blocks with access to the global document, you should keep an eye on this.

Expert opinion by Dominic Vogl: With the WP AI Client, WordPress has now also created a native standard interface for AI integrations – and this is bigger than it seems at first glance. Instead of each plugin building its own OpenAI or Anthropic integration, there is now a standardised connector layer in the core. This means that if you connect one provider today, you can use another tomorrow without having to rebuild everything. This opens the door for meaningful, well-integrated AI features in WordPress in a way that was previously noticeably more complicated and customised. – Dominic Vogl, Web Dev, Raidboxes

Should you update to WordPress 7.0?

The answer is: it depends.

An immediate update can be useful for simple websites such as blogs or portfolios that use a modern plugin stack and run on a current PHP version.

More caution is required for more complex installations, such as WooCommerce shops, membership sites or websites with many individual customisations. Here, changes in the block editor, new core functions or plugin dependencies can lead to individual components having to be customised first.

Especially with major releases such as WordPress 7.0, it is therefore advisable to test updates in a secure test environment first. This way you can ensure that plugins, themes and individual functions continue to work smoothly.

How to test the WordPress update safely

An untested update on a live website is risky. Failures or errors can lead to loss of sales and damage to reputation. With a staging environment, you can test WordPress updates without jeopardising the live system.

This is how you proceed:

1. Create a staging environment: A staging environment is a 1:1 copy of your live website in a protected, separate environment.
2. Perform update: Install the WordPress 7.0 update in the staging environment. If you can’t install WordPress updates on your hosting provider’s staging server, create a live clone of your website and test it there.
3. Test functions: Check all important areas of your website in the preview: Are plugins and theme still working correctly? Can pages be edited and saved? Are there any problems in the block editor or frontend?
4. Prepare a rollback: Make sure that your host offers a simple rollback function so that you can quickly revert to the previous version in an emergency.

What comes after WordPress 7.0?

WordPress 7.0 is just the first step in the further development of the platform in 2026. According to the official roadmap, the WordPress project is planning several major releases per year, which will gradually introduce new functions and improvements.

Further versions have already been announced:

• WordPress 7.1 (planned for August 2026): Introduction of the collaborative editing features that were removed from the 7.0 release, as well as other improvements to the Site Editor.
• WordPress 7.2 (planned for December 2026): Expansion of collaboration features and first steps towards native multilingualism in the core

---

Conclusion: WordPress 7.0 brings important improvements for modern websites

With WordPress 7.0, the CMS is staying true to its course: a more modern editor and more robust developer APIs. Unfortunately, we’ll have to wait a little longer for the first building blocks of collaborative workflows. Nevertheless, the platform is becoming noticeably more flexible and future-proof.

For agencies, developers and professional website operators, this means one thing above all: more flexible blocks, native PHP block registration and AI connectors directly in the core. WordPress 7.0 makes agencies and developers less dependent on page builders and external tools.

As with every major release, the update should first be tested in a staging environment – especially for websites with many plugins or customisations. With Raidboxes, you can create a test environment with a click, check everything at your leisure and only go live when you are sure.

---

Frequently asked questions (FAQ) about the WordPress 7.0 release