Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Plugin how-tos · Guide

How to Enable Gutenberg Editor in WordPress (Step by Step)

How to Enable Gutenberg Editor in WordPress (Step by Step)

Short answer

The block editor is on by default from WordPress 5.0, so something is turning it off. Go to Settings, then Writing, and set the Classic Editor plugin's default to Block editor, or deactivate it. If that is not the cause, check for Disable Gutenberg, theme code or a post type without REST support.

Key takeaways

  • The block editor is built into WordPress 5.0 and later.
  • The Classic Editor plugin is the most common cause.
  • Disable Gutenberg can switch it off per role or post type.
  • Old posts open in a Classic block until converted.
  • Custom post types need REST support for blocks.
  • The Gutenberg plugin is optional and meant for testing.

How do you enable the Gutenberg editor in WordPress?

Gutenberg, the block editor, is on by default since WordPress 5.0, so enabling it usually means turning off whatever disabled it, most often the Classic Editor or Disable Gutenberg plugin.

If you open a post and see the old editor with a single toolbar and Visual and Text tabs, something on your site is switching the block editor off.

The cause is usually a plugin, a setting, a theme, or custom code. Occasionally an outdated WordPress version is to blame.

This guide works through each cause in order, from the most common to the least. If you want to know what the block editor offers first, see our explainer on the WordPress block editor.

Why switch to the block editor at all?

The block editor gets new features with every WordPress release, while the classic editor only receives maintenance, so switching keeps your site on the path WordPress itself is following.

The Classic Editor plugin is still supported, but it is a holdover. New features such as patterns, synced patterns, the Site Editor and block themes all depend on blocks.

Blocks also make layouts easier without a page builder. Columns, buttons, galleries, tables and embeds are all built in.

For writers, the block editor can feel different at first. Every paragraph is a block, and toolbars appear only when you click. Most people adjust within a few posts.

If several people write on your site, switch gradually. Let users choose their editor for a while, then make the block editor the default once everyone is comfortable.

What can stop the block editor from loading?

The usual causes are the Classic Editor plugin, the Disable Gutenberg plugin, a theme or plugin filter, a post type without REST support, or a WordPress version older than 5.0.

CauseHow to spot itFix
Classic Editor pluginListed under PluginsChange its settings or deactivate it
Disable Gutenberg pluginListed under PluginsChange its settings or deactivate it
Theme codeClassic editor returns when you switch themesRemove the filter in a child theme or ask the developer
Custom post typeOnly one post type shows the old editorRegister it with REST support
Old WordPress versionDashboard shows a version below 5.0Update WordPress
Page builder settingsBuilder replaces the editor on some pagesCheck the builder's post type settings

Step 1: How do you check your WordPress version?

Look at the bottom right of any dashboard screen or open Dashboard, then Updates; any version from 5.0 onward includes the block editor.

Very few sites still run a version this old, but it is worth a five-second check. Versions before 5.0 do not have the block editor in core.

If your site is out of date, update it before anything else. Old versions miss security fixes as well as editor features. Our guide on updating your WordPress website explains how to do it safely.

Step 2: How do you switch the Classic Editor plugin to blocks?

Go to Settings, then Writing, set the default editor for all users to the Block editor, allow users to switch if you like, and save, or simply deactivate the plugin.

The Classic Editor plugin is the most common reason the block editor is missing. It is still installed on many sites.

It adds two settings to the Writing screen:

  • Default editor for all users. Choose Block editor.
  • Allow users to switch editors. Choose Yes if some people still want the classic editor.

When switching is allowed, the post list shows links for both editors. You can then move one post at a time.

If nobody needs the classic editor, deactivate the plugin under Plugins. Your posts are not changed. Old posts open in a Classic block, which you can convert to blocks when you are ready.

Step 3: How do you check for the Disable Gutenberg plugin?

Open Plugins, look for Disable Gutenberg or a similar plugin, and either change its settings to allow the block editor or deactivate it.

Disable Gutenberg and similar plugins can turn off the block editor sitewide, per user role, per post type or per template.

Look in Settings for the plugin's screen. You may only need to untick one option, such as the one for posts, rather than removing the plugin entirely.

After changing any of these settings, open a new post rather than an old one to test. A brand-new post shows clearly which editor loads by default, without the confusion of a post that was last edited in the other editor.

Some multipurpose plugins also include a switch to disable Gutenberg. Search the settings of any toolkit or performance plugin you use.

Step 4: How do you convert classic posts to blocks?

Open the post in the block editor, select the Classic block, open its options and choose the convert to blocks option, then check the result and update.

Turning the block editor on does not change your old content. Each existing post shows a single Classic block holding everything.

Converting splits the content into paragraphs, headings, images and lists. Check the result, because shortcodes and custom HTML sometimes need small fixes.

You do not have to convert every post. Classic blocks keep working. Many site owners convert only the posts they edit.

The WordPress block editor documentation explains the Classic block and the convert option.

How do you fix a theme or plugin that disables the editor?

Switch to a default theme briefly to test, and if the block editor returns, look for code in the theme that filters the editor off and remove it in a child theme.

Code can disable the block editor using the use_block_editor_for_post filter or the matching filter for post types.

To find the culprit, use a staging site. Switch to a default theme such as Twenty Twenty-Five, then deactivate plugins one at a time until the block editor appears.

If your theme is the cause, do not edit the parent theme files. Ask the theme developer, or override the setting in a child theme.

Why does only one post type show the classic editor?

The block editor needs the WordPress REST API, so a custom post type registered without REST support will always open in the classic editor.

Developers register post types with a setting called show_in_rest. If it is false or missing, the block editor cannot load for that type.

The fix is to set it to true where the post type is registered. The register_post_type reference lists the option.

The post type also needs to support the editor. If the type was registered by a plugin, check the plugin's settings or ask its developer.

Some plugins keep the classic editor on purpose for their own post types. WooCommerce products, for example, have traditionally used their own product editing screen. If you want the reverse for certain types, see our guide on disabling Gutenberg for a post type.

What is the Gutenberg plugin, and do you need it?

The Gutenberg plugin is a separate feature plugin that adds the newest editor features before they reach WordPress core; you do not need it to use the block editor.

The block editor in WordPress core is stable and fully usable on its own. The Gutenberg plugin is mainly for testing upcoming features.

It updates often and can change things between releases. Use it on a staging site, not a busy live site, unless you need a specific new feature.

Development happens in public on the Gutenberg GitHub repository, and release notes appear on Make WordPress Core.

Should you use the block editor or a page builder?

The block editor is free, built in and keeps improving, while page builders add more design controls at the cost of extra code and lock-in.

Many sites use both. They use the block editor for posts and a builder for a few landing pages.

Our comparison of Gutenberg and page builders explains the trade-offs.

If you change your mind later, our guide on going back to the classic editor shows how to reverse these steps.

Frequently asked questions

Is Gutenberg the same as the block editor?

Yes. Gutenberg was the project name for the block editor, which became part of WordPress core in version 5.0. People still use both names. There is also a separate Gutenberg plugin that previews upcoming editor features before they reach core.

Will enabling Gutenberg break my old posts?

No. Your existing posts keep their content and open inside a single Classic block. They display the same on the front end. You can convert them to blocks one at a time when you edit them, or leave them as they are.

Can I use both editors on one site?

Yes. With the Classic Editor plugin, set Allow users to switch editors to Yes. Each post then remembers which editor was last used, and the post list shows links to open either editor.

Why does my custom post type still use the classic editor?

The block editor needs the REST API. If the post type was registered without show_in_rest set to true, or without editor support, WordPress falls back to the classic screen. The developer who registered it needs to change those settings.

Do I need to install the Gutenberg plugin?

No. The block editor is already in WordPress. The Gutenberg plugin only adds experimental and upcoming features, and it updates often. Most sites should use the core editor and leave the plugin to testers and developers.

Sources

  1. Classic Editor WordPress.org Plugins
  2. Block Editor WordPress.org Documentation
  3. use_block_editor_for_post filter WordPress Developer Resources
  4. register_post_type() WordPress Developer Resources
  5. Gutenberg WordPress.org Plugins
  6. Gutenberg repository GitHub

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.