Configure your Webflow app
The webflow.json file configures your Webflow app, defining how the CLI builds and deploys your code for each product. This file is created automatically when you run init commands, but you can modify it to customize behavior.
File location
Place webflow.json in the root of your app:
Schema
The webflow.json supports configuration for:
- Region targeting
- Code Components
- DevLink
- Webflow Cloud
- Designer Extensions
Each product has its own set of configuration options. See below for the configuration options for each product.
Region
Region targeting is available on every release channel, including stable, starting with this version.
Unlike the product-specific options below, region sits at the top level of webflow.json, alongside siteId:
The CLI resolves the active region in this order, highest priority first:
--region <us|eu>flagWEBFLOW_REGIONenvironment variableregioninwebflow.json- The region you last logged into (persisted in
~/.config/webflow/auth.json, or%APPDATA%\webflow\auth.jsonon Windows) us(default)
In a CI/CD pipeline, set the environment variable rather than editing the manifest:
See Production EU authentication for a full login walkthrough.
Code Components
DevLink
Configuration options
siteId sits at the top of webflow.json; every other option below lives under the devlink-export object.
DevLink assumes reasonable defaults for most of the settings, but you can specify certain options to customize the behavior of DevLink management and setup. See the DevLink documentation for more details.
Webflow Cloud
Legacy project_id field
Before this rename, the Webflow CLI wrote a project_id field to webflow.json. The CLI still reads project_id as a fallback, so existing manifests keep working without changes. New deploys always write app_id. A future major release will drop the legacy field — feel free to switch your manifest to app_id whenever you redeploy.