Troubleshooting
WPBakery Shortcodes Not Working: Causes and How to Fix It

Short answer
WPBakery shortcodes show as raw text when WPBakery or an add-on that defines them is inactive, the theme that bundled them was switched, or a template prints content without running shortcodes. Reactivate the right plugin or theme, update it, and make templates use the content filter.
Key takeaways
- Raw vc_ shortcodes mean WordPress does not recognize WPBakery's elements.
- Your content is safe; the layout returns when the right plugin is active.
- Theme switches often remove theme-specific elements.
- Only some elements raw points to a missing add-on.
- Custom templates must run content through the_content filter.
- Back up before stripping leftover shortcodes in bulk.
Why are WPBakery shortcodes not working?
WPBakery shortcodes show as raw text when WPBakery or an add-on that defines them is inactive, the theme that bundled them was switched, or a template outputs content without processing shortcodes.
WPBakery Page Builder saves layouts as shortcodes inside the post content. A page might contain [vc_row][vc_column][vc_column_text] and so on. WPBakery turns those into HTML when the page loads.
If WordPress does not know a shortcode, it prints it as plain text. That is why you suddenly see brackets all over a page.
This guide works through each cause in order of how often it happens. Fix one thing at a time and check the page after each change, so you know what actually solved it.
If shortcodes in general are new to you, read what is a shortcode in WordPress first.
The good news is your content is still there. Once the right plugin is active again, the layout returns. For wider WPBakery issues, see WPBakery page builder not working.
What do the symptoms tell you?
Which shortcodes appear raw, and where, usually points straight to the cause.
| What you see | Likely cause |
|---|---|
All [vc_...] shortcodes raw on every page | WPBakery inactive or removed |
| Only some elements raw, others fine | An add-on plugin or theme element is missing |
| Raw shortcodes after changing theme | The old theme bundled WPBakery or its elements |
| Raw shortcodes in excerpts or archives | Template does not process shortcodes |
| Raw shortcodes in a custom template or AJAX load | Content output without the content filter |
| Layout renders but styling is missing | Custom CSS not loaded or cached files stale |
Check one affected page and one working page side by side. Note which shortcode names appear, since the prefix often names the plugin that should handle it.
Is WPBakery active and up to date?
Go to Plugins > Installed Plugins and make sure WPBakery Page Builder is installed, active and current, because every vc_ shortcode depends on it.
Plugins can be deactivated by a failed update, a host security tool, or someone tidying up the plugin list. Reactivate it and reload the page.
Many themes bundle WPBakery and install it through a theme plugin installer. Those bundled copies update through the theme, not directly. If the theme is old, the bundled WPBakery may be too old for your WordPress version.
Check the WPBakery knowledge base for compatibility notes. If you bought a direct license from WPBakery, activate it under the WPBakery settings to get updates.
Did you switch themes?
Changing theme is a top cause, because many themes supply WPBakery and their own custom elements, which vanish when the theme is no longer active.
Theme-made elements often use a prefix such as the theme name, for example [themename_button]. Those are not WPBakery elements at all. They belong to the theme or its companion plugin.
Options:
- Switch back temporarily to confirm the theme is the cause.
- Install the theme's companion plugin if it has one, which sometimes keeps elements working with another theme.
- Rebuild affected sections with core WPBakery elements before switching.
- Convert to another builder, if you are leaving WPBakery for good.
Plan theme changes on a staging site so you see these problems before visitors do. Our staging site guide shows how to make one.
Before switching, search your content for the old theme's prefix. That tells you how many pages will need work.
Is an add-on plugin missing?
If only certain elements show raw shortcodes, the plugin that created them is probably inactive, removed or outdated.
WPBakery has many add-on packs that add extra elements. Each add-on registers its own shortcodes. When the add-on is off, its elements print as text while core vc_ elements still work.
Look at the shortcode name, search your plugin list for a matching name, and reactivate or reinstall it. If the add-on is abandoned, replace each element with a core one.
Is a template printing content without processing shortcodes?
Yes, custom templates that use get_the_content() or read raw post content skip WordPress's content filter, so shortcodes are never converted.
Normal theme templates call the_content(), which runs the the_content filter. That filter calls do_shortcode. A custom loop that echoes raw content does not.
The fix in a custom template is to run the content through the filter:
<?php
echo apply_filters( 'the_content', get_the_content() );
?>
The developer reference for do_shortcode explains how processing works.
The plugin handbook's Shortcode API page shows how shortcodes are registered. Make these changes in a child theme so updates do not undo them.
Our guide on do_shortcode not working covers more developer cases.
Why do shortcodes show in excerpts and archives?
Excerpts strip registered shortcodes but not unknown ones, and some themes build excerpts in ways that leave WPBakery markup behind.
If your blog listing shows bits of [vc_row] text, you have two simple fixes:
- Write a manual excerpt for each post in the Excerpt box.
- Use a theme or plugin setting that builds excerpts from clean text.
If raw shortcodes appear only on archive pages but not single posts, the archive template is the cause, not WPBakery.
Are shortcodes missing when content loads with AJAX?
Content loaded by AJAX, the REST API or some page builder modules may show raw WPBakery shortcodes, because WPBakery does not always register its elements in those requests.
This often happens with load-more buttons, infinite scroll, AJAX tabs or popups from other plugins.
Fixes include:
- Load that content normally instead of by AJAX, if the plugin allows it.
- Ask the theme or plugin developer whether they support WPBakery content.
- Developers can make sure WPBakery's shortcodes are registered in the AJAX request before running
do_shortcode.
WPBakery's developer documentation on its knowledge base covers how elements are mapped.
Could a plugin conflict be the cause?
Yes, a plugin that changes the content filter or breaks PHP execution can stop WPBakery from rendering, so test with other plugins disabled.
Use a staging site, or the Health Check & Troubleshooting plugin, to disable everything except WPBakery and the theme. If the layout returns, reactivate plugins one at a time.
Caching can also keep old broken pages alive after you fix the cause. Clear your cache plugin, host cache and CDN after each change. Our plugin conflict guide has the full method.
How do you remove leftover shortcodes for good?
If you no longer use WPBakery, convert pages to another builder or the block editor, or clean the shortcodes with a search-and-replace tool after a full backup.
Leftover shortcodes are common after leaving a page builder. You have a few choices:
- Rebuild key pages in your new builder. This gives the cleanest result.
- Use a conversion tool if one suits your content. Our guide on converting WPBakery to Elementor covers this route.
- Strip shortcodes in bulk with a database search and replace that removes
[vc_...]tags while keeping text.
Bulk cleaning is risky. Test it on staging, back up first, and check several pages before running it on the live site.
If you are staying with WPBakery, our guide on using WPBakery Page Builder covers good habits that make problems like this less likely.
Frequently asked questions
Why does my page show [vc_row] text?
WordPress prints shortcodes as plain text when no plugin has registered them. For vc_row and other vc_ shortcodes, WPBakery Page Builder is usually inactive, removed or broken. Reactivate or reinstall it and clear your caches.
Will I lose content if WPBakery is deactivated?
No. Your text, images and layout settings are still saved inside the shortcodes in the post content. When WPBakery is active again, the layout renders as before. Only the display is affected while it is off.
Why do only some WPBakery elements show as shortcodes?
Those elements come from an add-on plugin or your theme, not core WPBakery. When that add-on or theme is inactive, its elements print as raw shortcodes. Check the shortcode prefix to identify the source.
How do I remove WPBakery shortcodes after switching builders?
Rebuild important pages in the new builder, use a conversion tool, or strip the shortcodes with a careful database search and replace. Always back up and test on staging first, because bulk edits are hard to undo.
Can caching cause raw WPBakery shortcodes?
Caching does not create the problem, but it can keep serving a broken version after you fix it. Clear your cache plugin, host cache and CDN after reactivating plugins, then check the page in a private window.
Sources
- WPBakery Knowledge Base WPBakery
- do_shortcode() WordPress Developer Resources
- Shortcodes WordPress Plugin Handbook
- Health Check & Troubleshooting WordPress.org
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.


