How to Export Webflow Code: Native vs URL Export

There are two practical ways to export Webflow code: use Webflow's native Export code feature from the project, or capture the frontend from a published URL. They solve different access problems and neither automatically replaces every Webflow service.

For a URL-based export, open the Webflow to HTML exporter near the start of your migration. For the native path, follow Webflow's current official code export documentation.

Quick comparison

Method 1: export code from Webflow

Requirements

Webflow states that code export requires a paid Workspace plan. A Site plan alone is not the same requirement. Check the current Workspace permissions and pricing before upgrading because plan details can change.

Steps

1. Open the site in Webflow Designer.
2. Select the code export option from the project interface.
3. Prepare the ZIP and download it.
4. Unzip the package into a new version-controlled folder.
5. Open the HTML locally through a development server and review every page.

The download normally includes HTML for static pages plus CSS, JavaScript, images, and other project assets that Webflow includes in its export.

What native Webflow export excludes

According to Webflow's official documentation, exported code does not carry every hosted feature. Plan separately for:

• CMS content and CMS functionality;
• user accounts and gated-user functionality;
• ecommerce databases and ecommerce functionality;
• localized content beyond the primary locale;
• site search;
• Webflow form processing and reCAPTCHA;
• password protection;
• code components.

The visible markup of a form or collection page is not the same as the backend that powers it. Map each excluded feature to a new CMS, form handler, search service, commerce platform, or application backend before changing DNS.

Method 2: export a published Webflow URL

A URL exporter works from what a visitor can load, so it can be useful when the site is public and you have permission but do not have the required Workspace plan.

1. Publish the latest approved Webflow version.
2. Remove password protection only if doing so is authorized and safe.
3. Paste the public URL into the Webflow exporter.
4. Download the ZIP and keep an untouched archive.
5. Review the crawl list, files, external requests, and browser console.

URL export captures the published result rather than the original project model. It cannot recover unpublished pages, Designer components, CMS relationships, credentials, server-side code, or private data.

CMS migration

Choose the destination before launch: a new headless CMS, WordPress, another application database, or static content maintained in files. Export CMS records through an authorized Webflow data workflow where possible; do not rely on scraping visible cards as the only copy.

For each collection, preserve:

• field names and types;
• slugs and relationships;
• images and their usage rights;
• collection-template URLs;
• titles, descriptions, canonicals, and structured data;
• redirects for any changed URL.

Forms, search, and ecommerce

Replace Webflow form processing with a form service or backend you control. Reconnect validation, spam protection, email notifications, consent records, success/error states, and data retention.

Rebuild site search against the new content source. Treat ecommerce and user accounts as application migrations, not static-export tasks; orders, customers, inventory, authentication, and payments need dedicated systems and testing.

Interactions and JavaScript

Some published interactions may continue when their required Webflow scripts and attributes are present. Test instead of assuming. Check scroll triggers, menus, sliders, tabs, modals, hover states, reduced-motion behavior, and touch input. Remove a script only after verifying it is not required.

Assets, fonts, and external dependencies

Confirm which images, videos, fonts, CSS, and scripts are local and which still load from Webflow or another provider. Download assets you are licensed to host, update references, and preserve responsive image behavior. Review font and stock-asset licenses before moving them.

SEO migration checklist

• Preserve useful page paths or add direct permanent redirects
• Keep one self-canonical URL per page
• Restore titles, descriptions, headings, Open Graph, and required JSON-LD
• Generate a sitemap containing only final canonical URLs
• Check robots rules and remove staging noindex before launch
• Keep analytics and consent configuration valid for the new host
• Test broken links, missing assets, status codes, and 404 behavior

Deployment checklist

1. Run the exported site on a local or test server.
2. Compare important templates at desktop and mobile widths.
3. Test navigation, forms, interactions, CMS replacements, and third-party embeds.
4. Measure the exported site with browser tools; optimization gains vary by page and hosting setup.
5. Deploy to a staging URL, crawl it, and verify headers and redirects.
6. Change DNS only after the test deployment passes review, then monitor logs and Search Console.

Use native export when you have project access and the correct Workspace plan. Use a URL export when the published frontend is the available source. In both cases, inventory Webflow-only services and migrate them deliberately.

Related resources

• Webflow to HTML exporter
• What breaks when you export Webflow
• Website code exporter