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.

The Complete Checklist for Leaving Framer

Moving a live site off any platform has one golden rule: the order of operations matters more than any individual step. People who lose traffic in a migration almost never lose it because the new host is worse — they lose it because they cancelled first and exported second, or flipped DNS before redirects existed.

Here's the full sequence for Framer specifically. Done in order, the migration is invisible to your visitors and to Google.

1. Export while everything still works

Framer has no native code export, so this step means a third-party export. With SiteDownload: paste your published URL, scan for free, connect your Framer API key (Site Settings → General) so the CMS collections come out as JSON/Markdown/MDX, and download the ZIP.

Do this while your plan is active and the site is published. An expired Framer plan takes your site offline, and you can't crawl a site that isn't being served.

Verify the export locally — unzip it and open a few pages in your browser. Every URL is rewritten to relative paths, so it renders offline. Check a CMS-driven page and a page with heavy animations.

2. Inventory your URLs

Grab your live sitemap (yourdomain.com/sitemap.xml) and save the list of URLs somewhere. This is your source of truth for the redirect step — after the switch, every one of these should either resolve or 301 somewhere sensible.

3. Replace the form backend

Framer's form handling stays behind. Before going live anywhere else, wire your forms to Netlify Forms, Formspree, or a small serverless function. This is the only thing in the export that visibly breaks, and it fails silently — a form that looks fine and sends nothing.

4. Deploy to the new host

Netlify, Vercel, Cloudflare Pages, or GitHub Pages — see where to host an exported Framer site for the tradeoffs. Deploy to the host's preview URL first (yoursite.netlify.app), not your real domain.

Test on the preview URL:

A normal page, a CMS-driven page, and your 404
Forms (submit one for real)
Mobile layout and animations
Any third-party embeds (analytics, chat widgets, video)

5. Recreate redirects

Any redirects configured inside Framer need to exist at the new host (_redirects file on Netlify/Cloudflare, vercel.json on Vercel). If you changed any URL shapes during the move, add 301s for those too. Now diff against the URL inventory from step 2 — anything that 404s on the preview needs a redirect before DNS moves.

6. Flip DNS

Point your domain at the new host, following its custom-domain guide (they all provision SSL automatically). DNS propagation is minutes-to-hours; the Framer version keeps serving anyone with cached DNS during the overlap, which is exactly what you want — zero downtime.

7. Protect the SEO

Resubmit your sitemap in Google Search Console (the export includes one; regenerate it if URLs changed).
Watch the Coverage report for a week — a spike in 404s means a redirect you missed.
Don't change titles, descriptions, or URL structure in the same week as the migration. Change one variable at a time.

Rankings survive migrations when URLs keep resolving and content stays identical. The export preserves both, so the only real risk is a missed redirect — which step 2 and 5 exist to catch.

8. Cancel Framer — last

Only after DNS has fully switched and Search Console looks clean. Downgrade to the free plan rather than deleting the project if you want to keep the design source for reference — the published site is now yours either way.

Keep the export fresh

If you keep editing in Framer and re-publishing (some teams keep Framer as their design tool and export as their deployment step), re-export after each significant publish. Paid sites on SiteDownload re-export free, forever — and a fresh backup is also how you make sure a future migration is as boring as this one.