WPBakery Shortcode Input
Switch from WPBakery to Elementor without rebuilding each page by hand. Paste your [vc_row] shortcodes, get native Elementor containers and widgets, paste them into the editor. Free.
Moving a site from WPBakery Page Builder to Elementor usually means rebuilding every page by hand. WPBakery is the plugin most people still call Visual Composer, and it keeps your layout in [vc_row] shortcodes that mean nothing outside the plugin. This free converter reads that shortcode tree, including the design options each element carries in its css attribute, and rebuilds the layout as native Elementor structure. Rows become containers, columns keep their widths, and text, headings, images and buttons become real widgets with native settings. Copy the output, right-click in the Elementor canvas and choose Paste. The conversion runs in your browser.
Open the page, switch the classic editor to Text view (or the WPBakery backend editor) and copy everything from the first [vc_row] onward.
Paste it below and hit Convert. You get Elementor paste JSON plus a report of what mapped and what was skipped.
Copy the output, open the page in Elementor, right-click the canvas and choose Paste. Allow clipboard access if asked.
🔒 Conversion runs in your browser. To improve conversion quality we keep an anonymized structural copy of the input — all text is scrambled and URLs removed before anything leaves your browser. Details.
✓ You're on the list — we'll email you when this converter gets better.
Both plugins can run on the same site at the same time. Keep WPBakery active for now: every page you have not converted yet still needs it to render. Elementor only takes over the pages you open with Edit with Elementor.
Open a page, copy its [vc_row] shortcodes from the Text tab, convert them here and paste the result into the same page in Elementor. The URL, slug and SEO settings of the page stay as they are, because you replace the content, not the page.
Images that WPBakery stores as a media library ID can't be resolved outside your site, so the converter lists them instead of guessing. Re-pick them in Elementor's image widget. Icon-font glyphs are dropped for the same reason. Form shortcodes such as Contact Form 7 are kept and keep working as long as the form plugin stays active.
The converter handles page content. Headers, footers and menus usually come from your theme, so they don't move with the page and don't need to.
When every page is converted, search your pages for [vc_row to catch anything you missed, then deactivate WPBakery. A page that still holds shortcodes at that point shows them as raw text, which is the easiest way to spot it.
ready→made converts your Figma designs straight into Elementor: real structure from a real layout engine.
Yes. WPBakery Page Builder shipped as Visual Composer until 2018 and most existing sites and tutorials still use that name. If your pages are made of [vc_row], [vc_column] and [vc_column_text], this is your converter. A different, unrelated plugin now uses the "Visual Composer Website Builder" name; it stores data differently and is not what this tool reads.
Copy the page's [vc_row] shortcodes from the classic editor's Text tab. Paste them into the converter above and hit Convert. Then open the page in Elementor, right-click the canvas and choose Paste. Rows become containers, columns keep their widths, and text, images and buttons become native widgets. Repeat per page; nothing on the old site changes until you paste.
Yes. Both plugins can be active on one site, and that is the normal way to migrate: convert page by page while WPBakery keeps rendering the rest. Use one builder per page, though. Once a page is edited with Elementor, Elementor renders it.
Completely free, no signup, and no plugin beyond Elementor itself. The output uses Elementor's own clipboard paste format and works with free Elementor.
The page's raw post_content. The easiest way to get it is opening the page in the classic editor and switching to the Text tab, then copying everything from the first [vc_row].
WPBakery writes each element's design options (spacing, borders, backgrounds) into a css attribute on the shortcode itself, and the converter reads those along with the rest. Custom CSS you added elsewhere, for example in the theme, is not part of the page content and needs to move separately.
WPBakery usually references images by media library ID, which only means something inside your own WordPress install. Those images are skipped and listed in the conversion notes; re-pick them in Elementor. Images set as an external link carry over.
No. You paste the converted layout into the same page, so its URL, slug, title and SEO plugin settings stay the same.
Not with this tool. It converts away from WPBakery only. If you are leaving Elementor, the Elementor to Gutenberg and Elementor to Bricks converters are the ones to use.
Third-party or unrecognized [vc_*] addon shortcodes are skipped and listed rather than guessed at. Forms keep their shortcode and need the matching plugin on the target site. Anything driven by JavaScript at render time is not part of a static conversion.
Use the free WPBakery to Gutenberg converter: same input, native core blocks out, no page builder at all.
Then use ready→made: Figma to Elementor to convert the design directly.
Starting from a Figma design? Use the Figma to Elementor converter.