Discount codes land here first.
Members get offers on wpgraft, plus build tips and early word on what is shipping next.
WPBakeryAny WPBakery (Visual Composer) page
GutenbergCore WordPress blocks, no page builder at allMove a page from WPBakery to Gutenberg as real, editable Gutenberg elements, not a screenshot. What comes across, and what does not.
wpgraft never reads WPBakery’s data. There is no exporter, no importer and no shortcode translator anywhere in this, by design, because those are the parts that break. wpgraft reads the page as your browser rendered it: the real elements and the real computed styles on each one, at every breakpoint you ask for. It then rebuilds that as Gutenberg’s own native elements, with the styles written into Gutenberg’s own fields. Nothing that arrives depends on WPBakery still existing.
This is the migration that has been sitting on your list for years, and the reason it never happens is the shortcode graveyard: deactivate WPBakery and every page fills with [vc_row]. wpgraft never reads a shortcode. It reads the page WPBakery rendered and builds it again out of core WordPress blocks, with no builder, no shortcodes and nothing to deactivate later.
The WordPress block editor
Core blocks only. No third-party block plugin is needed, and none is assumed; what arrives is what a stock WordPress install can already open.
WordPress 6.0 or newer
That is the wpgraft plugin’s stated minimum. Newer WordPress has more native style fields, so on a current install more of the copy lands in a control you can see rather than in a style attribute.
wpgraft is a Chrome extension. Get it from wpgraft.com/releases. Install it, click the icon, sign in: the free tier needs an account but is never billed. On your very first copy it asks you to confirm you have the right to reuse what you are copying, once, and does not ask again.
The plugin is the WordPress half of wpgraft: it receives the copy, shows it in a panel inside the Gutenberg editor, inserts it, and pulls the images into your Media Library. Download the zip from wpgraft.com/releases, then upload it in wp-admin. It is free software with no licence key and nothing to configure. Its only admin screen, Settings → wpgraft, is a status page that tells you which builder it detected. It updates itself from inside wp-admin like any other plugin: a version check against wpgraft.com that carries no token and no licence key, only your WordPress and PHP versions and your site's own address in the request's User-Agent, as the privacy policy sets out. It touches nothing on your site until you send it something.
The published page. WPBakery’s back-end editor shows shortcode boxes rather than the design.
Click the wpgraft icon on the source tab and pick your destination under Copy into. There is one Gutenberg entry, labelled Gutenberg. Switch Also copy tablet & phone on unless you only want the desktop layout: it is off until you turn it on, and it captures three viewports instead of one, so the copy arrives responsive.
Select element starts a picker: hover to highlight, press ↑ to widen the selection to the parent and ↓ to narrow it again, click to confirm, Esc to cancel. Whole page takes the entire document in one pass and is a Pro capture. wpgraft scrolls the page for you first so lazy images and scroll-triggered effects have fired, then waits for the fonts and images to finish before it reads anything.
Pages → the page → Edit. That is wp-admin/post.php?post=<id>&action=edit; a brand-new page at post-new.php works the same way. The wpgraft panel appears in the bottom-right corner of the editor as soon as it recognises the builder.
The extension does not push copies at sites by itself, because that would mean any approved site could receive a capture made for another one. Click the wpgraft icon again with the editor open: it names the site and the copy and asks you to confirm, or press Send to open builder. The first time for a given site it also asks whether that site may receive copies at all; approve it once and it stays approved (you can take a site off the list later from the same popup).
The panel lists what is waiting for this builder. Decide whether to tick Import images to Media Library. On, and the images become yours; off, and they keep pointing at the original page. Then press Insert into builder. wpgraft parses the converted markup with WordPress’ own block APIs and applies it through the editor’s official store, as one editor change. A section or element copy is appended after the blocks already there; a whole-page copy replaces them.
Press Update (or Publish). It is one undoable change, so Ctrl+Z takes it back cleanly if you change your mind, and nothing is real until you save: the copy’s stylesheet and fonts are only promoted onto the page by that save.
This is where the product earns its keep. Click anything in the copy and Gutenberg’s own panel opens with real values in it. There is no wrapper you may not touch, no “generated, do not edit” block and no code view. Change the heading, swap the image, drag the padding.
Core blocks
Group, columns, heading, paragraph, image, buttons, list, quote, table, separator, video and the rest. Every block is valid to WordPress’ own parser, with no "this block contains unexpected content" warnings.
Block supports, not a CSS dump
Colour, typography, spacing, border and layout are written as the block support attributes the editor sidebar reads, so the sidebar shows the real values.
Images in your Media Library
Tick Import images to Media Library and the images are sideloaded and re-pointed at your own copies before the blocks are inserted.
After the insert: Press Update (or Publish). It is one undoable change, so Ctrl+Z takes it back cleanly if you change your mind, and nothing is real until you save: the copy’s stylesheet and fonts are only promoted onto the page by that save.
The published page. WPBakery’s back-end editor shows shortcode boxes rather than the design.
vc_row shortcode. It reads the page WPBakery rendered.vc_row, vc_column, wpb_wrapper and an inner column stack around almost everything. wpgraft removes wrappers whose removal provably changes nothing, so the destination does not inherit the stack.[vc_row] text all over the page; a copy built in the destination’s own elements has no shortcodes in it at all.A guide that only lists what works will waste your afternoon. These are the things that surprise people, set out before you start rather than discovered afterwards.
unfiltered_html capability, which normally means an administrator. Without it, the parts of the copy that would output markup verbatim are removed before the insert, or, where WordPress sanitizes them on save instead, left to it, and the panel tells you how many. Everything else in the copy still lands. Insert as an administrator if you want all of it.javascript: link in the source page is neutralised on the way in, for every account including an administrator’s, and you are told how many. It is the one thing wpgraft will not carry across for you.<iframe> is kept as the embed it is: a YouTube or Vimeo frame becomes a video element, a Google Maps frame becomes a map. wpgraft does not descend into it, same origin or not, which is also why a builder’s own editor canvas and an AI chat’s artifact preview have to be opened on their own URL before you can copy them.z-index and transform have no native block support in WordPress, only position: sticky, and only on a Group block whose theme supports it. Where a captured design needs the others, they are written into the block’s own custom-CSS field rather than a sidebar control: still editable, still yours, but not a slider.edit_css capability (WordPress maps it to edit_theme_options, so an administrator has it and an editor normally does not) or unfiltered_html. Without either, wpgraft drops the stylesheet and tells you it did, and the copy renders with your theme’s styling instead. Insert as an administrator.[vc_row] shortcodes anywhere?Not in the copy. wpgraft never reads the shortcodes. It reads the rendered page, and what it writes is the destination builder’s own elements. Your original WPBakery pages are untouched and still need WPBakery; the copies do not.
No. wpgraft writes core WordPress blocks only. That is deliberate: a copy that depends on a block plugin stops rendering the day that plugin is deactivated, and it cannot be moved to a site that does not run it.
They should not. The markup is produced with WordPress’ own block serializer rather than hand-written, so it is valid to the same parser the editor validates against.
A whole-page copy sets the page to wpgraft’s Blank template, which renders the content without the theme’s header and footer, because the page you copied already contains its own. If you would rather keep the theme’s chrome, switch the template back in the page sidebar (Page → Template) and delete the copied header and footer blocks.
No. Nothing is exported, moved or deleted. wpgraft reads the rendered WPBakery page the same way any browser does and writes a new copy into Gutenberg. Your WPBakery site keeps running exactly as it did, which is what lets you rebuild one section at a time and switch over when you are ready.
No. What lands in Gutenberg is Gutenberg’s own elements with the styles in Gutenberg’s own fields. There is no shortcode, no embed, no wrapper block and no stylesheet borrowed from WPBakery. The copy is fully yours and stands on its own.
Editable. Click anything in it and Gutenberg’s own settings panel opens with real values in it. That is the whole product, and it is measured on every release: an inserted copy has to be selectable through Gutenberg’s own API and the editor has to reopen cleanly on the saved page, or the build does not ship.
Yes, once you switch Also copy tablet & phone on. It is off by default, and with it off you get the desktop layout only, slightly faster. With it on, wpgraft measures the page three times: at your window’s own width, then at 768px, then at 375px. Core WordPress blocks have no per-breakpoint controls to write those values into, so the narrow layouts arrive as media queries in the stylesheet wpgraft stores on the page. The page reflows; what you will not find is a “tablet” tab in the sidebar, because WordPress does not have one. One honest caveat about the measurement: the Web Store build produces the narrow viewports inside the page rather than by resizing the window. It re-evaluates every media query at the target width, pins the layout width, resolves vw units and clamps position: fixed boxes to it, and the result is measured at 100% of the property values a real 768px and 375px window produces on getbootstrap.com and on a stock WordPress theme. What it cannot do is re-run the source site’s own JavaScript for the new width, so a layout a script computes on resize is copied as the desktop script left it, and the capture says so in a warning.
The free tier is three copies in total, usable on any destination, at full fidelity, with nothing watermarked or downgraded, within seven days of signing up. Whole-page copies are a Pro capture; sections and elements are not. Pro removes the copy limit and opens up whole-page captures.
Yes. It is the WordPress half of wpgraft, and it is free software with no licence key, no counter and no upgrade nag in it. It receives the copy, shows it in a panel inside the Gutenberg editor and imports the images. It does nothing on its own until you send it something.
That depends on whose page it is and what you copy. Your own site, your own client’s site, a template you have licensed, or your own design on a platform you are leaving. None of that is in question. Somebody else’s design is a decision you are making, and wpgraft asks you to confirm you have the right to make it before your first copy. Text, images, fonts and icons all carry their own licences, and they travel with the copy.
Read moreThe layout, usually yes. The words, photos and logo inside it, no. Take the shape, bring your own content, and you are on the safe side of the only line that really matters.
Read the postNot legal advice: the post says so too, and says why.
Other ways into Gutenberg
Three copies free, every destination unlocked, full fidelity. Point at one WPBakery section, put it in Gutenberg, then judge the result before you decide anything.
