By Mehdi HassanCan you export a Webflow site's code and host it yourself?
Yes, you can export a Webflow site's code and host it yourself, but only the static parts work afterward. Webflow's code export produces HTML for each static page, the site's CSS, the JavaScript that runs interactions and the image assets. Anything that depends on Webflow's servers, including the CMS, forms and ecommerce, stops working once the files leave Webflow.
So the honest answer is that an export is a copy of the front end, not a portable website. Teams that want to leave Webflow for good need a rebuild, which we lay out in our Webflow to Next.js migration guide.
What does a Webflow code export include?
A Webflow code export includes everything the browser needs to draw your static pages as they looked on the day you exported. You download it from the Designer as a ZIP file, and it requires a paid Workspace plan; check Webflow's current plan page for which ones.
Included in the export | Not included |
|---|---|
HTML for each static page | CMS collection items and their content |
The site's CSS files | Form submission handling |
Webflow's JavaScript for interactions | Ecommerce products, cart and checkout |
Images and other uploaded assets | Site search |
Page titles and meta set on static pages | 301 redirects and hosting settings |
Custom code embedded in pages | Password protection and user accounts |
Collection pages are the big gap. A blog post template exports as a page shell without the posts, so a site with a CMS-driven blog loses its blog. You get CMS content separately: Webflow lets you export collection content as CSV, and the Webflow API gives fuller access. Our guide on exporting Webflow CMS content covers both.
What are the Webflow export limitations?
The main Webflow export limitations are that dynamic features stop working and the code isn't built to be edited by hand. The first problem is functional, and the second is about maintenance.
- Forms post nowhere. The form markup survives, but Webflow's submission backend doesn't, so you need a form handler.
- No CMS. Content is frozen into static HTML. Every future edit means editing HTML files directly.
- Generated class names. The CSS follows how the site was built in the Designer, including combo classes and leftover styles, so it's hard to read and change.
- A dependency on webflow.js. Interactions rely on Webflow's script. It works offline, but you can't easily change interactions without the Designer.
- No ecommerce or memberships. These depend entirely on Webflow's platform.
- One-time snapshot. Change the site in Webflow and you have to export again and redeploy.
How do you self-host an exported Webflow site?
Self-hosting an export takes an afternoon for a small site: unzip it, fix what broke and upload it to a static host. The steps below are the minimum for a site you plan to keep running.
Export and back up
Download the ZIP from the Designer and the CMS content as CSV. Store both somewhere safe.
Run it locally
Serve the folder with any local web server and click through every page, checking links, images and interactions.
Replace forms
Point each form at a form service or a small serverless function that sends submissions to your CRM or inbox.
Fix URLs
Webflow exports pages as files ending in .html. Configure your host for clean URLs so /about stays /about.
Rebuild redirects and the sitemap
Recreate any 301 redirects on the new host and generate a sitemap, since Webflow's settings don't come with the export.
Deploy and switch DNS
Upload to a static host such as Cloudflare Pages or Vercel, test on a temporary URL, then point your domain.
After launch, run a crawl to catch broken links and check that pages still render titles and descriptions. If accessibility issues came across with the export, fix them while you're in the code; our guide to website accessibility remediation gives the order to work in.
Why isn't a Webflow export a migration?
An export isn't a migration because a migration gives you a working site that your team can keep editing, and an export gives you a frozen copy. The moment marketing wants to publish a post or change the pricing page, someone has to edit raw HTML, which is slower than Webflow ever was.
A real migration rebuilds the site in a system built for editing, such as Next.js with a headless CMS, moves the content into it, keeps the URLs and redirects the rest. The export still helps: it's an exact reference for the design, the copy and the page structure, and it's a useful input when you use AI coding tools for the rebuild. We walk through that approach in migrating off Webflow with Claude Code.
Using the export as input for an AI-assisted rebuild
Coding agents can read the exported HTML and CSS and turn them into clean components in Next.js or Astro, which removes much of the typing from a rebuild. The research we draw on notes public examples of teams doing this quickly, such as Vellum's write-up of moving off Webflow with coding agents in about a week.
The agent doesn't remove the judgment work. Someone still has to design the content model, decide which components to keep, move the CMS content, map redirects and check SEO and accessibility before launch. The export speeds up the code, not the decisions. The same pattern applies to rebuilding a Framer site in code with AI.
When is exporting Webflow code the right move?
Exporting is the right move in three situations: you want a backup of the front end, you're freezing a small site that won't change, or you need a reference while rebuilding somewhere else. It's the wrong move as a way to escape Webflow pricing for a site the team still edits.
Pros
- Cheap to host once exported
- A full backup of design and copy
- No platform dependency for a finished microsite
- A precise reference for a rebuild
Cons
- No CMS, forms or ecommerce
- Hard-to-edit generated code
- Every change means editing HTML
- Redirects and sitemap must be rebuilt by hand
If cost is the reason you're looking at the export, compare the real options first: a cheaper Webflow plan, a rebuild in code or a different builder. Our Webflow vs Next.js comparison helps you decide which platform fits, and Webflow to Next.js migration cost shows what a rebuild involves.
