Troubleshooting
WPBakery Page Builder Not Working? Causes and Fixes

Short answer
WPBakery Page Builder usually stops working because the plugin is outdated for your WordPress or PHP version, the post type is not enabled in its Role Manager, another plugin or the theme causes a JavaScript conflict, or PHP memory runs out. Theme-bundled copies often lag behind, so update WPBakery through your theme, then check the browser console for errors.
Key takeaways
- Outdated WPBakery versions are the most common cause of problems.
- Theme-bundled copies update through the theme, not directly.
- Role Manager controls which post types and users can use the editor.
- Browser console errors usually reveal JavaScript conflicts.
- Raw shortcodes on pages mean WPBakery is inactive or missing.
Why is WPBakery Page Builder not working?
Most problems come from an outdated plugin version, editor access disabled for a post type or role, a JavaScript conflict with another plugin or theme, low PHP memory, or a broken plugin installation.
WPBakery is a premium page builder used by many commercial themes. Our guide on using WPBakery Page Builder covers how it normally works.
Because it is often bundled, many site owners do not realise they are running an old copy until something breaks.
| Symptom | Likely cause | First fix |
|---|---|---|
| Editor button missing | Post type or role not enabled | Check Role Manager |
| Editor loads forever or blank | JavaScript conflict or old version | Update, check console |
| Raw shortcodes on pages | Plugin inactive or deleted | Reactivate WPBakery |
| Errors after WordPress update | Outdated WPBakery | Update plugin or theme |
| Crashes on large pages | Memory limit | Raise PHP memory |
Note what changed recently. Updates to WordPress, PHP, the theme or plugins often trigger the problem.
If you cannot remember, the update emails WordPress sends to the admin address and your host's backup list help rebuild the timeline.
Is WPBakery out of date?
Check the installed version on the Plugins screen against the latest release; old versions often break after WordPress or PHP updates, and updating usually fixes the problem.
The official WPBakery website lists the current version and changelog.
If you bought WPBakery directly, activate the licence to receive automatic updates.
Without an active licence, the plugin will not offer updates in the dashboard, even if newer versions exist.
Always back up before updating a page builder, since it controls the layout of many pages.
Test the update on a staging copy first if your site has many WPBakery pages.
What if WPBakery came with your theme?
Theme-bundled copies cannot be updated with the theme's licence on their own; update the theme, which ships a newer WPBakery, or buy your own licence for direct updates.
Check the theme's changelog for the bundled WPBakery version.
Some themes offer a separate download of the bundled plugin in their account area, which you can install manually.
If the theme is no longer maintained, plan a move to a supported theme or builder.
Contact the theme developer first, as they may have a fix or a newer bundled version waiting.
Why is the WPBakery editor button missing?
WPBakery's Role Manager controls which user roles and post types can use the builder, so the button disappears when your role or the post type is not enabled.
Go to WPBakery Page Builder > Role Manager and check the settings for your role and post types.
Custom post types must be enabled separately.
Administrators can still lose access if Role Manager settings were changed by another plugin or an import. Review them after migrations.
The WPBakery knowledge base explains the Role Manager options.
How do you find JavaScript conflicts?
Open the browser console on the page where the editor fails, look for red errors and note the plugin or theme file named in them.
Chrome's Console documentation explains how to read these errors.
Script optimisation features that combine or delay JavaScript can break the editor. Exclude admin pages from them.
WPBakery relies on jQuery and its own scripts. Plugins that remove or replace jQuery in the admin area can stop it from working.
Our guide on the edit post white screen covers similar editor-loading problems.
How do you test for plugin conflicts?
Deactivate other plugins on a staging copy, reload the WPBakery editor, then reactivate plugins one by one until it breaks again.
The Health Check and Troubleshooting plugin lets you disable plugins only for your session on a live site.
Popular suspects include other page builders, optimisation plugins and plugins that load their own versions of common scripts.
Running two page builders at once is a common source of conflicts, even if each is used on different pages.
Our guide on fixing plugin conflicts gives a safe testing order.
Could PHP memory be the problem?
Yes. Complex pages with many elements can exceed the PHP memory limit, which stops the editor or the page from loading.
Check the debug log for an allowed memory size exhausted message.
Our guide on enabling debug mode shows how to turn on logging safely.
Our guide on increasing the PHP memory limit shows where to raise it.
Very large pages can also be split into smaller ones for easier editing.
Removing unused elements and hidden rows also reduces memory use and speeds up editing.
Why do pages show raw shortcodes?
WPBakery saves layouts as shortcodes, so if the plugin is deactivated, deleted or fails to load, visitors see raw shortcode text instead of the designed page.
Reactivate WPBakery to restore the layouts immediately.
If the plugin is active but shortcodes still show, a fatal error may stop it loading. Check the debug log.
Our explainer on what a shortcode is explains why this happens.
If you want to stop using WPBakery, plan to rebuild pages before removing it.
Does WPBakery work with the block editor?
WPBakery has its own backend and frontend editors and is often used alongside the classic editor, so check its settings and your theme's recommendations if the block editor and WPBakery clash.
Some sites use the Classic Editor plugin for pages built with WPBakery.
Our guide on going back to the classic editor shows how to switch.
Avoid editing the same page in both the block editor and WPBakery.
Switching editors on one page can mix block markup with shortcodes and break the layout.
What if the frontend editor fails but the backend works?
The frontend editor loads the live page inside the editor, so caching, security headers, mixed HTTP and HTTPS content or redirect rules can block it.
Check that your site URLs match and use HTTPS everywhere.
Mixed content warnings in the browser console are a clear sign that some resources still load over HTTP.
Exclude logged-in users and editor URLs from page caching.
Browser extensions that block frames or scripts can also break the frontend editor. Test in a private window.
If security headers block framing, allow the site to frame its own pages.
How do you reinstall WPBakery safely?
Download a fresh copy from your licence account or theme package, deactivate and delete the old plugin, then upload and activate the new copy; your layouts stay in the content.
Deleting the plugin does not delete pages. Layouts return once it is active again.
Licence activation may need repeating after a reinstall, so keep your licence key at hand.
Keep a backup before reinstalling, as a precaution.
Clear any caches after reinstalling, so browsers load the fresh plugin files.
When should you consider replacing WPBakery?
If your theme is abandoned, updates are no longer available, or performance and editing problems keep returning, it may be time to rebuild with the block editor or another builder.
Plan the move page by page, starting with the most important pages.
Compare the time and cost of rebuilding with the cost of keeping an old builder alive. For large sites, a gradual move spreads the effort.
Keep WPBakery active until every page has been rebuilt, so nothing breaks in the meantime.
Frequently asked questions
Why is my WPBakery editor not loading?
Usually an outdated plugin, a JavaScript conflict or low memory. Update WPBakery, check the browser console for errors and test with other plugins disabled.
Why is the WPBakery button missing from my editor?
Your user role or the post type may not be enabled. Check WPBakery Page Builder, then Role Manager, and enable the right post types.
How do I update WPBakery that came with my theme?
Update the theme, which usually ships with a newer bundled WPBakery, or buy your own WPBakery licence so you can receive plugin updates directly.
Why does my page show WPBakery shortcodes?
WPBakery is inactive, deleted or failing to load. Reactivate or reinstall it to restore your layouts, which are still saved in the content.
Will reinstalling WPBakery delete my pages?
No. Your layouts are stored in the page content as shortcodes, so they display again as soon as WPBakery is installed and active.
Sources
- WPBakery Page Builder WPBakery
- WPBakery Knowledge Base WPBakery
- Console overview Chrome for Developers
- Health Check & Troubleshooting WordPress.org Plugins
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.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


