WordPress 7.0 “Armstrong”: All New Features, Risks and What Website Owners Need to Do Now

WordPress 7.0 is here – and it is the biggest major version in years. With native AI integration right in the core, the first real backend redesign since 2013 and dozens of editor improvements. But the update has its pitfalls too: a headline feature was cut twelve days before release, and some websites will stumble after the switch. Here you will learn everything that matters now as a website owner.

WordPress 7.0 “Armstrong” at a glance

WordPress 7.0 is code-named “Armstrong” – like every major version, it is named after a jazz musician, this time the legendary trumpeter Louis Armstrong. It is the 30th major release since the very first WordPress 1.0 in 2004 and the first big release of 2026.

The release was originally planned for April 9 but was deliberately postponed: the team extended the testing phase to put stability ahead of deadlines – a decision that, as we will see later, turned out to be spot on. Behind the version are more than 875 contributors from around the world, over 200 of them for the first time. In total, more than 420 improvements and bug fixes went in.

The most important context up front: WordPress 7.0 is a platform release. It brings fewer spectacular individual features than new foundations – above all a native AI interface and a completely renewed backend.

This overview shows what has concretely changed compared with the previous version 6.9 – we explain the individual points later in the article:

AI moves into the WordPress core

By far the biggest structural change: WordPress can now talk to AI services out of the box. Until now this always required a plugin – each with its own setup, its own place to store API keys and its own logic. That is over.

Under Settings → Connectors there is a new area where you store the credentials for AI providers centrally. Out of the box, WordPress 7.0 supports three providers: Anthropic (Claude), OpenAI and Google (Gemini). A key, entered once, is then available to all compatible plugins – no more entering it twice.

Technically behind this is the WP AI Client – a unified, provider-independent interface. For you as a website owner this means: plugins with AI functions (writing assistance, automatic alt texts for images, translations) no longer have to take care of the connection themselves. They simply use the central connector. That makes AI functions more consistent, easier to maintain and easier to swap.

Reassuring and important: WordPress 7.0 does not send any data to any AI on its own. The connectors only become active once you deliberately enter an API key yourself. If you don’t want to use AI, just leave the area empty – then WordPress behaves as before.

The new backend – first real redesign since 2013

At its core, the WordPress backend had looked almost unchanged since 2013. With version 7.0 it gets its first real redesign in over a decade. These changes stand out immediately:

• New color scheme & typography – higher contrast, a calmer look, fresher fonts. The Customizer and multisite registration were adapted as well.
• View transitions – switching between admin pages (e.g. from posts to settings) now happens with smooth transitions instead of a hard reload. If you have “reduce motion” enabled in your operating system, the animations are automatically turned off.
• Command Palette – with ⌘K (Mac) or Ctrl+K (Windows) a quick search opens from anywhere in the backend. It lets you jump to any setting or piece of content in seconds – just like in modern apps.
• Font Library for all theme types – the central font management already existed, but it only worked with block themes. Now it works with block, hybrid and classic themes.

What’s new in the block editor

The block editor (Gutenberg) also gets noticeable improvements that make everyday editing easier.

Visual revisions

Until now, version comparison was a sober list of text changes. WordPress 7.0 now shows changes visually – with a color-coded system, a slider for the before-and-after comparison and clickable markers that jump straight to the changed spot. If you often have to restore an older version of a post, you will love this.

The iframed editor

Technically in the background, but important: the editor now runs consistently in an isolated iframe (for blocks from Block API v3). This makes the preview in the editor more reliable and much closer to the real frontend. For most users it is invisible – but for older, custom-developed blocks it can become a stumbling block. More on that in the section Problems & pitfalls.

New and improved blocks

WordPress 7.0 significantly expands the block toolkit. Two new blocks are added and several existing ones are upgraded.

New blocks

• Breadcrumbs block – a “breadcrumb” trail that automatically maps the page hierarchy (Home › Category › Post). Good for orientation and SEO, and can be placed globally in the theme header.
• Icons block – a native block for icons, with no extra plugin or fiddling with your own SVG.
• Improved Heading block – headings of all levels with easy switching between H1 and H6.

Upgraded blocks

• Gallery – finally with a native lightbox including a slideshow option. Images open large on click, with no extra plugin.
• Cover block – now also supports video backgrounds.
• Grid block – becomes responsive and adapts flexibly to screen sizes.
• Paragraph block – can now display content in multiple columns.

On top of that come finer design controls (“block supports”): custom CSS directly per block, text indent, aspect ratios for wide and full-width images, and hover, focus and active states for buttons. This noticeably reduces the need for additional custom CSS.

Responsive Editing – control blocks per device

A feature that will especially please editors: Responsive Editing. Individual blocks can now be shown or hidden by device type – for example, showing a large image only on desktop and a compact notice only on smartphones. The control sits in the toolbar, in the sidebar and in the Command Palette; in the List View, small icons show which blocks have visibility rules.

Also new: customizable navigation overlays. The hamburger menu on mobile devices can now be freely designed with blocks and patterns, including its own “Close overlay” block. The mobile menu is thus no longer a rigid standard element.

For developers & agencies

A lot has changed under the hood too – briefly, for those who develop themselves or work with an agency:

• PHP-only block registration – simple blocks can now be registered entirely server-side in PHP (with autoRegister), with no JavaScript build at all. Inspector controls are generated automatically from the attributes.
• Interactivity API – with the new watch() function and data-wp-watch for reactive frontend logic.
• DataViews & DataForms – the React system behind the new backend gets new layouts (Activity, Details) and can be extended by plugins.
• Library updates – including PHPMailer 7.0.2 (with a bug fix for the sender address) as well as updated code editors and linters.
• Security – the “Administrator” and “Editor” roles were removed from the default selection for new user registrations.

What is NOT included in 7.0

And now perhaps the most surprising news: the actual headline feature of WordPress 7.0 is not included at all.

Real-time collaboration was planned – several people editing the same post at the same time, similar to Google Docs. Only twelve days before release, the feature was cut. The reason: testing revealed too many problems with stability, race conditions, server load and memory consumption.

Problems & pitfalls for website owners

WordPress 7.0 is a big update – and big updates have rough edges. These are the most important pitfalls you should know about:

• WooCommerce & shops – the modernized backend has to work together with shop plugins. WooCommerce from version 10.6.2 is prepared for 7.0, but a production shop should never be updated without a staging test. Complex backends with many extensions need especially thorough checking.
• Classic meta boxes – pages and posts that still use classic meta boxes automatically disable certain new editor features.
• PHP 7.2 and 7.3 are dropped – the minimum PHP is now 7.4. If you still run an older version, you simply can’t install 7.0 and stay on WordPress 6.9. The fix is long overdue anyway: raise PHP to 8.3 at your host – which also brings more speed and security.
• Plugin maturity – right after a major release, many plugins need a few days before they officially report “Tested up to: 7.0”. Anyone who updates immediately unwittingly becomes a guinea pig.

To reassure you: the vast majority of well-maintained websites with modern plugins will update without problems. The pitfalls mainly affect shops, heavily customized sites and outdated installations.

What website owners need to do now

Before you install WordPress 7.0, you should tick off the following points. The checklist applies to production live sites – a small test blog can afford to be bolder.

Point 1 is the most important: no backup, no update. This is what a complete backup should look like – database and files stored cleanly separated:

Recommended backup structure before the update

backup-wp7-2026-05-21/
├── datenbank/
│   └── wp_database_export.sql
├── dateien/
│   ├── wp-content/
│   │   ├── themes/
│   │   ├── plugins/
│   │   └── uploads/
│   ├── wp-config.php
│   └── .htaccess
└── checkliste-und-protokoll.txt

The update step by step

Everything ticked? Then the update runs in these seven steps:

1. Create a backup

   Complete backup of database AND files. Only when the backup has been checked and stored safely do you continue.

2. Check the PHP version

   At least PHP 7.4, better 8.3. You can see the current version under Tools → Site Health → Info. If necessary, have your host raise it.

3. Set up a staging copy

   Create a 1:1 clone of the live site. Many managed hosts offer this at the click of a button.

4. Update & test on staging

   Install WordPress 7.0 on staging only at first. Click through all important pages, forms, the editor and – if present – the shop thoroughly.

5. Check plugins & theme

   Does the layout look right in the new backend? Do custom blocks work in the iframed editor? Do all plugin functions run as expected?

6. Run the live update

   Only when staging runs cleanly: take a fresh backup of the live site, then update – ideally at a time with few visitors.

7. Follow-up check

   Check the frontend, editor, forms and load times again after the live update. If there are problems, roll back immediately using the backup.

Update now or wait?

The core question for many site owners: switch immediately or better wait? The answer depends on your specific setup.

Our general recommendation matches that of many expert sources: updating right on release day is only worthwhile if a tested staging copy is already ready. For everyone else, a window of roughly one to three weeks after release is ideal – by then the most important plugins have caught up with their 7.0 updates, without you going without security and feature improvements for an unnecessarily long time.

Conclusion

WordPress 7.0 “Armstrong” is not an update you wave through on the side with one click – and that’s a good thing. With the native AI interface and the modernized backend, it lays foundations on which WordPress will build for the coming years. The real-time collaboration cut at short notice shows: the team takes stability seriously.

For you as a website owner, that means: no reason to rush, but no reason to worry either. With a verified backup, a staging test and a bit of patience with plugins, the switch to 7.0 is straightforward. If you are still on PHP 7.2 or 7.3, you should use the update as an occasion to finally modernize your technology.

A major update is not an emergency – but not a formality either. If you take backups and staging seriously, WordPress 7.0 only has advantages for you.

Michael Rademacher, realmaker