Disable Gutenberg WordPress: 4 Ways [Guide]

You log in to update an old page and the editor looks nothing like it used to. WordPress 5.0 made the block editor the default, and many site owners would rather keep the editor they know.

That’s what disable Gutenberg WordPress is for. You can switch the editor off with a plugin or a few lines of code, for the whole site, for specific post types, or for a single post. This guide covers four methods and when to use each.

Disable Gutenberg With a Plugin

Plugins are the fastest route if you don’t want to touch code. Two options cover most needs.

Option 1: Classic Editor Plugin

The official Classic Editor plugin from WordPress.org brings back the old editor. Install and activate it, then go to Settings → Writing and set the default editor for all users. Users can still switch back to the block editor for each post unless you turn that option off.

Option 2: Disable Gutenberg Plugin

The Disable Gutenberg plugin gives you a settings page to turn the block editor off for all content, selected post types, or specific user roles. It also hides the block editor nag and its menu item, which suits sites where you want no block UI at all.

Disable Gutenberg Site-Wide With Code

If you’d rather not add a plugin, one filter turns the block editor off for every post type. Put the code in a child theme or a small site plugin so the change survives theme updates.

Add the Filter

Add this code to your child theme’s functions.php file or a site-specific plugin:

<?php

add_filter( 'use_block_editor_for_post', '__return_false' );

The use_block_editor_for_post filter receives a boolean. Returning false tells WordPress to load the classic editor for every post.

Tip: Older tutorials use filters such as gutenberg_can_edit_post. Those names are replaced by the filters in this guide, so use these on current WordPress versions.

Disable the Widgets Block Editor

The block editor also replaces the Widgets screen in WordPress 5.8 and later. To restore the classic widgets screen, add this filter:

<?php

add_filter( 'use_widgets_block_editor', '__return_false' );

Disable Gutenberg for Custom Post Types

You don’t have to turn the editor off everywhere. To keep the block editor for posts and pages but use the classic one for a custom post type, filter by post type.

Filter by Post Type

Replace book with your own post type slug:

<?php

add_filter( 'use_block_editor_for_post_type', 'my_disable_block_editor_for_post_type', 10, 2 );

function my_disable_block_editor_for_post_type( $use_block_editor, $post_type ) {
    if ( 'book' === $post_type ) {
        return false;
    }

    return $use_block_editor;
}

Register the Post Type Without the Block Editor

If you register the post type yourself, you can set it up so WordPress never uses the block editor for it. Setting show_in_rest to false does this, because the block editor reads content through the REST API. For background on REST routes, see the WordPress register_rest_route guide.

<?php

register_post_type( 'book', array(
    'label'        => 'Books',
    'public'       => true,
    'supports'     => array( 'title', 'editor' ),
    'show_in_rest' => false,
) );

Disable Gutenberg for a Single Post

To turn the block editor off for one post, use the use_block_editor_for_post filter and check the post ID. You can find the ID in the URL of the post’s edit screen.

<?php

add_filter( 'use_block_editor_for_post', 'my_disable_block_editor_for_single_post', 10, 2 );

function my_disable_block_editor_for_single_post( $use_block_editor, $post ) {
    if ( 123 === $post->ID ) {
        return false;
    }

    return $use_block_editor;
}

Which Method Should You Use?

Pick the lightest method that covers your case.

FAQs About Disabling Gutenberg

Does disabling Gutenberg turn off the Site Editor?

No. The filters in this guide control the post and widgets editors. They don’t remove the Site Editor under Appearance → Editor on block themes.

Can I disable Gutenberg for some users only?

Yes. The Disable Gutenberg plugin has user role settings. In code, check the current user inside your filter, for example with current_user_can( 'manage_options' ), and return false only for the users you choose.

Why did my custom fields disappear?

Classic meta boxes don’t always show in the block editor. Either turn the block editor off for that post type, or pass the __block_editor_compatible_meta_box argument when you register the meta box with add_meta_box(). See the WordPress add_meta_box() guide for details.

Will disabling Gutenberg speed up my site?

Not by itself. The filters change which editor loads on admin screens. Front-end speed depends on caching, images, and your theme and plugin choices.

Conclusion

Disabling the block editor takes one plugin or a few lines of code. Start with the Classic Editor plugin if you only need the old screen. Use the code filters when you want control over specific post types or posts.

Test on a staging copy first, especially if you use custom post types or meta boxes. Hire an expert WordPress developer or reach out to me directly.