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.

How to Back Up Your Framer CMS (Before You Need It)

Here's an uncomfortable fact about the Framer CMS: there is no export button. Not for collections, not for items, not for the site as a whole. Your blog posts, case studies, job listings, and changelog entries live in Framer's database, and the only first-party way to read them back out is one item at a time, in the editor.

That's fine — right up until it isn't. Accounts get locked, payments fail, teammates delete collections, companies decide to migrate. Every one of those situations is dramatically better with a backup you made before you needed it.

I run SiteDownload, so I'll be upfront that one of the three options below is my tool. But all three are real options, and for small sites the free ones are genuinely fine.

Option 1: Copy it out by hand

For a collection with six items, honestly, just do this. Open each item in the editor, copy the fields into a Markdown file or a spreadsheet, download the images, done in twenty minutes.

Where this falls apart: rich-text fields (formatting gets mangled in copy-paste), image fields (you have to chase each asset URL), and anything over ~20 items (you won't finish, and you definitely won't repeat it monthly). A backup process you won't repeat isn't a backup process.

Option 2: Write a script against the Framer API

Framer has a server API that can read CMS collections — the same one integrations use. If you're comfortable writing a small script, you can authenticate with an API key from your project's Site Settings → General and walk your collections into JSON files. Framer's server API quick start covers authentication and the available endpoints.

What you get: structured data, repeatable on a schedule, free.

What you don't get: the rendered pages (your layouts and design live outside the CMS), the images (you need to download and re-link them yourself), and any conversion to Markdown/MDX — the API hands you Framer's field structures, and turning a rich-text field into clean Markdown is its own small project.

This is the right answer for engineering teams that want backups inside their own infrastructure.

Option 3: Export everything with SiteDownload

SiteDownload does the whole job in one pass: it crawls your published site for the pages, reads your collections through the Framer API (you paste the same API key from Site Settings → General), and writes each collection out three ways — JSON, Markdown with frontmatter, and MDX — with every referenced image downloaded into the export and re-pathed.

The scan is free and shows you exactly what it found — every collection, every item count — before you pay anything. The download is a one-time payment per site, and re-exports are free forever, so "fresh backup after every publish" costs nothing extra.

The result is a backup that is also a migration: the Markdown/MDX drops directly into a Next.js, Astro, or Hugo project if you ever leave, and the HTML pages mean the site itself is preserved, not just the data.

Which one should you pick?

Your situation	Do this
A handful of items, one-time need	Copy it by hand
Engineering team, wants scheduled backups in-house	Script against the Framer API
Want pages + CMS + images, or planning a migration	SiteDownload

Whatever you pick, do it now

The pattern in every "I lost my content" story is the same: the backup plan was scheduled for later. Your Framer site is one failed payment, one team mix-up, or one pricing change away from being read-only to you. Twenty minutes today — whichever option you choose — removes that whole category of risk.

For the full picture of what a complete export contains (pages, assets, CMS, and what to fix afterwards), see Export Framer to HTML.