WordPress 6.5: New Features & Plugin Capabilities Explained

WordPress 6.5, code-named Regina, shipped on March 26, 2024. It was the first major release of the year, and it landed two things people had waited on for a while: a built-in Font Library and a real way to handle plugin dependencies.

This guide covers what changed, what it means for users and developers, and every point release that followed (6.5.2 through 6.5.5). If you’re trying to figure out whether 6.5 is worth updating to, or what the new plugin capabilities everyone mentions actually are, start here.

One honest note before we go further. 6.5 is no longer the current version of WordPress. The platform has moved well past it. But 6.5 still runs on a lot of sites, and the features it introduced are still part of WordPress today. So this is a complete record of what 6.5 brought, written for anyone running it or deciding.

WordPress 6.5 at a Glance

Here’s the short version of what’s new:

• Font Library: install, activate, and remove fonts from inside the editor, no code or FTP
• Plugin Dependencies: plugins can now declare which other plugins they need
• Interactivity API: a standard way for developers to build front-end interactions without a full page reload
• Block Bindings API: connect block content to custom fields and other data sources
• Revisions for templates and styles: time-stamped history for design changes, not just posts
• Data Views: table and grid layouts for managing site content
• 110+ performance fixes: the editor loads roughly twice as fast as 6.4
• AVIF image support: a newer, smaller image format
• 65+ accessibility fixes: the most accessible release WordPress had shipped to that point

The rest of this article breaks each of these down.

New Plugin Capabilities in WordPress 6.5

This is the part most people are searching for, so it goes first. WordPress 6.5 didn’t just add features for site owners. It changed what plugins themselves can do. Four additions matter here.

Plugin Dependencies (the “Requires Plugins” header)

Some plugins only work if another plugin is already installed. A payment add-on might need WooCommerce. An extension might need its parent plugin. Before 6.5, users had to figure that out on their own, usually after something broke.

6.5 fixed this with a new plugin header called Requires Plugins. A developer adds a comma-separated list of plugin slugs:

Requires Plugins: woocommerce, another-plugin-slug

WordPress then shows links to install and activate those dependencies first, pulled from the WordPress.org plugin repository. The dependency plugin gets a “Required by” note so you can see what relies on it. And you can’t delete a dependency while the plugin that needs it is still active.

There’s also a wp_plugin_dependencies_slug filter for developers who want to adjust slugs programmatically.

Two limits worth knowing. The system doesn’t do version management, so a plugin can’t require a specific version of its dependency. And it doesn’t support Must-Use plugins as dependencies. Useful as it is, it’s a first version.

Interactivity API

This was the headline feature for developers. The Interactivity API gives WordPress a standard way to build interactive front ends, things like instant search, live filters, or content that updates without reloading the whole page.

Before this, every plugin author solved that problem their own way, often by bolting on a JavaScript framework. That bloated sites and made blocks behave inconsistently. The Interactivity API gives everyone one shared approach, and it’s the same system powering features in core blocks like the Query Loop and Search.

For image-heavy sites and galleries, it’s the difference between a snappy page and a slow one.

Block Bindings API

Before 6.5, if you wanted to show a custom field value, you had to build a custom block to display it. The Block Bindings API removes that step. You can now connect a core block’s attributes directly to custom fields or other dynamic data with a few lines of code.

Point a block at a data source, and it pulls the value in. For developers building anything data-driven, this cut out a lot of repetitive work.

HTML API and Script Modules API

Two quieter additions that plugin developers care about.

The HTML API got a stronger Tag Processor that now reads every kind of token in a document: tags, comments, doctype declarations, and text nodes. That lets developers safely change the text inside an element without breaking the surrounding HTML structure.

The Script Modules API added native JavaScript module support to WordPress, including the modules that the Interactivity API runs on. It’s foundational plumbing, but it’s what makes the modern front-end features possible.

New Features for WordPress Users

Font Library

The Font Library is probably the most visible change in 6.5. It was planned for 6.4, pulled at the last minute, and finished here.

You manage fonts from the Styles panel in the Site Editor. Install Google Fonts or upload your own local font files, then activate or remove them across the whole site, all without touching code or a plugin. You can also group fonts into custom collections. For anyone who used to wrestle with @font-face rules or a separate typography plugin, this is a real time-saver.

Revisions for templates, styles, and patterns

Revisions used to be a post-and-page thing. 6.5 brought them to design.

You now get time-stamped revisions for templates, template parts, and global styles. Each one shows a quick summary of what changed, with a paginated list of every revision. You can view them from the Style Book and see how a change affects each block before you commit to it. Reverting a design tweak is now as easy as rolling back a draft.

Data Views

6.5 added Data Views to the Site Editor, letting you see your content in either a table or a grid. You can toggle which fields show, sort, and make bulk changes. It’s the start of a more spreadsheet-like way to manage pages, templates, and patterns from one screen.

Background and shadow controls

Group blocks got proper background image controls: size, repeat, and focal point. Cover blocks added aspect-ratio settings and color overlays that adapt to the image you drop in. Box shadows, which used to be limited, now work on more block types including images, buttons, and columns. Small changes, but they cut down on custom CSS.

Smoother editing and link controls

Drag-and-drop in the editor got clearer visual cues. Link management picked up a cleaner interface and a shortcut for copying links. Nothing dramatic on its own, but the editor feels less fiddly day to day.

Performance, Images, and Translations

WordPress 6.5 shipped over 110 performance fixes. The result: the Post Editor and Site Editor load more than twice as fast as 6.4, and input processing is up to five times faster in some cases.

Three more under-the-hood changes:

• AVIF support. WordPress can now handle AVIF images, a format that often beats JPEG and WebP on file size at the same quality. Smaller images, faster pages.
• Performant Translations. The i18n system got faster at loading translation files, which helps every non-English site.
• Minimum MySQL version. The floor was raised to MySQL 5.5.5, so check your host if you’re on something ancient.

Accessibility and Security

6.5 included more than 65 accessibility fixes, the most in any release up to that point. They covered screen reader behavior, color contrast in admin focus states, and keyboard cursor focus. If you build for public-sector or compliance-bound sites, these matter.

On security, the 6.5.0 release itself was a feature release. The security patches came in the point releases that followed, which is the next section.

WordPress 6.5 Release Notes: Every Point Release

After the main launch, WordPress shipped a series of minor releases. These are the 6.5.x versions people search for, and here’s what each one actually did.

WordPress 6.5.1 was never released. An issue with the initial package meant the team skipped straight to 6.5.2. So if you went looking for 6.5.1 and found nothing, that’s why.

WordPress 6.5.2 (April 9, 2024) was the first minor release. It carried 2 Core bug fixes, 12 Block Editor bug fixes, and 1 security fix: a cross-site scripting (XSS) flaw in the Avatar block, reported by John Blackbourn of the WordPress security team. Because it was a security release, the recommendation was to update right away.

WordPress 6.5.3 (May 7, 2024) was a maintenance release with 12 Core bug fixes and 9 Block Editor bug fixes. No security patch in this one, just stability.

WordPress 6.5.4 (June 2024) was a small maintenance release with 5 Core bug fixes.

WordPress 6.5.5 (July 2024) combined maintenance and security: 3 Core bug fixes plus security patches. Like 6.5.2, it was a recommended-update-immediately release.

If you’re still on any 6.5.x version below 6.5.5, you’re missing security patches. Move up to at least 6.5.5, and ideally onto a current major version.

New Features for WordPress Developers

1. Interactivity API

The new Interactivity API provides developers with a standardized approach to creating interactive experiences in WordPress. This API reduces dependencies on external tools and maintains optimal performance, ideal for developing features like instant search results or real-time content interaction.

2. Block Bindings API

With the Block Bindings API, developers can now link core block attributes to custom fields or other dynamic content sources. This extension allows for the seamless integration of external data into blocks with minimal coding, broadening the possibilities for dynamic content creation.

3. Enhanced Support for Classic Themes

Developers can now enhance Classic themes with modern design tools such as spacing, border, typography, and color options, even without the use of theme.json. This backward compatibility ensures that users of Classic themes can still enjoy the benefits of new design features.

4. Plugin Management and Performance Enhancements

The update simplifies the management of plugin dependencies, introducing a new Requires Plugins header that helps users install and activate necessary plugins more efficiently. Performance has also seen significant improvements, with loading times and input processing speeds greatly increased compared to previous versions.

5. Accessibility Improvements

Over 6.5 accessibility enhancements make WordPress 6.5 the most inclusive release yet. These improvements address various issues such as screen reader accessibility, color contrast in admin focus states, and cursor focus, ensuring a better experience for all users.

 

Should You Update, And How

If you’re on 6.5.0 through 6.5.4, update at minimum to 6.5.5 for the security fixes. If you’re on an older major version entirely, 6.5 was a safe, stable jump, and everything since has built on it.

The process is the same as always. Back up your site first. Then go to Dashboard > Updates and click Update Now, or let automatic background updates handle it if you’ve got those on. For a busy store or a media-heavy site, run the update on a staging copy before pushing to production. That habit has saved a lot of people from a bad afternoon.

If you’re on managed WordPress hosting, your provider often handles core updates and staging for you, which takes the risk out of it.

 

WordPress 6.5 And Future Releases

WordPress is gearing up for a steady stream of updates, with version 6.6 and 6.7 already lined up for later this year. These upcoming releases are set to build upon the foundation established by earlier versions, prioritizing maintenance and refining existing features before introducing collaborative functionalities by the year’s end.

Our team’s forward-thinking approach really shows our dedication to meeting users’ needs. Even though the Block Editor is already pretty easy to use with its drag-and-drop feature, we’re always looking for ways to make it even better.

 

Frequently Asked Questions

1. When was WordPress 6.5 released?

March 26, 2024. It was the first major release of 2024.

2. What is the WordPress 6.5 code name?

Regina, named after jazz musician Regina Carter, following WordPress tradition.

3. What are the new plugin capabilities in WordPress 6.5?

Plugin Dependencies, the Interactivity API, the Block Bindings API, plus improvements to the HTML API and a new Script Modules API. Together they change how plugins handle requirements, front-end interactions, and dynamic data.

4. Was there a WordPress 6.5.1?

No. A packaging issue meant 6.5.1 was skipped, and 6.5.2 became the first minor release.

5. Is WordPress 6.5 still supported?

WordPress has released several major versions since 6.5. While 6.5 still functions, you should run a current version to get the latest security patches. At a minimum, never run below 6.5.5.

6. What’s the difference between the Font Library and a font plugin?

The Font Library is built into core, so there’s no extra plugin to install or maintain. You manage Google Fonts and your own uploads from the Site Editor directly.