Disable Gutenberg Editor WordPress: 4 Easy Ways

Yes, you can disable the Gutenberg block editor in WordPress and switch back to the classic editor. The simplest method is installing the official Classic Editor plugin, but there are also code-based and theme-level options. This article explains each approach, the pros and cons, and what to consider before making the switch.

Why Disable Gutenberg?

Gutenberg, introduced in WordPress 5.0 (December 2018), replaced the classic TinyMCE editor with a block-based system. While many users appreciate the flexibility, others find it confusing or unnecessary for simple content. Common reasons to disable it include:

• Familiarity: Long-time users are comfortable with the classic editor’s toolbar and text-based workflow.
• Speed: The classic editor loads faster on older computers or slow connections.
• Compatibility: Some older plugins and themes were never updated to work with Gutenberg.
• Accessibility: Some users with screen readers or keyboard navigation find the classic editor easier to use.

Method 1: Classic Editor Plugin (Recommended)

The official Classic Editor plugin is the most reliable and widely used solution. It is maintained by the WordPress team and will be supported until at least 2024 (and beyond, as it remains in the plugin directory). Here’s how to use it:

1. In your WordPress admin, go to Plugins → Add New.
2. Search for “Classic Editor�.
3. Click Install Now, then Activate.
4. After activation, go to Settings → Writing.
5. Under “Classic editor settings�, choose “Disable the block editor and use the classic editor� for all users.

You can also set it to allow users to switch between editors per post. The plugin works out of the box and requires no coding.

Method 2: Disable Gutenberg by Theme (Code)

If you prefer not to use a plugin, you can add a small snippet to your theme’s functions.php file. This method requires a child theme to avoid losing changes on theme updates. Add this code:

add_filter('use_block_editor_for_post', '__return_false');

This disables the block editor for all post types. To disable it only for specific post types, use:

add_filter('use_block_editor_for_post', function($enabled, $post) {
    if ($post->post_type === 'post') {
        return false;
    }
    return $enabled;
}, 10, 2);

After adding the code, the classic editor will appear automatically. Remember to back up your site before editing files.

Method 3: Disable Gutenberg for Custom Post Types

Sometimes you only want to disable Gutenberg for specific custom post types (CPTs). You can achieve this with a filter in your theme or a custom plugin. For example, to disable it for a CPT called “portfolio�:

add_filter('use_block_editor_for_post_type', function($enabled, $post_type) {
    if ($post_type === 'portfolio') {
        return false;
    }
    return $enabled;
}, 10, 2);

This is useful when you have a CPT that relies on custom meta boxes or a simpler editing interface.

Method 4: Use a Page Builder (Alternative)

If your goal is to have more design control without Gutenberg, consider using a page builder plugin like Elementor, Beaver Builder, or Divi. These plugins replace the editor with their own drag-and-drop interfaces. They are not “disabling� Gutenberg per se, but they often bypass it for page/post editing. Note that page builders add extra weight to your site and may have a learning curve.

Common Issues After Disabling Gutenberg

After switching back to the classic editor, you might encounter:

• Shortcodes not rendering: Some blocks are converted to shortcodes; classic editor may not render them without the block plugin.
• Layout shifts: Content created with Gutenberg blocks may look different in the classic editor.
• Plugin conflicts: Some plugins assume Gutenberg is active and may not load their scripts.

If you see broken layout, try installing the Classic Editor plugin and also the Classic Widgets plugin (if you want the old widget screen). For content that uses blocks, you can convert it to classic blocks using a plugin like “Convert to Blocks� or simply edit manually.

How to Choose the Right Method

Your choice depends on your technical comfort and long-term plans:

• Non-technical users: Use the Classic Editor plugin. It’s one-click and safe.
• Developers: Use the code snippet in a child theme or a custom plugin. This avoids an extra plugin and gives fine control.
• Site with many custom post types: Use the per-post-type filter to selectively disable.
• Design-heavy sites: Consider a page builder instead of disabling Gutenberg.

Also consider that WordPress core continues to evolve; Gutenberg will remain the standard. Disabling it is a temporary solution. Eventually, you may need to adapt or migrate to blocks.

Frequently Asked Questions

Will disabling Gutenberg affect my existing block content?

No, existing block content remains in the database. When you edit a post that contains blocks, the classic editor will show a “block� as a single shortcode-like element. You can still edit the text inside, but you lose the visual block layout. To preserve the layout, you can use the “Classic Editor� plugin’s ability to show blocks as a “Gutenberg� meta box, but it’s not ideal.

Does the Classic Editor plugin work with the latest WordPress?

Yes, the Classic Editor plugin is actively maintained and works with current WordPress versions. It is the official solution recommended by WordPress.org for users who need the classic experience. It will continue to work as long as WordPress supports plugins.

Can I disable Gutenberg for only certain users?

Yes, the Classic Editor plugin allows you to set the editor per user. Under Settings → Writing, you can choose “Allow users to switch editors� and then each user can select their preferred editor in their profile. Alternatively, you can use a snippet to check user roles.

Is it safe to disable Gutenberg?

Yes, it is safe. Gutenberg is just an editor; disabling it does not affect your site’s front-end or security. The only risk is that some plugins or themes may expect Gutenberg to be active, but that is rare. Always test on a staging site first.

What if I want to re-enable Gutenberg later?

Simply deactivate the Classic Editor plugin or remove the code snippet. Your block content will still be there, and you can continue editing with Gutenberg. No data is lost when switching back and forth.

Related

• AI Voice and Likeness Cloning: Consent and Misuse
• Url2png Alternatives for Competitor Page Monitoring
• Samsung Note 7 Users: Was There an Extra $100 Phone Offer?