WordPress 7.1 Field Guide for Developers
A developer's field guide to WordPress 7.1 — client-side media processing, Abilities API upgrades, the always-iframed editor, SVG Icon API, global styles, and a compatibility checklist.
What you'll learn
Process images in the browser with the new media APIs
Filter, expose, and audit abilities for REST and AI clients
Fix plugins that break in the always-iframed post editor
Register SVG icons and use new Global Styles controls
Know what 7.1 shipped — and what was punted
Ship a plugin or theme that is WordPress 7.1-ready
Tutorials in this series
- 01 18 minWhat's New in WordPress 7.1 for DevelopersThe 7.1 map: 310 Core tickets, the features that matter, and what to test first.
- 02 25 minClient-Side Media Processing in WordPress 7.1wasm-vips in the browser, sideload REST, HEIC/AVIF, and how plugins still hook in.
- 03 25 minAbilities API Changes in WordPress 7.1public exposure, wp_get_abilities() filtering, lifecycle hooks, and typed REST input.
- 04 22 minWordPress 7.1 Editor Changes: Iframe, Blocks & DataViewsAlways-iframed post editor, new block supports, DataViews, and the persistent toolbar.
- 05 20 minGlobal Styles, SVG Icons & Design System in WordPress 7.1Responsive styles, text-shadow, the SVG Icon API, and Design System theming tokens.
- 06 22 minHow to Prepare Your Plugin or Theme for WordPress 7.1A step-by-step compatibility checklist — plus everything that did not ship in 7.1.
WordPress 7.1 is in release-candidate as of August 2026. It is not another “AI headline” release — that was WordPress 7.0. This one is infrastructure: images process in the browser, abilities become discoverable for REST and AI clients, and the post editor is always iframed.
The official WordPress 7.1 Field Guide is the source. This series is the working-developer version: what each feature actually does, which hooks you need, and what will break the day your users update.
Who this series is for:
- You build or maintain WordPress plugins and themes and need the 7.1 changelog in code terms
- You ship custom blocks and still reach for
documentorwindowin the editor canvas - You registered abilities in 7.0 and now need
public, filtering, and lifecycle hooks - You want a test checklist, not a press-release recap
What this series is NOT:
- An end-user “what’s new” tour — this is developer-facing throughout
- A replacement for the official Field Guide — confirm signatures against Core docs
- Coverage of features that did not ship (collaboration, React 19, Classic-block hiding) except in Part 6, so you do not plan around them
Start at Part 1 for the map. If you maintain block plugins, skip to Part 4 — the always-iframed editor is the change most likely to break existing JavaScript. If you ship AI or MCP integrations, start at Part 3.
Get weekly notes in your inbox
Practical tips, tutorials and resources. No spam.