Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Short answer: the Block Editor already included in WordPress is the production version of Gutenberg. The separately installed Gutenberg plugin is an earlier, faster-moving channel for testing features that may enter a future WordPress release. Most live sites should use core; install the plugin only for a specific feature, bug reproduction, or contribution, and test it on staging first.
For sites that need a managed WordPress environment while testing editor changes, Antihost managed WordPress hosting offers isolated resources for each site, one-click staging, automated and manual backups, free migration and free SSL.
As an Amazon Associate I earn from qualifying purchases.
What “Gutenberg” means in WordPress today
“Gutenberg” can refer to both the project that developed WordPress’s modern editing system and the plugin that continues that work. WordPress merged Gutenberg into WordPress 5.0 in December 2018. Since that release, every current WordPress installation has included a Gutenberg-derived Block Editor in core; you do not install a separate plugin to write posts with blocks.
Recommended Free Tools
WordPress documentation may call the built-in interface the Block Editor, WordPress Editor or Gutenberg Editor. They describe the same core editing experience in normal usage. The Gutenberg plugin is an optional companion that exposes newer, experimental or otherwise not-yet-merged work.
#1 Best Overall
A block is a discrete content element such as a Paragraph, Heading, image, video, gallery or Embed. Blocks are stored as structured content rather than as one undifferentiated text field. Themes and plugins can register their own blocks and extend the editor through WordPress’s block APIs, which is why the exact experience varies from site to site.
Core editor and plugin: the essential difference
| Aspect | Block Editor in WordPress core | Gutenberg plugin |
|---|---|---|
| What it is | A tested Gutenberg snapshot shipped with a particular WordPress release. | The separately released development channel for newer editor work. |
| Availability | Included automatically in WordPress 5.0 and later. | Optional installation from the WordPress administration area or the WordPress.org plugin repository. |
| Release cadence | Moves with WordPress’s planned major and maintenance releases. | Continues to receive releases between WordPress versions, so it is usually ahead of core. |
| Primary purpose | Reliable editing for production sites, with support tied to that WordPress version. | Trying upcoming features, exploring new blocks, reproducing editor issues and providing feedback or code. |
| Feature maturity | Features have passed the process for inclusion in the corresponding core release. | Features can be experimental, changing or still under active development. |
| Required for ordinary block editing? | Yes, this is the editor most sites already have. | No. |
The two are related codebases, not two unrelated editors. Installing the plugin adds a newer layer to the editor that WordPress already provides; it does not replace WordPress core or create a separate content format.
How WordPress versions map to Gutenberg versions
Each major WordPress release embeds a particular Gutenberg version. The Gutenberg project then keeps moving, so the plugin can contain work that is absent from the embedded snapshot. The official developer version table, updated in 2026, lists these mappings:
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →| WordPress line | Gutenberg version included in that line | How to interpret it |
|---|---|---|
| WordPress 6.8.x | Gutenberg 20.4 | The core editor is based on 20.4, while maintenance releases can include later fixes without changing the base mapping. |
| WordPress 7.0.x | Gutenberg 22.6 | The 7.0 editor reflects the 22.6 snapshot plus WordPress-specific fixes and integration. |
| WordPress 7.1.x | Gutenberg 23.6 | The 7.1 editor reflects the 23.6 snapshot; the table is a major-version map, not a promise that every point release has identical code. |
This is why a tutorial demonstrating a plugin feature may not match a site running an older WordPress release. Check Dashboard > Updates for the site’s WordPress version, then compare it with the feature’s documented availability. Do not assume that installing the plugin is the only way to obtain a capability: the next WordPress release may include it in core, while some experiments may never be merged.
What the plugin can add before core does
The plugin is the place where the Gutenberg project publishes its latest editor work for people willing to test it. Depending on the plugin release and the WordPress version underneath it, you may see changes to block behavior, editing workflows, Site Editing, collaboration or other editor components before those changes are scheduled for a core release.
Upcoming features
If a project announcement or developer document says a feature is available in Gutenberg but not yet in WordPress core, the plugin can let a site owner evaluate it early. Availability is not permanent: a feature can be renamed, redesigned, disabled by default or removed while it is being developed.
Issue reproduction
Support requests sometimes ask whether a problem occurs with the latest Gutenberg code. Installing the plugin on a staging copy can isolate whether an issue is already fixed upstream or whether it is specific to the site’s WordPress version, theme or another extension. That test is useful for a report; it is not a reason to expose a live site to experimental code indefinitely.
Feedback and contribution
The official Gutenberg repository describes the plugin as a way to test bleeding-edge features, explore blocks and contribute feedback. Designers, developers and site owners who want to help shape the editor can use it for that purpose, provided they understand that the interface and APIs can change.
Which one is safer for a live site?
For a normal production site, the editor in core is the safer default because it is the version WordPress supports as part of that release. “Safer” here means a more predictable compatibility and support baseline, not a universal performance or security guarantee. Official sources do not provide a benchmark proving that the plugin is faster, slower, more secure or more accessible than core. Results depend on the WordPress version, theme, custom blocks, meta boxes and other plugins on the individual site.
The Gutenberg plugin is not inherently unusable on production sites, but its purpose is experimentation. A change that works with one theme can expose a bug in another; an extension that relies on an internal behavior can break when the plugin updates. Use it on a live site only when the site owner has accepted that maintenance burden and has a tested recovery plan.
Use core when
- The site needs dependable publishing rather than early access to editor work.
- Editors, clients or support staff require a stable interface and repeatable instructions.
- The theme or plugins provide custom blocks, traditional meta boxes or other editor integrations that you cannot readily test after every update.
- The site is business-critical and does not have a staging copy, backups and a rollback procedure.
Consider the plugin when
- You need a documented feature that has not reached the site’s core WordPress version.
- You are reproducing an issue for a support request or a Gutenberg project report.
- You are deliberately testing or contributing to upcoming editor work.
How to install and evaluate the Gutenberg plugin safely
Do this on a staging site that mirrors the production theme, active plugins, custom blocks and PHP/WordPress configuration. A staging copy lets you test publishing, front-end output and editorial workflows without risking the public site.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →- Create a current backup and staging copy. Confirm that you can restore the database and files, and record the active WordPress, theme and plugin versions.
- Install the plugin in the staging administrator. Open Plugins > Add New, search for “Gutenberg,” choose the official Gutenberg plugin and select Install, then Activate. Alternatively, download the plugin from the WordPress.org plugin repository and upload it through the administrator’s plugin installer.
- Record the starting behavior. Open representative posts and pages before changing anything. Note how custom blocks, reusable content, metaboxes, embeds, media uploads and previews behave.
- Test the workflows that matter. Create a new post, edit an old post, schedule a post, save drafts, preview on the front end, upload media, use block patterns and complete any editorial approval process your team relies on.
- Check the browser console and server logs. JavaScript errors, failed REST requests or PHP warnings can reveal an incompatibility that is not obvious in the editor. Record the error and the exact plugin and WordPress versions.
- Test with the production theme and extensions enabled. Do not conclude that the plugin is compatible after testing with a blank or default theme. Custom blocks, metaboxes, multilingual tools, SEO fields and workflow plugins can change the result.
- Decide on a narrow purpose and update policy. If the test was for one feature or bug, document that reason, who owns follow-up testing and when the plugin will be removed or re-evaluated.
- Promote only after sign-off. Repeat the same test on a second staging run if the site is important, take a fresh backup and schedule the production change when a rollback is practical.
To remove the experiment, deactivate and delete the plugin from Plugins > Installed Plugins after confirming that the site still opens, saves and renders content normally. Removing the plugin does not downgrade WordPress’s built-in editor; it returns the site to the editor provided by its installed core version.
Theme, block and meta-box compatibility
Compatibility is determined by more than the editor label. Check the following layers together:
- WordPress version: Core contains a specific Gutenberg snapshot, and newer plugin code may assume APIs or behavior that the site’s version does not provide.
- Theme type: Block themes expose Site Editor and block-based templates differently from classic themes. A theme can support the Block Editor for post content without supporting every Site Editing capability.
- Custom blocks: A block’s registration, editor scripts, styles and saved markup must remain compatible with the editor version being tested. A block that saves different markup can trigger validation warnings or alter the rendered result.
- Traditional meta boxes: Plugins that add fields outside the block canvas can affect how the post editor is loaded and displayed.
- Other editor extensions: Plugins that add sidebars, panels, patterns, templates or keyboard shortcuts can conflict with changing Gutenberg interfaces.
The iframe post editor and Block API version 3
WordPress 6.3 introduced an iframe-based post editor when all registered blocks use Block API version 3 or higher and no traditional meta boxes are present. The iframe isolates the editor canvas so its styles more closely match the content environment, but that isolation also means a block’s assets and assumptions must be prepared for it.
Later behavior changed. WordPress 7.0 evaluates the blocks in post content when deciding whether to use the iframe, and Gutenberg 23.6, included with WordPress 7.1, always uses the iframe for the post editor. These version-specific rules matter to developers: a block that appeared to work in an older editor can fail to load its styles, depend on a parent document or make incorrect DOM assumptions after the iframe decision changes.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesWhat to test when a block is intended for the iframe
- Editor and front-end styles load without relying on selectors outside the iframe.
- Toolbar buttons, popovers, media controls and keyboard interactions still open and close correctly.
- Saved markup validates after reopening the post.
- Responsive previews and embeds render as expected.
- Any script that accesses
window, the document or editor selection APIs uses supported interfaces rather than assumptions about the parent page.
If a site contains a traditional meta box, do not use the absence of an iframe as proof that the plugin is broken. The documented conditions determine whether the iframe is used, and a meta box can intentionally prevent it.
Site Editing, block themes and the Gutenberg roadmap
The Block Editor began the first broad Gutenberg phase: easier content editing in WordPress 5.0. The second phase expanded customization through the Site Editor, block themes and block-based tools. Those capabilities grew from the same project, but their availability still depends on the installed WordPress version and the theme.
The official roadmap describes four broad phases: editing, customization, collaboration and multilingual work. In the 2026 roadmap, Phase 3 concentrates on collaboration and smoother publishing workflows, with WordPress 7.0 goals tied to that direction. A roadmap is a development plan, not a promise that every item is present in the plugin or core on a particular day. Verify the feature in the version you will actually run.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Do you need the Classic Editor instead?
The Classic Editor is a separate plugin for people who need the pre-5.0 editing interface. It is not the same as the Gutenberg plugin and is not a switch inside the Gutenberg plugin. WordPress user documentation and the Core Editor component describe it as the maintained fallback for the older interface.
Free tools Windows power users keep installed
One-click scans. No signup required.
Choose that route when a workflow depends on the classic editor’s meta-box layout or when a team cannot yet update its themes and customizations for blocks. Test the fallback with the same care as any editor change: switching interfaces can affect shortcodes, custom fields, publishing instructions and user permissions.
Troubleshooting common Gutenberg-plugin problems
The plugin is active but no new feature appears
Check the plugin version, the WordPress version and whether the feature is enabled or still experimental. Some features are limited to particular post types, themes or settings. Clear browser and server caches only after verifying that the feature is supposed to be available in that combination.
A block shows a validation warning
Compare the block’s saved markup before and after activation. A changing block serializer, missing editor asset or incompatible custom-block version can cause the warning. Restore the last valid content on staging, update the block implementation or disable the plugin before touching the production post.
A metabox or custom panel disappears
Identify whether the extension registers a traditional meta box, a block-editor sidebar or an iframe-incompatible script. Reproduce the issue with only the production theme and the affected extension enabled, then report the exact WordPress, Gutenberg and extension versions to the relevant developer.
The editor is blank or JavaScript errors appear
Use the browser console and server logs to find the first error, not just the last cascade of failures. Temporarily disable other editor extensions on staging, switch to the production theme and test again. If the problem disappears, re-enable extensions one at a time to identify the conflict. Keep the plugin disabled on production until the cause is understood.
The site breaks after an update
Use the backup or staging image to restore service, deactivate the Gutenberg plugin if it is the changed component and preserve the error details. Do not delete posts to make the editor load; the content may be valid even when an editor script is failing. Re-test with a fixed plugin or core release before reactivation.
A practical decision framework
| Your situation | Recommended choice | Reason |
|---|---|---|
| Routine posts and pages on a production site | Core Block Editor | It is already included and aligned with the site’s supported WordPress release. |
| You need a feature documented as plugin-only | Gutenberg plugin on staging first | You can evaluate the feature without making the public site an experiment. |
| You are diagnosing a reported editor bug | Compare core and plugin builds on a reproducible staging copy | The comparison helps determine whether the issue is fixed upstream or caused by the site. |
| You maintain custom blocks or legacy metaboxes | Core unless a planned compatibility test justifies the plugin | Each plugin update can expose assumptions in those integrations. |
| You need the pre-5.0 interface | Classic Editor plugin | It is the separate fallback for the older editing workflow. |
Before installing anything, write down the outcome you need: an early feature, a reproducible bug report or contributor testing. If you cannot state that outcome, the core editor is the appropriate choice.
Bottom line
WordPress already includes Gutenberg’s Block Editor. The standalone Gutenberg plugin is an optional, faster-moving testing channel, not an upgrade that every site needs. Keep production on core unless a defined requirement warrants the plugin; then use a production-like staging copy, test custom blocks and meta boxes, monitor iframe behavior and retain a rollback path.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
