Guides

Everything about ejecting your site

Straight answers on what the exports contain, which export style to pick, and what to do after you own the code.

Faithful vs. editable components — which export style to pick

React and Next.js exports come in two styles, chosen at download time. Faithful ships the site's original runtime alongside your pages: animations, hover states and scripted motion keep working exactly as published, but each page is a thin wrapper mounting the original markup — treat it as a pixel-perfect snapshot you deploy, not code you redesign. Editable components converts every page into per-section JSX named after your Framer layers, with shared headers and footers deduplicated into a shared/ folder. That's the export to pick when the goal is to own and evolve the code — the trade is that scripted motion from the original runtime is not carried over.

A good default: download faithful to have a working mirror, and editable components as the codebase you build on. One credit unlocks the format for that extraction permanently, and re-downloads in either style are free.

What the HTML, React and Next.js exports contain

Static HTML (free) is one self-contained page per crawled route — CSS inlined, images and fonts downloaded and rewritten to local paths — plus a package.json with a static server so npm start just works. React is a Vite 5 project with react-router-dom, one page component per route and extracted section components. Next.js targets the Pages Router with per-route files under pages/, shared components, and a generated next.config.mjs. Every export includes a README and an EXTRACTION_REPORT.md that lists anything the converter had to degrade, so surprises are written down rather than discovered.

Which sites can be ejected

EjectSite is built for published Framer sites— that focus is what makes the animation and structure fidelity possible. Point it at your site's live URL (custom domain or *.framer.app/*.framer.website). Sites on other builders are detected and declined before any credit is involved. Crawls cover up to 50 pages found via your sitemap and internal links; very large media files are capped rather than downloaded endlessly.

After you eject: run it, deploy it, point your domain

Unzip, npm install, and npm run dev — every export runs locally with no extra setup. The HTML export can be dropped on any static host. React builds with npm run build to a dist/ you can serve anywhere; Next.js deploys directly to Vercel, Netlify or your own server. Once the deploy looks right, move your domain's DNS to the new host — from that moment the site is fully yours, with no builder subscription behind it.

Ownership and ethics — what cloning is for

The intended use is ejecting your own site— or one you have the rights to — out of a subscription builder and into code you control. Design and content remain the author's intellectual property: extracting someone else's site doesn't transfer any rights to it. The acceptable-use policy spells this out, and accounts used to rip off other people's work get closed.

Something unanswered? The homepage FAQ covers pricing and credits, and the team reads every message.