WordPress 6.7, named “Rollins” after jazz saxophonist Sonny Rollins, shipped on November 12, 2024. It was a meaningful release at the time, introducing a new default theme, a genuinely useful editor mode, and a batch of media and typography improvements. But WordPress moves fast: since 6.7 landed, the project has shipped 6.8, 6.9, 7.0, and, as of this week, 7.1. If you’re running a site still on 6.7 or just catching up on what changed, here’s what that release actually delivered, what shipped in 6.8, 6.9, and 7.0, what just landed in 7.1, and a practical checklist for moving a production site forward without breaking anything along the way.
New Default Theme
Twenty Twenty-Five Overview: WordPress 6.7 introduced the Twenty Twenty-Five theme, which focuses on flexibility and adaptability. This theme is crafted to cater to a wide audience, particularly bloggers, with its minimalist design and emphasis on typography.
Key Features:
- Pattern-Based Design: The theme comes with a plethora of pre-designed patterns, making it easy to create stylish websites swiftly.
- Enhanced Typography: Fluid typography options that automatically adjust text size for optimal reading across different devices.
- Customization: With new block patterns and customizable templates, users can craft unique looks without diving deep into code.
Zoom Out Mode in the Editor Overview
A significant addition to the WordPress editor is the “Zoom Out” mode, which allows users to see the bigger picture of their content layout.
How It Works:
- Pattern-Level Editing: Edit at a higher level by managing content through patterns rather than individual blocks, which streamlines the editing process.
- Improved Workflow: This feature allows for quick layout adjustments, bulk content manipulation, and a cleaner workspace when designing complex pages.
Media Management Improvements Overview
Media handling in WordPress 6.7 saw several advancements aimed at enhancing user interaction with media files.
New Features:
- HEIC/HEIF Support: WordPress now automatically converts these modern image formats to JPEG for broader compatibility.
- Lazy Loading Enhancements: The introduction of auto sizes for lazy-loaded images, which helps in optimizing page load times.
- Gallery Improvements: Enhanced gallery functionality with lightbox support for a more interactive user experience.
Block Customization Enhancements Overview
Blocks, the cornerstone of WordPress’s block editor, received further customization options in 6.7.
What’s New:
- More Styling Options: Additional controls for borders, colors, and shadows, providing users with more creative freedom.
- Background Images: Background images can be applied to various content blocks, not just group blocks.
- Dynamic Content Display: Improvements to the Query Loop block for easier management and display of dynamic content.
Font Library and Typography Overview
The Font Library, introduced in an earlier version, got more attention in WordPress 6.7 with better management and display options.
Image source
Enhancements:
- Centralized Font Management: Easily view and manage all fonts available in your WordPress installation.
- Fluid Typography: This feature ensures text scales appropriately across different screen sizes, enhancing readability.
Security:
- Advanced Authentication Mechanisms: WordPress 6.7 included updates to bolster site security, protecting against common vulnerabilities like XSS and SQL injections.
Performance:
- PHP 8.x Compatibility: Continued refinement for compatibility with modern PHP versions, enhancing site performance.
- Optimized Script Loading: Removal of obsolete polyfills to reduce load times and improve efficiency.
Developer Features Overview
WordPress 6.7 brought new tools and APIs for developers, making site customization and extension more straightforward.
New Developer Tools:
- Template Registration API: Simplifies the process of registering templates and template parts, allowing for easier theme and plugin development.
- Preview Options API: Developers can add custom preview settings in the editor, aiding in tailored content presentations.
User Experience Enhancements
Small but impactful changes were also made to improve the overall usability of WordPress in this release.
Improvements:
- Editor Interface: The block inserter remains open, and the editor topbar was reorganized for better accessibility.
- Data Views: Enhanced with custom sorting, filtering, and bulk actions for managing site content more effectively.
What Came Next: WordPress 6.8 “Cecil”
WordPress 6.8, named for jazz pianist Cecil Taylor, shipped on April 15, 2025, roughly five months after 6.7. Its headline feature was speculative loading, a performance mechanism that predicts which link a visitor is likely to click next and prefetches that page in the background, which measurably improved Largest Contentful Paint scores on sites that adopted it. The Style Book, previously limited to block themes, also became available to classic themes in this release, giving more site owners a single place to preview how block styles render before publishing.
WordPress 6.9: Gutenberg Phase 3 Lands in Core
WordPress 6.9 released on December 2, 2025, as the second major release of that year, and it’s the version where the long-promised collaborative editing work (Gutenberg Phase 3) started meaningfully showing up in core. Block-level Notes let teams comment, review, and resolve feedback directly on individual blocks, similar to commenting in Google Docs, which matters for any site with more than one person touching content. The release also added new blocks, Accordion, Math, Time to Read, and Word Count, along with block visibility controls. On the developer side, 6.9 introduced the Abilities API and expanded the Interactivity API, plus support for multiple templates per slug and safer theme switching for both block and classic themes.
WordPress 7.0 “Armstrong”: AI in Core, Minus One Big Feature
WordPress 7.0 was originally slated for early April 2026 but slipped to May 20, 2026. Its most notable addition is a provider-agnostic AI Client built into core, giving plugins and themes a standard way to integrate with different AI providers rather than each one rolling its own connector. The release also began a full admin redesign, including an admin-wide command palette, added Visual Revisions to the editor, and gave the Notes system from 6.9 a Suggestions mode.
What didn’t ship is worth knowing too. Real-time co-editing, the feature most pre-release coverage led with, was pulled just twelve days before launch after the core team hit race conditions, fuzz testing failures, and memory concerns under concurrent load that made it unsafe to release at that scale. It’s expected to return once those issues are resolved, but 7.0 shipped without it.
WordPress 7.1: What Just Shipped
WordPress 7.1 released on August 19, 2026, launched live from WordCamp US in Phoenix. The headline items are responsive styling controls, client-side media processing (handling image resizing and format conversion in the browser before upload rather than only on the server), a persistent admin toolbar, and two new blocks: Playlist and Tabs. If you’re planning an upgrade, this is the version to test against now, since it’s brand new and worth watching for the inevitable early point releases that follow a major launch.
Community Involvement and Testing
WordPress, being open-source, thrives on community involvement, and that held true across all of these releases. Each major version goes through extensive beta and release candidate testing, where users are encouraged to try pre-release builds and report issues before the final release ships. This collaborative approach helps iron out problems ahead of time and folds community feedback directly into the finished product, which is part of why a feature like real-time co-editing in 7.0 got pulled rather than shipped broken: the testing process caught it in time.
What Speculative Loading Actually Changed for Site Owners
Of everything that shipped in 6.8 and 6.9, speculative loading is probably the change most site owners felt without necessarily knowing why. The mechanism watches how visitors interact with a page, hovering over a link, scrolling toward it, and prefetches that destination in the background before the click even happens. On sites with predictable navigation patterns, blog archives, product listings, documentation, that shaved real time off the perceived load speed without requiring a plugin or a caching configuration change. It’s not a silver bullet for a genuinely slow site with unoptimized images or bloated plugins, but it’s one of the few core performance features that works automatically once you’re on a supported version.
What the Admin Redesign in 7.0 and 7.1 Means for Day-to-Day Use
The command palette introduced in 7.0 is the kind of feature that sounds minor in a changelog and turns out to matter a lot in daily use. Instead of navigating through nested admin menus to find a specific settings page or post, a keyboard shortcut opens a searchable command interface, similar to what many code editors and project management tools already offer. Combined with 7.1’s persistent admin toolbar, which stays accessible during long-scroll admin pages instead of disappearing off-screen, the overall admin experience in the newest releases is noticeably faster to navigate than what shipped in 6.7, even though neither individual change looks dramatic on its own.
Plugin and Theme Compatibility Considerations
Each of these releases touched enough of the editor and admin interface that plugin developers had real work to do keeping up. Page builders and admin-UI-heavy plugins are the most likely to need updates before they behave correctly on 7.0 or 7.1, given how much the admin interface itself changed. Before upgrading a production site running heavily customized plugins, check the plugin’s own changelog for explicit compatibility statements against the WordPress version you’re moving to, rather than assuming “it worked on 6.9” guarantees it’ll work identically on 7.1.
Classic themes generally fared better across this stretch of releases than heavily customized block themes, since core’s block-related changes (Zoom Out mode, the expanded Style Book, new blocks like Accordion and Tabs) affect block theme rendering more directly. If your site runs a classic theme, the upgrade path tends to be lower-risk, though it’s still worth testing on staging rather than updating a live production site directly.
Should You Upgrade Now, or Wait?
If you’re still running 6.7, there’s no single blocker keeping you there, but you’re missing three major versions of performance work, editorial tooling, and now a first pass at AI integration in core. Sites running custom themes or a lot of third-party plugins should test upgrades on staging first, particularly the jump to 7.0 and 7.1, since both introduced meaningful admin UI changes that can surface plugin compatibility issues that didn’t exist on 6.7’s more familiar interface.
For most sites, updating in stages, 6.7 to 6.9 first, confirming stability, then moving to 7.0 and 7.1, is safer than jumping straight to the newest release, especially on a production site without a recent backup. WordPress’s own compatibility notices in the admin dashboard will flag known plugin conflicts before you commit to an update, and it’s worth reading those rather than skipping past them.
Hosting providers with managed WordPress plans often run their own compatibility checks before applying major version updates automatically, which is worth confirming with your host before assuming an update will show up on your site the same day it’s released. Some managed hosts intentionally lag a few weeks behind a new major version specifically to let early compatibility issues surface and get fixed elsewhere first.
A Practical Migration Checklist
Before moving a production site from 6.7 to a current release, run through a short checklist rather than clicking update and hoping. Back up the database and files first, ideally somewhere outside your hosting environment so a bad update can’t take the backup down with it. Spin up a staging copy and run the update there, checking every plugin’s admin screen and every custom page template for visual breakage, not just whether the site loads. Pay particular attention to any page builder, membership plugin, or forum/community plugin, since those tend to hook deeply into the editor and admin UI that changed most across 6.8 through 7.1.
Once staging looks clean, update the production site during low-traffic hours and monitor error logs for the first few hours afterward. Most compatibility issues surface immediately, but a few, particularly ones tied to caching or object storage plugins, sometimes only appear once real traffic hits the updated site.
What’s Coming in WordPress 7.2
WordPress follows a three-major-release cadence in 2026, and 7.2 is planned for early December, timed to land around State of the Word. Specifics are still firming up this early after 7.1’s launch, but given the pattern across this year’s releases, expect continued refinement of the admin redesign started in 7.0, further work on the AI Client introduced in core, and likely another attempt at bringing real-time collaborative editing back now that the team has more runway to address the concurrency issues that got it pulled from 7.0.
Where WordPress Stands Today
WordPress 6.7 “Rollins” was a solid, well-received release in its own right, and the Twenty Twenty-Five theme, Zoom Out editing mode, and font management improvements it introduced are still part of how WordPress works today. But treating 6.7 as “the latest” in August 2026 misses three major releases of real substance: 6.8’s performance work, 6.9’s collaborative editing tools, and 7.0 and 7.1’s admin redesign and AI integration. Whether you’re a blogger, a business owner, or a developer, the platform has moved meaningfully since November 2024, and it’s worth knowing what you’re missing before deciding whether to upgrade.
How This Compares to Past WordPress Release Cadences
WordPress historically shipped three major releases a year, then experimented with a two-release cadence for parts of 2024 and 2025. The 6.7-to-6.9 stretch reflected that slower pace, roughly five months between 6.7 and 6.8, then about eight months from 6.8 to 6.9. The return to three releases in 2026 (7.0 in May, 7.1 in August, 7.2 planned for December) puts the project back on its older, faster rhythm, which means staying current requires checking in more often than the 6.7-era cadence trained site owners to expect.
For agencies and site owners managing multiple WordPress installs, that faster cadence is worth building into a maintenance schedule rather than treating each major release as a one-off event. A quarterly review of what’s shipped, checked against your specific plugin stack, catches compatibility issues before they turn into an emergency fix on a live site.
Frequently Asked Questions
Is WordPress 6.7 still safe to run in 2026?
It still receives security patches as long as it remains within WordPress’s supported version window, but running four major versions behind means missing performance and security hardening that shipped in 6.8 through 7.1. Staying current is generally the safer long-term choice.
What’s the single most useful change since WordPress 6.7?
It depends on your site. For editorial teams, 6.9’s Block-level Notes are the most immediately useful addition. For performance-sensitive sites, 6.8’s speculative loading tends to deliver the most measurable improvement with the least setup effort.
Did real-time collaborative editing ever ship?
Not as of WordPress 7.1. It was pulled from 7.0 shortly before release due to stability issues under concurrent load and hasn’t reappeared in a subsequent release yet.
Should I upgrade directly to 7.1, or go through the intermediate versions?
WordPress updates are designed to be applied sequentially without issue, so jumping straight to 7.1 from 6.7 works technically. The staged approach is more about giving yourself checkpoints to catch plugin or theme conflicts, not a technical requirement of the update process itself.
Will WordPress 7.2 bring back real-time collaborative editing?
It’s plausible given the project’s stated intent to revisit the feature, but nothing is confirmed this early. Treat any pre-release claims about 7.2’s exact feature set with the same caution that real-time editing’s pulled 7.0 debut deserves: features announced ahead of a release sometimes ship differently than planned, or not at all.
Interesting Reads
Best AI Tools for Bioinformatics