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:

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.jsonc

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

  • Asset handling
  • Node.js API compatibility
  • Observability (e.g., logging and metrics)

While you can make local changes to the wrangler.jsonc file, Webflow Cloud will generate a default configuration when you deploy. This production file is generated automatically and can’t be edited directly.

wrangler.jsonc
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}
Custom bindings to Cloudflare services aren't available through Webflow Cloud

Custom bindings to Cloudflare services (like KV, Hyperdrive, D1) aren’t currently supported. Use external services via HTTP APIs. This may change in the future.

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.

Next.js apps require the following files:

  • cloudflare.env.ts: Enables your app to access your environment variables.
  • .open-next.config.ts: Enables Next.js to run on the edge runtime.
  • next.config.js: Ensures your app uses your environment’s mount path and the Cloudflare adapter.
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
5interface CloudflareEnv {}

Troubleshooting and common questions

Webflow Cloud manages this file to ensure compatibility and security.

If you’re migrating an existing project, follow the steps in the Bring your own app guide.