---
title: "Gutenberg 24.4 Release Candidate Explained"
url: https://nexterwp.com/blog/gutenberg-24-4-release-candidate/
date: 2026-11-09
modified: 2026-11-09
lang: en
author: "Aditya Sharma"
description: "Gutenberg 24.4 RC1 brings Notes search and reactions, faster Rich Text, core-admin icons and a few changes extension developers must check. Here is what matters."
image: https://nexterwp.com/wp-content/uploads/2026/11/gutenberg-24-4-featured-1024x538.webp
word_count: 1770
---

# Gutenberg 24.4 Release Candidate Explained

## Key Takeaways

- wp-env añade un tiempo de ejecución experimental que usa PHP y SQLite instalados localmente en lugar de Docker para desarrollar y probar Gutenberg.
- Notas incorpora búsqueda, filtro de estado y reacciones de pulgar arriba y signo más, con el selector de reacciones mostrado como una fila de emoji.
- Rich Text ordena los formatos del menú More de forma consistente y asigna ranuras de barra de herramientas por nombre a los formatos principales para evitar que la barra cambie cuando los plugins añaden formatos.
- Global Styles lista los tipos de bloque principales que sobrescriben estilos de elementos, mientras que las herramientas de diseño muestran un icono para cada opción de relación de aspecto y ponen primero los colores de fondo y texto en la paleta.
- Gutenberg 24.4 marca cambios que pueden romper extensiones, como la eliminación de lockOutline y lockSmall, insertBefore, insertAfter y offline, además del traslado de Theme build y Stylelint plugins a @wordpress/theme-build-tools.

The Gutenberg 24.4 release candidate landed on November 3, 2026, just days after Gutenberg 24.3 shipped. It is a large release made of many small improvements: sharper focus rings, search and reactions for Notes, a faster Rich Text field, a promoted set of admin icons, and a handful of changes that extension developers should check before they update. If you run the Gutenberg plugin on a staging site, or you build blocks and editor extensions, this guide sorts the long changelog into what matters.

Everything below comes from the official [Gutenberg v24.4.0-rc.1 release notes](https://github.com/WordPress/gutenberg/releases/tag/v24.4.0-rc.1) on GitHub. This is a release candidate, not the final build, so items can still change. The previous release is covered in the core team post [What's new in Gutenberg 24.3](https://make.wordpress.org/core/2026/11/02/whats-new-in-gutenberg-24-3-28-october/).

Table of Contents

## Gutenberg 24.4 At A Glance

The changelog is organised by area. The table below shows where the visible changes are. Most of the volume is design system and component work, which matters mainly to people building interfaces on top of the editor, while the editor-facing changes are smaller and more targeted.

![Table summarizing Gutenberg 24.4 RC1 changes by area](https://nexterwp.com/wp-content/uploads/2026/11/gutenberg-24-4-at-a-glance.webp)The main areas touched by Gutenberg 24.4 RC1, with one headline change for each.

## New: An Experimental wp-env Runtime

The only item filed under Features is for contributors and plugin authors. wp-env, the local environment tool used to develop and test Gutenberg, gains an experimental runtime that uses a locally installed PHP and SQLite instead of Docker. If you only need a quick WordPress to try a block or a patch, this can remove the container setup step. It is experimental, so treat it as a convenience and not a replacement for your normal test setup.

## Editor Changes You Will Notice

### Block Library

- **Content-only editing improves.** Button content, Comments Pagination link labels and Query Loop pagination link labels are easier to edit when a pattern is locked to content-only mode.
- **More design controls on pagination.** Comments Pagination Numbers gain border support, and Query Pagination Numbers gain border and padding support.
- **Group block.** The Auto/Manual grid toggle is removed, and an experimental Canvas variation of the Group block is added.
- **Social Icon.** You can edit the link from the inspector.
- **Select controls.** Archives, Audio, File, Latest Comments, List, Playlist, Post Author Avatar, Social Icons and Tag Cloud move their dropdowns to the `@wordpress/ui` package. You may see slightly different dropdown styling in those block settings.

### Block And Site Editors

- **Rich Text formats.** Formats in the More dropdown get a consistent order, and known core formats get dedicated, name-based toolbar slots. That should stop the toolbar from shuffling as plugins add formats.
- **Alignment menu.** A new action selects the block that constrains a child block's width, which helps when a wide or full-width block sits inside a constrained layout and you cannot tell why it will not grow.

### Design Tools And Global Styles

- The Dimensions tool shows an icon for each aspect ratio option.
- Global Styles lists the core block types that override an element's styles, so you can see why a heading or link looks different in one block.
- Background and text colors are placed first in the color palette.
- Fixes include preserving individual sides when editing padding and margin shorthand, showing the current value in Apply globally, and checking the visible color of text clipped to its background in the contrast checker.

***Also Read:** [WordPress 7.2 Guide](https://nexterwp.com/blog/wordpress-7-2/) for how these editor updates fit into the next WordPress release.*

## Notes And Collaboration

Notes, the commenting feature inside the editor, gets the most visible polish. The All Notes sidebar gains search and a status filter, which matters once a long post has dozens of threads. Notes also gain thumbs-up and plus reactions, and the reaction picker appears as a row of emoji. Collaborator avatars are hidden while you type so they do not sit in your way.

![Table of Notes and collaboration changes in Gutenberg 24.4](https://nexterwp.com/wp-content/uploads/2026/11/gutenberg-24-4-notes-collaboration.webp)Notes and collaboration changes in the 24.4 release candidate, from new features to bug fixes.

Several fixes make Notes safer in real editing sessions: inline notes are handled in merged text, notes shared by duplicated or split blocks are handled, thread-focus recovery is shared across actions, and reaction deletion now respects author checks and no longer changes resolved threads. If your team writes together, our guide to [WordPress real-time collaboration](https://nexterwp.com/blog/wordpress-real-time-collaboration/) explains the surrounding feature set.

## Media Editor: Still Experimental

The experimental media editor keeps growing. It now shows the file type and size in the header, adds PDF previews, animates its sidebar when it opens and closes, and groups Reset and Restore original under a History menu. Fixes correct canvas border radii and footer controls, and one fix prevents endless image-sideloading loops when the browser cannot decode a large image. All of this sits behind the experimental label, so do not build workflows around it yet.

## Icons: The core-admin Collection Grows

Two icon changes connect directly to WordPress 7.2. Gutenberg adds a database icon and exposes error, info and postComments in the `core-admin` collection. It also promotes the Dashicon replacements to `core-admin` and maps their Dashicons. That is the collection WordPress 7.2 uses to replace Dashicons in the admin bar and menu, as covered in our guide to [WordPress 7.2 SVG admin icons](https://nexterwp.com/blog/wordpress-7-2-svg-admin-icons/). The Storybook icon library also now shows icon details.

## Widget Dashboard And Developer Tools

The experimental Widget Dashboard receives several changes. Grid settings are forwarded to the surface, row heights render without snapping to presets, and widgets can declare an `example` in `widget.json`. A new `useWidgetIdentity` hook returns translated widget titles, and the Grid supports column-count steps based on container width. One of these is a behavior change, covered in the next section.

For tooling, the Design System MCP adds pattern tools built from the Storybook MDX manifest, wp-build limits esbuild concurrency, and the build pipeline later migrates from esbuild to Rolldown. The repo also adds an `npm run browse` command for driving the local WordPress site from the command line.

## Check Before You Update: Changes That Can Break Extensions

This is the section that deserves a careful read if you ship a plugin or theme that extends the editor. The release notes mark several changes as ones that consumers must act on.

![Table of changes extension developers should check in Gutenberg 24.4](https://nexterwp.com/wp-content/uploads/2026/11/gutenberg-24-4-developer-checks.webp)Six changes in the changelog that can affect extensions, with who each one touches.

| Change | What to do |
| ------ | ---------- |
| CheckboxControl now uses design system color tokens. Legacy `--wp-components-color-accent` and `--wp-components-color-accent-inverted` overrides no longer apply | Use `ThemeProvider` for customization |
| Widget Dashboard no longer applies automatic 600px and 960px breakpoints to numeric column counts | Supply a column-step map if you relied on them |
| DataViews standardizes action-label punctuation | Supply labels without ellipses; modal menu actions add translated ellipses |
| `lock` icon uses the former outline artwork; `lockOutline` and `lockSmall` exports are removed | Import `lock` instead |
| `insertBefore`, `insertAfter` and `offline` icon exports are removed | Replace them with another icon |
| Theme build and Stylelint plugins move to `@wordpress/theme-build-tools` and leave `@wordpress/theme` | Update your imports |
| Public `checkbox-control` and `radio-control` Sass mixins are removed from `@wordpress/base-styles` | Their styles now live in the components themselves |
| Legacy FormToggle, Tooltip, ProgressBar, TabbableContainer and CustomGradientPicker are deprecated | Plan a migration to the newer components |

A few smaller items are worth knowing too. RadioControl moves its group help text below the fieldset label and drops the legacy `components-base-control__help` class, so custom CSS that targets that class will stop matching. The Global Styles inheritance-indicators experiment is removed. Obsolete `--wp-components-color-*` overrides are removed as well.

## Performance And Accessibility

Performance work in this release targets the editor itself. Rich Text initialization and editing overhead drops by batching DOM updates, parsing unfocused fields on mount, and simplifying field registration, event listeners, selection tracking and undo handling. Resetting content now preserves unchanged blocks, so undo does not re-render the entire post. The parser uses less memory and time on documents with deeply nested, unclosed blocks. Block migrations are logged only when `SCRIPT_DEBUG` is enabled.

![Table of performance and accessibility fixes in Gutenberg 24.4](https://nexterwp.com/wp-content/uploads/2026/11/gutenberg-24-4-performance-accessibility.webp)Performance and accessibility changes, grouped by area.

Accessibility fixes include preventing invalid LaTeX from trapping keyboard focus in the Math block and inline math controls, adding `Notice.List` with live announcements, preserving dialog boundaries in Modal under forced-colors mode, showing the pressed state of reaction pills in forced-colors mode, and giving URL submit buttons consistent identification. The Interactivity API also gets two changes: it ignores router regions and `attachTo` targets inside `data-wp-html` content, and it loads Interactivity Router script modules without `eval()` or WebAssembly, which helps sites with strict Content Security Policy rules.

## Security And Output Hygiene

Two items touch security-adjacent behavior. The KSES filter now allows CSS color functions in inline styles, and the sanitizer allows CSS custom properties in block gaps. Documentation also adds agent guidance for escaping PHP output and preventing cross-site scripting, and records the 7.1.4 security patch releases. None of these is an advisory. They are the kind of small changes that decide whether valid styles survive saving, so check any content that depends on modern color syntax.

## How To Test The Release Candidate Safely

- **Use a staging copy.** Install the Gutenberg plugin release candidate on a clone, not on a live site.
- **Open your most complex post** and check the toolbar, the alignment menu, and the Group and pagination blocks.
- **Try Notes with a teammate** if you use collaboration: search, filter, add a reaction and resolve a thread.
- **Review custom CSS** that targets `components-base-control__help`, CheckboxControl colors or legacy component styles.
- **Search your build files** for the removed icon exports and for imports from `@wordpress/theme` that moved.
- **Run with `SCRIPT_DEBUG` on** to see block migration logs and catch console warnings.
- **Compare with the final release notes** once 24.4 ships, because RC items can change.

## Should You Install It?

For most site owners the answer is to wait. The Gutenberg plugin is a testing ground, and the features that matter most, such as Notes and the icon work, flow into WordPress core releases over time. Install the release candidate if you build blocks, maintain an editor extension, or want early notice of changes that will land in WordPress 7.2. If you build themes, the pagination and Global Styles changes are the ones to try first. Our guide on [block themes versus classic themes](https://nexterwp.com/blog/wordpress-fse-block-themes-vs-classic-themes/) explains why those editor features matter for site design.

## What This Doesn’t Cover

This guide summarises the release candidate changelog and did not run the plugin, so it makes no claims about measured speed gains. The tables are reference summaries built from the notes, not screenshots of the editor. It also skips most of the internal items, such as TypeScript conversions, test stabilisation, CI changes and Storybook updates, which affect contributors more than users. For the full list with pull request links, use the GitHub release page above.

#### Suggested Reading

- [WordPress 7.2 Guide](https://nexterwp.com/blog/wordpress-7-2/)
- [WordPress 7.2 SVG Admin Icons](https://nexterwp.com/blog/wordpress-7-2-svg-admin-icons/)
- [WordPress Real-Time Collaboration](https://nexterwp.com/blog/wordpress-real-time-collaboration/)
- [How To Fix WordPress Block Patterns](https://nexterwp.com/blog/how-to-fix-wordpress-block-patterns/)

#### Stay updated with Helpful WordPress Tips, Insider Insights, and Exclusive Updates – Subscribe now to keep up with Everything Happening on WordPress!

Subscribe

## Frequently Asked Questions

**Q: Why is Gutenberg 24.4 worth testing on staging instead of a live site?**
A: Gutenberg 24.4 is a release candidate, so the safest move is to test it on a staging clone first. The release includes editor changes, Notes updates, icon changes, and several extension-breaking shifts such as removed icon exports and moved theme-build imports. That mix makes it useful for early compatibility checks, but not something to trust on production until the final notes land.

**Q: What changes in Gutenberg 24.4 are most likely to break custom blocks or extensions?**
A: The biggest risk is in the extension-facing cleanup. CheckboxControl now uses design system color tokens, several icon exports were removed, Theme build and Stylelint plugins moved to @wordpress/theme-build-tools, and legacy FormToggle, Tooltip, ProgressBar, TabbableContainer and CustomGradientPicker are deprecated. If your code targets old Sass mixins or old icon names, this release can expose it fast.

**Q: How does Gutenberg 24.4 affect Notes and real-time collaboration?**
A: Notes gets the most visible polish in this release candidate. The All Notes sidebar adds search and a status filter, reactions now include thumbs-up and plus options, and collaborator avatars hide while you type so they do not get in the way. The safer part is under the hood too: inline notes in merged text, duplicated or split blocks, and reaction deletion all got fixes that matter in shared editing sessions. For context, see [WordPress Real-Time Collaboration](https://nexterwp.com/blog/wordpress-real-time-collaboration/).

**Q: What should theme developers check first in Gutenberg 24.4?**
A: Theme developers should start with pagination and Global Styles. Pagination blocks gained more design control, while Global Styles now lists the core block types that override an element’s styles, which helps explain why a heading or link looks different in one block than another. The color palette also puts background and text colors first, so visual decisions are easier to spot when you are tuning a theme.

**Q: Does Gutenberg 24.4 change anything for block themes versus classic themes?**
A: The release leans into block-theme style workflows more than classic-theme ones because several changes sit in Global Styles, pagination design tools, and editor layout behavior. That matters when a theme depends on inherited styles or constrained layouts inside the block editor. If you are comparing approaches, [block themes versus classic themes](https://nexterwp.com/blog/wordpress-fse-block-themes-vs-classic-themes/) is the right lens for why these editor changes matter.

**Q: What is the safest way to test Gutenberg 24.4 without breaking a site?**
A: The safest test path is a staging copy with your most complex post open first. Check the toolbar order, alignment menu behavior, Group and pagination blocks, then review any custom CSS that targets components-base-control__help or old CheckboxControl colors. It also helps to search build files for removed icon exports and run with SCRIPT_DEBUG enabled so block migration logs show up during testing.