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
ElementorAtomic elements or classic widgetsMove a page from WPBakery to Elementor as real, editable Elementor 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 Elementor’s own native elements, with the styles written into Elementor’s own fields. Nothing that arrives depends on WPBakery still existing.
Moving off WPBakery normally means rebuilding every page by hand, because there is no honest path from vc_row shortcodes to Elementor’s widgets. wpgraft does not try to find one. It reads the page WPBakery rendered and rebuilds it as Elementor’s own elements, so the design survives and the shortcodes do not come with it.
Elementor 4: atomic elements
The new document model. wpgraft writes atomic e-* elements and puts each style on the element’s own style variant.
Elementor 3: classic widgets
The widget model most sites still run. wpgraft writes real widgets and fills their own controls.
Which one your site takes is not decided by the version number
It is decided by Elementor’s e_atomic_elements experiment, which Elementor marks hidden, so it is not in the Experiments screen and you cannot read it off a settings page. A fresh 4.0-or-later install resolves it active; a site UPGRADED to 4.x usually does not; 3.x has no such setting at all. A site with the experiment off discards every atomic element silently, which is why wpgraft treats the two as different destinations instead of letting the save find out. The plugin answers the question for you, see the FAQ below.
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 Elementor 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. Elementor appears twice, as Elementor 4 (atomic) and Elementor 3 (classic), because those are genuinely different formats. Pick the one your site runs; the section above says how to tell. Choose the wrong one and the copy never shows up in the editor panel, because the panel only lists what was queued for the model the site reports. 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.
From the page list or the admin bar. The editor opens at wp-admin/post.php?post=<id>&action=elementor. 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. Elementor 4 has no public client API for building an atomic subtree, so wpgraft hands the tree to the server and lets Elementor’s own Document::save() run it, with the same validation, schema registration and image sideloading a normal save gets. The editor then reloads to read the document back.
Nothing to press. The panel confirms the insert and reloads the editor so it reads the saved document back. Because it went through Elementor’s own save it is not in the undo history; restore a page revision if you want it gone.
This is where the product earns its keep. Click anything in the copy and Elementor’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.
Real Elementor elements
Atomic e-* elements on Elementor 4, classic widgets on Elementor 3. Selectable in the panel, editable in the panel, deletable in the panel.
Styles in Elementor’s own fields
Typography, spacing, background, border and layout are written where Elementor’s controls read them, not into a custom-CSS box the editor cannot see.
Images in your Media Library
Tick Import images to Media Library in the wpgraft panel and every image is sideloaded through WordPress and re-pointed at your own copy.
After the insert: Nothing to press. The panel confirms the insert and reloads the editor so it reads the saved document back. Because it went through Elementor’s own save it is not in the undo history; restore a page revision if you want it gone.
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.Default template). A captured page carries its own header, nav and footer; rendered through the theme’s default template it would be wrapped in a second set and squeezed to the theme’s content width. If you have already chosen a template for that page, wpgraft leaves it alone, and you can change it back at any time in the page’s own settings.[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 is tested against a WordPress install running Elementor Free with Elementor Pro never installed, and it produces the same element tree and the same native-field coverage as the Pro site. Nothing in the copy path asks about your Elementor licence.
Install the wpgraft plugin and open Settings → wpgraft. The "Detected builder" row names the exact entry to pick in the extension, Elementor 4 (atomic) or Elementor 3 (classic), because the plugin asks Elementor the same question the paste will ask. Do not go looking in Elementor → Settings → Features: the setting that decides this (e_atomic_elements) is marked hidden by Elementor and does not appear there. The version number does not answer it either; an install upgraded to 4.x usually still stores the classic model.
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 Elementor. 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 Elementor is Elementor’s own elements with the styles in Elementor’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 Elementor’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 Elementor’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. The per-breakpoint values are written into Elementor’s own responsive controls. 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 Elementor 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 Elementor
Three copies free, every destination unlocked, full fidelity. Point at one WPBakery section, put it in Elementor, then judge the result before you decide anything.
