Plugin how-tos · Guide
How to Remove WPBakery Page Builder (Step by Step)

Short answer
Back up the site, find every page that uses WPBakery, rebuild or convert those pages, then deactivate and delete the plugin from the Plugins screen. Finally strip leftover vc_row shortcodes and clean old settings, or pages will show raw shortcode text.
Key takeaways
- Deleting WPBakery leaves raw shortcodes on your pages.
- Back up and work on a staging copy first.
- Search for vc_row to find every page built with it.
- Check whether your theme depends on WPBakery.
- Rebuild key pages and strip shortcodes from minor ones.
- Leftover settings in the database are harmless but can be tidied.
How do you remove WPBakery Page Builder?
Back up the site, rebuild or convert every page that uses WPBakery, then deactivate and delete the plugin from Plugins > Installed Plugins, and finally clean up the leftover shortcodes and settings it leaves behind.
Deleting the plugin is the easy part. The hard part is the content it created.
WPBakery stores layouts as shortcodes inside your post content, such as [vc_row] and [vc_column]. When the plugin is gone, those tags show up as plain text on your pages.
This guide walks through a safe removal from start to finish. If you plan to move to Elementor, our guide on converting WPBakery to Elementor covers that route in detail.
What happens if you just delete WPBakery?
If you delete WPBakery without cleaning up, every page built with it shows raw shortcode text, loses its columns and styling, and may look broken to visitors and search engines.
You will see text like [vc_row][vc_column][vc_column_text] wrapped around your content. Images, buttons and other elements built with WPBakery widgets may disappear or show as code.
Your actual text usually survives inside the shortcodes. That makes cleanup possible, but it still needs work.
| Item | Where WPBakery stores it | What happens after deletion |
|---|---|---|
| Page layouts | Shortcodes in post content | Shown as plain text |
| Custom CSS per page | Post meta fields | Ignored, styles lost |
| Saved templates | Options and custom post types | Left in the database |
| Plugin settings | Options in the database | Left in the database |
| Theme add-ons | Theme or add-on plugin files | May break or show errors |
Understanding this table helps you plan. Content needs rebuilding, while settings just need tidying.
Should you back up the site first?
Yes, take a full backup of files and the database before you start, because removing a page builder changes many pages at once and mistakes are hard to undo by hand.
A full backup lets you restore the site in minutes if something goes wrong. Our guide on how to back up a WordPress site covers plugin and host options.
Better still, do the whole job on a staging copy first. You can rebuild pages there without affecting visitors, then push the finished site live.
Our guide on setting up a staging site for WordPress explains how.
How do you find every page that uses WPBakery?
Search your posts, pages and other post types for the vc_row shortcode, because almost every WPBakery layout starts with it.
You can do this in a few ways:
- Use the search box on Pages and Posts screens and search for vc_row.
- Use a search and replace plugin in dry-run mode to count matches.
- Run a database query or a WP-CLI command if you have server access.
Do not forget custom post types, such as portfolio items, products or team members. Themes often use WPBakery in these too.
Make a list of every page you find. Sort it by importance, so key pages such as the home page, service pages and top blog posts are rebuilt first.
Does your theme depend on WPBakery?
Check whether your theme bundles WPBakery or adds its own WPBakery elements, because removing the builder can break theme features and layouts that rely on it.
Many premium themes include WPBakery and add extra elements to it. Those elements often stop working without the builder.
Look in your theme's documentation for a list of required plugins. If WPBakery is required, removing it is usually part of a larger move to a new theme.
If you are changing themes anyway, our guide on what the WordPress block editor is explains the editor most modern themes are built around.
How do you rebuild pages without WPBakery?
Rebuild each page in the block editor or your new page builder, copying text and images from the old layout, then remove the old WPBakery content.
A practical method for each page:
- Open the page in the WPBakery backend editor and take a screenshot of the front end.
- Copy the text and note the images used.
- Switch the page to the block editor or your new builder.
- Recreate the layout using columns, groups or your builder's sections.
- Paste text, add images and check headings.
- Preview on desktop and mobile, then update.
Rebuilding is slow, but it gives you clean content with no leftover shortcodes. It is also a good chance to update old content.
Important pages deserve a careful rebuild. For low-value posts, a quick shortcode strip may be enough.
How do you strip leftover shortcodes?
For pages you do not want to rebuild, remove the WPBakery shortcode tags while keeping the text inside them, using a cleanup plugin or a careful regular-expression search and replace.
Plugins in the WordPress directory can help, such as Editor Cleanup for WPBakery. Check its reviews and latest update date before using it, and test it on staging.
If you are comfortable with the command line, WP-CLI's search-replace command supports regular expressions. Always run it with the dry-run option first to see what would change. The WP-CLI site explains how to install the tool if your host does not include it.
A pattern that removes opening and closing vc_ tags but keeps the text between them is the usual approach. Test it on a few posts before running it across the whole site.
Stripping tags leaves plain text with no columns. Review each page afterwards and fix spacing, headings and images.
Our explainer on what a shortcode is in WordPress helps if you are new to shortcode syntax.
How do you deactivate and delete the plugin?
Once your content no longer depends on WPBakery, go to Plugins > Installed Plugins, click Deactivate under WPBakery Page Builder, then click Delete and confirm.
Before deleting, switch off any WPBakery add-on plugins too. Add-ons that depend on WPBakery may show errors once it is gone.
If the dashboard will not load after deactivation, rename the plugin folder over FTP to disable it. Our guide on uninstalling broken plugins explains that method.
The plugin's official site at wpbakery.com also covers licence deactivation. Deregister your licence first if you want to use it on another site.
What leftover data stays in the database?
WPBakery leaves settings, saved templates and per-page custom CSS in the database after deletion, which does no harm but adds clutter you can remove once the site is stable.
Settings are stored as options, usually with names that start with wpb_js. Per-page custom CSS is stored in post meta fields linked to each page.
You can remove these with a database cleanup plugin or a careful query in phpMyAdmin. Take a fresh backup first, because database edits cannot be undone.
If you are not confident editing the database, leave the leftovers in place. They are small and do not load on the front end.
How do you check the site after removal?
Visit every important page logged out, search the site for any remaining vc_ text, check forms, menus and mobile layouts, and fix broken links or images.
Use your list of pages from earlier. Tick each one off as you check it.
Run a site search for vc_ in post content again. Any match is a page that still needs cleaning.
Clear all caches before checking. Cached pages may still show the old layout even though the content has changed.
Will removing WPBakery make your site faster?
Often yes, because WPBakery loads its own CSS and JavaScript on pages that use it, but the real gain depends on what you replace it with and how your theme loads assets.
Moving to lightweight blocks usually cuts page size. Moving to another heavy builder may not change much.
Our guide on whether WPBakery slows down a site looks at its impact in more detail.
Measure speed before and after the change. That way you know whether the work paid off.
Frequently asked questions
Will I lose my content if I remove WPBakery?
Your text usually survives inside the shortcode tags, but layouts, columns, styling and some elements are lost. Pages will show raw shortcode text until you rebuild them or strip the tags, so plan the cleanup before deleting the plugin.
Can I remove WPBakery without rebuilding every page?
Yes. You can strip the shortcode tags and keep the text, which turns pages into simple single-column content. This is fine for minor posts, but important pages usually need a proper rebuild to look good.
Is WPBakery bundled with my theme?
Many premium themes bundle WPBakery and list it as a required plugin. Check your theme's documentation or its plugin installation screen. If the theme depends on it, removing WPBakery may break theme features.
How long does it take to remove WPBakery?
It depends on how many pages use it. A small site with a few pages can be done in an afternoon, while large sites with hundreds of WPBakery posts may need days of rebuilding or a careful bulk shortcode cleanup.
Should I deactivate my WPBakery licence before deleting it?
Yes, if you want to use the licence on another site. Deregister it from the plugin's settings or your WPBakery account first, then deactivate and delete the plugin.
Sources
- WPBakery Page Builder WPBakery
- wp search-replace WordPress Developer Resources
- Editor Cleanup for WPBakery WordPress.org Plugin Directory
- Shortcode API 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.
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.


