Free tools Windows power users keep installed
One-click scans. No signup required.
WordPress 6.8, released April 15, 2025, is a refinement release rather than a redesigned WordPress. Its most visible changes are the reorganized Style Book and clearer editor controls. Under the hood, it adds speculative loading, automatic bcrypt password hashing, accessibility fixes, and performance work in the editor, block registration, and query caching.
What WordPress 6.8 changes
WordPress 6.8 “Cecil” focuses on polishing tools that site owners and developers already use. The release has no alternative editions to compare; the features are part of the standard WordPress 6.8 core release.
| Area | What changed | Who will notice |
|---|---|---|
| Site design | More structured Style Book layout and clearer labels | Site owners working with global styles |
| Editor | More readable Data Views controls and other interface refinements | Authors and administrators |
| Query Loop | Option to exclude sticky posts | Editors building post listings |
| Navigation | Speculative loading can preload a linked destination | Visitors using modern browsers |
| Security | Automatic bcrypt password hashing | All WordPress installations using core passwords |
| Accessibility | More than 100 fixes and enhancements, including over 70 in the Block Editor | Keyboard, screen-reader and assistive-technology users |
| Performance | Work on editor behavior, block type registration and query caching | Sites with complex editing or high query volume |
Style Book: a clearer view of global styles
The Style Book now uses a more structured layout and clearer labels, making it easier to inspect colors, typography and other global styles together. The view is intended for checking how a theme’s design system is assembled while you edit it.
Where to find it
In the interface highlighted by WordPress, open Appearance > Design. The exact label and location can vary with the active theme and enabled editing experience.
#1 Best Overall
Classic-theme eligibility
Classic themes do not all expose the Style Book. A Classic theme needs editor styles or a theme.json file for the feature to show global styles. This requirement matters when comparing screenshots: two sites on WordPress 6.8 can present different design screens because their themes support different editing features.
What a Style Book screenshot should show
A useful screenshot is a full view of the Style Book with its labeled sections for colors and typography, plus the active theme context. Caption it as “Style Book under Appearance > Design; availability in Classic themes requires editor styles or theme.json.” Do not present it as a screen every Classic theme receives automatically.
Editor and Query Loop refinements
Data Views are easier to scan
WordPress 6.8 improves the way Data Views options are presented, so controls and available views are easier to see. This is interface polish within the editor rather than a separate publishing system.
Exclude sticky posts from a Query Loop
The Query Loop block gains a setting to leave sticky posts out of a listing. That is useful when a homepage, archive or related-post section should follow normal query ordering instead of promoting posts marked sticky.
To document this change in a screenshot, show the Query Loop block selected in the editor and the sticky-post exclusion control in its settings. The option affects that Query Loop; it does not remove the sticky status from the post itself.
How speculative loading works
WordPress 6.8 can use speculative loading to begin preloading a destination after a visitor hovers over or clicks a link. The goal is to make navigation feel faster by starting work before the next page is fully requested.
Browser support and fallback
The feature works in modern browsers. Older browsers ignore it without impact, so they continue using ordinary link navigation. Speculative loading is not a guarantee that every page will load faster: network conditions, caching, the destination page and the visitor’s timing all affect the result.
Control and troubleshooting
WordPress’s feature showcase says the behavior can be controlled with a plugin or custom code. If preloading creates unwanted requests, extra server work or conflicts with a site’s navigation logic, review that configuration rather than assuming the browser is broken. Measure with the same theme, plugins, host, content, browser and method before and after any change; the release documentation does not publish a universal before-and-after speed result.
Automatic bcrypt password hashing
WordPress 6.8 uses bcrypt for password hashing automatically. WordPress describes bcrypt as harder to crack because it requires more computing power. The change is applied without an administrator having to migrate passwords manually.
This is an improvement to password storage in WordPress core, not a promise that every part of a site is secure. Strong unique passwords, multi-factor authentication where available, timely updates and trustworthy plugins remain separate security controls.
Accessibility work in 6.8
The WordPress 6.8 release announcement reports more than 100 accessibility fixes and enhancements across the project, including over 70 improvements in the Block Editor. The reported work spans bundled themes, navigation-menu management, the Customizer, labels, blocks and Data Views.
Rank #4
These are publisher-reported release totals, not a claim that every accessibility issue is solved. Test the specific theme, plugins and content patterns used on your site, especially custom blocks and navigation components.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPerformance improvements—and what the numbers do not mean
Editor, blocks and queries
WordPress 6.8 includes performance work in the Block Editor, block type registration and query caching. Improvements to WP_Query cache-key generation are intended to reduce database load, with particular relevance to high-traffic sites that repeat similar queries.
The Interactivity API’s 50-millisecond goal
The official feature showcase describes 6.8 as a first step toward an Interactivity API goal in which interactions do not wait longer than 50 milliseconds. That figure is a project target, not a benchmark showing that every WordPress 6.8 site responds within 50 milliseconds. Actual results depend on code, hosting, plugins, browser and network conditions.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Release and maintenance details
- Initial release: April 15, 2025.
- Documented database version: 58975.
- Documented Trac revision: 60168.
- 6.8.1: April 30, 2025, with fixes for 15 bugs across Core and the Block Editor.
- 6.8.2: July 15, 2025, with fixes for 20 Core tickets and 15 Block Editor issues.
- 6.8.3: September 30, 2025, a security release containing two fixes.
Those maintenance figures describe the 6.8-series announcements. WordPress’s 6.8.3 notice recommended immediate updating and said only the most recent WordPress version was actively supported at that time; check current WordPress support guidance before treating that statement as current policy.
How to update to WordPress 6.8
- Make a current database and file backup, and confirm that your host can restore it.
- Check theme and plugin compatibility, especially for custom editor blocks and performance or navigation plugins.
- In the dashboard, open Dashboard > Updates.
- Review the offered WordPress update and start the update from that screen.
- Afterward, test front-end pages, login, publishing, the Style Book or site editor, Query Loop listings, forms and any custom functionality.
- If a problem appears, use the backup or your host’s rollback process, then isolate the conflicting theme or plugin before retrying.
Testing on a staging copy first is preferable for a busy or heavily customized site. A hosted WordPress service can be useful for readers without an existing installation, but the features described here are WordPress software features rather than requirements to buy particular hardware.
What screenshots should document
- Style Book: Appearance > Design, with labeled global-style sections visible; note the editor-styles or theme.json requirement for Classic themes.
- Data Views: the clearer options area in the editor.
- Query Loop: the setting that excludes sticky posts.
- Speculative loading: use a browser-development view or explanatory diagram only if it accurately represents the site’s configuration; do not imply a guaranteed speed gain.
Captions should identify the interface area and theme context. A screenshot is evidence of how one installation looks, not proof that every theme or plugin exposes the same controls.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
