About the Webflow Cloud edge environment
Webflow Cloud runs your app on Cloudflare Workers, executing code at edge locations worldwide using the Workers runtime. While it shares some concepts with traditional serverless platforms, Workers differs from Node.js environments.
This guide outlines those key differences and provides best practices to prepare your code for deployment on Webflow Cloud.
Understanding the workers runtime
Unlike traditional serverless platforms built on containers or virtual machines, Workers use lightweight V8 isolates to deliver fast, scalable, and secure performance. The Workers runtime is designed to start code instantly with minimal overhead, allowing each function to run in its own isolated, sandboxed environment. This reduces cold start times and provides strong security boundaries between executions.
Because of this architecture, there are important differences in how your app runs—especially around API support, state management, resource limits, and deployment workflows. The guides below outline what to expect and how to prepare your code for Webflow Cloud.
Edge runtime vs Workers runtime
Throughout the documentation, you may encounter the term “edge runtime.” The Workers runtime is a specific implementation of the edge runtime, and the terms are often used interchangeably.
Configure your project for deployment on Webflow Cloud.
Some frameworks need additional configuration to run as expected on Webflow Cloud.
Webflow Cloud partially supports Node.js APIs. Review your code and dependencies for compatibility.
Define environment variables in Webflow Cloud Environments.
The runtime enforces strict limits on memory, CPU, and bundle size.
Before deploying, review your code and dependencies for compatibility. If you’re migrating, pay close attention to API routes, authentication, and third-party libraries.