Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Troubleshooting

WPBakery Not Showing Frontend Editor: Causes and How to Fix It

WPBakery Not Showing Frontend Editor: Causes and How to Fix It

Short answer

The WPBakery frontend editor usually goes missing because Role Manager disables it for your role, the post type isn't enabled, or your theme turns it off. If the button shows but the editor stays blank, frame-blocking security headers or a plugin conflict are the likely cause.

Key takeaways

  • Check WPBakery Role Manager first for each user role.
  • Enable the post type you want to edit in Role Manager.
  • Bundled themes sometimes disable the frontend editor in code.
  • X-Frame-Options DENY or strict CSP headers can leave the editor blank.
  • Test plugin conflicts on a staging copy.

Why is the WPBakery frontend editor not showing?

The WPBakery frontend editor usually disappears because it is switched off in Role Manager, your theme disables it, the post type isn't enabled, or security headers stop the page loading inside its preview frame.

The frontend editor is the live, on-page view where you drag and edit elements while seeing the real design. When it goes missing, you may only see the Backend Editor button, or the frontend view opens to a blank screen.

Below you'll find each cause, how to confirm it and how to fix it. Start at the top, since the first two causes are the most common.

If the backend editor is the one missing, see our separate guide on WPBakery not showing the backend editor.

What are the main causes at a glance?

Most cases trace back to one of six causes: role settings, theme code, post type settings, the block editor, security headers or a plugin conflict.

CauseWhat you noticeWhere to fix it
Frontend editor disabled in Role ManagerNo Frontend Editor button at allWPBakery, then Role Manager
Theme turns it off with codeButton missing for every userTheme options or child theme
Post type not enabledWorks on pages, not on posts or custom typesRole Manager post types setting
Block editor activeWPBakery buttons hidden or limitedClassic editor or WPBakery settings
X-Frame-Options or CSP headersEditor opens to a blank or refused frameSecurity plugin, server or CDN headers
Plugin or script conflictEditor loads half way or freezesDeactivate plugins one by one

Check the button first. If no Frontend Editor button appears, it's a settings problem. If the button is there but the editor won't load, it's a loading problem.

Is the frontend editor turned off in Role Manager?

Yes, this is the most common cause, so open WPBakery, then Role Manager, choose your user role and make sure the frontend editor option is enabled.

WPBakery lets admins control which roles can use each feature. A site owner or developer may have turned the frontend editor off for Editors or even Administrators.

To check:

  1. In the dashboard, go to WPBakery Page Builder and click Role Manager.
  2. Expand the role you use, such as Administrator.
  3. Find the frontend editor setting and make sure it is enabled.
  4. Check the Post types setting for the same role.
  5. Save your changes and reload a page in the editor.

Repeat this for every role that needs it. Settings for one role don't apply to others.

The WPBakery knowledge base covers the related problem of the builder not appearing on posts and custom post types.

Is the post type enabled for WPBakery?

If the frontend editor works on pages but not on posts or custom post types, the post type is not enabled for WPBakery in Role Manager.

In the Role Manager, set Post types to custom and tick each type you want, such as posts, pages, portfolio items or products. Save and test again.

Some post types can't use the frontend editor at all. Types that aren't publicly viewable have no front-end URL, so there is nothing for the editor to load. In that case only the backend editor works.

Theme templates such as archives and search results also aren't edited this way. They're controlled by the theme.

Could your theme be disabling the frontend editor?

Yes, some themes ship WPBakery bundled and switch the frontend editor off in code with the vc_disable_frontend function, often to avoid layout bugs.

If the button is missing for every role even after Role Manager looks right, search your theme's files for that function. A developer can also look in the theme's functions.php file or its WPBakery integration file.

You have a few options:

  • Check the theme's options panel for a setting that turns the frontend editor back on
  • Ask the theme author whether the frontend editor is supported
  • Remove the call in a child theme if the author says it's safe

Don't edit the parent theme directly. An update will undo your change. Our guide on what a child theme is explains the safer route.

Also check that the bundled WPBakery version is current. Bundled copies often fall behind, and an old builder with a newer WordPress can break the editor.

Does the block editor hide WPBakery's buttons?

WPBakery is built around the classic editor, so on sites using the block editor its Backend and Frontend Editor buttons may be missing or limited until the classic editor is used for those posts.

Many sites that run WPBakery also run the Classic Editor plugin for this reason. WPBakery's own settings may include an option related to Gutenberg, depending on your version.

To test:

  1. Install and activate the Classic Editor plugin.
  2. Open a page for editing.
  3. Look for the WPBakery buttons above the content area.

If they appear, the block editor was the issue. Our guide on going back to the classic editor covers the settings in detail.

Are security headers blocking the editor frame?

Yes, the frontend editor loads your page inside a frame, so an X-Frame-Options header set to DENY or a Content-Security-Policy that forbids framing will leave the editor blank.

This one is easy to miss because the button shows up and the editor starts to open, then the preview area stays empty.

How to confirm it:

  • Open your browser's developer tools and look at the Console for messages about refusing to display a page in a frame
  • Check the response headers of your page in the Network tab
  • Look for X-Frame-Options: DENY or a frame-ancestors rule set to none

MDN's pages on X-Frame-Options and CSP explain how these headers work.

Change the header to SAMEORIGIN, or allow your own domain in frame-ancestors. These headers are often set by a security plugin, your server config, a CDN or your host. Change them in the place that sets them.

Mixed content can cause the same blank frame. If your admin loads over HTTPS but some site URLs still use HTTP, the browser may block the frame. Make sure the WordPress Address and Site Address both use HTTPS.

Could a plugin conflict break the frontend editor?

Yes, a plugin that loads heavy scripts in the admin, optimises JavaScript or changes how pages render can stop the frontend editor from loading.

Common suspects include:

  • Cache and minify plugins that combine JavaScript
  • Lazy load or script delay features
  • Other page builders running at the same time
  • Security plugins that strip scripts

Test on a staging copy. Deactivate all plugins except WPBakery, check the editor, then turn plugins back on one at a time. Our guide on fixing a plugin conflict shows a safe method.

If you use a cache plugin, exclude logged-in users from caching and turn off script delay for admins. Then clear all caches. Our guide on how to clear cache in WordPress covers each layer.

Could PHP memory or errors be the problem?

Yes, the frontend editor loads more code than a normal page view, so a low memory limit or a PHP error can stop it halfway.

Check your memory under Tools, then Site Health, then Info, in the Server and WordPress constants sections. A limit of 256M is a sensible target for builder sites.

Turn on debug logging to catch errors. Add WP_DEBUG and WP_DEBUG_LOG to wp-config.php, reload the editor and read wp-content/debug.log. The WordPress debugging guide lists the settings.

If you see memory errors, our guide on increasing the PHP memory limit explains how to raise it.

What if WPBakery itself is broken or outdated?

Update WPBakery to the latest version, make sure the licence is active if you bought it directly, and reinstall it if files may be damaged.

Bundled theme copies are updated by the theme author, not by WPBakery. If your theme is old, the builder inside it is old too.

To reinstall safely:

  1. Take a full backup of the site.
  2. Download a fresh copy from your WPBakery account or theme package.
  3. Deactivate and delete the old plugin.
  4. Upload and activate the new copy.

Your layouts are stored as shortcodes in post content, so removing and reinstalling the plugin doesn't delete them. For other builder issues, see our guide on WPBakery Page Builder not working.

When should you contact support?

Contact your theme author first if WPBakery came bundled with the theme, and WPBakery support if you hold your own licence and the checks above haven't worked.

Send them:

  • Your WordPress, PHP and WPBakery versions
  • Screenshots of browser console errors
  • The relevant lines from debug.log
  • A list of what you already tested

WPBakery's own blog post on common WPBakery issues lists more fixes worth trying before you write in.

Frequently asked questions

Where is the WPBakery frontend editor button?

When enabled, it appears near the top of the classic edit screen next to the Backend Editor button. It also shows in the WordPress admin bar as an edit option when you view a page while logged in.

Why does the frontend editor work for admins but not editors?

Role Manager settings are separate for each user role. Open WPBakery Role Manager, expand the Editor role, enable the frontend editor and the needed post types, then save.

Will reinstalling WPBakery delete my page layouts?

No. WPBakery saves layouts as shortcodes inside post content, so removing and reinstalling the plugin keeps them. Take a backup first anyway, and check a few pages after reinstalling.

Can I use the WPBakery frontend editor on archive pages?

No. The frontend editor edits individual posts and pages that have their own content. Archive and search pages are built by your theme templates, so you change them through theme options or a template builder.

Why is the frontend editor blank after it opens?

A blank editor usually means the page can't load inside the editor frame. Frame-blocking headers, mixed HTTP and HTTPS content, JavaScript errors or low PHP memory are the common causes.

Sources

  1. I can not use WPBakery Page Builder on posts and custom posts WPBakery Knowledge Base
  2. 7 common WPBakery issues and how to fix them WPBakery
  3. X-Frame-Options MDN Web Docs
  4. Classic Editor plugin WordPress.org
  5. Debugging in WordPress WordPress Developer Resources

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.