Select a section on a web pageIt converts into your page builder, editable

No. The companion plugin has no login or licence key and no settings to fill in, and the only request it ever makes to us is its own update check. Install it, activate it, and open your builder: the extension sends the copy to whichever builder editor you have open, after Chrome asks you once for permission to reach that site. Local and staging installs work exactly like production.

Nothing. Converted pages are ordinary builder content stored in your own database, your own Shopify theme or your own Figma file. They have no runtime dependency on wpgraft. Cancel, uninstall the extension, delete the plugin, and every page you already imported keeps rendering.

No, unless you send one to us on purpose. Copies are converted in memory and returned to you; what we keep is metadata: which builder, which source URL, whether it succeeded, and when. Your dashboard shows a history from that. The one exception is the rating card in the plugin: if you leave its tick-box ticked, that one copy is sent to us so the fault can be reproduced, encrypted at rest and deleted after 90 days. Untick it and nothing is sent.

No. Every plan is paid: Pro monthly, Pro yearly or Lifetime. The way to find out whether wpgraft works for what you build is the refund policy: ask within 7 days of the charge and 90% of the plan price comes back, with no reason needed. Accounts created while a free tier existed are still there, with their history; they need a plan to copy again.

All of them, on every plan. No destination is locked and nothing is downgraded: a copy into Bricks, Elementor, Divi 5, Oxygen, Shopify or Figma is the same full-fidelity conversion whichever plan you are on, and whole-page copies are included alongside sections and single elements. The plans differ in how you pay, not in what they do.

Yes, with the extension alone: there is no Figma plugin and no Shopify app to install. Pick Figma or Shopify under Copy into. For Figma, have a Design file open in Chrome (not the desktop app): the copy is built there as layers, one frame per width you copied, with auto layout where the page really was a row or a column, real text and its images. A font Figma does not have is replaced and named. For Shopify, have your Shopify admin open: a section goes onto the page open in the theme editor, and a whole page arrives as a new hidden page with its own template, built from blocks whose styles are settings you edit in the theme editor. Both are included in every plan.

Yes. Choose Code under Copy into in the extension, or right-click the page and pick Export as code. The section, or the whole page, comes back as one HTML file or as a React, Vue, Svelte, Astro or Angular component, styled with plain CSS or Tailwind. You can switch between them on the Export page without copying again. Menus and sliders arrive static, because a copy carries no JavaScript. It is included in every plan.

No. Every plan is unlimited for ordinary human use, including heavy agency use. Each copy is logged so your dashboard can show a history, but there is no counter to run out of. What unlimited does not cover is automated conversion at machine scale; the Terms call that fair use, and we would contact you before acting on it.

No. It asks for access to the tab you are on at the moment you click, and, once each, for the places you send copies to: your WordPress site, figma.com or your Shopify admin. Your browsing is never read in the background.

On most sections, very close. The converter measures computed styles instead of guessing from stylesheets. Where a builder has no native equivalent for something (an exotic filter, a scroll-driven animation) the element still arrives editable, minus that effect. We would rather hand you something you can edit than something that only looks right.