WordPress 6.7, 6.8, and 6.9: What’s Actually New for Site Builders

Three WordPress core releases shipped in the space of about a year — 6.7, 6.8, and 6.9 — and between them they quietly changed how fast WordPress sites feel, how secure default installs are, and what “collaboration” in the block editor actually means. If you’ve been putting off checking what actually landed in core recently, here’s what’s genuinely worth knowing.

WordPress 6.7 “Rollins” — November 12, 2024

6.7 shipped a Zoom Out mode for the site editor, letting you see and rearrange page sections at a higher level without editing individual blocks directly — a genuinely useful addition for anyone building layouts visually rather than block-by-block. It also brought an enhanced Font Library and fluid typography improvements, and introduced Twenty Twenty-Five as the new default theme, itself a full block theme.

WordPress 6.8 “Cecil” — March 25, 2025

6.8 is the release I’d point to as the most quietly consequential of the three for performance and security, even though neither made the flashiest headlines. It shipped Speculative Loading — a browser prefetch/prerender mechanism that anticipates likely next-page navigations and starts loading them before a visitor actually clicks, which can meaningfully improve perceived navigation speed on content-heavy sites without requiring any theme or plugin changes to benefit from it.

On the security side, 6.8 switched WordPress’s default password hashing to bcrypt — a much stronger, more modern hashing algorithm than what WordPress had been using. That’s a foundational security improvement that applies to every new password hash generated going forward, quietly strengthening the baseline for the entire ecosystem. 6.8 also restructured the Style Book interface, optimized WP_Query’s caching keys for better database performance, and included more than 100 accessibility fixes.

A password-hashing upgrade doesn’t get a highlight reel the way a new editor feature does, but switching WordPress’s default to bcrypt is exactly the kind of unglamorous change that matters more, at scale, than most visible feature releases.

WordPress 6.9 “Gene” — December 2, 2025

6.9 delivered the first genuinely real piece of Gutenberg’s long-promised Phase 3 collaboration work: block-level Notes, letting people leave comments directly on specific blocks within the editor, similar to commenting on a specific paragraph in a shared document. This has been on the roadmap conceptually for years — 6.9 is where it actually shipped in a usable form.

The release also added new blocks — Accordion, Math, Terms Query, and a Time-to-Read block — an Abilities API for more structured plugin/theme capability declarations, and PHP 8.5 compatibility.

Why the phase-by-phase context matters

WordPress’s official four-phase Gutenberg roadmap is genuinely worth knowing, because it explains why certain features show up when they do: Phase 1 was easier editing (the original block editor itself), Phase 2 was customization and full site editing (which culminated around WordPress 6.3), Phase 3 is collaboration — the phase 6.9’s Notes feature actually belongs to — and Phase 4, multilingual support, hasn’t started yet as an official phase of work. If you’ve been wondering when native multilingual features might land in core rather than requiring a plugin, the honest answer based on the official roadmap is: not yet, and not imminently.

A note on how these releases actually reach production sites

It’s worth remembering that a core release shipping doesn’t mean every site benefits from it immediately — plenty of production WordPress installs run on hosts or maintenance schedules that lag several minor versions behind current, sometimes deliberately, out of caution about plugin compatibility. That caution is reasonable in isolation, but it means features like bcrypt password hashing or Speculative Loading — genuine, free improvements — sit unused on a meaningful share of the WordPress installs that are technically eligible for them. If you manage a site through an agency or host that controls the update schedule, it’s worth explicitly asking where you currently sit relative to 6.8, rather than assuming “recent enough” without checking the actual version number.

What’s actually worth doing with this information

• If you’re still running anything below 6.8, the bcrypt password-hashing upgrade alone is a solid reason to prioritize updating — it’s a meaningful, foundational security improvement, not a cosmetic one.
• Speculative Loading works automatically once you’re on 6.8+, with no configuration required to get some benefit — but it’s worth knowing it exists so you’re not surprised by prefetch-related network activity if you’re reviewing server logs.
• If you have a multi-author or client-review workflow, 6.9’s block-level Notes feature is worth actually testing — it may replace an external commenting or review-workflow plugin some teams have been using as a workaround.
• Don’t wait for native multilingual support in core if you need it now — Phase 4 hasn’t started as official development work, so a dedicated multilingual plugin remains the realistic path for the foreseeable future.

None of these three releases individually reads as revolutionary in isolation, and that’s honestly typical of how WordPress core evolves — steady, incremental, occasionally landing something (like bcrypt, or Speculative Loading) that matters more in practice than it does as a headline. Checking what actually shipped, rather than assuming core hasn’t changed much since you last paid attention, is worth the ten minutes it takes.

Why the unglamorous releases matter more than they seem to

It’s easy to judge a WordPress release by its headline feature and conclude a version without a dramatic new capability was a quiet one. 6.8 is the clearest counterexample in this trio — no flashy new block or editor mode, but a default password-hashing upgrade and a native browser-prefetch mechanism, both of which affect essentially every site that updates, without requiring a single configuration change. Judging a release purely by what shows up in a highlight reel misses exactly the kind of change that ends up mattering most at the scale WordPress actually operates — millions of sites, most of which will never notice bcrypt shipped, all of which are safer because it did.