WordPress 7.0 is here — the first major release of 2026 — and it focuses on AI integration, editor improvements, and smoother admin workflows. Whether you run a small blog or a large multi-author site, 7.0 introduces tools that change how you build, edit, and manage content.
What’s new at a glance
– AI Connectors: a centralized Settings » Connectors screen to install and authenticate AI providers (OpenAI, Google, Anthropic at launch) so multiple plugins can reuse a single, secure connection. You can disable AI sitewide with a single wp-config flag.
– Admin refresh: updated colors, cleaner typography, and fewer full page reloads give the dashboard a faster, more app-like feel. The Command Palette (⌘/Ctrl+K) is now available everywhere in the admin for quick navigation and actions.
– Responsive block visibility: show or hide any block by device (desktop, tablet, mobile) from the block toolbar or inspector — no custom CSS required. List View shows icons for blocks with visibility rules.
– Visual revisions: side-by-side revision diffs with color-coded overlays show added, removed, or changed blocks and text. The sidebar lists changed block attributes so you can see exactly what settings changed.
– Per-block Custom CSS: a Custom CSS field in the block inspector lets you add styles that apply only to the selected block instance; CSS lives with the block and renders live in the editor.
– New native blocks: Icons (SVG library with sizing and color controls), Breadcrumbs (auto-generates a trail for navigation and SEO), and a consolidated Headings block (switch H1–H6 without transforming blocks).
– Navigation overlays: guided creation of mobile menu overlays from the Navigation block with pre-built patterns and a theme template area for navigation-overlay.
– Pattern editing improvements: patterns default to a content-only editing mode that simplifies editing text and images; developers can opt out if they need full pattern internals.
– Gallery lightbox navigation: back/next buttons and arrow-key support let visitors browse gallery images inside the lightbox.
Developer and under-the-hood updates
– theme.json pseudo-element support: you can declare :hover, :focus, :focus-visible, and :active states in theme.json for cleaner theme code.
– PHP-only block registration: simple blocks can be registered in PHP without client-side JavaScript for basic functionality and lower overhead.
– Block Selectors API: blocks may declare selectors.css to control which CSS selector Global Styles target, improving style scoping.
– Font Library page: a dedicated dashboard page to manage, upload, and install fonts for block, hybrid, and classic themes.
– WP-CLI 3.0: ships with new commands including wp block (read-only block access) and wp ability (for AI Abilities API).
– wp-env update: phpMyAdmin support on the Playground runtime is now available via configuration.
– OPCache visibility: Site Health now shows OPCache info under Tools » Site Health » Info » Server for easier diagnosis.
– Iframed editor: the post editor automatically uses an iframe when all blocks are Block API v3+, improving stability and performance; older blocks keep the non-iframe flow for compatibility.
– More secure defaults: Administrator and Editor roles are no longer options in the default role selector to prevent accidentally assigning high privileges to new users.
– PHP requirement: minimum PHP is 7.4; PHP 8.3 or 8.4 is recommended for best performance and security.
Miscellaneous enhancements
– Cover blocks now accept video URLs as backgrounds.
– Text alignment standardized across additional post-related blocks.
– Interactivity API added a watch() helper for cleaner interactive patterns.
– DataViews and DataForm packages received updates including new layouts and validation improvements; developers using @wordpress/dataviews should review breaking changes.
– Note: Client-Side Media Processing preview from beta was moved out of core into a standalone plugin and is not included in 7.0.
Removed or delayed features
– Real-time collaboration (RTC) did not ship in 7.0. It remains in active development and can be tested through the Gutenberg plugin; it was delayed due to concerns about race conditions, server load, and memory efficiency.
How to approach the update
– Back up your site before updating. For mission-critical sites, test 7.0 in a staging environment first.
– Check plugins and themes for compatibility, especially if they add custom blocks or rely on older block API versions.
– Explore the Connectors screen and the visual revisions tools — they’re easy to miss but very useful.
Final thoughts
WordPress 7.0 brings practical editor and admin upgrades that streamline content creation and site management while laying groundwork for standardized AI integration. It’s a solid release focused on usability, developer ergonomics, and safer defaults. If you manage a WordPress site, review the new features in a staging environment, update safely, and take a few minutes to try the Command Palette, block visibility controls, and per-block CSS.