Classic Editor Addon


GDPR-compliant: does not collect any user data

The “Classic Editor” plugin doesn’t remove Gutenberg by default. With this free addon we set the option that controls this from no-replace to replace, so no additional action is needed anymore. This is what the Classic Editor should have done out of the box.

In addition to this most basic requirement, the “Classic Editor Addon” removes the Settings link from the main Plugins page and removes the plugin’s Settings from the Settings > Writing screen. Also the drop down buttons Gutenberg adds to the post type screens is replaced with the regular “Add New” button.

Update: With version 2.0.0 we have added a class that detects whether the main “Classic Editor” plugin already has been installed and activated. If it hasn’t, that plugin can be installed with one click. The notice can also be dismissed.

Last but not least the Classic Editor Addon suppresses the Nag screen that is slated to arrive in the Dashboard with WP version 4.9.8.

The free Classic Editor Addon plugin is targeted at everyone who is not yet ready for Gutenberg and/or who does not want to bother clients with Gutenberg. Install it now on sites and by the time WP 4.9.8 and eventually 5.0 are released, the UX remains the same as you are used to!

We support this plugin exclusively through Github. Therefore, if you have any questions, need help and/or want to make a feature request, please open an issue over at Github. You can also browse through open and closed issues to find what you are looking for and perhaps even help others.

Thanks for your understanding and cooperation.

If you like the Classic Editor Addon plugin, please consider leaving a review. Thanks!

Classic Editor Addon by Pieter Bos and Greg Schoppe.


What is Gutenberg?

Gutenberg is a new editing experience that will drop with WordPress 5.0, whether we like it or not. More information can be found on the Gutenberg FAQ.

Why this addon? Isn’t the purpose of the Classic Editor plugin to disable Gutenberg?

The “Classic Editor” plugin, by Andrew Ozz, doesn’t completely disable Gutenberg without changing settings. “Classic Editor Addon” is a second plugin that fixes both of these behaviors in “Classic Editor”. If you install both plugins, Gutenberg will be completely disabled, and you will not see a nag screen.

How does this compare to other plugins that disable Gutenberg?

Great question! “Classic Editor” is the official plugin for removing Gutenberg, and the install count is apparently being used as a metric to gauge success of the Gutenberg project. So, although other plugins exist to force-disable Gutenberg, using them doesn’t properly notify the WP Core team of the number of issues users are having, that is why “Classic Editor Addon” doesn’t disable Gutenberg itself, it just properly sets the options for “Classic Editor” and disables the Gutenberg Nag notice, making it easier to mass-install classic editor.

The plugin doesn’t do anything!

Is Gutenberg active on the site and do you have the Classic Editor plugin installed? Those two are requirements for this addon plugin to do anything. If you have and the plugin still doesn’t do anything, then please open a support ticket.

I have an issue with this plugin, where can I get support?

Please open an issue on Github


WordPress Apartheid

What Automattic going to do is a deliberate act of prevarication. I don’t think I can stand it. I love the plugin if it can save us from Gutenberg, but I am afraid it won’t.

The “classic editor plugin” is going to be like the South African Apartheid, or the Indian Reservations for the Native American Tribes. I don’t think free people should accept it.


A must have if using the Classic Editor plugin. Together with this addon a perfect solution now. Thanks a lot.

Read all 5 reviews

Contributors & Developers

“Classic Editor Addon” is open source software. The following people have contributed to this plugin.


Translate “Classic Editor Addon” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.



  • July 16, 2018
  • add WP Dependency Installer to facilitate with installing and activating Classic Editor plugin (changed color of admin notice to blue)
  • adjust minimum PHP version (to 5.3) due to addition of WP Dependency Installer


  • July 12, 2018
  • fix issue #2
  • adjust readme text and FAQs


  • July 8, 2018
  • release of plugin on WordPress Plugin Directory, ready for the world 🙂


  • early July, 2018
  • more feature/function/code improvements by both Pieter & Greg