No Gutenberg?

The most configurable way to leave the block editor behind. Activate it and everything block related is gone: the block editor, Global Styles, patterns, block widgets, the Site Editor and the block CSS and JavaScript that every page loads. From there you decide the scope: everywhere, or only for the post types, roles, templates and entries you choose.

What this plugin removes:

Core Gutenberg Features

• Gutenberg Block Editor (completely disabled)
• Full Site Editing (FSE) Global Styles and inline CSS
• Block-based Widget Editor (reverts to Classic Widgets)
• Block Patterns and Pattern Directory
• Theme.json support and processing
• Block Directory integration
• Site Editor functionality

Performance Optimizations

• The block library CSS and JavaScript that every page loads
• The Global Styles inline CSS, which dequeuing the handle never reaches
• The block assets of any other plugin that registers blocks, on pages where no block appears
• The block editor assets in the admin, wherever the Classic Editor is the one opening

WooCommerce Integration

• The block based product editor, which follows the same rules as any other post type
• The WooCommerce block styles and scripts, removed along with the rest of the block assets
• Nothing else: leave blocks on for products and the block product editor keeps working

Admin Experience

• Removes the welcome panel that promotes the block editor
• Removes the Patterns submenu from the Appearance menu (WP 6.5+)
• Removes the Fonts submenu from the Appearance menu (WP 7.0+)
• Blocks access to Site Editor pages
• Shows activation success notice
• Warns you when a block theme is active
• Adds settings and support links to plugin actions

A default that asks nothing, and a settings page for everything else – Activating the plugin disables the block editor and every block feature across the site, which is what most people install it for. The rest of this page is about wanting less than that.

Full control when you need it – The settings page lives under Settings > No Gutenberg?, built around one master switch. Leave it on and the whole site keeps the complete disable. Turn it off and you decide where the block editor goes away: by post type, by user role, by page template or by individual entry. The site wide pieces (classic widgets, block patterns, frontend block assets, theme.json and the Site Editor) are then yours to keep or remove one by one. Every checkbox means the same thing, so no setting ever undoes another one.

Switch editors entry by entry, where it makes sense – Editor switching is chosen per post type, right next to the rule that disables the block editor. Enable it for pages, for instance, and every page gets “Edit (Classic)” and “Edit (Blocks)” links in the list plus a switch inside both editors, while your posts stay untouched. Each entry remembers the editor chosen for it, and that choice beats the rules in both directions: one landing page can stay on the Classic Editor while the rest keep blocks, or the other way around.

It tells you what it is doing – The settings screen opens with a status panel for your particular site: how many block patterns are being blocked, how much weight is off every page, whether your theme is a block theme, and how much of your published content is really built with blocks. That last number is the one that should decide whether you strip the block styles from the frontend or not, and no other plugin tells you.

Built for agencies and managed sites – The whole configuration can be fixed from wp-config.php, and the settings screen locked as read only or hidden altogether, so a site you deliver keeps the setup you left behind.

A whole network configured in one file – This is where the plugin stands alone. Every single setting it has, and not just which editor opens, can be written in wp-config.php, the same file every site of a multisite network reads. A network of a hundred sites is set up once, all of them with the same rules, all of them with the same block CSS gone, and none of them able to drift away from it. The plugin can also be network activated and left alone, because settings are stored per site, so a network can equally let each site decide for itself. Same mechanism as the locking above, and this is how it is written.

Read the full description on the official page →