Working with Webflow Cloud

Limits

Overview

This page lists the resource limits and constraints for Webflow Cloud projects. Use these tables to understand the maximums for projects, environments, assets, storage, and other resources. Limits may vary by plan and are subject to change.

App limits

Project limits

TypeLimitDescription
Projects per site5 (Free, Basic)
15 (CMS, Business)
50 (Enterprise)		Projects are connected to a GitHub repository and contain environments.
GitHub repository connections1 per siteA GitHub repository can only be connected to one project within a Webflow site.
Active environments10Maximum number of environments per project.
Supported frameworksNext.js, AstroCurrently supported web frameworks.

Environment limits

ResourceLimitNotes
Worker size10 MBMaximum bundle size per deployment.
Worker CPU time30 secondsMaximum execution time per request.
Worker memory128 MBMaximum memory per worker instance.
Worker startup time400 msMaximum cold start time.
Environment variables100Maximum per environment.

See Cloudflare Workers documentation for more details.

Asset limits

Asset typeSize limitDescription
Images20 MBMaximum size per image file.
Videos1 GBMaximum size per video file.
3D Models500 MBMaximum size per 3D model file.
Other static files20 MBMaximum size for other static assets.

Request handling limits

Limit typeValue
Request body size500 MB
Request headers32 KB total, 16 KB per header
Response body sizeUnlimited
Response headers32 KB total, 16 KB per header
Request timeout30 seconds
URL size16 KB
Simultaneous outgoing requests6
Subrequests per request1,000

Requests exceeding these limits are rejected with a 413 (Request Entity Too Large) error.

Header behavior limitations

Webflow Cloud’s infrastructure enforces specific header behaviors that can override custom settings. These behaviors are:

Header typeDirectionBehavior
Cache-ControlResponseAlways replaced with private, no-cache
Cache-ControlRequestStripped by Webflow Cloud
cache-tagResponseRemoved from responses
x-wf-usys-gate-group-accessResponseRemoved from responses
x-wf-usys-variantResponseRemoved from Vary header
HSTS headersResponseConditionally added by Webflow

Caching implications

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.

Retention periods

The following table shows how long different types of deployment and log data are retained, based on your Webflow Cloud plan:

TypeStarter, BasicCMS, BusinessEnterprise
Previous deployments1 hour1 day3 days
Deployment logs1 hour1 day3 days
Runtime logs1 hour1 day3 days

Storage limits

Storage for Webflow Cloud is currently in private beta

Limits are subject to change.

Bindings

FeatureLimit
Maximum bindings per Webflow Cloud app5,000

SQLite

FeatureLimit
Databases per app50,000
Maximum database size10 GB
Queries per invocation1,000
Columns per table100
Rows per tableUnlimited (subject to storage limits)
String/BLOB/table row size2 MB
SQL statement length100 KB
Bound parameters per query100
Arguments per SQL function32
LIKE/GLOB pattern length50 bytes
SQL query duration30 seconds
File import size5 GB

Key Value Store

FeatureLimit
Reads per dayUnlimited
Writes to different keys per dayUnlimited
Writes to same key1 per second
Operations per invocation1,000
Namespaces1,000
Storage per accountUnlimited
Storage per namespaceUnlimited
Keys per namespaceUnlimited
Key size512 bytes
Key metadata1,024 bytes
Value size25 MiB
Minimum cache TTL60 seconds

Object Storage

FeatureLimit
Data storage per bucketUnlimited
Buckets per account1,000,000
Management operations per bucket¹50/sec
Object key length1,024 bytes
Object metadata size8,192 bytes
Object size5 TiB per object
Upload size5 GiB (multipart uploads supported)
Upload parts10,000
Concurrent writes to same object1/sec