This page lists the resource limits and constraints for Webflow Cloud apps. Use these tables to understand the maximums for apps, environments, assets, storage, and other resources. Limits may vary by plan and are subject to change.
Accounts are limited in the number of apps that they can deploy to sites and Workspaces.
See Cloudflare Workers documentation for more details.
Requests exceeding these limits are rejected with a 413 (Request Entity Too Large) error.
The Webflow Cloud infrastructure enforces specific header behaviors that can override custom settings. These behaviors are:
Webflow Cloud overrides custom cache headers from your application. Once content is cached, you can’t control caching behavior through standard HTTP headers like Cache-Control.
This means traditional cache invalidation methods won’t work - you’ll need to work within Webflow Cloud’s caching behavior rather than trying to override it.
The following table shows how long different types of deployment and log data are retained, based on your Webflow Cloud plan: