Gutenberg 23.9 is now available with a quicker way to insert blocks, clearer indicators for customized styles and a long list of editor, accessibility and performance improvements. Here are the changes that matter to ordinary WordPress users and site builders.
What you need to know
- Gutenberg 23.9 was released on 2 September 2026.
- The most visible changes improve block insertion and reveal which blocks have custom style overrides.
- Group blocks gain separate horizontal and vertical spacing controls, while Global Styles expands to more elements.
- Gutenberg remains a feature plugin; production sites should back up and test compatibility before updating it.
What is Gutenberg 23.9?
Gutenberg is the WordPress project’s feature plugin for developing block-editor and site-editor capabilities before suitable work reaches WordPress core. Version 23.9 is a regular plugin release, not WordPress 7.1.1 and not a replacement for the WordPress core update.
The official release post emphasizes quality-of-life improvements. That description is accurate: the headline features reduce searching and make existing design changes easier to understand. The full changelog also contains many component, accessibility, bug-fix and experimental changes aimed primarily at contributors and plugin developers.
| Area | Change | Main audience |
|---|---|---|
| Block insertion | Add a block from the selected parent’s toolbar | Editors |
| Global Styles | Identify and filter blocks with custom overrides | Designers |
| Layout | Set horizontal and vertical Group gaps independently | Site builders |
| Colors | Add custom duotone colors through Global Styles | Designers |
| Performance | Reduce expensive editor selector and style work | Editors and developers |
1. Insert blocks from the parent toolbar
Adding content inside a Group or Gallery could require changing the selection or moving through the document to find an inserter. Gutenberg 23.9 adds an inserter to the parent selector in the block toolbar.
In practical terms, an editor working inside a container can add another block closer to where the action is happening. This is a small interface change, but it reduces interruption on long pages and nested layouts. The release team says further inserter improvements are planned, so this should be treated as one step rather than a complete redesign.
2. Find blocks with custom style overrides
Global Styles now places an indicator beside blocks that have custom style overrides. It also offers a filter that gathers customized blocks together instead of making the user open every block’s settings to discover what changed.
This helps when inheriting a website or investigating why one block does not follow the theme defaults. It does not automatically reset or repair custom styles; it simply makes them easier to locate and review.
3. Set horizontal and vertical Group gaps separately
Flex and grid layouts can now use independent axial gaps in the Group block. A site builder can adjust the space between columns separately from the space between rows instead of relying on one value for both directions.
This is particularly useful when cards wrap on smaller screens. A layout may need a narrow horizontal gap on desktop but more vertical separation after items form multiple rows. Theme support and the exact controls exposed by a site can still affect what appears in the editor.
4. Customize more elements through Global Styles
Gutenberg 23.9 expands the Global Styles interface for citations, inputs and select elements. These elements could already be represented in theme.json, but exposing them through the visual interface makes the options more approachable for people who do not want to edit configuration files.
The release also allows <label> styling through the same system. Theme developers should test forms carefully because browser defaults, plugin CSS and theme rules can still interact in unexpected ways.
5. Add custom duotone colors in Global Styles
Theme-defined duotone palettes were already supported. The new release adds a Duotone tab that lets users create custom duotone colors through Global Styles rather than accepting only the theme’s supplied choices.
Publishers should still use a restrained palette and verify contrast. A visual effect that looks attractive on one image may reduce readability on another, particularly in dark mode or when text is placed over media.
6. Get several smaller editing conveniences
The release includes a command for viewing the current post, bulk metadata editing for Playlist tracks, an aspect-ratio option for DataViews grids and border-and-spacing support for the Query No Results block. The editor also receives improvements around hierarchical taxonomy filtering and List View shortcuts.
These additions do not have equal value for every website. Playlist work matters to audio publishers, while Query No Results controls are more relevant to block-theme templates. The useful takeaway is that 23.9 improves both day-to-day editing and less visible framework components.
7. Improve keyboard and screen-reader behavior
Accessibility work includes announcing publication-date changes to screen readers, improving labels in the Playlist block and keeping initial focus on the media-editor dialog. There are also refinements to the block styles interface and navigation controls.
These fixes are welcome, but installing the update does not make an entire website accessible automatically. Themes and third-party blocks still need correct headings, keyboard support, labels, color contrast and meaningful alternative text.
8. Reduce expensive editor work
Performance changes target several sources of repeated work inside the editor. The hierarchical term selector is faster for large taxonomies, relational :has() selectors should no longer force broad recalculation on every block selection, and Global Styles experiments with caching generated results.
Component theme code also avoids root-level relational selectors. These changes are aimed at editor responsiveness; they should not be advertised as a guaranteed front-end PageSpeed increase. A visitor-facing page is affected more directly by its theme, images, fonts, plugins, advertisements and caching configuration.
Should production websites install Gutenberg 23.9 immediately?
A development or staging website can install 23.9 to test upcoming editor behavior. On an important production site, take a database and files backup first, then check custom blocks, reusable patterns, forms, templates and publishing workflows.
Websites that do not use the Gutenberg plugin do not need to install it simply because a new version exists. WordPress core already includes stable block-editor features on its own schedule. The plugin is most appropriate for people who want earlier access or who actively test and contribute to the editor project.
- Create a restorable database and files backup.
- Update Gutenberg on staging.
- Open representative posts, pages and templates.
- Test saving, previews, reusable content and custom blocks.
- Check desktop and mobile output in both light and dark designs.
- Deploy only after the tests pass.
Our assessment
Gutenberg 23.9 is not a release built around one spectacular feature. Its value comes from removing friction: insert blocks where you are working, expose hidden style overrides and provide more precise layout controls.
That makes it worthwhile for block-theme builders and editorial teams that regularly work with nested layouts. Ordinary site owners can wait for these capabilities to mature into WordPress core unless they already use the feature plugin and have a safe update process.
Common questions
Is Gutenberg 23.9 the same as WordPress 7.1.1?
No. Gutenberg 23.9 is a feature-plugin release. WordPress 7.1.1 is a separate planned maintenance release for WordPress core.
Will Gutenberg 23.9 make a public website faster?
The release includes editor-performance work, but it does not guarantee a higher front-end performance score.
Do all WordPress sites need the Gutenberg plugin?
No. WordPress core includes the block editor. The plugin provides earlier access to ongoing Gutenberg development.
Should Gutenberg be tested on staging?
Yes, especially when a site uses custom blocks, a block theme, page-building extensions or an important editorial workflow.
Official sources
- WordPress Core: What’s new in Gutenberg 23.9?
- Gutenberg 23.9 official release checklist
- Gutenberg plugin on WordPress.org
Continue with our WordPress 7.1 update guide, follow security and maintenance coverage through the WordPress Security and Update Hub, and use a verified backup before following our Plesk on Ubuntu administration guide.
Comments