Which Builder Uses [vc_column]? The Shortcode Origin Explained

If you've ever peeked inside a WordPress page's source code or classic text editor and spotted [vc_column], you're looking at a shortcode from WPBakery Page Builder — one of the oldest and most widely distributed WordPress page builders ever released.

[vc_column] Belongs to WPBakery Page Builder

The [vc_column] shortcode is a core layout element generated by WPBakery Page Builder, formerly known as Visual Composer. The "vc" prefix in every shortcode this plugin produces stands directly for Visual Composer, its original product name before the rebrand.

WPBakery works by translating your visual drag-and-drop layout into a string of nested shortcodes stored in the WordPress post content field. Every row, column, and content element you place on a page gets encoded as a shortcode pair — for example:

[vc_row] [vc_column width="1/2"] [vc_column_text]Your content here[/vc_column_text] [/vc_column] [vc_column width="1/2"] [vc_column_text]More content[/vc_column_text] [/vc_column] [/vc_row] 

This is how WPBakery stores and renders your page structure. The shortcodes are processed server-side by the plugin, which converts them into structured HTML output when a visitor loads the page.

Why You Might Be Seeing This Shortcode 🔍

There are a few common reasons [vc_column] appears in your WordPress environment:

• WPBakery is actively installed and running on your site, and pages were built using its visual editor.
• WPBakery was previously installed and then removed or deactivated. WordPress stores the raw shortcode text in the database, so if the plugin is gone, those shortcodes render as plain visible text on the frontend — which is a common cause of broken-looking pages.
• A theme bundled WPBakery as an included plugin. Many commercial WordPress themes, particularly those sold on ThemeForest, ship with WPBakery licensed as part of the theme package. If your theme included it, your page content was built with it automatically.
• You imported a demo or starter template that was originally designed with WPBakery layout data embedded.

Understanding which of these applies to your situation changes what you'd need to do next.

How WPBakery Shortcodes Differ From Other Builders

Not every page builder uses shortcodes this way. It's worth knowing how WPBakery's architecture compares to alternatives.

Divi is worth noting separately — it also uses shortcodes in post content, but its shortcodes use a et_pb_ prefix, not vc_. So [et_pb_column] is Divi; [vc_column] is WPBakery. These are distinct, incompatible systems.

The width Attribute and What It Controls

Within [vc_column], the width parameter defines how wide that column is within the row, expressed as a fraction:

• 1/1 — full width
• 1/2 — half width
• 1/3, 2/3 — one-third or two-thirds
• 1/4, 3/4 — quarter and three-quarter splits

WPBakery translates these fractions into CSS grid classes at render time. The exact CSS framework used depends on the theme, but WPBakery traditionally relied on a Bootstrap-based grid, using 12-column grid math internally.

Additional attributes inside [vc_column] can control CSS classes, animations, background styles, padding, offset behavior for responsive layouts, and more — though the defaults produce a clean, unstyled column.

What Happens If the Plugin Is Missing

This is a practical issue many WordPress site owners encounter. If [vc_column] shortcodes are visible as raw text on your live site, it almost always means the WPBakery plugin is deactivated or uninstalled. WordPress isn't processing the shortcodes, so it just prints them literally.

Reinstalling or reactivating WPBakery will typically restore the rendered layout immediately, since the shortcode data is still in your database. However, the version of WPBakery may matter — older content built with significantly earlier versions can sometimes behave differently with newer plugin versions, particularly if deprecated elements were used.

Variables That Affect Your Specific Situation 🔧

How relevant all of this is to you depends on several factors:

• Whether you're maintaining an existing WPBakery site or evaluating whether to migrate away from it
• Your WordPress version — WPBakery has evolved its compatibility with newer WordPress versions over time
• Whether your theme depends on WPBakery or whether it's a standalone plugin choice
• How much content was built with it — a site with dozens of pages of WPBakery content has a very different migration consideration than one with two landing pages
• Your technical comfort level — working directly with shortcode markup requires understanding the nesting structure, while the visual editor abstracts that away

Sites that were built with WPBakery years ago and are being modernized face a different calculus than a developer who just inherited a client site and wants to understand what they're looking at.

The shortcode itself is simple to identify and trace. What you do with that information — whether that's maintaining the existing build, cleaning up orphaned shortcodes, or evaluating a migration path to a different builder — depends entirely on the context of your own site and goals.