{
    "title": "Gutenberg",
    "seo_title": "Gutenberg plugin: review, recommended settings and limits",
    "h1": "Gutenberg",
    "description": "Gutenberg plugin: who it is for, production risks, experiments to leave off, recommended settings and patched vulnerabilities.",
    "lead": "The Gutenberg plugin, published by WordPress.org, gives you early access to new block editor and Site Editor features before they reach WordPress. Our take on where it belongs, its risks in production, the experiments to leave off and its past vulnerabilities.",
    "language": "en",
    "locale": "en-US",
    "type": "plugin-sheet",
    "url": "https://www.wp-masquerade.com/features/camouflaged-plugins/gutenberg/",
    "canonical": "https://www.wp-masquerade.com/features/camouflaged-plugins/gutenberg/",
    "markdown": "https://www.wp-masquerade.com/features/camouflaged-plugins/gutenberg/index.md",
    "json": "https://www.wp-masquerade.com/features/camouflaged-plugins/gutenberg/index.json",
    "published": "2026-11-04T08:00:00+00:00",
    "modified": "2026-11-05T21:10:53+00:00",
    "site": {
        "name": "WP Masquerade",
        "url": "https://www.wp-masquerade.com/"
    },
    "translations": [
        {
            "language": "en",
            "hreflang": "en-US",
            "title": "Gutenberg",
            "url": "https://www.wp-masquerade.com/features/camouflaged-plugins/gutenberg/",
            "markdown": "https://www.wp-masquerade.com/features/camouflaged-plugins/gutenberg/index.md",
            "json": "https://www.wp-masquerade.com/features/camouflaged-plugins/gutenberg/index.json"
        },
        {
            "language": "fr",
            "hreflang": "fr-FR",
            "title": "Gutenberg",
            "url": "https://www.wp-masquerade.com/fr/fonctionnalites/extensions-camouflees/gutenberg/",
            "markdown": "https://www.wp-masquerade.com/fr/fonctionnalites/extensions-camouflees/gutenberg/index.md",
            "json": "https://www.wp-masquerade.com/fr/fonctionnalites/extensions-camouflees/gutenberg/index.json"
        },
        {
            "language": "es",
            "hreflang": "es-ES",
            "title": "Gutenberg",
            "url": "https://www.wp-masquerade.com/es/funcionalidades/plugins-camuflados/gutenberg/",
            "markdown": "https://www.wp-masquerade.com/es/funcionalidades/plugins-camuflados/gutenberg/index.md",
            "json": "https://www.wp-masquerade.com/es/funcionalidades/plugins-camuflados/gutenberg/index.json"
        },
        {
            "language": "de",
            "hreflang": "de-DE",
            "title": "Gutenberg",
            "url": "https://www.wp-masquerade.com/de/funktionen/getarnte-plugins/gutenberg/",
            "markdown": "https://www.wp-masquerade.com/de/funktionen/getarnte-plugins/gutenberg/index.md",
            "json": "https://www.wp-masquerade.com/de/funktionen/getarnte-plugins/gutenberg/index.json"
        },
        {
            "language": "it",
            "hreflang": "it-IT",
            "title": "Gutenberg",
            "url": "https://www.wp-masquerade.com/it/funzionalita/plugin-camuffati/gutenberg/",
            "markdown": "https://www.wp-masquerade.com/it/funzionalita/plugin-camuffati/gutenberg/index.md",
            "json": "https://www.wp-masquerade.com/it/funzionalita/plugin-camuffati/gutenberg/index.json"
        },
        {
            "language": "pt",
            "hreflang": "pt-BR",
            "title": "Gutenberg",
            "url": "https://www.wp-masquerade.com/pt/recursos/plugins-wordpress-camuflados/gutenberg/",
            "markdown": "https://www.wp-masquerade.com/pt/recursos/plugins-wordpress-camuflados/gutenberg/index.md",
            "json": "https://www.wp-masquerade.com/pt/recursos/plugins-wordpress-camuflados/gutenberg/index.json"
        },
        {
            "language": "nl",
            "hreflang": "nl-NL",
            "title": "Gutenberg",
            "url": "https://www.wp-masquerade.com/nl/functies/gecamoufleerde-plugins/gutenberg/",
            "markdown": "https://www.wp-masquerade.com/nl/functies/gecamoufleerde-plugins/gutenberg/index.md",
            "json": "https://www.wp-masquerade.com/nl/functies/gecamoufleerde-plugins/gutenberg/index.json"
        }
    ],
    "headings": [
        {
            "level": 1,
            "text": "Gutenberg"
        },
        {
            "level": 2,
            "text": "What the Gutenberg plugin changes on a WordPress site"
        },
        {
            "level": 2,
            "text": "Who should run Gutenberg on top of WordPress"
        },
        {
            "level": 2,
            "text": "Gutenberg plugin strengths and limitations"
        },
        {
            "level": 3,
            "text": "Strengths"
        },
        {
            "level": 3,
            "text": "Limitations"
        },
        {
            "level": 2,
            "text": "The settings we recommend for Gutenberg"
        },
        {
            "level": 2,
            "text": "Gutenberg security: editor flaws ship through the plugin too"
        },
        {
            "level": 2,
            "text": "Gutenberg plugin FAQ",
            "id": "faq"
        }
    ],
    "body": "## The essentials\n\n- Best for testing themes, blocks and plugins against the editor in the next WordPress release.\n- Main caveat: a beta plugin that replaces the whole editor, so keep it off production sites.\n- Free with no paid tier, published by WordPress.org.\n\n## What the Gutenberg plugin changes on a WordPress site\n\nGutenberg started as the name of the project that gave WordPress its block editor, followed by the Site Editor, global styles and the font library. All of that already ships with WordPress: each major release folds in the stable features of several plugin versions. So installing the Gutenberg plugin is about something else: getting those features weeks or months before they land in WordPress.\n\nOnce active, the plugin swaps the editor scripts, styles and blocks bundled with WordPress for its own, newer versions. On the front end, block styles are then loaded from the plugin’s folder. It adds a Settings > Gutenberg screen where experimental features can be turned on one at a time, and it takes over some WordPress screens, such as Appearance > Fonts. Its own listing describes it as a beta plugin for tech-savvy early adopters who want to test features still in active development.\n\nThe plugin is published by WordPress.org and built in the open by WordPress contributors. It is completely free, with no paid tier and no account to create. A new version ships roughly every two weeks, and bug reports go to the project’s GitHub repository rather than the plugin’s support forum.\n\n![Diagram: Gutenberg works on visitors and bots, wordpress, database and files. Public traces: folder name (hidden with Pro); CSS classes (still visible).](https://www.wp-masquerade.com/media/wpm-sheets/gutenberg/diagram-en.svg?v=202a1d10)\n\n## Who should run Gutenberg on top of WordPress\n\nThe plugin pays off when you have a concrete reason to work with tomorrow’s editor:\n\n- **Theme and plugin developers**: check that your blocks, templates and theme.json work with the next editor release before your customers do.\n- **Agencies planning updates**: spot interface changes on a copy of client sites and brief editors ahead of time.\n- **Contributors and testers**: try the experiments (real-time collaboration, the new media modal, the new dashboard) and report problems.\n- **Sites waiting on a specific fix**: an editor bug fixed in the plugin can be available before the WordPress release that includes it, as long as you test.\n\nIt is the wrong pick for a production site that has to stay stable, and for anyone who simply writes in the editor: WordPress already contains every feature considered ready. If you need the opposite and want to keep the old editor, look at [Classic Editor](https://www.wp-masquerade.com/features/camouflaged-plugins/classic-editor/) instead.\n\n## Gutenberg plugin strengths and limitations\n\n### Strengths\n\n- **Official and free.** This is the code that will end up in WordPress, with no upsell and no ads.\n- **A head start on WordPress.** New blocks, layout tools and editor fixes show up here before the next major release.\n- **Opt-in experiments.** Each experimental feature has its own checkbox, and nearly all of them are off by default.\n- **A real test bench.** Testing a theme or plugin against the upcoming editor saves you from finding an incompatibility on WordPress update day.\n\n### Limitations\n\n- **A beta plugin.** It presents itself as a tool for testing features under development, not as a stable release.\n- **It replaces the whole editor.** A bug in one release affects the entire editor, not just an added feature.\n- **A fast release pace.** A version roughly every two weeks, with interface changes your editors will notice.\n- **Content tied to the plugin.** An experimental block does not exist in WordPress: if you deactivate the plugin, content that uses it may display incorrectly.\n- **Recent WordPress only.** The plugin only accepts recent WordPress versions: a site stuck on an older release cannot install it.\n\n## The settings we recommend for Gutenberg\n\nExperiments live under Settings > Gutenberg, grouped into Blocks, Media, Interactivity, Real-Time Collaboration and Other. Test anything you turn on in a [staging copy](https://www.wp-masquerade.com/glossary/staging-environment/) before carrying it over to the live site.\n\n| Setting | Recommended value | Why |\n| --- | --- | --- |\n| **Experimental blocks**  Settings > Gutenberg > Blocks | Off (default) | The plugin itself warns that these blocks can change enough to cause validation errors and display issues. |\n| **Enable real-time collaboration**  Settings > Gutenberg > Real-Time Collaboration | Off in production | Several people edit the same post at once: try it on staging with your usual plugins first. |\n| **Full-page client-side navigation**  Settings > Gutenberg > Interactivity | Off (default) | It changes how front-end pages load, so test your analytics and consent scripts before turning it on. |\n| **Media Upload Modal** and **Media Editor (Route)**  Settings > Gutenberg > Media | Off (default) | They replace the WordPress media modal and Edit Media screen, which many plugins rely on. |\n| **Admin design tokens**  Settings > Gutenberg > Other | Off (default) | Its own description reserves it for testing: it can change how plugin screens look and is not meant for a live site. |\n| **React 19**  Settings > Gutenberg > Other | Default value | The plugin turns it off by itself when it detects an incompatible theme or plugin; uncheck it only if a screen breaks. |\n| **Enable auto-updates**  Plugins > Installed Plugins | On for staging; in production, only if the plugin stays there | Editor security fixes also ship through the plugin, and an outdated copy keeps flaws that have since been patched. |\n\n- Open an existing post in the editor and check that no block shows an unexpected or invalid content warning.\n- Click through the screens of your main plugins (forms, SEO, store): they should load and save normally.\n- Before deactivating the plugin, find content that uses an experimental block and replace it.\n- Write down the plugin version you tested, so you know which WordPress release will bring the same features.\n\n## Gutenberg security: editor flaws ship through the plugin too\n\nThe plugin contains the WordPress editor’s code, so an editor flaw can affect both WordPress and the plugin, with two separate fixes. That was the case with CVE-2023-38000, a stored [XSS vulnerability](https://www.wp-masquerade.com/glossary/xss/) in the navigation link block that a contributor account could exploit (CVSS 6.5). It was fixed in WordPress 6.3.2 (plus maintenance releases of the 5.9 to 6.2 branches) and in Gutenberg plugin 16.8.1.\n\nUpdating WordPress is not enough if the plugin falls behind, because its files take the place of the core ones. Keep it current, ideally with automatic plugin updates, or delete it from sites where it no longer serves a purpose. Security issues are reported through the WordPress HackerOne program. The `wp-block-*` classes come from WordPress itself; the box below shows what WP Masquerade covers for the plugin.\n\n## Gutenberg plugin FAQ\n\n**Do I need the Gutenberg plugin to use the block editor?**\n\nNo. The block editor has been part of WordPress since version 5.0. The plugin only gives you upcoming features early.\n\n**Can I run the Gutenberg plugin on a production site?**\n\nYou can, but it presents itself as a beta. Test every update on staging first (see our guide to WordPress staging) and leave the experiments off on the live site.\n\n**What happens if I deactivate the Gutenberg plugin?**\n\nYou get back the editor that ships with your WordPress version, and your content stays saved. Only content built with an experimental block or a feature missing from WordPress can cause trouble.\n\n**Where do I report a Gutenberg plugin bug?**\n\nOn the issues page of the project’s GitHub repository, after checking that nobody has reported it already. The team responds faster there than on the plugin’s forum.\n\n## Key facts\n\n- Category: Builders and themes\n- Vendor: WordPress.org\n- Price: Free, with no paid version\n- Active installations (wordpress.org): 400 000+\n- Version: 24.3.1\n- Official page: https://wordpress.org/plugins/gutenberg/\n\n## What WP Masquerade hides\n\n- Handled by the free version of WP Masquerade\n- With Pro: folder name\n- Still visible: CSS classes",
    "catalog": "gutenberg",
    "essentials": [
        "Best for testing themes, blocks and plugins against the editor in the next WordPress release.",
        "Main caveat: a beta plugin that replaces the whole editor, so keep it off production sites.",
        "Free with no paid tier, published by WordPress.org."
    ],
    "format": "application/json"
}