#4 by installs
Classic Editor
Enables the previous "classic" editor and the old-style Edit Post screen with TinyMCE, Meta Boxes, etc. Supports all plugins that extend this screen.
- Installs
- 8+ million
- Rating
- 4.9 (1.3K)
- Updated
- 5 months ago
Classic Editor +
The "Classic Editor +" plugin disables the block editor, removes enqueued scripts/styles and brings back classic Widgets.
- Active installs
- 30,000+
- #943 of 1,000
- Downloads, all time
- 747.8K
- 747,817
- Downloads, 30 days
- 59.8K
- 8.4K in the last 7
- Rating
- 4.9 / 5
- 31 reviews
- Last updated
- 8 days ago
- Oct 23, 2026
- Version
- 4.4.5
- 30 releases
Upkeep and compatibility
| Last updated | October 23, 2026Updated in the last 3 months |
|---|---|
| Tested up to | WordPress 7.1.4Covers WordPress 7.1.4, the current release |
| Needs WordPress | 5.5 or newer |
| Needs PHP | 5.6 or newer |
| First published | July 8, 2018 |
| Support, last two months | 2 of 2 threads resolved (100%) |
Reviews
4.9 / 5 from 31 reviews
| 5 stars | 30 |
|---|---|
| 4 stars | 0 |
| 3 stars | 0 |
| 2 stars | 1 |
| 1 star | 0 |
Downloads, last 30 days
What the author says it does
GDPR-compliant: does not collect any user data
The free “Classic Editor +” plugin is targeted at everyone who does not want to use the WP Block Editor (Gutenberg), introduced in WordPress 5.0. Install it now on sites and the UX remains the same as you are used to without redundant styling being added to the frontend of your site!
What’s New:
Several fixes that remove scripts/styles from frontend
This plugin simply disables the WP Block Editor, removes any and all styling from both front- and backend and disables the block editor for widgets too.
And if WooCommerce and/or WPML are installed on the site, “Classic Editor +” removes the block styles of those plugins too.
There are no Settings, it simply does what it says on the label.
Therefore I highly recommend installing this “Classic Editor +” plugin.
I 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 here. 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 +” plugin, please consider leaving a review. Thanks!
“Classic Editor +” by Pieter Bos and Greg Schoppe.
The opening of the plugin's own description. The full text, installation notes and changelog are on its WordPress.org page.
Questions the author answers
What is the WP block editor?
The release of WordPress 5.0 came with a replacement of the TinyMCE editor you had gotten used to for adding or editing content. Some find it an improvement, others don’t. More information can be found on the WP 5.0 release post.
Why this plugin? Isn’t the purpose of the Classic Editor plugin to disable the new block editor?
The Classic Editor plugin does not remove any of the frontend styling, even when one selects the option to disable the block editor. In terms of site optimisation that is not good practice.
This “Classic Editor +” simply removes the block editor and all its styling from both frontend and backend and if your site uses WooCommerce, it also removes block styling related to that from the frontend.
Do I still need the Classic Editor plugin on my site?
Version 4.0 of the “Classic Editor +” plugin has been a complete rewrite (and simplification) and it is no longer depending on the Classic Editor plugin. When the latter is active, it will be deactivated and then you can safely remove it.
Why does my content area (.entry-content) shift or look misaligned with my theme?
Classic Editor + removes WordPress’s global styles from the front end to keep the page lean. Some themes, Blocksy for example, rely on those styles for the layout of the content area, which can make .entry-content shift to the left margin.
To bring the global styles back, add the following to your child theme’s functions.php or to a functionality plugin:
I have an issue with this plugin, where can I get support?
Please open an issue on Github
Latest changelog entry
- date: October 22, 2026
- Docs: added a FAQ entry explaining why .entry-content can shift with some themes (for example Blocksy) and how to restore WordPress’s global styles with a short snippet in child theme’s functions.php file or functionality plugin.
Tagged
Plugins that share its tags
#25 by installs
Classic Widgets
Enables the previous "classic" widgets settings screens in Appearance - Widgets and the Customizer. Disables the block editor from managing widgets.
- Installs
- 2+ million
- Rating
- 4.9 (272)
- Updated
- 11 months ago
#30 by installs
Advanced Editor Tools
Extends and enhances the block editor (Gutenberg) and the classic editor (TinyMCE).
- Installs
- 1+ million
- Rating
- 4.5 (354)
- Updated
- 2 months ago
#117 by installs
Disable Gutenberg
Disable Gutenberg Block Editor and restore the Classic Editor and original Edit Post screen (TinyMCE, meta boxes, etc.).
- Installs
- 500,000+
- Rating
- 5.0 (735)
- Updated
- 3 months ago
Widget Options gives you super powers to control your site’s sidebar widgets and all Gutenberg blocks on pages, posts & other custom post types.
- Installs
- 100,000+
- Rating
- 4.9 (1.5K)
- Updated
- 5 days ago
#448 by installs
Custom Sidebars – Dynamic Sidebar Classic Widget Area Manager
Flexible sidebars for custom classic widget configurations on any page or post. Create custom sidebars with ease!
- Installs
- 100,000+
- Rating
- 4.7 (1K)
- Updated
- 3 months ago
Where this page's numbers come from
Read from the WordPress.org plugin API on , when WordPress 7.1.4 was the current release. WordPress.org rounds active installs into buckets. These are the directory's figures, not my verdict, and I haven't tested this plugin.