Disable Gutenberg: Classic Editor restoration tool

Name: Disable Gutenberg
Availability: InStock
Rating: 5 (735 reviews)
Author: Jeff Starr

Download Trends

Loading download data...

Vulnerabilities

✓

No known vulnerabilities

This plugin has no records in the Wordfence Intelligence vulnerability database.

Support Statistics

1 Support threads

1 Resolved

100% Resolution rate

About Disable Gutenberg

Disable Gutenberg Block Editor and restore the Classic Editor and original Edit Post screen (TinyMCE, meta boxes, etc.).

This plugin disables the new Gutenberg Editor (aka Block Editor) and replaces it with the Classic Editor. You can disable Gutenberg completely, or selectively disable for posts, pages, roles, post types, and theme templates. Plus you can hide the Gutenberg nag, menu item, and more!

♠ The all-in-one, COMPLETE solution for handling Gutenberg
♠ Hide ALL traces of Gutenberg and replace with Classic Editor
♠ Restores original Edit Post screen (TinyMCE, meta boxes, etc.)

The Disable Gutenberg plugin restores the classic (original) WordPress editor and the “Edit Post” screen. So you can continue using plugins and theme functions that extend the Classic Editor. Supports awesome features like Meta Boxes, Quicktags, Custom Fields, and everything else the Classic Editor can do.

Easy to Use

Just activate and done! The default plugin settings are configured to hide all traces of the Gutenberg Block Editor, and fully restore the original Classic Editor. Further options for customizing when/where Gutenberg is enabled are available in the plugin settings.

♠ Disable Block Widgets and restore Classic Widgets 🙂

Options

Disable Gutenberg completely (all post types)
Disable Gutenberg for any post type
Disable Gutenberg for any user role
Disable Gutenberg for any theme template
Disable Gutenberg for any post/page IDs
Disable Gutenberg admin notice (nag)
Option to restore Classic Widgets
Option to hide the plugin menu item
Option to hide the Gutenberg plugin menu item (settings link)
Adds “Classic Editor” link to each post on the Posts screen
Adds item to the WP sidebar menu: “Add New (Classic)”
Option to enable Custom Fields Meta Box for ACF
Choose which editor to use for each post
Whitelist any post title, slug, or ID
Option to enable/disable frontend Gutenberg stylesheet

♠ Works same as Classic Editor plugin, but can do a LOT more!
♠ Lightweight and super fast, built with WP APIs 🙂

Fully configurable, enable or disable Gutenberg and restore the Classic Editor wherever is necessary.

Automatically replaces Gutenberg with the Classic Editor.

Features

Super simple
Clean, secure code
Built with the WordPress API
Lightweight, fast and flexible
Regularly updated and “future proof”
Works great with other WordPress plugins
Plugin options configurable via settings screen
Focused on flexibility, performance, and security
One-click restore plugin default options
Translation ready

♠ Works great with Google AMP and the WordPress AMP plugin

Disable Gutenberg is developed and maintained by Jeff Starr, 15-year WordPress developer and book author.

Super light & fast plugin, super easy on server resources!

Why?

Gutenberg is a useful editor but sometimes you want to disable it for specific posts, pages, user roles, post types, and/or theme templates. This plugin enables you to disable Gutenberg and replace it with the Classic Editor wherever you want. For example, lots of WordPress users already enjoy robust page-building functionality via one of the many great plugins like Composer or Elementor. So many options, no need to feel “locked in” to using Gutenberg!

If you like Disable Gutenberg, please give it a 5-star rating, thank you!

Privacy

This plugin does not collect or store any user data. It does not set any cookies, and it does not connect to any third-party locations. Thus, this plugin does not affect user privacy in any way.

Support development

I develop and maintain this free plugin with love for the WordPress community. To show support, you can make a donation or purchase one of my books:

And/or purchase one of my premium WordPress plugins:

BBQ Pro – Blazing fast WordPress firewall
Blackhole Pro – Automatically block bad bots
Banhammer Pro – Monitor traffic and ban the bad guys
GA Google Analytics Pro – Connect WordPress to Google Analytics
Head Meta Pro – Ultimate Meta Tags for WordPress
REST Pro Tools – Awesome tools for managing the WP REST API
Simple Ajax Chat Pro – Unlimited chat rooms
USP Pro – Unlimited front-end forms

Links, tweets and likes also appreciated. Thanks! 🙂

Screenshots

Plugin Settings screen (showing default options)

Plugin Settings screen (showing expanded options)

Frequently Asked Questions

Will this work without Gutenberg?

Yes. When Gutenberg is active, the plugin disables it (depending on your selected options) and replaces with the Classic Editor. Otherwise, if Gutenberg is not active (like with older versions of WordPress), the plugin does nothing. So it is safe to activate on any WordPress site.

What’s the difference between Classic Editor plugin?

Classic Editor plugin enables you to disable Gutenberg across the board, and replace it with the Classic Editor. The Disable Gutenberg plugin does the exact same thing, in the exact same way, BUT it also provides more granular control over when and where Gutenberg is replaced with the Classic Editor. Disable Gutenberg plugin makes it easy to replace Gutenberg everywhere, OR you can choose to replace only for specific post types, user roles, post IDs, theme template, and more. Check out the list of features and compare them to the alternatives. It’s not even close! 😉

Bottom line: both Disable Gutenberg and Classic Editor plugins are lightweight and enable you to replace Gutenberg with the Classic Editor for the entire site. The difference is that Disable Gutenberg also gives you advanced configuration options such as restoring Classic Widgets, controlling block styles, and allowing block editor on certain pages, post types, and so forth.

Can I use this plugin and Classic Editor at the same time?

Yes, if both plugins are active at the same time, Disable Gutenberg gives priority to Classic Editor plugin. So if you want to use Disable Gutenberg, deactivate the Classic Editor plugin (you do not have to remove it, just deactivate via the WP Plugins screen).

Classic Editor is planned to expire in 2022, what about Disable Gutenberg?

I can’t make any promises, but I intend to develop with WordPress for the long-haul. Who knows what the future holds, but the plan is to keep Disable Gutenberg going for many years to come. Why? Because the original RTE/Visual Editor is awesome. I strongly feel it’s one of the many reasons why WordPress has enjoyed its great success. I’ve been using the original/classic editor for over 10 years now and it’s always been 100% smooth experience. I’ve tried Gutenberg, and yes it is much better now than in previous versions, but for me it’s just not as comfortable or streamlined as the classic editor. So yeah, will do everything possible to keep Disable Gutenberg (and the Classic Editor) going well beyond 2022.

Why does Classic Editor plugin have way more users?

Because it is being promoted by the Gutenberg developers and the “official” plugin for replacing Gutenberg. That’s fine, but understand that Disable Gutenberg functions the same way AND provides way more features and settings. FWIW, I use Disable Gutenberg on my own sites Perishable Press, DigWP.com, Plugin Planet, and many others. 100% solid.

Template exclusions not working?

In order for template exclusions to work, the template must be registered with the page itself. The only way to do this is via the “Edit Page” screen, in the “Page Attributes” meta box. There you will find an option to set the page template. Remember to save your changes.

After assigning some templates, they will be recognised by Disable Gutenberg. So to disable Gutenberg on any registered template, you can add them via the plugin setting, “Disable for Templates”. Examples:

Template name is page-custom.php, located in the root theme directory: enter page-custom.php in the Template Exclusion setting
Template name is page-custom.php, located in a subdirectory named templates: enter templates/page-custom.php

How to disable default Gutenberg frontend styles?

The default Gutenberg/Block styles are disabled by default when DG plugin is active. To enable/disable the styles, visit the plugin setting, “Enable Frontend”.

Does this work with full site editing and block themes?

No, because block themes rely on blocks. See Block themes article for more information.

What does the setting “Display Edit Links” do?

When “Display Edit Links” is enabled in the plugin settings:

On Post, Page, and Custom Post Type menus (in the sidebar), a link is displayed that says “Add New (Classic)”. Clicking the link takes the user to the “Add New” screen with the Classic Editor enabled.
On Posts, Pages, and Custom Post Types screens (where lists of posts are displayed), two links are added beneath each post. The first link says “Classic Edit” and takes the user to the “Edit” screen with the Classic Editor enabled. The second link says “Block Edit” and takes the user to the Edit screen with the Block Editor enabled.

Note that these links display only on pages where the Block Editor is enabled. So for example, if Gutenberg is disabled sitewide, none of the links will display anywhere. If disabled only on Pages, then the links will not display on the Pages menu or on the Pages screen.

Got a question?

Send any questions or feedback via my contact form

Ratings & Reviews

Recent Reviews

Loading reviews...

View all reviews on WordPress.org (opens in a new tab)

Changelog

Thank you to everyone for using Disable Gutenberg and for all the awesome 5-star reviews!

If you have any feedback or suggestions to make this plugin the absolute best it can be, and/or would like to help with development, please reach me via the contact form at Plugin Planet.

3.3.2 (2026/07/18)