How to Disable the Gutenberg Block Editor and Restore the Classic Editor in WordPress

Are you experiencing compatibility issues, workflow disruptions, or a preference for the familiar interface of the classic WordPress editor? Many administrators and content creators seek to revert from the newer Gutenberg block editor for practical reasons related to plugin conflicts, team efficiency, or specific site management needs.

This guide provides a structured, problem-solution methodology to help you accurately restore the classic editing environment based on your technical context and objectives.

Core Issue Identification and Solution Mapping

Selecting the correct technical approach begins with pinpointing your primary objective. The following flowchart maps common user scenarios to the most effective and appropriate solution.

Solution 1: Utilize the Official Classic Editor Plugin

Optimal Scenario: Standard restoration requiring a stable, user-friendly, and officially supported method.
Technical Rationale: This plugin, maintained by WordPress core contributors, cleanly overrides the use_block_editor_for_post filter via a managed interface, ensuring compatibility and ease of use.

Step-by-Step Implementation

1. From your WordPress admin dashboard, navigate to Plugins > Add New.

2. In the search field, enter "Classic Editor".

3. Locate the plugin authored by "WordPress Contributors" and select "Install Now," followed by "Activate."

4. The classic TinyMCE editor interface will be restored for all standard posts and pages immediately upon activation.

5. For configuration (e.g., setting a site-wide default or allowing user switching), visit Settings > Writing.

Pro Recommendation: To fully revert to the classic dashboard experience, also install the companion "Classic Widgets" plugin from the same author.

Solution 2: Implement a Code Snippet via functions.php

Optimal Scenario: Environments where minimizing plugin count is a priority, or for developers performing direct theme-level modifications.
Technical Rationale: This method directly applies a WordPress filter to disable the block editor at the code level, offering a lightweight solution with no plugin overhead.

Step-by-Step Implementation

1. Create a complete backup of your website's files and database before proceeding.

2. Access your server via Secure FTP (SFTP) or your hosting control panel's file manager.

3. Navigate to /wp-content/themes/[your-active-theme]/.

4. Open the functions.php file for editing.

5. Insert the following filter at the end of the file, before any closing ?> tag:

   php

   // Disable the Gutenberg block editor site-wide
   add_filter('use_block_editor_for_post', '__return_false');

6. Save the file and upload it back to the server.

Critical Development Note: This modification is tied to your active theme. To prevent loss during theme updates, always implement such changes within a Child Theme.

Solution 3: Develop a Custom Functionality Plugin

Optimal Scenario: Advanced control requiring persistent, theme-independent rules, such as conditional disabling by post type or user role.
Technical Rationale: A custom plugin separates this functionality from your theme, providing a permanent and portable solution that allows for complex conditional logic using WordPress hooks.

Step-by-Step Implementation

1. Connect to your server via SFTP/File Manager and navigate to /wp-content/plugins/.

2. Create a new directory named, for example, custom-editor-manager.

3. Inside this directory, create a new PHP file named custom-editor-manager.php.

4. Open the file and insert the following plugin header and code structure:

   php

   <?php
   /**
    * Plugin Name: Custom Editor Manager
    * Description: Conditionally disables the Gutenberg block editor.
    * Version: 1.0
    */
   
   // Security check: Prevent direct file access
   if ( ! defined( 'ABSPATH' ) ) {
       exit;
   }
   
   /**
    * Disable Gutenberg for specific post types.
    *
    * @param bool   $use_block_editor Whether to use the block editor.
    * @param string $post_type        The current post type.
    * @return bool Modified boolean value.
    */
   function custom_disable_gutenberg( $use_block_editor, $post_type ) {
       // Disable for 'post' type only; modify array as needed
       $disabled_post_types = array( 'post' );
       if ( in_array( $post_type, $disabled_post_types, true ) ) {
           return false;
       }
       return $use_block_editor;
   }
   add_filter( 'use_block_editor_for_post_type', 'custom_disable_gutenberg', 10, 2 );

5. Save the file. In your WordPress admin area, go to Plugins. Locate "Custom Editor Manager" and activate it.

Technical Advantage: This plugin remains active regardless of your active theme, allowing for scalable and complex management of the editor environment across your site.

Post-Implementation Verification and Troubleshooting

After deploying your chosen solution, perform these critical checks in 2026 to ensure full functionality:

1. Clear Caching Layers: Purge any server-side (e.g., object cache) and application-level caching (e.g., WP Rocket, W3 Total Cache). Also, clear your web browser's cache.

2. Functional Testing: Create a new post and page to confirm the classic editor loads. Verify that any essential meta boxes, custom fields (e.g., from Advanced Custom Fields), or shortcodes render correctly in both the editor and on the front end.

3. Cross-Role Validation: If your solution includes conditional logic, log in as users with different roles (e.g., Editor, Author) to confirm the editor behaves as intended for each.

For ongoing support, advanced configurations, and community discussions, you can reference established resources like WP Troubleshoot.