The ZIP covers the static site
The code export includes page files, three CSS files, Webflow JavaScript, and assets from the Assets panel. Collection templates appear as empty pages, and the export only includes the primary locale.
Self host Webflow with the design your customers know and the marketing features your team still needs. Use the Agentic Website Template to turn your exported site into an owned Next.js repository, reconnect content and lead capture, and deploy through your own hosting account.
Webflow can export HTML, CSS, JavaScript, images, and static pages from a paid Workspace plan. Your live site may also rely on Collections, forms, site search, localized routes, user access, ecommerce, and Webflow hosting. Those parts need clear replacements before the domain moves.
Use the templateThe code export includes page files, three CSS files, Webflow JavaScript, and assets from the Assets panel. Collection templates appear as empty pages, and the export only includes the primary locale.
Collection content can be exported separately as CSV. Dynamic routes, Collection layouts, accounts, ecommerce, password protection, and localized pages must be rebuilt or connected to services you choose.
Webflow form processing, file upload, reCAPTCHA, and site search do not operate on an exported site. Each form destination, search experience, analytics script, redirect, and integration needs to be reconnected and tested.
The Agentic Website Template provides the structure around your exported design. Your AI coding agent can rebuild the pages as maintainable components, connect the content and lead systems, preserve useful URLs, and leave your team with a site it can keep editing after launch.
See the three ways to use the templateOwn the website
Pages, components, routes, styles, and project instructions live in a codebase your team controls. Deploy through your own hosting account and choose the content, analytics, and form services that fit your work.
Move Webflow Collections
Map Collection fields and CSV exports into routes, templates, rich text, images, references, and metadata. Start from the included blog pattern or connect the content source your marketing team prefers.
Reconnect lead capture
Replace Webflow form processing with the included form route or a provider you choose. Preserve the visible fields and success states, then verify delivery, spam protection, consent, and campaign context.
Keep search traffic
Render useful content and navigation in the page HTML. Carry over page titles, descriptions, canonical URLs, structured data, internal links, and direct redirects so search engines and AI agents can understand the new site.
Move the domain safely
Test routes, Collection pages, forms, search, scripts, mobile layouts, redirects, analytics, crawl settings, and production configuration. Review the working deployment before sending your existing domain to the new host.
Start with the live site, the Webflow exports available to you, and a list of every connected feature. Build one representative page in the Agentic Website Template, review it, then use the approved patterns for the rest of the website.
Start with the Agentic Website TemplateList every public URL, Collection, locale, form, search feature, script, redirect, protected area, and ecommerce flow. Confirm the licenses for any Webflow Marketplace template, font, image, or third-party asset.
Download the site ZIP from a paid Workspace plan. Export Collections, redirects, form records, products, or accounts separately when they apply, and save the original assets and project settings.
Ask your coding agent to read README.md and AGENTS.md, then recreate the homepage inside the starter. Review the design, responsive behavior, interactions, content, metadata, and connected form before expanding the work.
Build the remaining routes, move CMS content, reconnect lead capture and search, add redirects, and test the production configuration. Deploy through your own account, move the domain, and monitor the site.
Choose where the Next.js site runs and which tools handle content, forms, search, analytics, and customer data.
Keep the familiar design while Collection pages, localized routes, forms, redirects, and important integrations work from their new homes.
Brief Claude Code, Codex, or Cursor in plain language and review updates in a working preview before they reach production.
Straight answers for teams moving a Webflow marketing site to infrastructure they control.
Yes. Webflow says you can export HTML, CSS, JavaScript, and assets and host them anywhere. The exported site does not require Webflow attribution or an ongoing Webflow plan. A complete move must also replace the hosted features your website uses.
Webflow currently requires a paid Workspace plan for code export. A Site plan on its own does not include code export. Confirm the current plan requirements in Webflow before planning the move.
CMS content and behavior, user accounts, ecommerce databases and checkout, password protection, native form processing, file upload, reCAPTCHA, site search, localized content beyond the primary locale, and code components need to be moved, rebuilt, or reconnected.
Webflow says a paid template can be hosted on another server under its Single-Use License, which continues to apply after export. Free templates have separate terms. Review the template license and confirm permission for custom fonts, images, icons, and other third-party assets before launch.