WordPress 7.0 landed on June 10, 2026, and if you blinked you might have missed it. No dramatic rebrand, no dashboard overhaul that breaks your site overnight. Instead, the update ships a handful of changes that quietly make your day-to-day content work faster — and one feature that could change how your team edits together.

The new media editor is the headline

Gutenberg 23.3 ships with a completely rebuilt media editor modal that's now the default image editing experience inside the block editor. Crop, rotate, zoom, flip, adjust aspect ratios, edit metadata — all without leaving WordPress. No more uploading an image, realizing it's sideways, opening a separate tool, re-exporting, and re-uploading. It sounds small until you've done it 400 times across a product catalog.

For anyone running a WooCommerce store, managing a restaurant menu, or publishing event photos weekly, this eliminates a real friction point. The old workflow was: upload, preview, swear, open Photoshop, crop, re-upload. The new one is: upload, fix it right there, move on.

Your browser is doing more of the heavy lifting

WordPress is also pushing client-side image processing forward. When you upload an image, the browser itself can now generate sub-sizes — the thumbnails, medium sizes, and other variants WordPress needs — instead of sending everything to the server first. If your browser can't handle it (older machines, unusual formats), the server still catches it as a fallback.

This matters for two reasons. First, uploads feel faster because the processing happens on your machine. Second, it opens the door to better support for modern image formats like WebP, AVIF, HEIC, and JPEG XL. If you've ever uploaded a photo from your iPhone and wondered why WordPress couldn't process the HEIC file, this is the fix in motion. It's not fully shipped yet — the 7.1 cycle is where it matures — but the foundation is in 7.0.

Collaborative editing is coming (but not yet)

The feature everyone's been waiting for — real-time collaborative editing, where multiple people can work on the same post simultaneously like Google Docs — didn't make it into 7.0. But the 7.1 development cycle has already started testing it. WordPress is treating this as a publisher and agency feature first: the goal is letting your content team work inside the same post without stepping on each other's changes.

If you run a site with multiple contributors, editors, or a marketing team that currently passes drafts around via email or Google Docs before copy-pasting into WordPress, this will eventually eliminate that entire round-trip. Not today, but soon.

What to do right now

Update to 7.0. It's a standard WordPress update — backup first, then one-click from your dashboard. If you're on managed hosting (WP Engine, Kinsta, SiteGround), your host may have already tested and staged it for you.

After updating, try the new media editor on your next post. Upload an image, click the edit button in the block editor, and see how it feels. If you've been using a plugin for basic image editing in WordPress, you might be able to drop it.

For developers maintaining custom themes or plugins: React 19 compatibility is the thing to watch. WordPress 7.0 makes progress here, and 7.1 will push further. If your site uses custom blocks or heavily modified Gutenberg integrations, test against the new release before pushing to production.

The full developer roundup is on the WordPress Developer Blog, published June 10. It covers the technical details on client-side processing, Playground updates, and what's ahead for 7.1.