WordPress 7.0 and 7.1: What's New and What Didn't Ship

WordPress 7.0 "Armstrong" shipped on 20 May 2026 and WordPress 7.1 "Mary Lou" followed on 19 August 2026. Together they brought AI plumbing into core (an AI Client and a Connectors screen), a redesigned admin, a higher minimum PHP version (7.4), new design tools, and in 7.1, image processing in the browser with native AVIF and HEIC support. The most talked-about feature, real-time collaborative editing, did not ship in either release.

As of October 2026, the current version is WordPress 7.1.2, released on 22 September 2026. The project says only the newest version is actively supported, so if you are still on 6.x or an early 7.0 point release, updating is a security task, not a nice-to-have. WordPress 7.2 is targeted for 10 December 2026.

This guide summarizes what actually shipped, what did not, what it means for business sites and an upgrade checklist you can hand to whoever maintains your site.

Release timeline at a glance

2026 is planned as a three-release year (7.0, 7.1, 7.2), a return to a faster cadence after the project briefly moved to one major release per year in 2025. For maintenance planning, that means more frequent compatibility testing than in 2025.

What shipped in WordPress 7.0

AI Client and Connectors

The release announcement says "a new AI Client in Core lets WordPress communicate with generative AI models." Developers call it through a provider-agnostic PHP API, so a plugin can ask for text generation without hard-coding a specific vendor. It works together with the Abilities API introduced in 6.9.

A new Settings > Connectors screen manages external connections. According to the Make WordPress Core dev note, 7.0 features three connectors on that screen, for Anthropic, Google and OpenAI, and each provider is a separate plugin maintained outside core. Crucially, the merge proposal states that core "does not ship any AI providers or automatically enable AI calls. Without explicit configuration and explicit calling code, WordPress will not send prompts or data to any external service." We cover the details, including where API keys are stored, in our guide to AI features in WordPress.

A redesigned admin

7.0 introduced what the announcement calls "a fully revitalized dashboard with a chic, modern new color scheme," plus a Command Palette shortcut (⌘K or Ctrl+K) in the admin bar and a dedicated font management page for installing, uploading and managing fonts. If you train staff or clients with screenshots, those screenshots are now out of date.

Design and editor tools

• New Breadcrumbs and Icons blocks, a change to the Heading block and a slideshow in the gallery lightbox.
• Per-device visibility: hide or show blocks on specific devices.
• Block-level custom CSS directly in the editor.
• Menu overlays built from blocks and patterns.
• PHP-only registration of blocks and patterns for developers.

PHP 7.4 minimum

The WordPress hosting handbook confirms that 7.0 "raised the minimum PHP version from 7.2.24 to 7.4 and dropped support for PHP 7.2 and 7.3." The MySQL minimum did not change: it is still 5.5.5, despite some blogs claiming 7.0 requires MySQL 8.0. The recommendation (not the requirement) is PHP 8.3 or greater and MySQL 8.0+ or MariaDB 10.11+, per the official requirements page.

What shipped in WordPress 7.1

• Client-side media processing. The announcement says "image compression, resizing, and thumbnail generation now happen in the browser, reducing server load and producing smaller files."
• Modern formats. Native support for AVIF, HEIC and HDR gain maps, so photos straight from phones are easier to upload.
• Responsive styling. Set styles per screen size from Global Styles or block settings "without custom CSS."
• Notes upgrades. Notes, the block comments added in 6.9, now support rich text and @mentions, multiple threads per block and inline notes on selected text.
• New blocks. Tabs, and Playlist for audio tracks.
• Persistent admin bar across all editors.
• Developer APIs. A public SVG Icon API, and Abilities API additions including "a filterable execution lifecycle, custom validation, and shared discovery."

The 7.1 announcement credits more than 800 contributors. Read it in full on WordPress.org News.

What did not ship

Real-time collaboration. Google Docs style co-editing was developed for 7.0 and then removed. The Make WordPress Core post of 8 May 2026 says "Real-time collaboration will not ship in WordPress 7.0," citing "surface area, race conditions, server load, memory efficiency, and recurring bugs found through fuzz testing." It is not in 7.1 either. On 18 September 2026, contributors wrote that their new approach "is in its early stages and not ready for Core inclusion today," with a feature plugin planned first and no date given.

A new default theme. There is no Twenty Twenty-Six. Twenty Twenty-Five remains the newest bundled default. A new default called Ipsum is proposed for 7.2; see block themes vs classic themes for the background.

Bundled AI providers. Core ships the AI Client and Connectors, but no provider is active until a site owner installs and configures one.

What it means for business sites

• Hosting. Sites still on PHP 7.2 or 7.3 cannot run 7.0 or 7.1. That usually also means the hosting stack is overdue for review; PHP 7.4, 8.0 and 8.1 are end-of-life and supported by WordPress only "for backward compatibility."
• Media workflows. With image processing in the browser, test uploads on the devices your team actually uses, and check how image-optimization plugins and CDNs behave with the new pipeline and AVIF files.
• Editorial teams. Notes make review easier, but plan for one editor per post at a time. Revisit who can comment versus publish; see WordPress user roles.
• Design work. Per-device visibility, block CSS and responsive styles reduce the need for custom CSS and some page-builder add-ons, especially on block themes.
• AI governance. Decide who is allowed to configure Connectors and which plugins may use them before someone pastes an API key into a production site.

Upgrade checklist for 7.1

1. Check PHP and database versions in Tools > Site Health. Move to a supported PHP version first (8.3 or newer is recommended).
2. Take a full backup of files and database, and confirm you can restore it.
3. Update on staging first. Update plugins and themes, then core, and test there.
4. Test critical paths: forms, checkout, logins, search, booking and any custom post types.
5. Test the editor: open several posts and templates, check custom blocks, page builders and meta boxes.
6. Test media: upload JPEG, PNG, HEIC and AVIF images, check thumbnails and image plugin output.
7. Review the admin: confirm custom admin pages and branding plugins still display correctly after the redesign.
8. Check Settings > Connectors and decide your AI policy, even if the answer is "not yet."
9. Update production during a low-traffic window and monitor error logs and Core Web Vitals afterward.
10. Keep automatic minor updates on so security releases such as 7.0.2 and 7.1.1 apply quickly.

Our guide to handling CMS, theme and plugin upgrades goes deeper on staging and rollback, and the WordPress security and updates checklist covers ongoing maintenance.

Looking ahead to WordPress 7.2

WordPress 7.2 is targeted for 10 December 2026 on the official roadmap. The 7.2 roadmap post (18 September 2026) lists planned work including "sudo mode" re-authentication for sensitive admin actions, a Secrets API, application password hardening, a suggestion mode for Notes, Description List and Table of Contents blocks and the new default theme Ipsum. The post itself cautions that a planned item "doesn't necessarily mean each will make it into the final release," so treat this as a direction, not a feature list.

Conclusion

WordPress 7.0 and 7.1 are substantial releases: AI infrastructure without AI by default, a refreshed admin, better design controls, a PHP 7.4 floor and in-browser image processing. They are not the collaborative-editing releases some coverage predicted. If you are not yet on 7.1.2, plan the upgrade now, starting with PHP. For more guides, visit the WordPress resource hub. If you would rather hand off testing and updates, eSEOspace provides website maintenance services for WordPress sites.

Frequently asked questions