WordPress 6.8 “Cecil”: Release Context and a Website Owner’s Update Checklist
An archival look at the WordPress 6.8 release announced on 15 April 2025, with a practical process for assessing changes and checking a business website.

What changed
WordPress announced version 6.8, named Cecil, on 15 April 2025. This is an archival release-context article, not a claim that 6.8 is the newest release or the version a site should install today. Use the announcement to understand the event, and check the current supported release before planning an update.
Three changes worth understanding
WordPress 6.8 was released on April 15, 2025. Its practical changes include navigation performance, password security and a more useful Style Book. This article describes that release historically; it is not advice to install an old version on a maintained site today.
Speculative loading prepares likely next pages
Core added speculative loading with conservative prefetching by default. In supported browsers, WordPress can fetch a page a visitor appears likely to open before navigation completes. That differs from rendering every possible destination in advance. The default excludes logged-in users and sites without pretty permalinks; custom configurations can change the behaviour.
bcrypt improves password hashing
WordPress switched user-password hashing to bcrypt. Existing password hashes remain usable and migrate when a user next logs in or changes their password, so the change does not require a blanket password reset. Application passwords and security keys use a separate BLAKE2b change; not every stored credential becomes a bcrypt hash.
Style Book becomes easier to inspect
The refreshed Style Book makes it easier to review site-wide element styles in one place. Compatible classic themes can also expose it when they support editor styles or provide theme.json. A classic theme’s eligibility does not make it a full block theme or move every existing setting into the Site Editor.
| Change | What an owner can notice | What it does not establish |
|---|---|---|
| Speculative loading | A possible improvement when navigating to likely next pages | A guaranteed speed score for every browser or website |
| Password hashing | A stronger user-password storage mechanism | A need to force all existing users to reset passwords |
| Style Book | A clearer overview of styles in compatible themes | Full Site Editing support for every classic theme |
For an update assessment, choose checks that correspond to these changes: public navigation, a normal account login and the style controls your theme actually exposes. Hosting, plugins and custom integrations still determine the behaviour of the finished site. Keep the release announcement separate from a current-version recommendation.
Who is affected
Editors should check the content tasks they perform repeatedly: opening an existing page, changing a heading, adding an image and previewing the result. A familiar page is a better acceptance test than an empty draft because it includes the patterns and content that matter to the business.
Site owners should check operational tasks and the route for getting help. Confirm that enquiries reach the right place and that staff can respond. If the website has a store, test the relevant buying process in an environment that does not create an unintended real transaction.
Developers and maintainers should record custom integrations and assumptions. Review relevant project documentation, reproduce important tasks and keep the recovery instructions available. Where a third-party component changes behaviour, consult that component’s current documentation instead of guessing from the WordPress announcement alone.
What to do next
- Read the official announcement and note its historical date.
- Check the current supported WordPress release separately.
- Record the existing theme, plugins and custom integrations.
- Verify a restorable backup before significant changes.
- Use staging to check representative visitor and editor tasks.
- Resolve relevant compatibility questions with current vendor documentation.
- Schedule the change with a responsible maintainer.
- Repeat the acceptance checks and record the outcome.