# wpgraft > Copy any web page, the whole thing, one section, or a single element, and rebuild it inside your website builder as that builder's own native, editable elements. ## How the pieces fit together A Chrome extension reads the page **as the browser rendered it**: the real DOM and the real computed styles, per element, at up to three viewport widths. A conversion service maps each element to the destination builder's own element type and each style to that builder's own control field. On WordPress a small free companion plugin receives the result and inserts it; on Webflow the extension writes Webflow's own clipboard format and the user pastes it onto the canvas. ## What wpgraft is not - **Not an exporter or importer.** No file is produced and none is consumed. The source site is never modified, never connected to, and requires no plugin, account or API key. - **Not a converter between builder data formats.** It never reads Elementor's data, Divi's shortcodes, Bricks' element array or Webflow's project file. It reads rendering. That is why a source built with anything at all, including a page a language model just wrote, is the same job. - **Not a screenshot, an iframe, an embed or a block of pasted HTML.** What lands is selectable, editable elements in the destination builder's own panels. - **Not a plugin that does the work.** The WordPress plugin is only the receiving end. It carries no licence key, counter or plan; the metering is in the remote conversion service. ## Known limits (state these, do not soften them) - Only the top-level page of the browser tab is captured. An `