Gutenberg 23.4: Resilient Media Uploads, an Opt-In React 19, and the Admin’s Visual Convergence

June 17, 2026 — Gutenberg 23.4 shipped June 17 with three threads that all point the same direction: an upload pipeline that survives bad networks, React 19 returning as an opt-in experiment after June’s revert, and the admin editor adopting one consistent visual shell. Where recent releases moved layout and image-production work into the editor, this one targets the unglamorous infrastructure underneath — retries, offline queues, and visual consistency — the reliability layer newsrooms have historically paid CMS teams to build by hand.

Key Themes

Media uploads now retry with exponential backoff, pause when the connection drops, and resume automatically — reliability that previously lived in custom upload code.
React 19 returns as an opt-in experimental flag after the June revert, giving publishers a real environment to run their compatibility audit before it becomes the default.
UltraHDR JPEGs are detected on upload and their gain maps preserved through resizing, a quiet acknowledgment that modern phone cameras are already in the field.
The Site Editor now follows each user’s admin color scheme, and Grid transforms let Columns and Gallery blocks convert without losing content.
The experimental dashboard keeps compounding — a community Events widget, container-query columns, and size-preset row heights.

Jump to: 🖼️ Media Uploads & Editor · ⚛️ React 19 · 🎛️ Admin & Dashboard · 📐 Grid Transforms · 👥 Collaboration · 🔧 Smaller Updates · 💡 Takeaways

🖼️ Uploads That Survive the Field

The media pipeline got the kind of hardening that only matters until the moment it does. Uploads now carry retry logic with exponential backoff and broader network resilience, and the upload queue pauses when a device goes offline and resumes automatically when it reconnects (#76765). The Block Editor gains an upload-progress snackbar with batch counts (#77249), so a bulk import reports its own status instead of leaving the editor guessing. UltraHDR JPEGs are now detected on upload, with originals left untouched while resized sub-sizes preserve their ISO 21496-1 gain maps (#74873). The modal media editor introduced last cycle kept refining: editable attachment fields moved to the top of the details panel (#78896, #78792), the mobile toolbar gained an aspect-ratio control (#78935), and zoom swapped its slider for plus/minus buttons (#78928).

Why this matters: 23.3 gave photo desks a better cropping modal; 23.4 makes the upload itself trustworthy. The reporter filing from a stadium concourse, the photographer on hotel Wi-Fi, the editor bulk-importing a gallery on deadline — these are the cases where stock WordPress uploads have always lost work, and where large publishers wrote their own resilient uploaders to compensate. Retries, offline queueing, and batch progress close that gap in core. UltraHDR support is the forward-looking note: the gain-map data that makes modern phone photos pop is now preserved by default, which matters for any publication whose contributors shoot on recent iPhone and Pixel hardware.

⚛️ React 19, This Time Behind a Flag

After 23.3 built the editor on React 19 and then reverted it on June 5 — plugins bundling React 18’s JSX runtime helpers crashed against the new version — the re-landing arrives as an opt-in experiment rather than a default. A new experimental flag registers the React 19 runtime scripts (react, react-dom, react-jsx-runtime) for testing, reachable at /wp-admin/admin.php?page=experiments-wp-admin (#79077, #78685, #79142). The flag stays off until React 19 becomes the default in a later cycle, targeted at WordPress 7.1.

Why this matters: The 23.3 recap called React 19 the audit trigger, and the June roundup tracked the pause. This release turns that audit from a paper exercise into something publishers can actually run — flip the flag on a staging environment, load every custom block, editor plugin, and admin screen against the React 19 runtime, and catch the string refs, ReactDOM.render fallbacks, and defaultProps on function components before the default flip removes the choice. The crash that forced the June revert is the warning: the riskiest code is the dependency you bundled and forgot. An opt-in flag is exactly the runway to find it on your schedule.

🎛️ The Admin Editor Converges

Two strands of the long admin-rebuild arc advanced together. The Site Editor’s sidebar and page shell now follow the user’s WordPress admin color scheme (#78397), erasing one of the last visual seams between the block editor and the surrounding dashboard. The experimental dashboard kept its steady cadence: a new Events widget surfaces WordPress community events (#78553), the widget grid moved to responsive columns driven by container breakpoints (#78732), and row-height controls were replaced with size presets (#78735). It remains behind a flag.

Why this matters: The color-scheme alignment is small on its own but consistent with the direction — the editor is no longer a foreign surface bolted onto wp-admin; it inherits the same shell. The dashboard arc is now four releases deep without wavering, and the shift to container-query columns is the tell: this is being built as a real responsive layout system, not a toy. Publishers running custom legacy dashboard widgets should keep an eye on compatibility, and platform teams should keep sketching what a newsroom home screen — editorial calendar, publish queue, traffic tiles — looks like as first-class widgets rather than admin-page bolt-ons.

📐 Grid Transforms Without the Rebuild

Block transforms can now target specific variations of other blocks, and the first payoff is the Grid block: Columns and Gallery blocks transform into Grid variations while preserving their content (#78713).

Why this matters: Layout migration is usually a copy-paste-and-rebuild chore. Letting an existing Columns or Gallery layout convert to Grid in place lowers the cost of adopting the newer, more flexible layout primitive across an archive of older posts and patterns — useful when a design-system refresh wants Grid behavior without re-laying-out every feature package by hand.

👥 Collaboration Plumbing, Quieter Still

Real-time collaboration got a maintenance-heavy cycle rather than new visible features:

A separate document-persistence endpoint splits save logic from the live sync layer (#78891).
Collaborator-overlay rerenders, polling, and forbidden-room handling were all tightened (#78636, #78811, #78748).
CRDT typing and undo-manager fixes address edge cases in concurrent editing (#78756, #78864).

Why this matters: The same lesson as 23.3 — co-editing earns trust through reliability, not features. Splitting persistence from sync and fixing undo and CRDT edge cases is the unglamorous work that decides whether a distributed newsroom keeps drafting in Google Docs or finally moves into the editor. No headline here, but the trajectory toward production-grade collaboration holds.

🔧 Performance, Components, and Smaller Fixes

The React Native codebase is gone. Gutenberg removed its React Native implementation, framework, and dependencies entirely (#78747) — a meaningful cleanup that sheds the mobile-app baggage from the web editor repository and trims build complexity.

DataViews extracted its entity view configuration from the REST controller into a reusable, filterable function (#78977) and added a “pickerActivity” layout to DataViewsPicker (#78941) — relevant to anyone building custom admin list screens on the framework.

The component library kept maturing: the Tooltip migrated to a Shell-level provider (#78692, #78691), Combobox primitives landed (#78399), theme element size tokens were added (#76545), stroke contrast targets rose to 2.9 (#77599), and @base-ui/react updated to 1.5.0 (#78448).

Smaller wins: the Playlist block gained a waveform-style selector and track-length setting (#76147, #78954); the Login/out block can now sit inside a Navigation Submenu (#75497); accessibility fixes covered boot navigation list semantics (#78829), inserter spoken messaging (#79004), and Font Library focus (#78671); and bug fixes resolved media-editor sidebar overflow (#78931), crop handles on large images (#79011), and a shortcode-transform crash (#78770).

💡 Takeaways

Run your React 19 audit in the new experiment. Flip the flag at experiments-wp-admin on staging, load every custom block and editor plugin, and fix string refs, ReactDOM.render, and defaultProps before the default flip in 7.1.
Put resilient uploads in front of your field team. Test the offline-pause-and-resume queue and batch progress against the way reporters and photographers actually file — from venues, on cellular, in bulk.
Evaluate UltraHDR handling. If your contributors shoot on recent phones, confirm the preserved gain maps render the way your art direction expects across your theme.
Pilot Grid transforms on a layout refresh. Convert existing Columns and Gallery patterns to Grid in place rather than rebuilding them, and check the result against your design-system rules.
Keep watching the admin rebuild. Four releases of dashboard iteration plus the Site Editor color-scheme alignment is a clear trajectory — inventory legacy dashboard widgets and start scoping a newsroom home screen.

The full changelog is available on Make WordPress Core.