Webflow Exporter logo
ResourcesContact
Webflow → HTML

Export Webflow to HTML

Every page on your Webflow site is built into a static .html file the moment it's published. The export pulls those compiled pages along with their CSS, JS, fonts, and assets, rewrites every Webflow-hosted URL to a relative path, and hands you a folder that renders identically on any static host.
Export to HTMLNo paid Webflow plan required

What ‘export to HTML’ actually means

Webflow itself does ship a native HTML/CSS export, but it has two sharp limits: it requires a paid Site plan, and it leaves out anything CMS-driven. Forms, CMS collections, and any data behind the Designer don't come out.

What you usually want is something different: a copy of the publishedsite — the version a visitor sees — including every CMS-driven page, with images pulled into the folder and URLs rewritten so the site has no remaining dependency on Webflow's CDN. That's what Webflow Export gives you.

Native Webflow export vs. Webflow Export

Webflow native exportWebflow Export
Plan requiredPaid Site planFree workspace is fine
Static pagesYesYes
CMS-driven pagesNoYes — rendered HTML for every item
CMS dataNoJSON + Markdown + MDX of every collection
Assets in CMS rich-textNot exportedDownloaded and re-pathed
Asset URLsOften absolute to Webflow CDNRewritten to relative
Form handlerNot includedNot included — bring your own backend
Re-download window—30 days, free re-exports

How to export Webflow to HTML, step by step

  1. 1

    Generate a Webflow API token

    In Webflow, open Site settings → Apps & Integrations → API access. Generate a token with read-only scopes for Sites, Pages, CMS, and Assets. Copy it. A free Webflow workspace can do this — no paid plan needed.

  2. 2

    Paste the token into Webflow Export

    Open the exporter, paste the token. The tool calls the Webflow API once to list your sites, and you pick which one to export.

  3. 3

    Scan the site for free

    The scan crawls every published page, walks every collection, and lists every asset it will download. You see the full inventory before paying — page count, asset count, total download size.

  4. 4

    Download the ZIP

    Click Download. The export builds in the background; assets are streamed in, URLs are rewritten, and you get a single archive — typically a few minutes for a normal marketing site.

  5. 5

    Drop it on any static host

    Unzip the folder, drag it onto Netlify Drop or run vercel --prod — and the site is live with a fresh URL. See where to host an exported Webflow site for the tradeoffs by host.

Folder structure of the export

/
  index.html
  about/index.html
  pricing/index.html
  blog/index.html
  blog/the-case-against-cms/index.html
  blog/shipping-faster/index.html
  css/normalize.css
  css/components.css
  css/site.css
  js/webflow.js
  images/hero.jpg
  images/blog/cover-the-case-against-cms.jpg
  fonts/Inter-Regular.woff2
  sitemap.xml
  robots.txt

Each route is a folder with an index.html, which is the convention every static host expects. Open any file in a browser locally — it renders the same as the published site, because every URL inside it has already been rewritten to be relative.

Things to handle after the export

  1. Forms.Webflow's native form handler is gone. Wire forms to Netlify Forms, Formspree, or a serverless function before flipping DNS.
  2. Trailing-slash convention. Pick /about or /about/and configure the host to 301 the other shape, so you don't lose Google's indexed version.
  3. Sitemap. The export includes one, but if you change the domain regenerate it against the new origin.
  4. 301 redirects. If any URLs changed during the move, add redirects with _redirects on Netlify or vercel.json on Vercel.

FAQ — Webflow HTML export

Will the exported site look identical to my published Webflow site?

Yes. The export captures the rendered HTML and the same CSS and JS bundles Webflow served, so the pages render byte-for-byte the same on any static host.

Are CMS-driven pages included?

Yes. Every CMS item that has a template page in Webflow is rendered as static HTML in the export. This is the biggest difference from Webflow's native export, which only ships static pages.

Do interactions and animations still work?

Yes. Webflow interactions are implemented in webflow.js, which is included in the export. Anything that worked on the published site keeps working.

What happens to images in CMS rich text?

Every image referenced by a CMS field — including inline images inside rich-text fields — is downloaded into the assets folder and the HTML is rewritten to point at the relative path.

Can I export password-protected pages?

Password protection is a Webflow hosting feature; it doesn't survive a static export. If a page is published and visible to the API, it can be exported — and from that point it's just an HTML file you can protect at the host level.

Does the exported site lose SEO ranking?

Not from the export itself. SEO regressions during a Webflow migration almost always come from broken redirects, lost sitemaps, or trailing-slash mismatches — not from the static files. Handle those four items at the host before flipping DNS.

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