How to Export Code From Webflow (And Host It Anywhere)

You built something great in Webflow. The design is pixel-perfect, the animations are smooth, and your client loves it. But then you look at the hosting bill - $15 a month for a single static site on yearly billing, $25 if you pay monthly - and start wondering: can I just export this code and host it somewhere cheaper?

Short answer: yes, you can export Webflow code. But the process of getting your webflow export code running on a different host comes with some caveats that nobody warns you about until you're staring at a broken contact form. Let me walk you through the entire process - what you get, what you lose, and how to actually host your exported site on any static host.

What Does Webflow Code Export Actually Give You?

When you export code from Webflow, you get a ZIP file containing clean, semantic HTML, CSS, JavaScript, images, and fonts. It's a fully self-contained static site that you can open in a browser right from your desktop.

Here's what's inside that ZIP:

• HTML files - one per page, with clean class names and structure
• CSS - Webflow's generated stylesheets, including responsive breakpoints
• JavaScript - the Webflow.js library that powers interactions and animations (this is Webflow's runtime that handles things like scroll-triggered animations, tabs, sliders, and navbar toggling)
• Images - everything you uploaded, in the sizes configured in the Designer (worth running these through an optimizer like Squoosh or TinyPNG before deploying)
• Fonts - web fonts bundled locally (or referenced via CDN links)

The code is surprisingly readable. Webflow has gotten better over the years at generating HTML that doesn't make developers cringe. It's not hand-written quality, but it's solid - way better than what most visual builders spit out.

What You Lose After Export

Read this one closely, because it's where people get tripped up. A Webflow export is a snapshot of your static site. Anything that relies on Webflow's backend or hosting infrastructure simply won't work once you move the files elsewhere.

Things that break after Webflow code export:

• CMS content - if you used Webflow's CMS (blog posts, portfolio items, dynamic collections), none of that dynamic content gets exported. You get the template, but not the data that populates it. This is the biggest gotcha.
• Webflow forms - your contact forms will render visually, but submissions won't go anywhere. They rely on Webflow's form handling service, which only works on Webflow-hosted sites.
• E-commerce - product pages, carts, checkout flows - all of it stays behind. Webflow's e-commerce is completely tied to their hosting.
• Some interactions - basic CSS-based animations typically survive the export. Complex multi-step interactions that rely on Webflow's runtime may not work correctly.
• Site search - Webflow's native search feature won't function on an exported site.
• Localization - if you translated the site with Webflow Localization, those localized versions stay behind too.
• Password protection - page-level password protection is a hosting feature, not something baked into the HTML.

If your site is mostly static pages - a portfolio, a marketing site, a landing page - the export works great. If you're heavily using CMS or e-commerce features, you're going to have a harder time.

Which Webflow Plan Do You Need to Export Code?

Here's the part that trips up a lot of people searching for "webflow free code export" - you cannot export code on Webflow's free Starter workspace plan. Code export needs a paid Workspace plan, and a Site plan on its own won't unlock it either (Webflow's help center says so directly). The cheapest way in is the Freelancer plan at $16/month billed yearly, built for freelancers and agencies. If your team builds its own sites in-house, Core at $19/month billed yearly is the entry point.

Webflow splits its Workspace plans into two tracks: Starter, Core and Growth for in-house teams, and Freelancer and Agency for people building client sites. Quick breakdown (per webflow.com/pricing in October 2026 - check there for current rates):

Code export belongs to the Workspace, so once you pay for a Workspace plan you can export any site in it. That's handy for freelancers and agencies: one Freelancer or Agency Workspace plan covers export for every client site you keep there.

The workaround for free plan users: There isn't a clean official workaround. Some people try inspecting the page source and saving it manually, but you'll miss Webflow's bundled JS and interactions, and the code quality won't match a proper export. If you're serious about owning your code, a paid Workspace plan is the most reliable path.

How to Export Webflow Code (Step by Step)

The actual webflow code export process is straightforward once you're on the right plan. Here's how to do it:

1. Open your site in Webflow
2. Open the Main menu - click the "W" logo in the upper-left corner
3. Choose "Code export" - or skip the menu entirely and press Shift + E
4. Click "Prepare ZIP" - Webflow packages everything up (there's a "Minify HTML" checkbox in the same window if you want leaner files)
5. Download the ZIP file to your computer

There's no per-page option. The ZIP always holds the full site: all your pages, styles, scripts, and images.

Once you've got the ZIP, unzip it and you'll see a clean folder structure with your HTML files at the root level and assets organized in subfolders.

Before you move on to hosting, open the index.html file in your browser. Click around. Make sure things look right. Check your animations, hover states, and responsive layouts by resizing the browser window. Catching issues now saves headaches later.

Fixing Forms After Export

This is the number one pain point I see people run into after a Webflow code export, so it deserves its own section.

Your Webflow forms will still render - the HTML is all there - but submissions won't go anywhere, because Webflow's own form handling only works on Webflow-hosted sites. You need to swap in a third-party form backend.

Option 1: Formspree

Formspree gives you a form endpoint you can point your existing form at. Its free plan handles 50 submissions per month, though Formspree pitches that plan for testing and development.

1. Sign up at formspree.io
2. Create a new form and copy the endpoint URL
3. Back in the Webflow Designer, select your form and open the Settings panel
4. Under Send to, remove the Webflow and Email notifications destinations (they can't be combined with a custom action), then add a Custom action with your Formspree endpoint as the URL
5. Set the method to POST, save, and re-export

Doing it in the Designer means every future export ships with a working form. Hand-edit the exported HTML instead and your next re-export wipes out the fix.

Here's roughly what the form tag looks like in the export afterward (Webflow adds a few attributes of its own):

<form action="https://formspree.io/f/your-form-id" method="POST">
  <!-- your existing form fields stay the same -->
  <button type="submit">Send</button>
</form>

Option 2: Formspark / Basin / Web3Forms

These work similarly to Formspree - you get an endpoint, set it as the form's Custom action in the Designer, and submissions get forwarded to your email or a dashboard. Most have generous free tiers.

Option 3: Netlify Forms (if hosting on Netlify)

If you end up hosting on Netlify, you can just add a netlify attribute to your form tag and it handles everything automatically. But that ties you to Netlify's hosting, which may or may not be what you want.

The fix usually takes about five minutes per form. Not a big deal.

The Cost Argument: Why Agencies Are Moving Off Webflow Hosting

Let's talk numbers, because this is really what drives most people to export webflow code in the first place.

Webflow's Basic Site plan is $15 per month per site billed yearly, or $25 if you pay monthly (per webflow.com/pricing in October 2026). That's reasonable for one personal project. But if you're a freelancer or agency managing client sites, the math gets ugly fast:

• 5 client sites: $75/month ($900/year), or $125/month ($1,500/year) billed monthly
• 10 client sites: $150/month ($1,800/year), or $250/month ($3,000/year) billed monthly
• 20 client sites: $300/month ($3,600/year), or $500/month ($6,000/year) billed monthly

And that's just the Basic plan. If clients need CMS features, that's now the Premium plan (it replaced the old CMS and Business plans) at $25 per site billed yearly, which pushes 20 sites to $6,000 a year, or $9,360 billed monthly at $39 a site.

Still paying the old prices on client sites in a Freelancer or Agency Workspace? That's $14 for Basic or $23 for CMS billed yearly ($18 or $29 monthly), and those sites move to the new prices at their first renewal on or after November 16, 2026.

Meanwhile, static hosting for exported Webflow sites costs a fraction of that - often free for low-traffic sites, and a few dollars per site at scale. The Workspace plan that unlocks code export is a recurring cost too, starting at $16/month billed yearly. Move two client sites off Basic onto a free static host like Cloudflare Pages and it pays for itself.

Hosting Your Exported Webflow Site

Once you've got your exported ZIP file and fixed up any forms, you need somewhere to put it. Since exported Webflow sites are purely static - HTML, CSS, JS, and images - any static hosting platform will work. If you're looking for the fastest way to get an exported site live, check out how to host an HTML file online - the same approach works for exported Webflow projects. Here are a few solid options:

GitHub Pages (Free, Developer-Friendly)

Push your exported files to a GitHub repository, enable GitHub Pages in the repo settings, and you've got a live site. It's free for public repos, with a 1 GB site limit and a soft bandwidth limit of 100 GB a month. The downsides: it's built around a Git workflow, and GitHub's own docs say Pages isn't meant to be free hosting for an online business or e-commerce site. Great for your own portfolio, a gray area for a paying client's business site.

Netlify (Free Tier, More Features)

Netlify's free plan comes with automatic HTTPS, form handling built in, and a monthly allowance of 300 credits that a small static site rarely gets near. One thing to know for client work: once the month's credits run out, Netlify pauses every project on the account. You can drag and drop your folder onto their deploy screen or connect a Git repo. The dashboard has a lot going on though, which can feel heavy if you just want to host a static site.

Cloudflare Pages (Free Tier, Fast CDN)

Cloudflare Pages gives you unlimited bandwidth on the free tier and sits on Cloudflare's global CDN. Great performance, and you can connect a Git repo or upload the folder directly, but it all happens inside a dashboard that's really a full DNS and security console.

Hostsmith (Drag-and-Drop, Fast CDN)

Me? I usually just want the thing to work. Hostsmith is built for exactly this use case - take your exported Webflow code ZIP, drag it onto the page, and get a live URL in under a minute. No Git, no build configuration, no framework selection screens.

Your site gets served from a global CDN, so it loads fast regardless of where your visitors are. The Free plan gives you one site with 5,000 monthly visitors on a hostsmith.link address and 5 MB of storage (also the cap on a single upload), so it suits a lean landing page or a quick client preview. An image-heavy portfolio export will outgrow it fast. If you're managing multiple client sites, or any of them needs its own domain, you'll want Pro: $15/month billed yearly ($21 monthly) for 5 sites, 5 custom domains, 500 MB of storage and 100,000 monthly visitors. That's a fifth of the $75/month those five sites would cost on Webflow Basic billed yearly (you'll still need a Workspace plan for the exports, if you don't already pay for one).

For agencies doing the Webflow-export workflow regularly, this is probably the fastest path from "I have a ZIP file" to "here's the live URL."

If you want a deeper comparison of drag-and-drop platforms, I put together a breakdown of drag-and-drop website hosting options that covers the workflow differences in detail.

Making Your Exported Site Look Professional

A few finishing touches that separate an exported-and-dumped site from one that feels intentional:

• Custom domain - a .webflow.io URL screams "template site." Even after export, set up a custom domain on whatever host you choose. If you're building a portfolio website, this is especially important for making a strong first impression.
• Favicon - Webflow exports include your favicon, but double-check it's there. A missing favicon is a small thing that clients notice.
• Meta tags and OG images - open your HTML files and make sure your page titles, descriptions, and social sharing images are set correctly. Webflow exports these, but it's worth verifying.
• Performance check - run your exported site through Google PageSpeed Insights. Without Webflow's tracking scripts, you might actually see better scores than you did on Webflow hosting.
• SSL/HTTPS - any decent static host gives you free SSL automatically.

When You Should NOT Export From Webflow

I'm not going to pretend that exporting is always the right call. Keep your site on Webflow hosting if:

• You rely heavily on Webflow CMS - blog posts, dynamic collections, content that non-technical team members update regularly. There's no clean way to replicate this with a static export.
• You use Webflow E-commerce - the entire shopping experience is tied to Webflow's hosting.
• Your client needs to edit content themselves - a Webflow client seat lets clients make text and image changes on their own (the old Legacy Editor was retired in August 2026). This goes away with an export.
• You need Webflow's form handling - if setting up Formspree or a similar service feels like too much friction, keep the built-in forms.

The sweet spot for export is static marketing sites, landing pages, portfolios, and event pages - anything where the content is set once and doesn't change frequently.

Frequently Asked Questions

Here are the most common questions people ask about how to export code from Webflow.

Can I export Webflow code for free?

No. You need a paid Workspace plan to access the webflow export code feature. The cheapest is Freelancer at $16/month billed yearly ($24 monthly), and in-house teams can use Core at $19/month billed yearly ($28 monthly), per webflow.com/pricing in October 2026. The free Starter plan doesn't include code export, and a Site plan on its own doesn't either.

Does Webflow export CMS content?

No. Dynamic CMS content - blog posts, portfolio items, anything stored in a Collection - isn't part of the code export. Collection lists show their empty state, and anything bound to a CMS field comes out blank. You can still get the data out separately: in the CMS panel, open a Collection and click Export to download its items as a CSV (rich text comes out as HTML, images as Webflow-hosted URLs). From there you can rebuild those pages by hand or feed the CSV into a static site generator.

Will my Webflow interactions still work after export?

Basic interactions and animations usually work because the exported code includes the Webflow.js library. However, some complex multi-step interactions may not function correctly outside of Webflow's hosting environment. Always test thoroughly after export.

Can I re-import exported code back into Webflow?

No. Webflow's code export is one-way. You cannot take an exported HTML/CSS/JS package and import it back into the Webflow Designer. Keep your Webflow project intact in case you need to make design changes later.

How often can I export my Webflow site?

As often as you like, as far as I can tell - Webflow doesn't publish a cap on exports. Many designers iterate in Webflow, export, and re-deploy whenever they make changes. It's a bit of a manual process, but it works.