WordPress Version 6.1 – Released With New Features [GUIDE]

Updated on

WordPress 6.1

WordPress 6.1 update was released on November 1, 2022, and it comes with a few new features and improvements. If you’re not sure how to update, or what to do if something goes wrong, we’ve got you covered.

It’s a third major release of 2022. As of the time of this release, WordPress powers 43% of websites worldwide.

In this article, we’ll go over the new features in WordPress 6.1 and show you how to update your wordpress website. We’ll also give you some tips on what to do if something goes wrong after you update.

Important: Don’t forget to create a complete database WordPress backup manually and with plugins before updating.

WordPress 6.1 Release Schedule

  • 21 September 2022- Release Beta 1
  • 27 September 2022- Release Beta 2
  • 4 October 2022- Release Beta 3
  • 11 October 2022- Release Candidate 1
  • 18 October 2022- Release Candidate 2
  • 25 October 2022- Release Candidate 3
  • 28 October 2022- Dry Run
  • 1 November 2022- Stable WordPress 6.1 Release

WordPress update 6.1

If you’re running WordPress 6.0, we recommend upgrading to 6.1 as soon as possible. We’ll take a look at some of the new features and changes in WordPress 6.1.

WordPress 6.1 New Features

In a summary,

  • Create templates for specific pages
  • Replace template parts in WordPress 6.1 Beta
  • Globally Style buttons in WordPress 6.1 BETA
  • Global styles for Headings
  • Changes to Navigation block
  • Improvement to Placeholder
  • Customize any border in Columns block
  • Visualize padding and margin
  • Image block in WordPress 6.1 BETA
  • Changes to Duotone filter
  • Changes to Categories block in WordPress 6.1 BETA
  • Improvements to Quote Block
  • List block in WordPress 6.1 BETA
  • Changes to Heading block
  • Axial spacing in Gallery Block
  • Featured image in Cover block
  • Lock blocks in WordPress 6.1 BETA
  • Time to Read
  • Block List view in Preference
  • New Twenty Twenty Three theme

What's in WordPress 6.1 New Features

Massive Performance Improvements: wp_query cache

Perhaps the most important improvement in WordPress 6.1, which will go unnoticed by most users, is that with this version database queries will be cached using wp_query.

This will be a HUGE performance improvement in that if the same database query is executed more than once, the result will be loaded from the cache.

  • Sites that use persistent object caching, will mean that the database query will not be executed again until the caches are invalidated, resulting in far fewer database queries.
  • Sites that use caching, such as Memcached, will also see the benefit of not repeating these queries, although the performance improvement won’t be as significant.
  • Caching all database queries using wp_query will mean that thousands of common queries, perhaps millions, will load much faster, which will greatly improve a load of repetitive processes, both in WordPress administration and loading of pages and resources. This change is very relevant and is one of the most important performance improvements in WordPress in recent years, by far.

For plugin or theme developers who want to disable this behavior by default, they can disable it with the following function:

/* Disable wp_query cache */

function disable_caching( $wp_query ) {

$wp_query->query_vars['cache_results'] = false;


add_action( 'parse_query', 'disable_caching' );

Of course, deactivating the cache wp_query will very negatively affect the performance of the web, so it should only be done in particular and totally justified cases.

Performance Improvements in the REST API

The improvements introduced in the REST API, this will also help improve the performance of the sites, as they will also help reduce the number of queries to the database, avoiding unnecessary queries from the API and caching the most common queries.

Cache Checks in the Site Health Tool

Another novelty, this one that is visible, is that the site health tool will check the active cache systems on the site, making recommendations in this regard in the event that caches are not active that would improve the performance of the web.

In addition to the default information that WordPress will show, hosting and/or web maintenance companies will be able to add their own personalized messages and links, with which to indicate to the site administrator the system or object cache plugin that they want to recommend, through a function like the following:

/* Custom text on cache */

add_filter( 'site_status_persistent_object_cache_notes', function( $notes ) {

$notes = __( 'My custom object cache text.', 'text-domain' );

return $notes;

} );

/* Custom link to cache documentation */

add_filter( 'site_status_persistent_object_cache_url', function() {

return 'https://myhostingcompany.com/my-cache-system/';

} );

If you want to recommend different recommended thresholds for when the object cache is beneficial , you can do it like this:

add_filter( 'site_status_persistent_object_cache_thresholds', function( $thresholds ) {

$thresholds = array(

'alloptions_count' => 600,

'alloptions_bytes' => 200000,

'comments_count' => 2000,

'options_count' => 2000,

'posts_count' => 2000,

'terms_count' => 2000,

'users_count' => 2000,


return $thresholds;

} );

As for the full page cache, you can also customize the texts and links, for example changing the default WordPress threshold for the need for this type of cache or the recommended headers:

/* Change good response threshold - 600 by default - from cache */

add_filter( 'site_status_good_response_time_threshold', function() {

return 200;

} );

/* New recommended headers */

add_filter( 'site_status_page_cache_supported_cache_headers', function( $cache_headers ) {

$cache_headers['cf-cache-status'] = static function ( $header_value ) {

return false !== strpos( strtolower( $header_value ), 'hit' );


return $cache_headers;


Twenty Twenty-Three – New default theme

As in every new major version of WordPress we have a brand new default theme – Twenty Twenty-Three.

The main novelties in WordPress 6.1 are the following –

  • 10 style variations.
  • Accessibility ready.
  • Fluid fonts.
  • Templates and custom template parts
  • Custom block patterns.
  • Clear design.
  • Fast charging, although less than Twenty Twenty-Two (see screenshots)

Here is a top web metrics result for a page with Twenty Twenty-Three and the previous theme, Twenty Twenty-Two.

Permalink recommendation

This is a minor change of WordPress 6.1 update, but one that will help some users, is the text recommending the use of the permalink structure %postname%, in the settings.

Improved Storage of Editor Settings and Preferences

Until WordPress 6.1, the editor preferences were saved as in the browser, which caused the settings to be lost if the user cleared the browsing data, or browser cache, something sometimes necessary to see changes on websites and the like.

From now on these preferences are stored for each user in the database, remaining between sessions, browsers and even devices.

No Site Description by Default

Since WordPress was born in the general settings, there was a short generic site description, by default, since WordPress 6.1 will be empty by default, waiting for you to describe your website.

So the “Just another WordPress site” thing is over, or “Just another WordPress site” that has accompanied us for years, and we still see it in Google results thanks to website owners who are not careful with their SEO.

“Just Another WordPress site”

So, since WordPress 6.1, you should review the general settings of your site and add a short description of the site, which really tells what your website is about.

Improvements in the Editor (of Blocks)

From here on, everything else is an improvement in the WordPress block editor, because as in every update for more than 5 years, the new features of the Gutenberg plugin have been incorporated.

Global Styles

The biggest improvement when it comes to Full Site Editing, or FSE, is that it’s finally easier to make consistent styling changes by unifying these settings in the global styling section of the site editor.

In this way, when making changes to the colors, fonts, structure, or general appearance of the blocks, the changes will be applied to the entire web, and the settings are all unified in a single place in the editor.

In each section of the global style settings, you can customize what you want and, when you save, the changes will be applied globally to the entire site.

Fluid Typography

One of the great novelties in the WordPress 6.1 block editor is the introduction of fluid fonts or fonts, so that the texts adapt “fluidly” to any screen size and device. Any blocky or classic theme can incorporate the use of fluid fonts through the long-ubiquitous theme.json.

The font settings customization interface does not change when registering fluid fonts, but its operation does, adapting what is written perfectly to the screen size. This implies that you can make font size changes using em, rem, px, rem, vw o vh.

More Template Types

In WordPress 6.0.x you could already create template types but in version 6.1 they have been extended, and you will be able to create templates for all types of content and taxonomies included in WordPress, but also for custom content types (CPT) registered on your site.

But the novelty does not end there, when you click on the patterns of new templates, you will now be offered the possibility of choosing between various types of templates in several of them.

Start patterns across all content types

If WordPress 6.0 already introduced the ability for plugin and theme authors to include full page patterns when creating a new post or page, now they can be created for any type of registered content.

Improvement and unification of design controls

The design controls of the structure of the different elements of the site have been greatly improved.

Default Navigation Menus

Until now, if the site did not have a custom navigation menu defined, nothing was displayed. As of WordPress 6.1, there is a default, or alternative, navigation menu functionality that will work like this:

If there are no block menus or classic menus, the navigation menu block will display a list of available pages using the page list block. If there are multiple block menus already created, the navigation block will display the most recently created block menu.

Interior Block Lock

Block locking, to prevent unintentional modifications, now also allows you to lock inner blocks, those included within the selected block.

Block Theme Browser

Have no doubt that there will be more and more block themes, and the visibility given to them in WordPress 6.1, incorporating a specific search for this type of block, will help this. Now when you install a new theme you will find a special section dedicated to blocking themes.

What you won’t find in WordPress 6.1 Update?

Something that had been announced for some time and that, in the end, you will not find in WordPress 6.1 is the automatic conversion of the images that you upload to WebP format.

Despite the fact that there was consensus among the team that led the version, and the push From the Performance team, it seems that at the last minute Matt Mullenweg had second thoughts and PROPOSED removing that functionality from WordPress 6.1. Before the WordPress 6.1 update, they released a short cycle update which is WordPress 6.0.3.

 WordPress 6.0.3 Security Update Patch

The WordPress 6.0.3 Security version of WordPress has been released containing security fixes. Update to version 6.0.3 from WordPress.org or the dashboard, by clicking “Updates” and then “Update Now”.

The security vulnerabilities reported are of types:

  • XSS stored through different ways,
  • open redirect on ‘wp_nonce_ays’,
  • sender’s email address exposed in ‘wp-mail.php‘,
  • media library: reflected XSS via SQLi,
  • CSRF in ‘wp-trackback.php’,
  • revert shared user instances introduced in 50790,
  • exposing data via REST Terms/Tags Endpoint,
  • email content filtering,
  • SQL injection due to improper sanitization on ‘WP_Date_Query’.

Do you know what is WordPress 6.0.3 update?

You’re probably wondering what was new in WordPress 6.0.3. It’s a WordPress Security Updates, which means that it contains important fixes to the platform.

One of the main things that this update address is a vulnerability that could allow unauthorized users to access your site. It also fixes an issue where a user could be logged in indefinitely if their session was terminated mid-way through a login process.

So if you’re running WordPress 6.0 or 6.0.3, but now it’s important to update to 6.1 as soon as possible to ensure that your site is as secure as possible.

What we think about WordPress 6.1 Update?

If you ask us for our opinion about WordPress 6.1 update, We would divide it between the positive and the negative, which are following…

Positive aspects of WordPress 6.1 Update

Massive performance improvement thanks to the wp_query cache and improvements to the REST APISave the editor preferences in the database. Global styles go in the right direction for full site editing, by unifying general look and feel settings in one place. The constant improvements in the block editor, some necessary years ago, especially regarding the navigation between blocks.

Negative aspects of WordPress 6.1 Update

The missed opportunity to incorporate automatic (even optional) conversion to WebP and even AVIF.

avif image

That the site editor remains as BETA, which gives an impression of poor and half-finished software. The site editor, templates and template parts offer a completely chaotic navigation flow, which does not follow any logic.

It was missing, is missing, and will continue to be missing a site editing assistant that guides the user through the complete edition. I still don’t understand how for something as basic as configuring four settings of an SEO or WooCommerce plugin there is a startup wizard and there is still no such thing in WordPress, at least for the complete edition of the site.

Do you know How to Speed up WooCommerce Store for Higher Conversion?

As for years, WordPress updates (with small and honorable exceptions) are still mostly based on improving the block editor. Yes, it has improved a lot and is getting closer and closer to something really alternative to the currently leading builders and editors, but we have been living with an unfinished application for years.

Well without a clear and defined focus on the final product, which lurches from one version to another, and without finishing to see where it will end, or at least it will stabilize as a solid tool, without bugs, and with a clear usability structure and flow.

Should I Upgrade to WordPress 6.1?

Absolutely YES.

The changes to the editor aren’t going to break anything, and the performance gains from caching database queries alone are worth upgrading to WordPress 6.1 for.

So far, WordPress 6.1 has been pretty solid, but as with any update, there’s always the chance of something going wrong. If you run into any problems after updating, don’t panic – we’ve got you covered, contact WordPress experts of WP Hacked Help team.

Having said that,

I hope you will find this article helpful and now know what’s new in WordPress 6.1