# WordPress 7.1 RC1 Ships: What Changes Before the Aug 19 Launch

Page: https://hirantha.me/blog/wordpress-71-rc1-ships-what-changes-before-the-aug-19-launch
Published: 2026-08-16
Written by: hirantha.me Newsroom (AI-generated). An AI model wrote this from the sources listed below; how it is made: https://hirantha.me/about/newsroom
Topics: wordpress, wordpress-7-1, block-editor, gutenberg, cms-updates

> WordPress 7.1's release candidate adds responsive block styling, client-side media processing, and two new blocks ahead of its August 19 general release.

WordPress 7.1 has reached Release Candidate 1 (RC1), the testing build that precedes a final release. WordPress.org published RC1 on August 5, 2026, alongside the official Field Guide that documents every developer-facing change in the version. The final, general-availability (GA) release is scheduled for August 19, 2026, timed to close out WordCamp US 2026 in Phoenix, Arizona (August 16-19).

The headline number is 145: that is how many updates and fixes landed since Beta 4, split between 57 in the block editor and 88 in Core, according to the official WordPress.org announcement. Zoomed out further, the Field Guide reports more than 310 Core Trac tickets for the release (over 100 enhancements and feature requests, plus more than 180 bug fixes), alongside almost 600 enhancements and over 630 bug fixes contributed through the Gutenberg plugin, as reported by The Repository. A code diff between WordPress 7.0.2 and the current trunk shows roughly 1,480 changed files and more than 88,000 line insertions, also per The Repository.

## What changes for people who build pages

The biggest shift in this release is that responsive design and interactive styling move into the block editor itself, rather than requiring custom code or a page-builder plugin. Editors get responsive style variations and configurable viewport breakpoints defined through a theme's theme.json file, plus controls for hover, focus, and active states on blocks, according to the official Field Guide. Text-shadow support has also been added to global styles.

Two new blocks arrive alongside those styling tools: a Playlist block for embedding a list of audio files, with an optional waveform display, and a Tabs block for building clickable content panels, as detailed by SmartWP and The Repository. Both were part of the feature set introduced back at Beta 1 and remain unchanged through RC1.

Media handling also gets an overhaul. Client-side media processing moves supported image operations, such as cropping and rotating, into the browser before a file ever reaches the server, per the Field Guide. The REST API now validates image dimensions, picks size-aware encoding quality, and can register a single sideloaded file across multiple image sizes. SmartWP additionally reports expanded format support, including HEIC, UltraHDR, AVIF, and WebP, along with GIF-to-video conversion, a new media editor modal for cropping, rotation, and metadata, and automatic retry of uploads that drop mid-transfer.

On the admin side, the toolbar now stays visible while navigating between the front end, wp-admin, the Site Editor, and the Block Editor, instead of disappearing inside the full-screen editing views, according to the Field Guide and SmartWP. SmartWP also reports smaller admin changes: the command palette now groups results into Recent, matching, and Suggestions; site title, tagline, and icon settings move into a consolidated Identity section; the posts list shows excerpts; and comment threading has been fixed so a comment's parent can be changed after the fact.

## What changes for theme and plugin developers

WordPress 7.1 completes the editor's move to an iframed, isolated rendering context. The Repository and SmartWP both report that blocks still built on Block API version 2 or earlier will need updating to version 3 to keep working correctly under the enforced iframed editor. This is the kind of change that can silently break older custom blocks, so it is worth auditing any third-party or in-house blocks before updating a production site.

The bundled jQuery UI library moves to version 1.14.2, which The Repository and SmartWP both flag as worth testing against, since plugins that hook into older jQuery UI behavior can be affected. The Field Guide also documents refinements to the Abilities API, and The Repository counts 20 new hooks (19 filters and one action) introduced across the release.

Two features that were expected earlier in the cycle did not make it into 7.1. Real-time collaboration, which was pulled from WordPress 7.0 earlier in 2026, remains excluded from 7.1 as well, per The Repository. A planned upgrade to React 19 has also been deferred beyond this release and continues only as an experiment inside the Gutenberg plugin.

## Where things stand and what happens next

Reaching RC1 puts WordPress 7.1 into a hard string freeze: no new translatable text can be added, which lets the Polyglots translation team finish its work, and only regression fixes or test-suite additions are meant to land from here, as reported by The Repository. According to WordPress.org's published release schedule, RC1 arrived August 5, RC2 followed August 6, and RC3 landed August 12, with a 24-hour code freeze and dry run set for August 17 ahead of the general release party on August 19.

## What this means in practice

RC1 is a testing build, not a production release. Site owners running production sites should not install it live; the safer path is to update a staging copy, or a disposable test install, and confirm that active plugins and any custom blocks still behave correctly under the enforced iframed editor and the updated jQuery UI. Plugin and theme developers are specifically encouraged by the WordPress project to test their products against RC1 now and update the "Tested up to" line in their readme files before GA lands.

For everyday site owners, once WordPress 7.1 reaches general availability on August 19, the update itself should be routine for most sites, since the core changes are additive: new editing controls, new blocks, and a smoother media upload flow. The main risk sits with older or poorly maintained plugins and custom blocks built against outdated APIs, so a quick staging test before updating a live site remains the sensible move, particularly for sites that rely on heavily customized blocks or older jQuery UI-dependent plugins.

## Questions

**When does WordPress 7.1 release?**
WordPress 7.1 is scheduled for general release on August 19, 2026, timed to WordCamp US 2026 in Phoenix. Release Candidate 1 shipped August 5, 2026.

**Is WordPress 7.1 safe to update to right now?**
The current build is a release candidate meant for testing on staging sites, not production. Wait for the August 19 general release, and test plugins and custom blocks on staging first.

**What's new in the WordPress 7.1 block editor?**
Built-in responsive style controls with configurable viewport breakpoints, hover/focus/active state styling, text-shadow support, and two new blocks: Playlist and Tabs.

**Does WordPress 7.1 include real-time collaborative editing?**
No. Real-time collaboration was pulled from WordPress 7.0 earlier in 2026 and remains excluded from the 7.1 release, according to The Repository.

**Will WordPress 7.1 break my theme or plugins?**
It can, particularly for custom blocks still built on Block API v2 or earlier, since 7.1 enforces the iframed editor, and for plugins tied to older jQuery UI behavior, since the bundled library moves to version 1.14.2.

## Sources

- [WordPress 7.1 Release Candidate 1](https://wordpress.org/news/2026/08/wordpress-7-1-release-candidate-1/), WordPress.org News
- [WordPress 7.1 Release Candidate 1 Ships With Field Guide and 145 Fixes Ahead of WordCamp US Launch](https://www.therepository.email/wordpress-7-1-release-candidate-1-ships-with-field-guide-and-145-fixes-ahead-of-wordcamp-us-launch), The Repository
- [WordPress 7.1: Everything You Need to Know](https://smartwp.com/wordpress-7-1/), SmartWP
- [WordPress 7.1 Field Guide](https://make.wordpress.org/core/2026/08/05/wordpress-7-1-field-guide/), Make WordPress Core
- [WordPress 7.1 Release Party Schedule](https://make.wordpress.org/core/2026/07/03/wordpress-7-1-release-party-schedule/), Make WordPress Core