MW
Tutorial

What's New in WordPress 7.1 for Developers

WordPress 7.1 field guide for developers: client-side media, Abilities API, always-iframed editor, SVG Icon API, global styles, and what to test before users upgrade.

intermediate 18 min Aug 20, 2026
Comfortable with WordPress hooks, REST, and the block editor You have read — or at least skimmed — the WordPress 7.0 series

WHAT'S NEW IN WORDPRESS 7.1 FOR…

WordPress 7.1 is the follow-up to WordPress 7.0. 7.0 put AI into Core. 7.1 makes the platform around that AI — media, abilities, editor isolation, icons, and styles — actually usable at scale.

This tutorial is the map. The rest of the series is the terrain.

The numbers

WordPress 7.1 closed more than 310 Core Trac tickets: over 100 enhancements and feature requests, more than 180 bug fixes, and 40+ editor tickets. Gutenberg 22.7 through 23.6 added almost 600 enhancements and more than 630 bug fixes. Diff vs 7.0.2: 20 new hooks (19 filters, 1 action), 1,480 files changed.

310+
Core Trac tickets
180+
Core bug fixes
20
New hooks
46
A11y-focused tickets

Accessibility (46), UI (40), and administration (28) took the most Core focus. That is the character of this release: fewer splashy user-facing blocks, more plumbing.

The six things that matter

  • Client-side media
  • Abilities API
  • Always-iframed editor
  • SVG Icon API
  • Global Styles
  • Persistent toolbar
If you only remember six names from WordPress 7.1, remember these.
  1. Client-side media processing — images compress, resize, convert, and generate thumbnails in the browser via wasm-vips. HEIC from iPhones just works. Server PHP memory limits stop being the bottleneck.
  2. Abilities API — 7.0 introduced abilities. 7.1 makes them filterable, publicly exposable, schema-ready for clients, and auditable on every invocation.
  3. Always-iframed post editor — 7.0 iframed the editor only when every block in the post was API v3. 7.1 iframes it always, including sites with legacy meta boxes.
  4. SVG Icon API — register collections and icons, render them in PHP with wp_get_icon(), and expose them over REST. The Icon block can pick from your set.
  5. Global Styles — responsive style variations, configurable viewports, extra interaction states, and text-shadow. Themes stay inside the Global Styles system instead of inventing CSS.
  6. Persistent admin bar — the toolbar stays visible in the Post and Site Editors. The W logo no longer means “exit.”

How this series is organised

What 7.1 is not

Real-time collaborative editing was tested during the cycle and is not enabled. React 19 was punted (still an experiment in the Gutenberg plugin). The Classic block stays in the inserter. The “On This Day” dashboard widget did not ship.

Those absences matter. Do not budget a 7.1 launch around collaboration or React 19. Part 6 lists every punt so you can plan against reality.

Who should jump where

  • Block plugin authors → Part 4 first, then the Part 6 checklist.
  • AI / MCP / abilities authors → Part 3. Pair with WordPress 7.0 AI if you skipped 7.0.
  • Media, watermarking, CDN plugins → Part 2. wp_generate_attachment_metadata still fires — twice.
  • Theme authors → Part 5.

Frequently asked questions

WordPress 7.1 — quick answers

When did WordPress 7.1 ship?

The Field Guide published during the release-candidate phase on 5 August 2026. Treat RC as the moment to test; do not wait for the final blog post on wordpress.org/news.

What is the biggest breaking change in WordPress 7.1?

The post editor is always iframed, regardless of block API version or legacy meta boxes. Plugins that query the global document or window for canvas nodes will break.

Does client-side media processing replace server image editors?

On supporting Chromium browsers, yes for the editor upload path. Other browsers fall back to GD/Imagick. Plugins that hook wp_generate_attachment_metadata still run.

Is WordPress 7.1 an AI release like 7.0?

No. 7.0 shipped the WP AI Client, Abilities API, and Connectors. 7.1 hardens abilities for discovery, exposure, validation, and client schemas.

Did the Classic block get removed?

No. An early proposal to hide it from the inserter was reverted. Existing Classic block content and new insertions both remain.

Next: Client-Side Media Processing in WordPress 7.1 — the feature that changes every image upload.

Part 1 of 6 in WordPress 7.1 Field Guide for Developers
You've completed this tutorial!

Get the next one in your inbox. Practical tips, no fluff.

Subscribe

More tutorials

View all

Get weekly notes in your inbox

Practical tips, tutorials and resources. No spam.