WordPress 7.0 features worth knowing about

WordPress 7.0 ships on 20 May 2026 and it is the biggest release in years. This is a walkthrough of the new WordPress 7.0 features as they actually arrive on production sites, so you can decide what to enable, what to ignore and what to test before pushing the update to clients.

A unified admin and a calmer interface

The first thing you notice after upgrading is that wp-admin and the site editor now share a visual language. Border radius is consistent across both, buttons match, form fields look the same and the default colour scheme is the one previously called modern. Page transitions inside the admin area now have a subtle fade rather than a hard reload, which makes the dashboard feel less like two products bolted together.

The admin bar also gains a command palette, opened with command+K. It is small, but if you live inside wp-admin every day it removes a meaningful number of clicks.

A proper font manager in Appearance

Appearance now includes a Fonts panel that lists every font installed by the active theme. You can upload your own files or connect to Google Fonts and install directly from there. Until now this needed a plugin or a child theme, so for sites that rely on a custom typography setup it is one fewer dependency to maintain.

Visual revisions replace the old diff screen

The revisions screen has been rebuilt. Instead of the old two-column HTML diff, you now see the page as it actually looks, with a timeline slider in the header to scrub through versions. Deletions are red, additions are green and modified blocks are highlighted in orange. You can also toggle the colour indicators off and just see the page state at a given moment. For anyone who has tried to talk a client through a revision restore over the phone, this alone is worth the upgrade.

Navigation overlay templates

The Navigation block now has an Overlay template setting in the gear icon. Mobile menus stop being a hardcoded list of links and become a full template you can fill with any blocks: a logo above the menu, a search field, social icons, a contact button. The overlay group keeps a close icon pinned to the top right, and the resulting overlays are managed under Patterns, so they can be renamed, edited or reused across templates.

New blocks: Icon and Breadcrumbs

Two long-overdue core blocks arrive in 7.0:

• Icon block: a small built-in library with text colour, background colour, width, padding and border controls. The library is intentionally limited, but it covers most common cases without reaching for a plugin.

• Breadcrumbs block: toggle the home crumb and the current page crumb on or off, change the separator character and drop it into any template.

Block editor improvements

A few smaller editor changes are worth knowing about because they replace common workarounds:

• Cover blocks can now embed video from a URL. Paste a YouTube or Vimeo link as a background video without dropping a custom block in front of it.

• Block-level Hide with shift+command+H. You can hide a block from published content, or hide it on specific devices, without writing custom CSS.

• Per-block Additional CSS in the Advanced tab, so block-specific styling no longer has to live in the theme stylesheet.

• Pattern editing mode. Inserted patterns are now editable only, with style variations available, until you click Edit pattern for full block-level access. This stops editors accidentally breaking a pattern they only wanted to populate.

• Gallery lightbox. Enable enlarge on click and visitors can step through images with arrow keys or on-screen arrows rather than closing and reopening each one.

The AI Client API and Connectors

The most structural change in WordPress 7.0 is the new AI Client API and the Connectors panel in Settings. Connectors lets you pick an AI provider, currently OpenAI, Anthropic or Google, and install the matching provider plugin in one step. You drop in your own API key and the credentials are then available to any plugin that wants to use them.

The important thing to understand is that core ships the plumbing only. The AI features themselves live in a separate, free AI Experiments plugin from the WordPress AI team. Without that plugin installed, Connectors does nothing visible. With it installed, you get a settings page where you can toggle individual AI features on or off.

What the AI Experiments plugin actually does

Inside a post, the new AI features show up in a few places:

• Regenerate title produces three title suggestions from the post content. There is no prompt input yet, so you cannot ask for shorter or punchier. You regenerate until something usable appears.

• Generate summary inserts a paragraph block summarising the post into the page.

• Generate review notes scans the page for accessibility issues and content gaps and surfaces a set of suggestions.

• Featured image generation creates an image from the post content. Quality is uneven and generation time can be long.

• Inline image generation lets you describe an image with a prompt and drop the result into the page.

• Image editing inside the media library includes refine, expand background, remove background, remove item and replace item, with a brush selection tool.

• Generate alt text from an image, one image at a time. Bulk alt text is not yet supported.

These features are flagged as experimental, so expect occasional errors and limited control. The interesting part is not any single feature but that core now provides a shared interface for them, so future plugins can use the same provider credentials rather than each asking for their own keys.

Before you update production sites

The visual changes in 7.0 are friendly. The structural changes around AI and the editor are not. Older page builders, custom blocks and pattern-heavy themes are the most likely sources of breakage. I cover the safe sequence for major WordPress upgrades in how to de-risk CMS updates, and the longer-term cost of an unmanaged plugin stack in the hidden cost of plugin sprawl. For most production sites the right order is: read the changelog, test on staging with the full plugin stack, then schedule the production update during a quiet window with a backup ready.

If you would rather not run that update yourself, I look after WordPress upgrades as part of support and maintenance, and I cover what to look for in an in-house developer in how to find a reliable WordPress developer in the UK.