by
Fernando Tellado
5 (16 reviews)
No Gutenberg? - Choose Where to Use the Block Editor or the Classic Editor
Decide where the block editor stays and where the Classic Editor comes back. It also removes Global Styles, patterns, block widgets and block CSS.
No Gutenberg? ranks #2,293 among WordPress.org plugins with 9,000+ active installations, is #88 of 1,182 in the Editor & Writing category, a 5/5 rating from 16 reviews, and was last updated Oct 27, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7.1
v2.4.0
Current Version v2.4.0
Updated 1 week ago
Last Update on 27 Oct, 2026
Refreshed 1 week ago
Last Refreshed on
#88 of 1,182 in Editor & Writing
Top 5% by installs
Downloads -79.2% this week
Actively maintained
Rank
#2,293
—
No change
Active Installs
9K+
-3.2%
KW Avg Position
45.3
0.8 worse
Downloads
157.3K
+26 today
Support Resolved
100%
—
No change
Rating
100%
Review 5 out of 5
5
(16 reviews)
Next Milestone 10K
9K+
10K+
129
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 729 more installs to reach 10K+
Rank Changes
Current
#2,293
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
5.0
16 reviews
Overall
100%
5
16
(100%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Support Threads Overview
Resolved
Unresolved
1
Total Threads
1
Resolved
0
Unresolved
100%
Resolution Rate
Security History
Source: WPVulnerabilityNo known vulnerabilities on record for No Gutenberg?. Checked 1 month ago.
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 2.4.0
- Last Updated
- Oct 27, 2026
- Requires WP
- 6.1+
- Tested Up To
- 7.1
- PHP Version
- 7.4 or higher
- Author
- Fernando Tellado
Support & Rating
- Rating
- ★ ★ ★ ★ ★ 5
- Reviews
- 16
- Support Threads
- 1
- Resolved
- 100%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade NowSimilar Plugins
Adminify – White Label, Admin Menu Editor, Login Customizer
6K+ installs
#2,757
Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits
30K+ installs
#1,015
Elementor Website Builder – more than just a page builder
10M+ installs
#1
Classic Editor
8M+ installs
#4
CW
Classic Widgets
2M+ installs
#25
Advanced Editor Tools
1M+ installs
#30
File Manager
1M+ installs
#45
Spectra Legacy – Gutenberg Blocks
1M+ installs
#63
Redux Framework
900K+ installs
#70
User Role Editor
700K+ installs
#90
TL;DR
AI summary of the plugin's readmeThis plugin is for WordPress site owners who prefer the Classic Editor and want maximum compatibility or performance on their site. It removes the Gutenberg Block Editor and all related block functionality, including FSE Global Styles, Block Widgets, Patterns, and WooCommerce blocks.
- Disables Gutenberg Block Editor
- Removes FSE Global Styles
- Reverts to Classic Widgets
- Removes Block Patterns
- Disables Site Editor
- Disables WooCommerce block checkout and cart
- Removes block-related CSS and JavaScript
- Zero configuration required
Frequently Asked Questions
Common questions about No Gutenberg? - Choose Where to Use the Block Editor or the Classic Editor
No. Activating the plugin disables everything across the site. The settings page under Settings > No Gutenberg? is there only if you want to bring some part of the block editor back.
Yes. Go to Settings > No Gutenberg?, uncheck "Disable Gutenberg completely", and then choose where the block editor should go away: post types, user roles, page templates or individual entry IDs. Rules are independent, so anything that matches gets the Classic Editor and everything else keeps working as usual.
Yes. Once the master switch is off, the site wide pieces are independent checkboxes, so you can, for example, restore the classic Widgets screen and remove the block patterns while leaving the editor itself alone.
That is exactly why the plugin unchecks the frontend block assets and theme.json options for you when you switch to a partial setup: the content that still uses blocks would lose its styles on the frontend. The status panel tells you how many of your published entries are built with blocks, so you can decide with real numbers.
Yes, from wp-config.php. define( 'NO_GUTENBERG_LOCK_SETTINGS', true ); leaves Settings > No Gutenberg? visible but read only, and define( 'NO_GUTENBERG_HIDE_SETTINGS', true ); takes it out of the menu. To fix the configuration itself, and not only lock the screen, there is NO_GUTENBERG_OPTIONS. The description has the three of them together, with the settings you can fix and the details worth knowing.
Yes, and it is what the plugin is best at. Activate it site by site, or Network Activate it and it runs on every site of the network. Settings are stored per site, so each site has its own Settings > No Gutenberg? and each site administrator manages their own. For the whole network at once, the place is wp-config.php, the same file every site reads: what you define there reaches all of them, covers every setting the plugin has and wins over whatever each site has stored. There is no network settings screen, because that file does the job for the entire network in a couple of lines. They are in the description, under "One configuration for a whole network, or for a site you deliver".
Yes. In the post types table there is a second column, "Let each entry switch": check it for the post types where it makes sense. Those entries then get "Edit (Classic)" and "Edit (Blocks)" links in the list and a switch inside both editors, and each one remembers the editor you chose for it.
Yes. Products behave like any other post type: with the master switch on, or with Products checked in the rules, the classic product editor is forced and the WooCommerce block assets are removed from the frontend. If you leave blocks on for products, the block based product editor keeps working, without a separate setting contradicting it.
No, and the plugin goes out of its way to keep it that way. It never rewrites a single entry, and an entry that is already built with blocks keeps the block editor whatever the rules say, so nothing you set here can send it to an editor that would reflow its markup. The entries list labels those entries and can be narrowed down to them, so you can see exactly what you have. There is one visible change on the frontend: with the frontend block assets removed, content built with blocks loses the block styles. The status panel tells you how many entries are affected before you decide.
Yes. Uncheck the content protection under the master switch, on the settings page. From that point the rules apply to every entry, and the plugin warns you inside the Classic Editor whenever you open one that is built with blocks, because saving it there can break its blocks.
