Disable Gutenberg and Get the Classic Editor Back
Bring back the classic WordPress editor—globally, per post type, per role, or per single post—plus classic widgets and block-CSS cleanup, without a separate plugin.
I still write most of my posts in the classic editor. Not out of stubbornness—for straight text, the block editor’s panels, popovers and ”+” buttons are friction I don’t need. But the usual advice, “install the Classic Editor plugin,” is blunt: it flips Gutenberg off everywhere, for everyone, or not at all. What I actually want is nuance—classic for blog posts, blocks for landing pages, the simple editor for the client, the full one for me. Here’s how to disable Gutenberg with that kind of control, and clean up what it leaves running while you’re at it.
The essentials
- The module makes the classic editor the default, but the real value is granularity: choose the editor per post type, per role, or per individual post.
- It restores the classic Widgets screen (WordPress switched widgets to blocks too), on by default.
- It removes the block library’s front-end CSS by default—loaded on every page even when you use no blocks—and can strip it in the admin too.
- It stops Gutenberg fetching remote block patterns from the WordPress.org API, removing an external request on the editor.
- It quietly removes the obsolete “Try Gutenberg” dashboard panel—one less bit of clutter.
Why do people still disable the block editor?
Gutenberg is genuinely good at building complex layouts. But a lot of WordPress work isn’t layout—it’s writing. For a text-first blog, a business site, or a client who just needs to update a page, the classic TinyMCE editor is faster and less intimidating. The common reasons:
- You write mostly text and don’t need block-based layouts.
- You use a page builder (Elementor, Divi, Beaver Builder) that brings its own editing canvas anyway.
- You manage a site for a client who finds blocks confusing.
- You want a lighter, quicker admin.
None of these mean “kill Gutenberg forever, everywhere.” Which is exactly the problem with the usual on/off approach.
How do you disable Gutenberg—everywhere or just where you want?
Activate the Classic Editor module in Blaminhor Essentials. Out of the box it sets the classic editor as the default, so posts and pages open in familiar TinyMCE with no blocks, no side panels, no ”+” button. But the settings are where it earns its place over a blunt on/off plugin.
Set the default, then override it where you need to—by post type, by role, or on a single post.
The editor is resolved from the most specific level to the most general:
| Level | What it sets | Example |
|---|---|---|
| Single post | Per-post editor choice (with switching enabled) | Force blocks on one landing page |
| Post type | Classic or blocks for a whole type | Posts classic, pages on blocks |
| User role | Editor decided by who’s logged in | Classic for clients, blocks for you |
| Global default | The fallback for anything not overridden | Classic everywhere by default |
That layering is the difference between “I turned Gutenberg off” and “I put the right editor in front of each person and each content type.”
What does disabling Gutenberg clean up behind the scenes?
Two things you don’t see, both on by default where it’s safe:
Classic Widgets come back. WordPress didn’t only move the editor to blocks—it did the same to the Widgets screen. The module restores the traditional Widgets interface so your sidebar and footer widgets behave the way they always did.
Block CSS stops loading. WordPress enqueues the block library’s stylesheet on every front-end page, even one that contains no blocks at all. The module removes it by default, trimming kilobytes and an HTTP request off each page load, and can strip the block styles from the admin too if you want an even leaner backend. It also blocks Gutenberg’s call to the WordPress.org API for remote block patterns—one fewer external request every time you open the editor.
One toggle instead of one more plugin
You can install WordPress’s official Classic Editor plugin—it works, and it’s maintained. But it’s another plugin to install, update and watch for conflicts, and it stops at a global switch. If you’re already running Blaminhor Essentials, the Classic Editor module is a toggle away, and it gives you the per-type, per-role and per-post control the standalone plugin doesn’t.
If the per-role angle interests you—handing different users different experiences—it pairs neatly with managing WordPress user roles, where you shape what each role can see and do.
Classic Editor is one of the 20+ tools in Blaminhor Essentials—free and open-source on WordPress.org.
– blaminhor
FAQ
Can I keep Gutenberg for pages but use the classic editor for posts?
Yes. The Classic Editor module resolves the editor per post type, so you can set posts to classic and leave pages on the block editor (or the reverse). It can also decide by user role, and it remembers a per-post choice when you enable switching—far more granular than an all-or-nothing toggle.
Is the Classic Editor going away?
WordPress has committed to supporting the official Classic Editor plugin « for as long as is necessary », and has renewed that promise year after year, so it isn't disappearing any time soon. A module that restores the classic editor achieves the same result without depending on one plugin's lifecycle, and adds per-type and per-role control the official plugin doesn't offer.
What's the difference between Gutenberg and the Classic Editor?
Gutenberg is the block editor: you build content from stackable blocks — paragraphs, images, columns — with side panels and a floating toolbar. The Classic Editor is the older TinyMCE box, a single formatted text area much like a word processor. Blocks suit rich layouts; the classic editor suits fast, text-first writing with far less on-screen furniture.
How do I disable Gutenberg without a plugin (functions.php)?
You can add a filter to functions.php: return false from the « use_block_editor_for_post » hook to force the classic editor everywhere. It works, but it's blunt and lives in your theme, so it vanishes on a theme switch and gives no per-type or per-role control. A dedicated module is more durable and far more flexible.
Will switching to the Classic Editor break my existing block posts?
Not the underlying content, but it looks messy. Switching a block-built post to TinyMCE shows the raw block markup — those « <!-- wp:paragraph --> » comments — instead of a clean layout. Keep existing block posts on the block editor with a per-post override, or clean the markup once before you switch them over.
Do I need the Classic Editor if I use a page builder like Elementor?
Usually not for the builder itself — Elementor, Divi and Beaver Builder bring their own canvas and bypass Gutenberg on the pages they edit. But posts and other content still open in the block editor, so many people pair a builder with the classic editor to keep everything else simple and consistent.
Comments