Getting your site out of a website builder.

The export situation across builders is worse than most people assume: Framer and Wix offer no HTML export at all, Squarespace exports content but not your site, and Webflow's export is paid and drops your CMS pages. The published site, though, is rendered HTML on a CDN, whoever built it. Mirror it, clean it up, host it anywhere.

Get started free

Can you export a site from a website builder?

Usually not as working HTML. Per each platform's own documentation: Framer and Wix offer no site export at all, Squarespace exports only content (WordPress-format XML, no design or CSS), Carrd gates downloads behind its top-tier plan, and Webflow's code export requires a paid Workspace plan and excludes CMS content. The reliable platform-agnostic path is mirroring the published site with wget and cleaning up the result, which the open-source website-builder-migrate skill automates end to end.

The export landscape, per the builders' own docs

Builder	Official export	The catch
Webflow	Yes, paid Workspace plans	CMS content excluded (collection pages export empty); forms, search, and password protection do not survive
Framer	No	Sites depend on Framer's backend rendering; React plugin exports components, not a site
Squarespace	Content only	WordPress-format XML of posts and pages; no design, templates, or CSS
Wix	No	Sites must be hosted on Wix's servers; no export or transfer
Carrd	Pro Plus plan only ($49/yr)	Unminified zip download; form elements present but non-functional

Every row is from the platform's own help center (linked in the sources below). The pattern is consistent and rational from the builders' side: hosting is the business, so a complete, working export is never the priority. The practical consequence is that the most complete copy of your site is not in any export tool. It is the published site itself.

Mirroring works on all of them, with one workflow

Whatever built the site, what visitors receive is HTML, CSS, JS, and media, and wget --mirror fetches all of it, including assets on the builder's CDN. The raw mirror is not deployable, though, and the cleanup is where migrations actually fail: SRI integrity hashes that no longer match after URL rewriting (the classic blank-page symptom), webpack chunks loaded at runtime that wget never sees, inline background-image assets, double-encoded filenames, and CSS-relative font paths that break when files move.

The website-builder-migrate skill packages the whole workflow, mirror through verified deploy, as a free Claude Code skill with per-platform notes for each builder's CDN domains and quirks:

npx skills add stevysmith/website-builder-migrate-skill

Webflow mirrors best, and the result beats the paid export: CMS pages come along as rendered HTML. We cover it in depth on the Webflow page.
Framer mirrors well; it is a React SPA, so verify hydration in a real browser, not just with file checks.
Squarespace mirrors with attention to its server-side image transforms; capture each referenced variant.
Carrd barely needs the workflow: typically one page with inlined styles.
Wix is the honest exception. Pages are largely client-rendered from dynamic configs, and mirroring is reliable only for simple static template sites. If a Wix migration matters to you, prototype it before promising it.

Verify on a private URL before anything public changes

Whichever builder you are leaving, the same discipline applies: check the migrated copy against the original before DNS moves. The migrated folder publishes to a private, unguessable preview URL with no account:

(cd site && zip -qr ../site.zip .) && curl -F "file=@site.zip" https://api.stacktr.ee/sites

Anonymous previews last 24 hours at up to 10 MB, enough to click through every page side by side with the original. When it holds up, an API key keeps it (free tier covers 5 sites at 25 MB each), and a custom domain is $5 for 30 days when DNS cuts over. Since the skill runs in an agent session, the agent can handle that step itself, paying over x402 or printing a scan-to-pay QR. The skill's docs also cover deploying to Render, Netlify, and Vercel; the workflow is host-agnostic by design.

What no migration path fixes

Three limitations hold across every builder and every export method, official or mirrored. Forms depend on the builder's backend, so swap in Formspree, Basin, or Web3Forms. Native site search is gone; Pagefind runs client-side and suits a static mirror. And dynamic content is frozen at mirror time; re-run the mirror when content changes, or treat the copy as an archive. Notably, the official exports share these limitations: Webflow's export disables forms and search, and Carrd's download ships non-functional forms.

FAQ

Frequent questions

Can you export a Framer site to HTML? +

No. Framer's help center is explicit: there is no HTML export and no self-hosting, because Framer's rendering depends on its backend services (pre-rendering, dynamic image resizing, font subsetting). The official React plugin exports components for developers, not a working site. Mirroring the published site captures the server-rendered HTML shell; verify hydration in a real browser, since some content renders client-side.

Can you export a Squarespace site? +

Only the content, not the site. Squarespace's export tool produces a WordPress-format XML of blog posts and certain pages; your design, templates, and CSS are not included, and there is no HTML export. Mirroring the published site is the only way to get the site as visitors see it.

Can you export a Wix site? +

No. Wix's support docs state your site must be hosted on Wix's servers and cannot be exported or transferred to another host. Mirroring partially works but with the biggest caveat of any builder: Wix pages are heavily client-rendered, so treat mirroring as viable only for simple, static template sites.

Can you export a Carrd site? +

Only on the top-tier Pro Plus plan ($49/year), which downloads the unminified HTML, CSS, and JS as a zip; per Carrd's docs, form elements are present but non-functional in the download. Carrd sites are also the easiest of any builder to mirror: usually a single page with inlined styles.

What does mirroring a builder site actually involve? +

wget downloads every published page and asset (including from the builder's CDN), then a cleanup pass makes it deployable: rewriting CDN URLs to local paths, stripping SRI integrity hashes that otherwise blank the page, fetching lazy-loaded webpack chunks, fixing double-encoded filenames, and verifying every reference in a browser. The open-source website-builder-migrate skill automates all seven phases from a Claude Code session.

Is it legal to mirror a website builder site? +

Mirror sites you own or control: your own project, your company's site, or a client migration done with permission. The technique only fetches what the site already serves publicly, but the use case is getting your own work out of a platform, not copying someone else's.

Keep reading

Related guides

References

Sources and further reading

Whichever builder you're leaving, verify in private first.

Zip the migrated folder, post it to the API, get an unguessable preview URL with no account. Make it permanent when it checks out. Free tier, no card.