Is WPBakery dead in 2026? An honest assessment

01The honest status: faded, not finished

Let's answer the headline question plainly, because the internet loves to declare tools dead the moment they stop being fashionable. WPBakery Page Builder — the tool most people still call Visual Composer — is not dead in the literal sense. It still exists, it still runs, and its makers still ship updates to keep it compatible with current WordPress versions. If you go looking, you'll find a maintained product, not an abandoned one.

So when people ask "is WPBakery dead?", what they're really sensing is something softer and harder to pin down: momentum. And on that score, the honest answer is that WPBakery's momentum has faded badly. It is no longer where the WordPress ecosystem's energy, attention, or new development is pointed.

Two forces did most of that. Elementor arrived with a slicker, more modern visual builder and rapidly became the default name people reached for. Then WordPress itself shipped the native block editor (Gutenberg) and, later, full block themes — moving real layout power into core, where it doesn't depend on any plugin at all.

Against those two, WPBakery's share of new builds, tutorials, and excited chatter shrank. That's the accurate frame: not a shutdown, but a tool that's been quietly overtaken and now sits well outside the spotlight. Faded, not finished — and the distinction matters for what you should actually do about it.

02Why it feels "dead" to so many people

If WPBakery is still maintained, why do so many owners describe it as dead? Because the lived experience of using it in 2026 feels that way, even when the changelog says otherwise. A few specific frustrations show up over and over, and together they explain the gap between "technically maintained" and "feels abandoned."

The reasons it feels stuck

• You probably inherited it. Most WPBakery users never chose it — it came bundled inside a multipurpose ThemeForest theme they bought years ago. When a tool arrives by accident rather than by decision, it's easy to resent it the moment it gets in your way.
• Shortcode-soup lock-in. WPBakery stores your layouts as shortcodes baked into your content. That's invisible while it's running, but it quietly tethers your content to the plugin, and you feel the weight of that lock-in the instant you think about leaving.
• A dated editing experience. Next to Elementor's fluid frontend canvas or the native block editor, WPBakery's interface — especially the older backend grid view — feels a generation behind. Clunky day-to-day editing reads as "abandoned" even when it isn't.
• Nobody's recommending it. New tutorials, theme launches, and community buzz point elsewhere. When the whole ecosystem stops talking about a tool, it starts to feel like a ghost regardless of its release notes.

Put those together and you get the real meaning behind "WPBakery is dead." It's not a claim about the plugin's servers being switched off. It's a fair description of how it feels to be stuck on a builder the rest of WordPress has moved past.

03Who's still perfectly fine on it

Here's the part the "it's dead, run!" takes skip: plenty of WPBakery sites are completely fine, and their owners have no real reason to panic. A faded builder is not a broken one, and trend energy is not the same as whether your site works.

If you have an existing site built on WPBakery that loads, converts, and does its job — and you're not personally frustrated editing it — then nothing urgent is happening to you. The plugin still receives compatibility updates, so it isn't going to spontaneously break on the next WordPress release. "Out of fashion" and "out of service" are very different states.

• Stable, working sites where you rarely touch the layout and the pages perform fine as they are.
• Sites you don't plan to redesign soon — if you're not rebuilding anyway, forcing a migration just to chase a trend buys you little.
• Owners comfortable with the editor who know WPBakery's quirks and aren't fighting it day to day.

The honest guidance is to make this a deliberate decision, not a panic. If WPBakery is serving you, you're allowed to keep using it. The case for moving gets much stronger the moment you're starting something new — which is the next, and more important, distinction.

04Why you wouldn't start a new site on it

"Keep your working site" and "build your next one here" are completely different questions, and they deserve different answers. Tolerating a faded tool you already depend on is reasonable. Choosing that same faded tool for a brand-new project in 2026 is the part that's genuinely hard to justify.

When you start fresh, you have zero lock-in and a clean choice. Picking WPBakery means voluntarily signing up for shortcode lock-in from day one, an editing experience that already feels dated, and a tool the ecosystem's momentum has moved away from. You'd be opting into the exact problems other owners are trying to escape.

And the alternatives for a new build are simply better positioned. The native block editor on a block theme keeps your content in WordPress itself with no plugin lock-in. Elementor gives you a modern visual builder with a huge ecosystem. Bricks gives you visual control with lean output. All three are where new development and community energy actually live.

So the split is clean: an existing WPBakery site can be perfectly fine, but a new one is hard to defend. Why start a project already carrying the lock-in and the dated feel you'd eventually want to leave? For new builds, look at the modern options instead — we cover them in our roundup of the best WPBakery alternatives.

05The migration reality: shortcodes mean a rebuild

If you do decide to leave WPBakery, set your expectations honestly up front: this is a rebuild, not a one-click swap. The reason is the same shortcode lock-in that makes the builder feel like a trap. Your layouts aren't stored as portable content — they're stored as WPBakery shortcodes baked directly into your posts and pages.

There's no reliable magic button that cleanly converts [vc_row] markup into native blocks, into Elementor, or into Bricks. In practice, migrating means rebuilding your important pages in the new tool. It's also why you can't just deactivate WPBakery and walk away — turn it off without rebuilding and your pages fill with visible raw shortcode brackets, the literal "shortcode soup" that gives this builder its bad name.

Treat it as a project

• Inventory what matters. List the pages that actually drive traffic or revenue and rebuild those carefully. Thin or dead pages may not be worth carrying over.
• Work on a staging copy. Never rebuild on the live site — stand up staging, rebuild there, and push only when it's right. A good managed host makes this a one-click affair.
• Protect your SEO. Keep URLs, headings, and on-page content intact so a redesign doesn't quietly cost you rankings.
• Sweep the debris. Once WPBakery is off, hunt down orphaned [vc_*] shortcodes and unstyled fallbacks so nothing broken ships to visitors.

None of this should scare you off leaving — it should just stop you from underestimating the job. Budget the time honestly, and lean on a proper switch-without-losing-rankings process. We treat that as its own discipline in our migration guides.

06The modern alternatives, briefly

If your read is that WPBakery has run its course for you, the good news is that the options that replaced it in the spotlight are genuinely better fits for a 2026 site. Three are worth knowing, each suiting a different reason for leaving. We go deeper on all of them in the full alternatives roundup; here's the short version.

• Native block editor + a block theme (Kadence, GeneratePress, Blocksy) — the lightest, most future-proof move. Your content lives in WordPress itself, not in shortcodes, which is the direct cure for the lock-in. Best if your grievance is weight and being trapped.
• Elementor — the modern visual builder. If you like working in a drag-and-drop canvas and just want a polished, well-supported one, this is the obvious step up from WPBakery's dated interface.
• Bricks — the performance pick. A full theme-plus-builder built for lean, clean output, for owners who want strong visual control but treat page weight as non-negotiable.

One lever people forget: hosting moves real-world speed as much as your builder choice does. A lean setup on a slow server still feels slow, and the dynamic pages that can't be fully cached are where a weak host shows up most. We point owners toward managed WordPress hosting built for this — like Cloudways — rather than the cheapest shared plan, because the host and the builder are two separate levers and a fast site needs both.

None of this is financial or investment advice — it's our operating opinion from building and maintaining WordPress sites. Test changes on a staging copy, measure your own Core Web Vitals before and after, and let your real numbers decide.

07FAQ

Is WPBakery actually dead or discontinued?

No. WPBakery Page Builder still exists, still works, and still receives compatibility updates — it has not been shut down or formally discontinued. When people call it "dead," they mean its momentum has faded: the WordPress ecosystem's energy moved to Elementor and the native block editor, so WPBakery feels overtaken rather than switched off.

Do I need to move off WPBakery right now?

Not if your existing site works and you're not frustrated using it. WPBakery still gets compatibility updates, so it won't spontaneously break on the next WordPress release. The strongest reason to move is when you're starting a new project or planning a redesign anyway — then choosing a more modern, less locked-in tool makes clear sense.

Why does my WPBakery site feel so dated?

Mostly because newer builders raised the bar. Elementor's fluid frontend canvas and the native block editor feel more modern than WPBakery's older interface, and because WPBakery usually came bundled with an aging ThemeForest theme, the theme and builder feel dated together. The plugin being maintained doesn't change that day-to-day experience.

Is it hard to switch away from WPBakery?

Harder than most builders, because your layouts are stored as shortcodes inside your content. There's no clean one-click converter, so migrating means rebuilding your important pages in the new tool rather than swapping plugins. Treat it as a project: inventory the pages that matter, rebuild on a staging copy, and keep URLs and content intact to protect rankings.

What should I use instead of WPBakery?

For the lightest, most future-proof setup, the native block editor on a block theme like Kadence, GeneratePress, or Blocksy — it keeps your content out of shortcodes entirely. If you want to stay in a visual builder, Elementor is the modern all-rounder and Bricks is the performance pick. Our full WPBakery alternatives guide compares them in depth.