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 the Classic Editor.
Restores the original Edit Post screen (TinyMCE, meta boxes, et al).
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.
Does not “expire” in 2022! 🙂
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 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 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)”
NEW! Option to enable Custom Fields Meta Box for ACF
NEW! Choose which editor to use for each post
NEW! Whitelist any post title, slug, or ID
NEW! Option to disables frontend Gutenberg stylesheet
Works same way as Classic Editor plugin, but can do a LOT more!
Lightweight and super fast, built with the WP API 🙂
Fully configurable, enable or disable Gutenberg and restore the Classic Editor wherever is necessary.
Automatically replaces Gutenberg with the Classic Editor.
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
Disable Gutenberg is developed by Jeff Starr, 13-year WordPress developer, book author, and support guru.
Super light & fast plugin, super easy on server resources!
Gutenberg is a useful editor but sometimes you want to disable it for specific posts, pages, user roles, post types, or theme templates. Disable Gutenberg 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!
The Disable Gutenberg plugin is targeted at everyone who is not ready for the major changes brought by Gutenberg. Install Disable Gutenberg NOW to be ready for when Gutenberg is finally merged into core and released to the public (likely in WP 5.0). That way, your users and clients will experience the same awesome UX as before 😉
This plugin does not collect any user data. So it does not do anything to make your site less compliant with GDPR. I have done my best to ensure that this plugin is 100% GDPR compliant, but I’m not a lawyer so can’t guarantee anything. To determine if your site is GDPR compliant, please consult an attorney.
If you like this plugin, please give it a 5-star rating, thank you!
Support development of this plugin
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:
Links, tweets and likes also appreciated. Thanks! 🙂
Installing the plugin
Upload the plugin to your blog and activate
Configure the plugin settings as desired
Enable theme switcher via settings or shortcode
Out of the box, Disable Gutenberg makes your WordPress 100% Gutenberg-free. If you visit the settings page, you will see that the “Complete Disable” option is enabled, and so is the “Disable Nag” option. This is all that is required to disable Gutenberg (and the nag) sitewide.
Now, if you want to customize things and, say, only disable Gutenberg on specific post types, you can uncheck that first “Complete Disable” option. When you uncheck the box, more options will be displayed. So you can choose exactly where Gutenberg should be disabled.
In some cases, you may want to disable Gutenberg everywhere, but enable only on certain posts. To do this, set the “Complete Disable” option to enabled. Then visit the “Whitelist” settings to specify which posts always should open in the Block Editor.
Do not use Disable Gutenberg with other plugins (like the Classic Editor plugin) that also disable or replace Gutenberg. Why? Because it may cause loading of redundant scripts, which may in turn lead to unexpected/untested results.
Hide Menu Option
Disable Gutenberg provides a setting to disable the plugin’s menu item. This is useful if you don’t want your clients to get curious and start fiddling around.
If you enable the option to hide the plugin’s menu item, you will need to access the plugin settings page directly. It is located at:
So if WordPress is installed at this URL:
..then you would access the plugin settings at:
Or, if WordPress is installed in a subdirectory, for example:
..then you would access the plugin settings at:
So if you hide the plugin’s menu item, you always can access the settings directly.
This plugin cleans up after itself. All plugin settings will be removed from your database when the plugin is uninstalled via the Plugins screen.
For developers wanting to customize further, check out:
I strive to make this free plugin the very best possible. To show support, please take a moment to leave a 5-star review at WordPress.org. Your generous feedback helps to further growth and development of Disable Gutenberg. Thank you!
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, the plugin does nothing. So it’s totally fine to install before Gutenberg is added to WP core, so it will be ready when the time comes.
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 including menu hiding and more.
Can I activate Disable Gutenberg without Gutenberg?
Yes, you can install and activate Disable Gutenberg on any supported WordPress version (see Docs/readme.txt for details). If installed on WP versions less than 5.0 without the Gutenberg plugin active, the Disable Gutenberg plugin simply won’t do anything (but you can still configure settings, etc.).
Can I use Disable Gutenberg 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 Plugins screen).
Classic Editor expires 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 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 recognized by Disable Gutenberg. So to disable Gutenberg on any registered template, you can add them via the plugin setting, “Disable for Templates”. Important: the template name must be written as
page-custom.php, only using the actual file name of whichever template you want to use.
Got a question?
Send any questions or feedback via my contact form