Export Webflow without a paid plan
Why the native export needs a paid plan
Webflow positions the ZIP export as a Site plan feature, alongside custom-code injection and CMS publishing. The friction is product policy, not technical limitation: the site is already compiled to static files on Webflow's CDN the moment you publish.
The API exists for a different reason — letting integrations read site data — but it gives you the same access to pages, CMS items, and assets. Webflow Export uses that to produce an export that's actually more complete than the native one (CMS-rendered pages, structured CMS data, asset rewriting).
How to do it, end to end
- 1
Confirm you have a Webflow workspace
Any workspace tier works, including the free Starter. If you can log into webflow.com/dashboardand see the site, you're fine. No Site plan needed.
- 2
Generate an API token
Open the site in the Webflow dashboard. Go to Site settings → Apps & Integrations → API access. Click Generate API token, give it read-only scopes (Sites, Pages, CMS, Assets), and copy the value. The token shows only once — paste it somewhere safe while you work.
- 3
Paste the token into Webflow Export
On the home page, paste the token. The tool calls Webflow once to list the sites the token can read; pick the site you want to export.
- 4
Scan for free
The scan walks every page, every CMS collection, and every asset. You see a full inventory — page count, item count, total size — before any money changes hands. The scan is always free, no matter how big the site is.
- 5
Download the ZIP
Click Download. You get a single archive with rendered HTML for every page, every CMS collection as
.md/.mdx/.json, and every asset with relative URLs. - 6
Revoke the token (optional but smart)
The moment your download finishes, go back to API accessin Webflow and revoke the token. We don't store it on our end either — but revoking removes the key entirely, so there's nothing to leak.
Webflow free plan vs paid plan, for export purposes
| Free Starter workspace | Site plan | |
|---|---|---|
| Native ZIP export | No | Yes |
| Static pages via API | Yes (read-only) | Yes |
| CMS collections via API | Yes (read-only) | Yes |
| Assets via API | Yes (read-only) | Yes |
| Webflow Export support | Full | Full |
| Custom domain | No | Yes — but irrelevant for export |
| Forms work post-export | N/A — set up your own | N/A — set up your own |
FAQ
- Is this against Webflow's terms of service?
No. The Webflow API is a documented public surface and read-only access to your own site's data is exactly what API tokens are for. You're using your own credentials on your own site.
- Does the free-plan export include CMS?
Yes — that's the main reason this approach is so useful. Webflow's native paid export skips CMS entirely. Our export, using the API, pulls every collection regardless of plan. See the CMS export details.
- What if I'm on a legacy Webflow plan?
All legacy plans expose the API. Generate the token the same way and the exporter works identically.
- Will Webflow notice or rate-limit me?
The API enforces rate limits which we respect with adaptive batching, so you won't trip them on normal-sized sites. Webflow doesn't alert on legitimate API use.
- Can my client on a free plan use this to leave Webflow entirely?
Yes. The export is a complete copy of the site, including CMS, with no remaining dependency on Webflow's CDN. Once the export is hosted elsewhere, the Webflow workspace can be archived or cancelled.
Ready to try it?
Paste a Webflow API token, scan the site for free, and only pay when you download. Every page, asset, and CMS item is included.
Related
Last updated May 19, 2026