Easy Tech TutsHow to Export Webflow Code and Host It Online Easily 2026
By Impran M NLast checked against official docs
Exporting a Webflow project into plain HTML, CSS, and JavaScript is the escape hatch for anyone who wants their design without an ongoing Webflow hosting bill. The export panel itself has a catch that trips up a lot of people the first time they try it.
This guide walks through opening the Export Code dialog, understanding what your current plan gets you, and moving the result onto a static host. It also covers what quietly stops working the moment you leave Webflow's platform: forms, CMS content, password protection, and site search, so a broken contact form or a page that used to be gated isn't a surprise on launch day.
01Open the Export Code panel and check what your plan allows
In the Designer, open the Main menu (click the W logo top left) and choose Code export, or use the Shift+E shortcut. That opens a dialog with tabs for HTML, CSS, JS, and Assets.
The HTML tab shows your actual markup: navigation links, class names like w-nav-link and w-button, and the structure Webflow generated from your visual layout. It reads cleaner than the output some visual builders produce.
Read the notice below the code before you plan a workflow around it. Code export is a Workspace-plan feature, not something a Site plan alone unlocks, and on a workspace without it, what you're seeing is a limited preview rather than a downloadable package.
The dialog spells out the upgrade path plainly: a Workspace plan unlocks full code export and DevLink React components, while Site-plan features like CMS, ecommerce, forms, and search are a separate, per-site matter. Check which one applies before assuming you can download today.
02Download the export and check the folder
Once you're on a plan that supports full export, downloading gives you a zip with separate folders for CSS, JS, and images alongside your HTML pages. Open it and skim for anything obviously missing: a stylesheet that didn't generate, an empty image folder, a script reference pointing nowhere real. Catching this before you deploy saves a round of debugging on the live host later, where errors are harder to trace back to the source.
03Pick a static host and upload the files
Any host built for static files works: Netlify, Vercel, GitHub Pages, or something simpler like a drag-and-drop uploader such as Tiiny Host, which accepts a folder or a zip and gives you a live link almost immediately. The upload screen typically shows a drop zone alongside integration shortcuts for services like GitHub or Dropbox, plus a spot to claim a custom subdomain before you go live. Whichever you choose, the workflow is the same shape: drop the exported folder in, wait for the deploy to finish, and get back a URL.
04Point your custom domain at the new host
Once the files are live on a temporary subdomain, add your real domain through the host's custom domain settings and update your DNS records at your registrar to match. This step is identical to pointing any domain at any new host, and it's worth doing a test deploy on the free subdomain first so you're not debugging DNS and broken assets at the same time.
05Replace forms and dynamic features that no longer work
This is the step most people forget until launch day. Webflow disables native form submissions, CMS-bound content, and interactions tied to its own backend on exported sites, since there's no Webflow server behind the static files anymore.
Forms specifically are turned off to comply with GDPR, not left broken by accident. Point any forms at an external handler like Formspree or your static host's own form service.
If pages relied on CMS Collections for blog posts or products, that content needs rebuilding as static pages, or a headless CMS wired up separately, since Collection lists and pages just render empty on the exported site. Check password-protected pages too. Webflow enforces that protection on its own hosting; it isn't part of the exported HTML, so a page that required a password before export is publicly readable after it, unless you add your own access control on the new host.
| Feature | Works after export? |
|---|---|
| HTML, CSS, JavaScript, responsive layout | Yes |
| Images and other static assets | Yes |
| Native Webflow forms | No — needs an external form handler; disabled specifically for GDPR compliance |
| CMS Collections (blog posts, products, etc.) | No — renders empty state; rebuild as static pages or a headless CMS |
| Password-protected pages | No — protection isn't included; add your own access control |
| Site search | No |
Based on Webflow's own code-export documentation, checked September 2026.
When it doesn't work
A page that was password protected in Webflow is publicly viewable after export
Why: Webflow's password protection is enforced by Webflow's own hosting. It isn't part of the exported HTML at all.
Fix: Add your own auth, a hosting-provider password gate or server-side auth, before publishing the exported files anywhere the old content shouldn't be public.
Forms silently stop submitting after export, with no error in the browser
Why: Webflow disables native form handling in exported code to comply with GDPR, not because of a bug.
Fix: Point the form's action at an external handler like Formspree or your host's own form service.
Collection-bound content just disappears (empty state shows instead)
Why: CMS Collections rely on Webflow's database, which doesn't travel with the export. Collection lists render their empty state, and Collection pages show no bound content.
Fix: Rebuild that content as static pages before exporting, or connect a headless CMS to the exported site afterward.
Frequently asked questions
Will my Webflow forms still work after export?
No. Webflow turns off native form handling on exported sites to comply with GDPR, so point form submissions to an external service like your host's form handler or something like Formspree.
Is exporting code available on every Webflow plan?
No. Code export needs a Workspace plan; Site plans alone don't unlock it, and on a workspace without that plan the Export Code dialog only shows a limited preview.
Will my responsive layout still work after export?
Yes, the exported CSS preserves your breakpoints, so your responsive design renders the same outside Webflow.
What happens to CMS content when I export?
It doesn't come with the export. CMS Collections rely on Webflow's own database, so Collection lists show their empty state and Collection pages show no bound content until you rebuild it as static pages or connect a different backend.
What happens to password-protected pages after export?
They stop being protected. Webflow enforces that password on its own hosting, and it isn't part of the exported HTML, so add your own access control if that content still needs to be gated.
Can I still edit the site visually after exporting?
No. Once exported, the code is static. Future design changes need to happen back in Webflow with a fresh export, or directly in the downloaded code by hand.
Sources and last check
Click path, screenshots, and the hosting workflow come from a walkthrough recorded in July 2025. The Export Code entry point, the Workspace-vs-Site plan requirement, and what does and doesn't travel with the export were re-checked against Webflow's own help center in September 2026 (fetched via search indexing after Webflow's site blocked a direct page load; the quoted content came from its own official URL). That check added two things the article didn't previously mention: forms are disabled specifically for GDPR compliance, and password-protected pages lose their protection entirely on export.
About the author
Impran M N
I've been hooked on technology for as long as I can remember — especially the new tools and AI apps that seem to land every other week. Easy Tech Tuts is where I write up whatever I've just worked out: I do the task in the real product, record the screen, and turn it into the guide I wish I'd found first.
