Plugin how-tos · Explainer
What Is Js Composer WordPress Plugin? Explained

Short answer
js_composer is the internal folder and code name of WPBakery Page Builder, a premium drag-and-drop page builder for WordPress. The name comes from its original title, Visual Composer. It builds layouts with shortcodes and is often bundled with premium themes.
Key takeaways
- js_composer is WPBakery Page Builder, formerly called Visual Composer.
- It stores layouts as vc_ shortcodes inside post content.
- It is a premium plugin, but many themes bundle a copy.
- Bundled copies only update when the theme author ships an update.
- Outdated or unused copies are a security risk, so update or delete them.
What is the js_composer WordPress plugin?
The js_composer plugin is WPBakery Page Builder, a drag-and-drop page builder for WordPress; js_composer is simply the name of its plugin folder and code, left over from its original name, Visual Composer.
If you see js_composer in your plugins folder, in an error message or in a security report, it refers to WPBakery. It is not a separate JavaScript library or a hidden system file.
The plugin lets you build page layouts with rows, columns and content elements without writing HTML. It has been one of the most widely bundled page builders in premium themes for years.
Why is it called js_composer?
The plugin was first sold as Visual Composer, and its developers kept the original internal folder name js_composer after the product was renamed WPBakery Page Builder.
Changing a plugin's folder name breaks updates and existing sites, so developers rarely do it. That is why the old name lives on in file paths such as wp-content/plugins/js_composer/.
The rename happened in late 2017. The original team then launched a different product called Visual Composer Website Builder, which is not the same plugin. A SitePoint article on the name change tells the full story.
| Name you see | What it means |
|---|---|
| js_composer | Folder and code name of WPBakery Page Builder |
| WPBakery Page Builder | Current product name of that plugin |
| Visual Composer (old) | Former name of WPBakery, used until 2017 |
| Visual Composer Website Builder | A separate, newer builder from the original team |
| vc_ shortcodes | Shortcodes WPBakery uses, such as vc_row |
What does WPBakery Page Builder do?
WPBakery lets you design pages visually with drag-and-drop rows, columns and elements, using either a backend editor inside the WordPress admin or a frontend editor on the live page.
Its core features include:
- A backend editor that shows the page as blocks of elements
- A frontend editor that lets you edit the page as it looks to visitors
- Dozens of built-in elements, such as text, images, buttons, tabs and accordions
- Responsive controls to adjust columns on tablets and phones
- A template library for saving and reusing layouts
- Add-ons from third parties that add more elements
Our walkthrough on how to use WPBakery Page Builder shows these features step by step.
How does js_composer store page content?
WPBakery saves layouts as shortcodes inside the normal post content, so a page is stored as text like [vc_row][vc_column]...[/vc_column][/vc_row] rather than as separate layout data.
This approach has one big consequence. If you deactivate the plugin, WordPress no longer understands those shortcodes, so your pages show raw bracketed text instead of the design.
The content is not lost. It is simply no longer rendered. Reactivating the plugin brings the layout back.
WordPress explains how shortcodes work in its Shortcode API documentation. If you see broken brackets after an update, our guide to WPBakery shortcodes not working covers the fixes.
Is js_composer free?
No, WPBakery Page Builder is a premium plugin sold with a license, although many people get a copy for free because it comes bundled with a premium theme.
The plugin is sold through WPBakery's own site and has long been available on Envato's CodeCanyon marketplace. A direct license gives you automatic updates, support and access to the template library.
A bundled copy works differently. The theme author includes the plugin, and you get updates when the theme author ships them, usually as part of a theme update.
That means a bundled js_composer can fall behind the latest release. If you need the newest version right away, you may need your own license. Check WPBakery's FAQ for current license terms and prices.
Why do themes bundle js_composer?
Theme authors bundle WPBakery so buyers get a visual page builder and ready-made demo layouts out of the box, without needing to buy or configure another tool.
Many multipurpose themes built their demo content on WPBakery. Their custom elements, such as portfolio grids or pricing tables, often plug into the WPBakery editor.
The downside is lock-in. Pages built with a theme's custom WPBakery elements depend on both the theme and the plugin.
Switching themes later can leave you with leftover shortcodes and broken layouts. Plan for that before you commit.
Is js_composer safe to use?
WPBakery is safe when kept up to date, but like any popular plugin it has had security issues in the past, so outdated copies, especially stale bundled ones, are a real risk.
Attackers scan for old plugin versions with known flaws. A forgotten bundled js_composer folder is a common target.
Keep it safe with a few habits:
- Update WPBakery whenever a new version is available, either directly or through the theme
- Delete the plugin folder completely if you no longer use it
- Watch security advisories for the plugin
- Use a security plugin that warns about vulnerable versions
If you cannot update a bundled copy, ask the theme author for the latest package. Our guide on updating WPBakery manually shows how to replace the files safely.
Does js_composer slow down a website?
WPBakery adds its own CSS, JavaScript and nested markup to pages, which can make them heavier than pages built with the block editor, though caching and careful design limit the impact.
Each row and column creates extra wrapper elements. Pages with many nested rows produce more HTML for browsers to process.
Speed tools such as PageSpeed Insights can show how much the builder adds. Our explainer on whether WPBakery slows down a site looks at this in more detail.
For most small sites, a good host, a caching plugin and optimised images matter more than the builder choice.
Should I keep using js_composer or switch?
Keep it if your site works, stays updated and you are comfortable with it; consider switching when you redesign, because moving away means rebuilding pages that rely on its shortcodes.
There is no urgent reason to drop WPBakery on a healthy site. Rebuilding a large site takes real time.
Switching makes sense when:
- You are redesigning the site anyway
- You want to move to a block theme and the WordPress block editor
- Your theme is abandoned and its bundled WPBakery no longer updates
- You need features your current setup cannot provide
If you decide to move, our guide on converting WPBakery to Elementor covers the rebuild process.
Once the new pages are live, follow the steps for removing WPBakery Page Builder and cleaning up leftover shortcodes.
How do I check which version of js_composer I have?
Go to Plugins > Installed Plugins and find WPBakery Page Builder; the version number appears under its name, and the folder on the server is wp-content/plugins/js_composer.
If the plugin does not appear in the list but the folder exists, it may be installed as a must-use plugin or loaded by the theme. Check the theme documentation in that case.
You can also see the version in the WPBakery settings screen in the admin menu, depending on your version.
Compare it with the latest version listed on WPBakery's changelog. A large gap is a good signal to update.
What should I do if js_composer causes errors?
Most js_composer errors come from an outdated copy, a clash with the theme or another plugin, or a PHP version the plugin does not support, so update first and then test for conflicts.
Common symptoms include a blank editor, missing backend editor tabs, or a page that shows only shortcodes.
Work through these checks:
- Update WPBakery, the theme and WordPress.
- Switch on WordPress debug mode to see the actual error.
- Deactivate other plugins to find a conflict.
- Confirm your PHP version is supported by your WPBakery version.
If the editor itself is missing, see our guide to the WPBakery backend editor not showing.
For broader failures, the WPBakery not working guide covers the most frequent problems and their fixes.
Frequently asked questions
Is js_composer the same as Visual Composer?
js_composer is the plugin that used to be called Visual Composer and is now WPBakery Page Builder. The newer product called Visual Composer Website Builder is a different plugin from the original team and does not use the same code.
Can I delete the js_composer folder?
Only if no page on your site uses WPBakery. Deleting it on a site that does will leave raw shortcodes on those pages. If you have moved to another builder and cleaned up the shortcodes, deleting the folder is a good security step.
Why does my security scanner mention js_composer?
Scanners flag js_composer when the installed WPBakery version has a known vulnerability or is out of date. Update the plugin, or ask your theme author for a newer bundled copy, then scan again to confirm the warning is gone.
Do I need a license if my theme included js_composer?
You can use a bundled copy under the theme's license, but direct updates, support and the template library usually require your own WPBakery license. Updates for the bundled copy come through theme updates instead.
Does js_composer work with the block editor?
WPBakery replaces the default editing experience on pages where you use it. You can choose which post types use WPBakery in its settings, and keep the block editor for others, but mixing both on one page is not practical.
Sources
- WPBakery Page Builder Knowledge Base WPBakery
- WPBakery FAQ WPBakery
- Shortcode API WordPress Developer Resources
- Visual Composer: The Brain-Twisting Story of the Name Change SitePoint
- 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.
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.


