I just want out. Will this actually give me a working site?

Yes. You get a folder of HTML, CSS, JS, images, and your CMS content as Markdown. Drop it on Vercel or Netlify (both free) and it's live in minutes — looking exactly like your published site, with zero remaining hosted dependencies.

Does this work with Framer too?

Yes — Webflow and Framer are both fully supported. Paste any published Framer URL and the scan just works. Framer has no native code export on any plan, so this is the way to get your pages, assets, and CMS out. To include CMS collections, connect a read-only Framer API key (Site Settings → General) when prompted.

Can I edit it with Cursor, Claude, or v0 after?

That's the whole point. The CMS exports as Markdown and MDX — the formats AI coding tools handle natively. Ask Cursor to "add a blog post" or "redesign the homepage" and it just works, because it's reading plain files instead of fighting a visual editor.

Do I need a paid Webflow or Framer plan?

No. On Webflow, a free workspace is enough — you just need a read-only API token from Site settings → Apps & Integrations. On Framer, any published site can be scanned as-is, and the CMS unlock uses an API key every plan can generate.

Is my API token safe?

Yes. Your token stays in your browser (so your recent sites work) and is sent to our server only to run the requests you trigger — it's never stored or logged on our servers, and never shared. We recommend generating a read-only token scoped to the site you want to export — you can revoke it the moment your download finishes.

What happens to CMS-referenced images and assets?

Every image referenced by a CMS field is downloaded and bundled into the export. Asset URLs are rewritten to relative paths, so your export has zero remaining hosted dependencies.

What format does the CMS export in?

Each collection comes out as JSON, Markdown, and MDX side-by-side. Use whichever fits your stack — Next.js, Astro, Hugo, Contentlayer, or your own pipeline.

What's the difference between scanning and exporting?

Scanning is free and shows every page, collection, and asset that will be in the export — so you can verify the scope before paying. You only pay when you click Download.

Can I re-download my export later?

Yes — as many times as you want, forever. Paid sites stay unlocked, so re-scans and re-downloads are always free. Pull a fresh export whenever you publish changes.

Will this work on Enterprise plans or sites with custom domains?

Yes. If an API token can read it, this tool can export it. Custom domains and Enterprise sites are supported.

Where to Host an Exported Framer Site

Once your Framer site is exported to static files, hosting is the easy part. The export is a folder of HTML, CSS, JS, images, and fonts — every static host on the internet can serve it, and the free tiers of the big four are more generous than the Framer plan you were paying for.

This is the short version of the hosting guide I'd give a friend. If you came here from Webflow instead, the Webflow version of this guide goes deeper on each host — the tradeoffs are identical, because by the time a site is static files, its origin stops mattering.

The quick answer

Host	Best at	Free tier
Netlify	Fastest first deploy (drag & drop)	Generous — fine for any marketing site
Vercel	Sites that may grow into Next.js apps	Same
Cloudflare Pages	Global performance, high traffic	Effectively unlimited bandwidth
GitHub Pages	Personal sites, docs, archives	Free, with commercial-use caveats

Netlify — deploy before your coffee cools

Unzip your export
Open app.netlify.com/drop
Drag the folder onto the page
Live URL in ~10 seconds

Deploying an exported site to Netlify via drag-and-drop

Netlify has one feature that matters extra for ex-Framer sites: Netlify Forms. Framer's form backend stays behind when you export, and Netlify can accept those submissions without you running any server — add a netlify attribute to the form tag and you're done.

Vercel — if the site will keep evolving

npm i -g vercel
cd path/to/exported-site
vercel --prod

The pitch for Vercel is the growth path: if you ever rebuild the exported site as a Next.js app — which the export's MDX-formatted CMS content is designed for — you're already on the right platform.

Deploying an exported site to Vercel via the CLI

Cloudflare Pages — if traffic is the concern

Free-tier bandwidth is effectively unlimited, and your site is served from Cloudflare's edge everywhere on earth. Deploy by connecting a Git repo or with npx wrangler pages deploy. Pick this if your Framer bill was climbing because of traffic.

GitHub Pages — fine for personal sites

Push the export to a repo, enable Pages in settings, done. No custom response headers and a soft commercial-use policy make it a "personal projects" answer, but for a portfolio or docs it's unbeatable-free.

What changes after leaving Framer

Forms need a new backend. Netlify Forms, Formspree, or a serverless function. Do this before flipping DNS — it's the only thing that visibly breaks.
Redirects move to the host. Any redirects you set in Framer need re-creating: _redirects on Netlify, vercel.json on Vercel, _redirects on Cloudflare Pages.
Your CMS workflow changes. Static means edits happen in files, not the Framer editor. The export's Markdown/MDX content is exactly what AI coding tools and static site generators expect — many people find editing a Markdown file in Cursor faster than the visual editor.
Costs drop to zero. A typical marketing site fits comfortably in every free tier above. The $10–$30/month you were paying Framer becomes $0/month.

The part people forget: keep a re-export habit

If you keep the Framer project alive for design work, remember the exported copy doesn't update itself. Re-export after significant publishes — with SiteDownload, re-exports of a paid site are free forever, so this is a two-minute habit, not a recurring bill.