{"id":64228,"date":"2026-07-08T15:57:00","date_gmt":"2026-07-08T22:57:00","guid":{"rendered":"https:\/\/dhblog.dream.press\/blog\/?p=64228"},"modified":"2026-07-08T16:00:02","modified_gmt":"2026-07-08T23:00:02","slug":"wordpress-6-8","status":"publish","type":"post","link":"https:\/\/www-dev.dreamhost.com\/blog\/wordpress-6-8\/","title":{"rendered":"WordPress 6.8 \u201cCecil\u201d: Release Date, Features, and What Actually Shipped"},"content":{"rendered":"\n

WordPress 6.8 \u201cCecil,\u201d released on April 15, 2025, was a polish-focused major release whose headline changes were bcrypt password hashing (the first such change since 2008), built-in speculative loading for faster page transitions, and Style Book support for classic themes. More than 900 contributors from 60+ countries built it; the name honors jazz pianist Cecil Taylor.<\/p>\n\n\n\n

A lot has happened since: WordPress 6.9 \u201cGene\u201d arrived in December 2025, and WordPress 7.0 \u201cArmstrong,\u201d the current major release, shipped in May 2026. The 6.8 branch still receives courtesy security backports (6.8.3 landed in September 2025), but if you\u2019re running 6.8 today, the practical advice is simple: update to 7.0.<\/p>\n\n\n\n

Still, 6.8 deserves its place in the record books \u2014 mostly for a security change years in the making. Here\u2019s what actually shipped, what changed along the way, and which pre-release proposals never made it in.<\/p>\n\n\n\n

The Headline Change: Bcrypt Password Hashing<\/h2>\n\n\n\n

WordPress 6.8 strengthened password security by updating the hashing algorithm from phpass portable hashing to bcrypt, making password hashes significantly more difficult to crack. It was the first change to how WordPress hashes user passwords since 2008. That\u2019s why, for security folks, this understated update was the release\u2019s landmark.<\/p>\n\n\n\n

The update also shifted application passwords, user password reset keys, personal data request keys, and recovery mode keys from phpass to BLAKE2b hashing via Sodium \u2014 a faster, more secure cryptographic option.<\/p>\n\n\n\n

These security enhancements required no administrator action. Existing sessions remained valid, and users weren\u2019t forced to change passwords. WordPress simply rehashes each password with bcrypt the next time a user logs in or updates their credentials. Application passwords and security keys created before WordPress 6.8 stayed valid, and post passwords continued using phpass while the core team researched next steps.<\/p>\n\n\n\n

For the technical details, see the core team\u2019s bcrypt announcement<\/a>.<\/p>\n\n\n\n

Speculative Loading: Faster Page Transitions by Default<\/h2>\n\n\n\n

WordPress 6.8 integrated speculative loading into core to improve page load performance. This technique uses prefetching to load resources the browser anticipates users will need. Start to click a link, and the next page may already be on its way. The result: faster page transitions and a smoother browsing experience.<\/p>\n\n\n\n

The implementation built on the Performance Team\u2019s Speculative Loading plugin<\/a>. By default, core prefetches links with a \u201cconservative\u201d eagerness setting to minimize potential issues, and it only activates for logged-out visitors on sites with pretty permalinks enabled. Developers can customize the behavior with the new \u201cwp_speculation_rules_configuration<\/code>\u201d filter, or exclude specific paths with \u201cwp_speculation_rules_href_exclude_paths<\/code>.\u201d<\/p>\n\n\n\n

The result is one of those rare performance wins that requires zero configuration: anticipated resources load in the background, site transitions feel faster, and compatibility is preserved for everyone else.<\/p>\n\n\n\n

A Restructured Style Book \u2014 Now for Classic Themes, Too<\/h2>\n\n\n\n

The Style Book, the tool for previewing and managing your site\u2019s block styles in one place, got a structured new layout with clearer labels in 6.8. Typography, colors, and block styles are easier to navigate, with changes previewed in the panel as you move through the options.<\/p>\n\n\n\n

The bigger story: 6.8 brought the Style Book to classic<\/em> themes for the first time. If a classic theme supports editor styles or includes a theme.json file, its users get the same organized style overview that block themes enjoy \u2014 a meaningful step in closing the gap between the two theme worlds.<\/p>\n\n\n\n

\"WordPress<\/figure>\n\n\n
\n\tRelated Article<\/span>\n\t
\n\t\t
\n\t\t\tYour Complete Guide to WordPress Full-Site Editing\n\t\t<\/div>\n\t\t\n\t\t\tRead More\n\t\t<\/a>\n\t<\/div>\n<\/div>\n\n\n

Persistent Rendering Mode, Saved per Post Type<\/h2>\n\n\n\n

Since 6.8, users can choose whether the editor displays the site\u2019s template while editing content or shows only the content being added \u2014 and that preference now persists between sessions, saved per post type. Pages default to showing the template and content together.<\/p>\n\n\n\n

The option lets you see how content will interact with the final published page by rendering template blocks without making them editable. Because the setting is remembered, you don\u2019t need to reconfigure your preferred view each time you edit.<\/p>\n\n\n\n

Starter Content in the Block Inserter<\/h2>\n\n\n\n

WordPress 6.8 made starter content easier to reach: starter patterns now appear under their own \u201cStarter Content\u201d category in the Block Inserter, alongside the blocks and patterns you already use. The familiar starter-content modal didn\u2019t go away \u2014 it gained a preference toggle, so you can turn it off if you\u2019d rather work from the inserter alone.<\/p>\n\n\n\n

The updated workflow is consistent with the overall block editing experience<\/a>: new users get a smoother start, and experienced site builders can pull predefined layouts into a page without breaking stride.<\/p>\n\n\n\n

\"WordPress<\/figure>\n\n\n\n
\n\n\n

Get Content Delivered Straight to Your Inbox<\/h2>

Subscribe now to receive all the latest updates, delivered directly to your inbox.<\/p>

<\/div>