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.


Thank GODS for this plug-in

I was beginning to think that I would have to give up my blog, given how horrible the Gutenberg editor is. Then I found out about the classic editor plug-in. Hopefully, during the years of support for this plug-in, they’ll see just how many people detest the new version and make it optional instead of an automatic update. Gutenberg is totally un-intuitive, and if someone is sight-impaired, I can’t imagine trying to navigate that mess of an editor.

Thank God. The new post thing is terrible

There are just buttons and you click on them and things happen and you don’t know what or why. If I hit enter is that a new paragraph block or not? No way of knowing. Sometimes you move your cursor somewhere and arrows appear so you can move paragraphs around. Why would I want to do that? Why doesn’t copy paste work? If I want to align things, like put an image on the left, I drag things around and push buttons and somehow it maybe works. Learning WordPress is a totally non-transferrable skill. I learned enough html and css to format my WordPress posts and that was a totally transferable skill that has helped me in numerous projects. Having technology think for you and trying to automaticize processes like placing images is awful. There’s a reason no one liked Clippy. it wasn’t that it talked to you. This is like Clippy but you can’t shut him up and you don’t even know he’s there! Kill this block editor thing. KILL IT WITH FIRE<>

Gutenberg solidifies our plan to exit WordPress

After building hundreds of sites on WordPress, my team and I are now planning to discontinue our use of WordPress.

The imposition of Gutenberg is a major and unnecessary headache. I didn’t expect it would be helpful for us, but I tried anyway. I click to edit an article and I get a blank white screen.

This is following the completely reckless update to text html widgets that took months to resolve.

This is quite disappointing for us, but now that WordPress is going to require us to put in a bunch of extra effort to maintain the sites, we can go ahead and apply that effort toward moving to another platform. So long WordPress, it was a nice ride..

Its not the future but its better.

I find this way easier to use than gutenburg. That seemed rushed and buggy. Its also not going to work well with the way some people build sites with heavy use of meta boxes such as ACF.

Its sad there’s such a big conflict here. Gutenburg should be superior but it just makes things harder.

Looks like we are going to live with two editors from now on.

Read all 306 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 removal of the “Try Gutenberg” dashboard widget.
  • Fixed condition for displaying of the after upgrade notice on the “What’s New” screen. Shown when the Classic Editor is selected and users cannot switch editors.


  • 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.