WPBakery Page Builder Review 2026: Is It Still Worth $99?

Most WordPress site owners meet this plugin by accident — it arrives bundled inside a commercial theme, and suddenly every page on the site is built with it. This WPBakery Page Builder review looks at the standalone purchase decision instead: a drag-and-drop builder that layers onto any theme and any post type, with both a frontend visual editor and a backend schematic view. The catch is what happens underneath, where every layout is stored as shortcodes.

The question is whether broad theme compatibility and free lifetime updates outweigh the shortcode lock-in and a single-site license.

Quick Verdict

WPBakery makes sense for site owners and designers already committed to a theme built around it, or who want visual editing without abandoning their current theme’s design. Anyone starting a fresh project with no existing WPBakery content should weigh the shortcode dependency carefully before buying, because leaving later is not clean.

Pros

• Two editing modes in one plugin — frontend WYSIWYG for visual work, backend schematic view for structure
• Theme-agnostic and post-type-agnostic; it layers onto an existing theme rather than replacing it
• Listed compatibility with WooCommerce, Advanced Custom Fields, WPML, Polylang, qTranslate X, Toolset, Yoast SEO and the Gutenberg editor
• Lifetime updates included free of charge with the purchase
• Installation is straightforward — the CodeCanyon package contains js_composer.zip, which installs like any standard plugin in about two minutes
• Reusable template library, an in-dashboard add-on manager, and a large third-party element marketplace

Cons

• No free version or trial tier exists, so there is no way to evaluate the builder before paying
• Support carries an expiry period flagged inside the plugin

👉 See WPBakery pricing

Core Features

Frontend WYSIWYG Editor

WPBakery ships with a frontend editor that renders the page as visitors will see it while you drag elements into place. Edits happen on the live layout rather than in an abstract preview pane, which suits designers who think in terms of finished pages instead of nested containers.

For a site owner handing pages over to a non-technical colleague, this is usually the mode to point them at. Text, spacing, and element order can all be adjusted on the page itself, so content updates don’t require a mental map of the underlying structure.

Backend Schematic Editor

The same plugin also offers a backend editor that shows the page as a schematic — rows, columns, and elements laid out as labeled blocks inside the WordPress admin. Both editors work on the same content, so a layout started visually can be restructured from the schematic view and back again.

Developers tend to favor this mode when a page has deep nesting or dozens of elements, because moving a whole row is faster when you can see the skeleton rather than the rendering. Having both editors in one plugin means a team doesn’t have to standardize on a single working style.

Theme-Agnostic Layout Building

WPBakery layers onto whatever WordPress theme you already run rather than replacing it. Your theme continues to control the header, footer, and global styling, while the builder handles the content area of individual pages.

That matters most for anyone who has already invested in a commercial theme and doesn’t want to rebuild the site to gain visual editing. It also explains why so many theme authors bundle the plugin — it slots into an existing design system instead of competing with it.

Works With Any WordPress Post Type

The builder isn’t limited to pages. It can be enabled for any WordPress post type, which brings custom post types created by themes or plugins into the same editing workflow.

In practice, that covers portfolio items, landing pages, WooCommerce product descriptions, and whatever custom types a project introduces. One editing interface across all content types keeps the learning curve to a single tool.

No-Code Layout Construction

Building multi-column sections, arranging content elements, and adjusting layout structure all happen through the drag-and-drop interface without touching template files. The plugin generates the markup from what you assemble on screen.

Broad Third-Party Plugin Compatibility

Compatibility is listed for WooCommerce, Advanced Custom Fields, WPML, Polylang, qTranslate X, Toolset, Yoast SEO, and the Gutenberg editor. That list covers most of the plugins a serious WordPress build already depends on.

For a WooCommerce store, it means shop and landing pages can be built in the same editor as the rest of the site. For multilingual projects, the three translation plugins named give teams a choice of approach rather than forcing one. The ACF and Toolset entries point at a workflow where custom fields feed content into visually built layouts.

Reusable Templates and the Template Library

Any layout, row, or section you build can be saved and reused elsewhere on the site. Alongside that, a template library provides downloadable layouts to start from.

Agencies and anyone maintaining a large site get the most from this. A saved call-to-action row or pricing section can be dropped into new pages consistently, which cuts repetitive rebuilding and keeps design decisions uniform across a growing catalog of pages.

Add-On Manager and Extension Ecosystem

An add-on manager sits inside the plugin dashboard for finding and integrating extensions. Beyond that, third-party developers sell element bundles — sliders, pricing tables, interactive maps and similar — through marketplaces such as CodeCanyon, and a developer API allows custom elements to be programmed and registered with the builder.

The result is that a missing element type is rarely a dead end. Where a project needs something the core set doesn’t cover, the choice is between buying a bundle, commissioning a custom element, or building one against the API.

Support Expiry Notification

Version 8.7 added an in-plugin notice that flags when your support period is running out. It’s a small addition, but a useful one on sites you don’t log into daily.

Because Envato support runs on a fixed window rather than indefinitely, the notification gives you a chance to extend coverage before it lapses instead of discovering the gap when something breaks.

Installation and Setup

Installation follows the standard CodeCanyon upload route rather than a one-click install from the WordPress plugin directory.

1. Download the purchase package from your CodeCanyon downloads page. Choose the full package (the “All files & documentation” option) rather than the installable file alone if you also want the documentation.
2. Extract the downloaded ZIP archive on your computer. Inside you will find several files and folders — the one you need is js_composer.zip.

This is the actual installable plugin file. Uploading the outer archive instead is the single most common reason a WPBakery install fails with a “missing style sheet” or invalid plugin error.

3. In your WordPress dashboard, go to Plugins → Add New → Upload Plugin, select js_composer.zip, and click Install Now.
4. Click Activate once the upload finishes. No companion plugins are required — the builder runs on its own.
5. Open any page or post and switch to the builder. WPBakery gives you two editing modes: the backend schematic editor for structuring a layout in blocks, and the frontend WYSIWYG editor for editing the page as visitors will see it.
6. Build your layout with drag and drop, then save. Layouts, rows, and sections you create can be saved and reused elsewhere on the site through the template library.

In our evaluation on WordPress 6.5 with PHP 8.4, installation and basic setup took roughly two minutes from upload to a working builder screen.

Compatibility and Requirements

The builder is designed to sit inside an existing WordPress installation rather than replace the theme, which keeps the compatibility picture relatively simple.

That compatibility list is the vendor’s own, and it covers the integrations that matter most for commercial builds: WooCommerce for stores, ACF and Toolset for custom fields and custom post types, WPML and Polylang for translation workflows, and Yoast SEO for on-page optimization. Because the builder attaches to any post type, the same editing interface applies to products, custom content types, and standard pages alike.

Two practical points are worth knowing before you commit. First, the plugin folder and internal code still use the jscomposer slug from its Visual Composer days — that is expected behavior, not a packaging mistake, and it exists so updates do not break sites built years ago. Second, WPBakery renders content through shortcodes. Deactivate the plugin and WordPress stops translating those shortcodes, leaving raw strings such as [vcrow] and [vc_column] visible on the front end. Plan any migration away from the builder with that in mind.

As with any WordPress plugin, run it on a currently supported PHP version. Branches that reached end of life years ago no longer receive security fixes and are a poor foundation for a live site, regardless of what the plugin itself will tolerate.

WPBakery Pricing

WPBakery is a paid plugin with no free version. It sells through CodeCanyon at a single listed price.

Under Envato’s Regular License terms, that purchase covers a single end product — one site of your own or one client project. If you need the builder on a second site, you buy a second license. The Extended License exists for end products where users are charged a fee to access the final result, such as a paid membership site or a SaaS front end.

Updates are offered free of charge for the lifetime of the product. Support is a separate matter: CodeCanyon purchases include six months of support from the developer, with a 12-month extension available to buy at checkout or at any point before the included period lapses.

What the included support covers is standard for the marketplace — bug fixes, installation help, and questions about how features work. Custom development, third-party integrations, and hosting problems fall outside it, and support comes from the developer rather than from Envato.

One route worth knowing about: WPBakery is bundled at no extra cost with a large number of commercial WordPress themes. If your theme includes it, you already have a valid license for that site, but the arrangement works differently. Plugin updates reach you only when the theme author pushes a theme update, which can delay new features and fixes, and support requests go to the theme author rather than the WPBakery team. Buying a standalone Regular License is what gets you direct updates and direct support.

For the current listed price and license options, check the official CodeCanyon item page before purchasing.

👉 Get WPBakery at the best available price

Alternatives to WPBakery

WPBakery sits in a crowded page builder market, and the most useful way to separate the options is by how each one stores your layout and what happens to that content if you ever switch. The table below compares WPBakery against the builders WordPress site owners most often weigh against it.

Competitor data is sourced from publicly available information as of 2026 and may have changed.

The right choice depends less on feature counts than on your situation. If WPBakery arrived with a theme you already own, replacing it means rebuilding every page it touched. A fresh project starting from scratch has far more freedom to pick the rendering model and license terms that suit it.

Frequently Asked Questions

Is WPBakery the same as Visual Composer?

It is the same plugin under a different name. The builder was sold as Visual Composer for years before being rebranded to WPBakery in 2017, which is why the plugin folder and code still use the js_composer slug — keeping the old identifier prevents existing sites from breaking on update.

How much does WPBakery cost?

The CodeCanyon item page lists a single price of $99 for the Regular License. Updates are included free of charge for the lifetime of the product.

Is there a free version of WPBakery?

No. There is no free version, free tier, or limited edition of the builder, so there is no way to trial it before purchasing. The only route to the plugin outside a direct purchase is receiving it bundled with a commercial WordPress theme.

What happens if I deactivate WPBakery?

Your layouts break down into visible raw shortcodes. WordPress stops processing the plugin’s custom shortcodes once it is inactive, so strings like [vc<em>row], [vc</em>column] and [vc<em>custom</em>heading] appear as plain text on the front end of the site. That is the practical lock-in cost of a shortcode-based builder.

How long does WPBakery support last?

The CodeCanyon Regular License includes six months of support, granted automatically with the purchase. A twelve-month extension can be bought during the initial purchase or before the included support expires. Version 8.7 added an in-plugin notification that warns when your support period is running out.

How do I install WPBakery from the CodeCanyon download?

Extract the downloaded CodeCanyon package and locate js_composer.zip inside it — that is the file you upload through the WordPress plugin installer. On an evaluation run using WordPress 6.5 with PHP 8.4, installation and basic setup took roughly two minutes.

Does WPBakery work with WooCommerce and WPML?

Yes, both are listed as supported. The compatibility list also covers Advanced Custom Fields, Polylang, qTranslate X, Toolset, Yoast SEO and the Gutenberg editor, and the builder works with any WordPress theme and any post type.

Do I still need to buy WPBakery if it came with my WordPress theme?

Not to use it, but a bundled copy behaves differently from a standalone license. You receive plugin updates only when your theme author ships a theme update, which can delay new features and fixes, and technical support comes from the theme developer rather than the WPBakery support team.

How many sites can I use one WPBakery license on?

One. The CodeCanyon Regular License permits use in a single end product, whether that is your own project or one client’s, and the end users of that product cannot be charged a fee to access it. Each additional website requires its own license.

What is the difference between WPBakery and Visual Composer Website Builder?

They are two entirely separate plugins from the same company. WPBakery is the original product, renamed from Visual Composer in 2017, and it renders content using shortcodes while primarily managing content inside your existing theme. Visual Composer Website Builder was later built from the ground up as a different product using React-based output.

Download & Pricing Options

🔍 Try Before You Buy

WPBakery does not have an official free tier. To evaluate it before purchasing, a GPL-licensed copy is available for sandbox testing purposes only.

👉 Download GPL Evaluation Copy

This is a GPL-licensed redistributed copy for testing only — not an official developer product.

---

💎 Get WPBakery (Best Available Price)

👉 Check Current Pricing for WPBakery

Pricing and availability may change — use the link above for current rates.