Restoring the Classic Editor and Widgets
Disable Gutenberg replaces the Block Editor with the Classic Editor and restores the original post-editing screen. That includes support for tools such as meta boxes, Quicktags, and custom fields; an option can also restore Classic Widgets.
When Gutenberg is inactive, the plugin does nothing. If it is active alongside the Classic Editor plugin, Disable Gutenberg gives priority to Classic Editor, so the latter controls the editing experience.
Choosing where the Block Editor remains available
The settings let sites replace the Block Editor broadly or make exceptions for specific content and users.
- Post types and roles: choose where the Classic Editor applies, including by post type or user role.
- Templates and individual content: target theme templates or specific post and page IDs; choose an editor for each post.
- Whitelisting: keep the Block Editor available based on a post title, slug, or ID, which helps when only a small set of pages needs blocks.
- Interface controls: hide Gutenberg notices and menu items, and add Classic Editor links on the Posts screen or a sidebar shortcut for adding a post.
- Frontend styles: enable or disable the Gutenberg stylesheet, giving site owners control over whether block styles load on the public-facing site.
A focused replacement with signs of ongoing maintenance
Disable Gutenberg suits sites that want the Classic Editor as a default while retaining exceptions for selected content, users, or templates.
Its granular controls add flexibility to a free Classic Editor replacement, but the many settings may be unnecessary for sites that simply want one site-wide switch. Adoption is widespread and its rating is excellent among many reviewers, suggesting established use. The sole recorded support thread was resolved, a positive signal tempered by the very small sample. An update several months ago also points to continued maintenance. The developer states that the plugin collects no user data, sets no cookies, and makes no third-party connections. For sites considering it, the key question is whether selective editor rules are useful enough to justify configuring the extra options.
