What’s New in WordPress 7.0

WordPress 7.0 shipped in May 2026 as the first major version-number jump since WordPress 5.0 introduced the block editor in late 2018. The release reflects a meaningful shift in priorities: AI moves from an ecosystem plugin afterthought to a first-class connection surface in core, the block editor gets several long-requested usability improvements (a real pattern model, responsive block visibility, a visual revisions timeline), and capabilities that previously only worked in block themes (the font library, in particular) extend to classic themes too. Add a quieter and more modern admin experience, the new Icon block, and a handful of substantive performance and accessibility improvements, and 7.0 is the most significant WordPress release since the 5.0 / Gutenberg era began.

This post walks through what’s actually new in WordPress 7.0: AI Foundations and the new Connectors hub, the navigation overlay designer, patterns as single blocks, visual revisions with a timeline, per-breakpoint block visibility, the universal font library, the refreshed admin, the Icon block, and the performance and accessibility improvements that ship alongside everything else. It’s intended as a tour rather than a feature-by-feature manual, with pointers to where deeper coverage of each area is worth a follow-up.

AI Foundations and the Connectors hub

The headline architectural change in WordPress 7.0 is AI Foundations, introduced through a new Connectors screen in the admin. The Connectors screen is a centralized hub for managing connections to external services, including (but not limited to) AI providers. The intent is to give WordPress a standardized place to wire up credentials and integration settings for any third-party service a plugin or core feature needs to talk to, rather than every plugin building its own settings page and credential storage.

Connecting an AI provider is opt-in. Once connected, an optional AI plugin layers a growing set of tools directly into the editor: generating post titles and excerpts, generating and editing images, and suggesting alt text for images you’ve uploaded. The plugin is separate from core specifically so that AI features can iterate without being tied to the WordPress release cycle, and so that sites that don’t want AI capabilities pay no cost (in code, in bundle size, or in attack surface) for features they won’t use.

The broader significance is the standard. By introducing Connectors as a managed surface, WordPress is doing for external-service integrations what it did for plugin auto-updates and translations in earlier eras: providing a consistent platform so that the ecosystem can build on top of it instead of around it. Plugin authors who need OAuth flows, API key management, or service-account credentials can plug into Connectors instead of reinventing those primitives. Site owners get a single place to see what their site is connected to. For an industry where every plugin used to ship its own bespoke settings panel, that’s a real structural improvement, and one that will pay back over the next few releases as more plugins adopt the pattern.

A dedicated canvas for the navigation overlay

The navigation block has been one of the most-criticized parts of the block editor since it first shipped: powerful in theory, awkward in practice, and hard to design for mobile in particular. WordPress 7.0 gives the mobile and overlay states of the navigation block a dedicated design canvas. Instead of trying to design what visitors see when they tap the menu button by toggling layers of nested settings, you now build the overlay directly, with the same block-editing flow you’d use for any other section of your site.

The canvas is broad enough to accept columns, much larger font sizes than the inline navigation list would support, custom alignment, and any other blocks (search, social icons, images) you’d want to include alongside the links. Pre-built templates give you reasonable starting points; designing one from scratch is the equivalent of designing any other patterned block. For sites where the navigation overlay is the primary mobile experience, the practical impact is large: a piece of the site that was previously expensive to customize is now a normal block-editing job.

Patterns now behave like a single block

Patterns are reusable groupings of blocks that WordPress has supported since the early Gutenberg era. The friction in earlier versions was that once a pattern was dropped into a page, it dissolved into its constituent blocks: changing the headline meant clicking into the nested heading block, changing the image meant navigating into the column that held the image, and so on. The interaction model rewarded the people who built the pattern (because they could shape its internals freely) and punished the people who used the pattern (because every customization felt like spelunking).

WordPress 7.0 inverts the model. When you drop a pattern onto a page, it now behaves like a single block. The inspector exposes the slots you’re meant to customize (text, images, color choices, layout variants) without making you click into nested blocks. Need to change the headline? It’s right there in the block’s settings. Want to swap the image? Click the image, choose a new one. For deeper changes, a single "Edit pattern" action gives you access to the full block tree the way it worked before. The result is that patterns finally behave like the design components they were always meant to be: easy to use as-is, easy to customize at the surface level, easy to open up when you actually need to.

Visual revisions with a timeline

WordPress has had revision history for a long time, but the comparison view has always been heavy on diff highlighting and light on real visual context. WordPress 7.0 replaces the legacy revisions screen with a timeline slider. You scrub through the revisions of a page or post and see exactly what changed at each step, with visual markers showing which blocks were edited, added, or removed. When you find the version you want, restoring it is a single click.

For content teams that work iteratively (most teams do, even if they don’t think of it that way), the new revisions UI is a meaningful productivity improvement. Recovering from an accidental edit, comparing two versions of a draft, or walking back a change that turned out to be wrong all become substantially less stressful than they were in the legacy revisions interface. It also means revisions are more likely to be used as a workflow tool deliberately, rather than just a safety net that occasionally gets consulted.

Show the right blocks at every breakpoint

Responsive block visibility is one of the longest-running asks in the block editor community: the ability to choose, per block, whether it appears on mobile, tablet, or desktop. WordPress 7.0 ships it as a built-in capability. Each block has a visibility setting that lets you check or uncheck mobile, tablet, and desktop independently. You can keep a desktop-only hero image, an alternate mobile-only call-to-action, or a tablet-specific layout variant in the same template without resorting to custom CSS or third-party visibility plugins.

This is also the kind of feature that quietly changes how layouts get designed. Once visibility-per-breakpoint is built-in, the natural design instinct is to keep more variation options inside the editor rather than splitting designs across separate templates. The downstream effect is fewer custom workarounds and a tighter loop between designing in the editor and seeing the result on the live site.

Font library is no longer just for block themes

The font library, introduced in earlier 6.x releases, gave block-theme users a way to browse, install, and manage web fonts directly from the editor. In WordPress 7.0, the font library is available to all themes, including classic themes still using PHP templates and theme.json configurations. The practical effect for sites that haven’t migrated to a block theme is that font management becomes a normal editor task: browse the library, install what you want, apply it through theme customization, no need to drop into the file system or wire up a custom enqueue.

This continues a pattern visible across recent WordPress releases: features that started as block-theme-only capabilities are getting backported to work for the broader theme ecosystem. For sites that have stayed on classic themes (which is still the majority of sites in production), 7.0 closes some of the most-cited capability gaps.

A refreshed admin experience

The WordPress admin gets a visual refresh in 7.0. The new default color scheme is quieter and more contemporary, button and input styling is updated, and page transitions now fade between each other instead of jumping abruptly. Nothing has been moved, the menu structure is unchanged, and existing color schemes still work for users who prefer them, but the default experience feels less dated than the admin chrome WordPress has shipped since roughly 2013.

The other notable detail in the admin refresh is that the color contrast in the new default scheme has been tuned for accessibility. The visual update isn’t just cosmetic; it doubles as an accessibility improvement that benefits every user on every admin screen.

The Icon block

A new Icon block ships in WordPress 7.0. You drop it into a page like any other block, pick from a built-in icon library, and style it the way you’d style any other block (size, color, alignment, hover effects through the standard block settings). Until now, adding icons to a WordPress page typically meant either embedding raw SVG, relying on a theme that bundled icons, or installing a third-party icon plugin. The Icon block makes it a normal, themeable, accessible piece of the block toolkit.

Performance and accessibility improvements

WordPress 7.0 makes substantive technical improvements alongside the user-facing features. On the performance side, the highlights are sharper image-loading prioritization (so hidden images in navigation overlays and interactive blocks don’t degrade loading of the visible content), more reliable on-demand stylesheet loading for blocks in classic themes, and the ability for scripts to declare dependencies on script modules to reduce render-blocking.

On the accessibility side, the release ships fixes across media management, voice-control compatibility, and color contrast (the new admin color scheme is part of this), plus improvements to keyboard navigation in the editor. None of these are individually flashy, but the overall direction is consistent: every release should leave WordPress measurably more accessible than the last, and 7.0 holds that line.

What this means for site owners

For a typical WordPress site, the immediate practical impact of upgrading to 7.0 falls into a few buckets:

• If you use patterns heavily (or want to start), the new single-block pattern behavior is the biggest day-to-day usability improvement in the release. Pattern-driven design becomes substantially friendlier.
• If your site’s mobile navigation overlay has been a perennial design headache, the new navigation overlay canvas is worth re-doing your menu in.
• If you’ve been wishing for built-in responsive block visibility, 7.0 finally ships it. Plan to retire whatever workaround you’ve been using.
• If you’re interested in AI-assisted editing (titles, excerpts, alt text, image generation), the optional AI plugin is the easiest path to try it without commitment, since the Connectors hub centralizes credential management cleanly.
• If you’re on a classic theme, the font library becomes available to you for the first time. Font management without dropping into PHP is a meaningful workflow change.

As with every major WordPress release, the responsible upgrade path is the same: read the field guide, check your plugins for compatibility (especially anything that touches the navigation block, the patterns API, or the revisions screen), upgrade on a staging environment first, and confirm everything still works before promoting to production. For sites on managed WordPress hosts, expect the host to roll 7.0 out on a defined schedule rather than immediately; that’s the host doing exactly the staging-and-verification work you’d want them to do. If you’re choosing or comparing hosts, our guide to how to choose a managed WordPress host walks through what to look for, and our breakdown of WP Engine vs Pantheon for WordPress hosting covers the two platforms most often compared at the upper end.

For background on WordPress as a platform and how it got to this point, see our WordPress: a beginner’s guide, and for the writing experience the block editor enables (and that 7.0 continues to improve), see our Gutenberg block editor walkthrough.

Frequently Asked Questions