Configuration

Webflow Cloud is designed to handle most of your deployment configuration, so you can focus on building your app. This page explains what’s configured automatically and what you need to know if you want to understand or troubleshoot the process.

For step-by-step setup use the following guides:

Getting Started

Get started with Webflow Cloud by following our step-by-step guide.

Bring your own app

Migrate an existing project to Webflow Cloud.

Deployment details

Webflow Cloud runs your app on Cloudflare Workers.

When you deploy your environment, Webflow Cloud uses Wrangler, Cloudflare’s official command-line tool, to deploy your app to the Workers platform using a default configuration.

Since the Workers runtime differs from the standard Node.js environment, some frameworks may require additional setup—such as framework-specific adapters or configuration files—to function properly. The required configurations for supported frameworks are outlined below.

Default configuration

When you deploy an environment in Webflow Cloud, Webflow automatically sets up the necessary configuration for deployment to the Workers platform.

wrangler.json

On deployment, Webflow Cloud generates a wrangler.json file based on the framework specified in your webflow.json. This file includes recommended defaults for:

• Asset handling
• Node.js API compatibility
• Observability (for example, logging and metrics)

Webflow Cloud will generate a default configuration when you deploy your app. This production file is generated automatically and can’t be edited directly.

Storage resources

Webflow Cloud supports adding storage resources to your environment. by declaring bindings in your wrangler.json file. Webflow Cloud will read these bindings and create the necessary resources for your app. All other configuration options remain automatically managed by Webflow Cloud and can’t be edited directly.

1
{
2
  "$schema": "node_modules/wrangler/config-schema.json",
3
  "name": "nextjs",
4
  "main": ".open-next/worker.js",
5
  "compatibility_date": "2025-03-01",
6
  "compatibility_flags": [
7
    "nodejs_compat"
8
    ],
9
  "assets": {
10
    "binding": "ASSETS",
11
    "directory": ".open-next/assets"
12
  },
13
  "observability": {
14
    "enabled": true
15
  },
16
17
  // Storage resources = Beta
18
  "kv_namespaces": [
19
    {
20
      "binding": "KV",
21
      "id": "1234567890" // Webflow Cloud will automatically generate an ID for your environment
22
    }
23
  ],
24
  "d1_databases": [
25
    {
26
      "binding": "DB",
27
      "database_name": "my-database", 
28
      "database_id": "1234567890", // Webflow Cloud will automatically generate an ID for your environment,
29
      "migrations_dir": "./migrations" // Specify the directory containing your migrations
30
    }
31
  ]
32
}

For more details on Wrangler configuration, see the Wrangler documentation.

Framework-specific files

Some frameworks require additional configuration to run on the Workers runtime (such as Cloudflare adapters or runtime-specific settings). Webflow Cloud handles this differently depending on how your project was created:

• New projects using the Webflow Cloud CLI
  The CLI scaffolds any necessary files automatically when you create a new project.

• Existing projects (bring your own app)
  Follow the bring your own app guide to ensure all required files are present in your project.

1
/* eslint-disable @typescript-eslint/no-empty-interface */
2
// Generated by Wrangler
3
// by running `wrangler types --env-interface CloudflareEnv cloudflare-env.d.ts`
4
5
interface CloudflareEnv {}

Troubleshooting and common questions