From published URL to portable files

Webflow Exporter: Export Your Site Code to HTML

Download your published Webflow site as portable HTML, CSS and JavaScript for self-hosting, editing or client handoff.

How it works·01

Paste your Webflow URL and choose pages.

scanning…

Pages found0

/
/about
/blog/*
/pricing
/contact

Choose what to include

Paste the public Webflow link

Copy the address of your published site, not its editor. The page must open without a login.

Choose the pages to export

The scan follows links up to three levels deep. Select the pages you need from the results, within your plan’s limit.

How it works·02

Download your Webflow site as HTML files.

yoursite.webflow.io

HTML

IMAGES

CSS

Inside your ZIP download

Page content and design

Your published Webflow pages and styles, including collection pages found during the scan. The ZIP is not an editable Webflow project. Review page titles and search settings before publishing.

Images and fonts

Choose downloaded assets to include available images and fonts. Free exports keep them linked to the original site. Videos and embeds may still need an internet connection.

Menus and animations

Supported menus, sliders, tabs and animations are included. Test each interaction after export.

How it works·03

Test your exported site then publish it.

webflow-export.zip

Vercel

Netlify

Cloudflare

GitHub

Choose your hosting

Test the exported site

Unzip the download and open the files through a local web server or temporary hosting. Check layouts, links, forms and animations on desktop and mobile.

Publish on your chosen host

Upload the tested files to Vercel, Netlify, Cloudflare Pages or GitHub Pages. Check the live site before changing your domain. Hosting costs and provider terms apply.

Before you move your domain. CMS pages do not update automatically. Webflow Forms, search, accounts and ecommerce need Webflow or replacement services.

Webflow Native vs Export Code Tool

Webflow provides native code export on eligible paid Workspace plans. NoCodeExport instead starts from a public URL and can capture rendered CMS pages as static snapshots.

What you need	Webflow native workflow	Recommended path NoCodeExport
Access to deployable code	Available on eligible paid Workspace plans.	Creates a rendered static package from a published URL.
CMS content	CMS databases and dynamic content are excluded from native code export.	Reachable published CMS pages can be captured as static snapshots.
Migration planning	Still requires QA and replacement planning for hosted features excluded from the export.	Produces one static review build; forms, search, accounts, and ecommerce still need replacements.
Best fit	Teams using Webflow’s native code export from a paid Workspace.	Teams that need a rendered snapshot from a public URL, including reachable CMS pages.

Webflow code-export documentation, checked 7 September 2026: help.webflow.com

Webflow guides to pair with the tool page

These articles cover exporter options, code handoff details, and the practical steps teams use when moving a Webflow site off-platform.

One site or ongoing exports?

Export once with Site Pass, or choose Pro for regular updates and client projects.

Site Pass

One-time export

One site to move. One payment. No subscription.

$15once

Export once — $15

Features included:

One successful export, up to 100 pages
Website files with downloaded assets
30-day access to your download

Scan your site and review the pages before checkout.

A failed export restores your pass so you can retry.

Pro

Keep exporting as your sites evolve.

$10/ month

Get Pro — $10/month

Features included:

50 exports every month
Up to 100 pages per export
Download files and assets, or deploy to GitHub and Netlify

Billed monthly. Renews until canceled.

Annual billing and Agency options. See all plans

Frequently Asked Questions

Everything you need to know about the export process.

No. NoCodeExport works from a publicly accessible Webflow URL that you have permission to export. It captures the rendered frontend, so you do not need Webflow project access or its native code-export feature. You receive a static snapshot, not an editable Webflow project.

Supported CSS effects and Webflow interactions can continue through captured runtime files. Test IX2 sequences, sliders, tabs, dropdowns, lightboxes, menus and custom scripts after export because behavior varies by site.

Reachable published collection pages can be captured as separate static files, subject to crawl depth and plan limits. The CMS database, editor and publishing workflow are not exported, so content changes require another publish and export.

Yes. Compatible static hosts include GitHub Pages, Vercel, Netlify and Cloudflare Pages. Run the ZIP locally and verify navigation, assets, interactions, forms and redirects before sending production traffic to the new deployment.

Exporting is useful when you need a snapshot, backup or static handoff of a finished marketing site. Rebuilding is the better fit when you need reusable components, a new CMS, authentication, application state or substantial design changes.

Yes. NoCodeExport's Free plan includes 10 single-page exports per month. You can scan your public Webflow URL and review the detected pages before choosing an export option. Full-site exports and local asset downloads require an eligible paid option; check the limits shown in the exporter.

A developer can connect exported templates to another CMS, but that integration is not automatic. Plan the content model, templates, build process, test environments, forms and redirects as a separate implementation.

Webflow Export Options Explained

Webflow's native export downloads HTML, CSS, JavaScript and assets from eligible paid Workspaces. CMS databases, User Accounts, ecommerce functionality, content beyond the primary locale, form processing, search and code components are not included.

NoCodeExport starts from the public site instead. It can capture reachable published collection pages as static snapshots, but it likewise does not recreate the CMS database, editor or other server-backed features.

What Gets Exported

The ZIP contains the selected HTML pages, styles, JavaScript and reachable assets under the chosen settings. Forms can be connected to NoCodeExport's hosted handler, Formspree, Netlify Forms or a custom endpoint during export configuration.

Some plans reference remote assets, while local-assets export downloads reachable images and fonts. Large media, embeds and inaccessible third-party files may remain remote.

Static Deployment Checklist

After downloading the ZIP, run it over HTTP and test important pages. You can then deploy to Netlify, Vercel, GitHub Pages, Cloudflare Pages or another compatible host under that provider's current terms.

Before changing DNS, verify interactions, forms, search, assets, responsive layouts, metadata, canonicals, redirects and anything that still calls a Webflow or third-party service.

Ready to export your Webflow site?

Paste your published URL and review the pages. No payment is needed to scan.

Check my site

Also Explore Our Solutions For