Discount codes land here first.
Members get offers on wpgraft, plus build tips and early word on what is shipping next.
DiviAny Divi page, version 4 or 5
BricksNative elements plus global classesMove a page from Divi to Bricks as real, editable Bricks elements, not a screenshot. What comes across, and what does not.
wpgraft never reads Divi’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 Bricks’s own native elements, with the styles written into Bricks’s own fields. Nothing that arrives depends on Divi still existing.
Divi and Bricks store pages in formats with nothing in common: Divi 4 in shortcodes, Divi 5 in its own blocks, Bricks in a flat element array. No converter bridges that honestly. wpgraft does not try. It reads the page Divi rendered, at whichever version, and rebuilds it as Bricks elements with Bricks global classes.
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 Bricks 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, not the Visual Builder.
Click the wpgraft icon on the source tab and pick your destination under Copy into. There is one Bricks entry, labelled Bricks. 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 front-end admin bar. The builder opens on the page’s own URL with ?bricks=run. 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 writes straight into the builder’s live store, the flat {id, name, parent, children, settings} array Bricks keeps the page in, merges the copy’s classes into the global class list, regenerates ids so nothing collides with what is already on the page, and re-renders the canvas.
Press Bricks’ own Save. Until you do, the copy is only in the open builder session.
This is where the product earns its keep. Click anything in the copy and Bricks’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 Bricks elements
Section, container, block, heading, text, image, button and the rest, each one selectable in the structure panel and editable in Bricks’ own controls.
Global classes, not inline overrides
Repeated styles become entries in Bricks’ global class list. Each is named wpg-<role>-<hash> from a hash of the style itself, so re-copying the same page reuses the same class and two pages that genuinely share a style share one class.
Images in your Media Library
Tick Import images to Media Library in the wpgraft panel and the images are pulled into WordPress and re-pointed before anything is saved.
After the insert: Press Bricks’ own Save. Until you do, the copy is only in the open builder session.
The published page, not the Visual Builder.
et_pb_* classes. Those resolve into computed values before wpgraft ever sees them, so the copy does not depend on Divi’s CSS being present in the destination.body { font-size: 14px; color: #666 } is part of how a Divi page looks. It is captured as part of the design rather than silently dropped, which is why a copy out of Divi looks like the Divi page and not like the destination theme.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.wpg-* classes.Each class is named from a hash of its own styles, so copying the same page twice reuses the same classes rather than adding a second set, and two different pages that share a style share one class. A site you copy into constantly will still accumulate them; they are ordinary global classes, and the Bricks class manager can filter to Unused on this site and Delete selected, so clearing out the ones you dropped is a two-click job.
No. Nothing is exported, moved or deleted. wpgraft reads the rendered Divi page the same way any browser does and writes a new copy into Bricks. Your Divi 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 Bricks is Bricks’s own elements with the styles in Bricks’s own fields. There is no shortcode, no embed, no wrapper block and no stylesheet borrowed from Divi. The copy is fully yours and stands on its own.
Editable. Click anything in it and Bricks’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 Bricks’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 Bricks’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 Bricks 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 Bricks
Three copies free, every destination unlocked, full fidelity. Point at one Divi section, put it in Bricks, then judge the result before you decide anything.
