Classic Editor


Classic Editor is an official plugin maintained by the WordPress team that restores the previous (“classic”) WordPress editor and the “Edit Post” screen. It makes it possible to use plugins that extend that screen, add old-style meta boxes, or otherwise depend on the previous editor.
By default, this plugin hides all functionality available in the new Block Editor (“Gutenberg”).

At a glance, this plugin adds the following:

  • Administrators can select the default editor for all users.
  • Administrators can allow users to change their default editor.
  • When allowed, the users can choose which editor to use for each post.
  • Each post opens in the last editor used regardless of who edited it last. This is important for maintaining a consistent experience when editing content.

In addition, the Classic Editor plugin includes several filters that let other plugins control the settings, and the editor choice per post and per post type.

Classic Editor is an official WordPress plugin, and will be maintained until at least 2022.


  • Admin settings on the Settings -> Writing screen.
  • User settings on the Profile screen. Visible when the users are allowed to switch editors.
  • "Action links" to choose alternative editor. Visible when the users are allowed to switch editors.
  • Link to switch to the Block Editor while editing a post in the Classic Editor. Visible when the users are allowed to switch editors.
  • Link to switch to the Classic Editor while editing a post in the Block Editor. Visible when the users are allowed to switch editors.
  • Network setting to allow site admins to change the default options.


Excellent – This should be in the core!

Following upgrading to WP 5.0, the ability to copy & paste from MS-Word resulted in missing spaces, corropted text and a whole host of other issues.

This plugin should be in the core and users should be able to switch between the Gutenberg and the classic editor.

Thank you – well done!

So grateful for this plugin!

Gutenberg is not ready for production websites; no strong evidence that it ever will be. This plugin bridges what I hope is a gap to a better solution. ClassicPress maybe?

Make Gutenberg a plugin for masochists

This Classic Editor saved my bacon. I’m only giving it a 3-star rating because it is a consolation prize — something we already had, was capriciously taken away, only to be offered as a plugin (which has not solved all issues from what I gather).

Edit: I’ve added another star to my rating based on the latest update (1.2) which seems to totally disable GarbageBerg and removes the prompts to use the hated editor. So it is locked in the basement, for now, cooking up goodness knows what conspiracy to unleash on the unwary.

Gutenberg doesn’t just have teething problems, it’s a virus. A very bad virus; ill-conceived, badly executed and foisted upon the community against all protests. It feels very much like what a rogue government would unleash on a country, against the will of the people.

If I wanted Wix, I would choose Wix (they sure are advertising hard recently. Smell blood?).

I chose WordPress a decade ago because I liked the mechanics and the (apparent) ideals of the platform. After Gutenberg, I’m looking for an alternative.

And I won’t be recommending it (self-hosted or .com) to those who ask my advice.

Accessibility for the blind


One thing the Gutenberg plugin did not consider whatsoever is accessibility for the visually impaired blogger. I am a web designer of 20+ years and I am muddling through learning the new interface. Gutenberg is definitely not user friendly or intuitive. I could not imagine how difficult it will be for those with impaired site or blind… or even the regular sited user who is not computer savvy.

I have a client who is an avid journalist, but is blind. So he requires an interface that is accessible and works with his software and hardware modifications for visually impaired. If this plugin were not available it would put my enterprising client completely out of business. I was able to walk him through posting on the classic visual editor in a training session that lasted less than an hour. How the heck would I even begin to train him on Gutenberg? Seriously, was there any consideration for accessibility with the development of Gutenberg? Luckily my client has a sited person overseeing his back end who quickly put the classic visual editor plugin in place. What would he done had he run the 5.0 update and Gutenberg was there? What are other people with visual impairments going to do on their own?

Thanks again for making this available.

Read all 191 reviews

Contributors & Developers

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


“Classic Editor” has been translated into 39 locales. Thank you to the translators for their contributions.

Translate “Classic Editor” into your language.

Interested in development?

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



  • Fixed switching editors from the Add New (post) screen before a draft post is saved.
  • Fixed typo that was appending the edit URL to the classic-editor query var.
  • Changed detecting of WordPress 5.0 to not use version check. Fixes a bug when testing 5.1-alpha.
  • Changed the default value of the option to allow users to switch editors to false.
  • Added disabling of the Gutenberg plugin and lowered the required WordPress version to 4.9.
  • Added classic_editor_network_default_settings filter.


Fixed a bug where it may attempt to load the Block Editor for post types that do not support editor when users are allowed to switch editors.


  • Updated for WordPress 5.0.
  • Changed all “Gutenberg” names/references to “Block Editor”.
  • Refreshed the settings UI.
  • Removed disabling of the Gutenberg plugin. This was added for testing in WordPress 4.9. Users who want to continue following the development of Gutenberg in WordPress 5.0 and beyond will not need another plugin to disable it.
  • Added support for per-user settings of default editor.
  • Added support for admins to set the default editor for the site.
  • Added support for admins to allow users to change their default editor.
  • Added support for network admins to prevent site admins from changing the default settings.
  • Added support to store the last editor used for each post and open it next time. Enabled when users can choose default editor.
  • Added “post editor state” in the listing of posts on the Posts screen. Shows the editor that will be opened for the post. Enabled when users can choose default editor.
  • Added classic_editor_enabled_editors_for_post and classic_editor_enabled_editors_for_post_type filters. Can be used by other plugins to control or override the editor used for a particular post of post type.
  • Added classic_editor_plugin_settings filter. Can be used by other plugins to override the settings and disable the settings UI.


  • Updated for Gutenberg 4.1 and WordPress 5.0-beta1.
  • Removed some functionality that now exists in Gutenberg.
  • Fixed redirecting back to the Classic editor after looking at post revisions.


  • Fixed removing of the “Try Gutenberg” call-out when the Gutenberg plugin is not activated.
  • Fixed to always show the settings and the settings link in the plugins list table.
  • Updated the readme text.


  • Updated the option from a checkbox to couple of radio buttons, seems clearer. Thanks to @designsimply for the label text suggestions.
  • Some general updates and cleanup.


  • Update for Gutenberg 1.9.
  • Remove warning and automatic deactivation when Gutenberg is not active.


Initial release.