WPBakery Shortcode Input
Gutenberg Blocks Output
WPBakery, formerly Visual Composer, is legacy tech now. Paste your page's [vc_row] shortcodes and get native Gutenberg blocks with your design intact — nothing to install, completely free.
WPBakery Page Builder — still widely known by its old name, Visual Composer — hasn't meaningfully moved forward in years, and every page you build in it is locked behind the plugin's [vc_row] shortcode soup — deactivate it and your content turns to raw text. This free converter reads that shortcode tree and turns it into native Gutenberg blocks: rows become groups, columns become column blocks, and text/image/button elements become real core blocks, with your design-options CSS carried over in a single embedded style block. Paste the page's shortcode content from the Text/Code editor view, convert, and paste the result into Gutenberg's code editor. No plugin, no account, no lock-in — the output is plain WordPress.
Open the page, switch the classic editor to Text view (or the WPBakery backend editor) and copy the full [vc_row]…[/vc_row] content.
Paste it below, optionally add your design-options CSS, hit Convert, copy the result.
In the block editor open ⋮ → Code editor, paste, switch back to the visual editor — done. No plugin needed.
🔒 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.
ready→made converts your Figma designs straight into Gutenberg, Oxygen 6, Etch or clean HTML — real structure from a real layout engine.
The page's raw post_content — easiest way to get it is opening the page in the classic editor and switching to the Text tab (or your page builder's "backend editor"), then copying everything from the first [vc_row] onward.
WPBakery stores custom per-element CSS separately in _wpb_shortcodes_custom_css post meta. There's an optional field for it in the converter — paste it in and those rules land in the embedded style block alongside the rest.
WPBakery often references images by attachment ID, which only resolves on your own WordPress install. Convert on the same site the page lives on, or swap in the image URLs manually afterwards — the converter flags any ID it couldn't resolve.
Contact Form 7 and Gravity Forms shortcodes ([contact-form-7 …], [gravityform …]) are kept as-is in the output — they just need the corresponding plugin active on the target site to render.
Unrecognized or third-party [vc_*] shortcodes (custom addons, page-builder-specific widgets) are skipped and listed in the conversion notes rather than guessed at.
Yes. WPBakery Page Builder was called Visual Composer until 2018, and a lot of sites and tutorials still use the old name. If your pages are built from [vc_row], [vc_column] and [vc_column_text] shortcodes, this is your converter. Note that a separate, unrelated plugin now ships under the "Visual Composer Website Builder" name — that one stores its data differently and is not what this tool reads.
Use the dedicated Elementor → Gutenberg or Oxygen → Gutenberg converter — they read that builder's own data format directly.
Then use ready→made to convert the Figma design directly to Gutenberg.