Summarize with AI:

Disable Gutenberg

Switch posts or pages back to the classic editor while optionally keeping blocks for selected types.

Overview

Switches the block editor off for all applicable types or only for the types you list—falling back to the classic editor. Optional frontend dequeue of block library / global styles / WooCommerce blocks CSS. Loads a classic-editor shim when the Classic Editor plugin is not installed. Hard conflict with Gutenberg Block Control—enable only one. Defaults to classic everywhere (mode: all) with frontend CSS removal on.

Who is this for?

Sites standardized on the classic editor
Teams that want classic for some types and blocks for others
Agencies replacing the Classic Editor plugin with a PowerSuite toggle

Features

Classic everywhere or by type

Mode all or specific denylist.

Optional frontend CSS cleanup

Dequeue block styles when you do not need them publicly.

Classic Editor shim

Works even if Classic Editor plugin is absent.

High-priority filters

Overrides block editor for post types/posts as configured.

Use Cases

Classic-only editorial teams
Force classic on posts and pages site-wide.

Mixed workflows
Keep blocks for landing pages but classic for blog posts (specific mode).

Front-end CSS diet
Disable Gutenberg and remove unused block library CSS for visitors.

Frequently Asked Questions

What does Disable Gutenberg do in WP PowerSuite?
It switches selected (or all) post types back to the classic editor and can remove frontend block CSS.
How do I enable Disable Gutenberg in WP PowerSuite?
Enable the module, choose all vs specific types, set frontend CSS removal, and save. Keep Gutenberg Block Control off.
Who should use Disable Gutenberg?
Sites standardized on classic editing or mixed classic/block workflows.
Can I use it with Gutenberg Block Control?
No. They hard-conflict—enable only one.
Is Disable Gutenberg a free or Pro module in WP PowerSuite?
It is included (free) with WP PowerSuite.