Gutenberg 23.3, released June 3, replaces the inline cropping tool with a modal-based media editor as the default experience. For developers, the release upgrades the editor from React 18 to React 19 — a change that phases out legacy rendering patterns across the Gutenberg codebase.
The modal retains the familiar Crop button entry point but consolidates freeform and aspect-ratio cropping, flip, rotation with snap controls, and metadata editing into one dedicated interface.
The experimental customizable WordPress dashboard gains five new widgets in this release. The experiment, accessible via WP-Admin > Gutenberg > Experiments by enabling “New Dashboard experience,” now includes Welcome, Quick Draft, Activity, Site Health, and Site Preview panels, each adapting automatically to different tile sizes. Users can adjust column count, rearrange widgets, and resize individual panels. The three key additions at a glance:
- Modal media editor
- Replaces scattered inline controls with a single overlay; the Crop button entry point is unchanged. No block markup changes — editor UX only.
- Responsive styles for block instances
- Extends responsive layout and border control to individual block instances via the Block Style States API. Previously limited to global theme settings.
- React 19 upgrade
- Removes support for string refs and
ReactDOM.renderfallbacks present in React 17 and earlier code. Most plugin code is unaffected; legacy patterns require a targeted audit.
Responsive styles for block instances build on the responsive Global Styles foundation introduced in 23.2. The Block Style States API — which manages per-style responsive overrides — now operates at the per-instance level, meaning individual blocks can carry their own responsive layout and border styles independently of global theme settings. The block inspector also shows only the settings relevant to the currently selected style state, reducing visual noise.
Real-time Collaboration sees a set of reliability fixes: Notes blocks now support multiple discussion threads, oversized payloads above 16 MiB are handled more gracefully, and connection-loss states no longer trigger refresh storms when multiple peers are editing. The Image block gains a “Mark as decorative” toggle for accessibility, and the Revisions interface gets higher-contrast diff markers that scale with the user’s system text-size preferences.
On the performance side, the release widens preload coverage for post editor loads, lazy-fetches user pattern categories, and shares MediaQueryList listeners across block instances rather than creating one per block — reducing overhead on pages with many blocks. DataViews — the list and table UI component used in the Site Editor and post lists — adopts @wordpress/theme design tokens in what the team describes as the first significant in-codebase adoption of that package. Several experimental component aliases — including __experimentalText, __experimentalHStack, and __experimentalVStack — continue their migration to stable @wordpress/ui equivalents, the emerging component library replacing experimental prefixes across the editor.
The React 19 upgrade is the change most likely to affect third-party plugin developers. Most code works without modification, but authors relying on removed legacy patterns should consult the React 19 upgrade documentation and the Gutenberg 23.3 changelog for migration notes. Gutenberg 23.3 is available now from the WordPress plugin directory.
