Webflow Export Code Server-Side Execution Support Boundaries

Webflow's Export Code feature generates static HTML, CSS, and JavaScript files intended for deployment to any static hosting provider. The documentation confirms the output is purely client-side, but does not explicitly define which dynamic interactions—such as CMS collection rendering, form handling via Webflow's native endpoints, or Ecommerce cart logic—remain functional after export without additional server-side infrastructure.

For a low-traffic site relying on CMS-driven content and simple forms, the goal is to eliminate the recurring hosting fee by moving to a free static tier. The constraint is that Webflow's Lite plan still charges for hosting regardless of traffic, while the export path introduces uncertainty about which features degrade or break when no Webflow runtime is present. Free static hosts also impose bandwidth and request limits that could shift costs unexpectedly if traffic grows.

Which Webflow-native dynamic features are documented as unsupported in a fully static export? Does the exported Form Block continue to submit to Webflow's endpoints, or must it be rewired to a third-party handler? Are there published limits on CMS item counts or collection list pagination that apply only after export?