The WordPress Classic Editor Guide: Why It’s Sti

The WordPress Classic Editor is the original, TinyMCE-based text editor that powered WordPress for over a decade before the block-based editor (Gutenberg) was introduced in WordPress 5.0.

 

While Gutenberg is the modern standard, the Classic Editor remains incredibly popular with developers and content creators who prefer a distraction-free, rich-text interface or need to maintain legacy websites.

 

Why Many Developers and Creators Still Prefer It

The transition to Gutenberg has many benefits, but the Classic Editor is still widely used for several practical reasons:

  • Writing Speed: For pure, text-heavy content, a single rich-text field is often faster and less distracting than managing separate paragraph blocks.

  • Custom Meta Box Compatibility: Many older themes and custom plugins rely on classic meta boxes that do not render or function correctly inside the React-based Gutenberg sidebar.

  • Performance: The Classic Editor loads slightly faster in the WordPress admin panel because it does not have to load the heavy JavaScript frameworks required by the Block Editor.

  • Predictable HTML Output: It outputs clean, simple HTML rather than wrapping every element in block-specific comment delimiters (eg, <!-- wp:paragraph -->).

Gutenberg vs. Classic Editor: Quick Comparison

How to Keep Using the Classic Editor

The official Classic Editor plugin is fully supported and maintained by the WordPress core team. However, if you are developing custom plugins or themes, you can also manage this programmatically without installing another plugin.

1. Disable the Block Editor Programmatically (Globally)

To completely turn off Gutenberg and default to the Classic Editor  across your entire site, add this simple filter to your theme's functions.phpfile or a custom plugin:

 


// Disable the Gutenberg block editor globally add_filter('use_block_editor_for_post', '__return_false', 10);

2. Disable Gutenberg for a Specific Custom Post Type (CPT)

If you want to use Gutenberg for standard posts but prefer the Classic Editor for a custom post type (like portfolioor products), you can check the post type parameter before disabling it:

 

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

function toggle_block_editor_by_post_type($use_block_editor, $post_type) {
    // Disable Gutenberg only for the 'cars' custom post type
    if ($post_type === 'cars') {
        return false;
    }
    return $use_block_editor;
}

3. Disable the Block Editor for Specific Post IDs

Sometimes you just need to keep a few complex, legacy landing pages on the Classic Editor while using blocks for the rest of your site:

 

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

function disable_gutenberg_for_specific_ids($use_block_editor, $post) {
    // List of Post IDs to force into Classic Editor
    $classic_post_ids = [102, 205, 308]; 
    
    if (in_array($post->ID, $classic_post_ids)) {
        return false;
    }
    return $use_block_editor;
}