Title here
Summary here
Disable Gutenberg
Disable the Gutenberg block editor site-wide and return to the classic TinyMCE editor you know and love—simpler editing for users who prefer the traditional WordPress experience.
Use Cases
- Restore the classic editor for users who find Gutenberg’s blocks confusing or slow
- Improve admin performance by removing Gutenberg’s JavaScript-heavy interface
- Maintain consistency on sites built before Gutenberg that use classic page builders
- Speed up content creation for writers who prefer straightforward text editing
How It Works
When you enable this module:
- All posts and pages open in the classic TinyMCE editor instead of Gutenberg
- Block library CSS is removed from the frontend (reducing page weight)
- WooCommerce block styles are also dequeued
- The change affects all users site-wide
The classic editor works exactly like WordPress did before version 5.0—familiar toolbar, simple interface, no blocks.
Settings
This module has no configurable settings. Enable it to disable Gutenberg everywhere, or leave it disabled to use the block editor.
Where to Find It
Location: Switchboard → Modules → Optimization → Disable Gutenberg
After enabling, go to Posts → Add New — you should see the classic editor instead of the block editor.
What Gets Removed
In the Admin
- Gutenberg block editor interface replaced with classic TinyMCE
- Block inserter and block toolbar removed
On the Frontend
These stylesheets are dequeued:
| Stylesheet | Size | Purpose |
|---|---|---|
wp-block-library | ~50KB | Core block styles |
wp-block-library-theme | ~5KB | Theme block styles |
wc-blocks-style | ~40KB | WooCommerce block styles |
Potential frontend savings: 80-100KB of CSS
Existing Block Content
Important: If you have existing posts created with Gutenberg, they’ll still work—but editing them in the classic editor shows the raw block markup.
Example of what you’ll see:
<!-- wp:paragraph -->
<p>Your paragraph text here.</p>
<!-- /wp:paragraph -->This is the block syntax. You can edit around it, but it’s not as clean as native classic editor content.
For best results, use this module on sites that:
- Were built before Gutenberg and never adopted it
- Are starting fresh with classic editor content
- Have very simple content (text and basic images)
FAQ
Will my existing Gutenberg posts break?
No. Posts display correctly on the frontend. However, when you edit them in the classic editor, you’ll see the HTML with block comments (<!-- wp:paragraph -->). It works, but it’s messier than editing native classic content.Can I enable Gutenberg for some users?
This module disables Gutenberg for all users. If you need per-user or per-role control, you’ll need a different solution like the Classic Editor plugin with user choice enabled.What about widgets and the site editor?
This module focuses on the post/page editor. Block-based widgets and the Full Site Editor (for block themes) may still have block functionality. For complete Gutenberg removal, you may need additional configuration.Does this improve admin performance?
Yes. The classic editor loads faster than Gutenberg because it uses simpler JavaScript. Users on slower computers or connections often notice the difference.Is the Classic Editor plugin still needed?
No. This module provides the same core functionality—disabling Gutenberg and restoring the classic editor. You don’t need both.If you’re building a new site and know you won’t use blocks, enable this module from the start. All your content will be native classic editor format—no block markup to deal with.
Performance Comparison
| Metric | Gutenberg | Classic Editor |
|---|---|---|
| Editor JS Size | ~1.5MB | ~300KB |
| Time to Interactive | 2-4 seconds | <1 second |
| Frontend CSS Removed | - | 80-100KB |
The classic editor is lighter and faster, especially beneficial for:
- Sites on shared hosting
- Users on older computers
- High-volume content teams
PRO
Upgrade to Pro
Get access to all 147 modules with a single license
Prev
Disable Feeds