This is an overview of the changes to the Webflow APIs and related tools. To filter the list, select one or more tags.

CLI: app-named flags for webflow cloud and renamed manifest field

The Webflow CLI now uses app-named flags and an app-named manifest field for webflow cloud to match the “Apps” product naming. The legacy spellings keep working as deprecated aliases — you don’t need to migrate immediately.

New flags on webflow cloud

New flagReplacesAvailable on
-n, --app-name--project-namecloud init, cloud deploy
-a, --app-id-p, --project-idcloud deploy
  • --project-name and --project-id continue to work as deprecated long-form aliases. Using either prints a warning pointing at the new spelling.
  • The -p short flag for --project-id was removed in favor of -a. Long-form --project-id still works.
  • Passing both spellings together (for example, --app-name X --project-name Y) errors instead of picking one.

For full options, see the cloud init and cloud deploy reference.

Renamed webflow.json manifest field

The cloud.project_id manifest field is now cloud.app_id. New deploys write cloud.app_id. Existing manifests carrying cloud.project_id keep working — the CLI reads the legacy field transparently as a fallback, so you don’t need to update your webflow.json to keep deploying. A future major release will drop the legacy field.

webflow.json
1{
2 "cloud": {
3 "app_id": "<Your App ID>",
4 "framework": "astro"
5 }
6}

See the configuration reference for details.

Upgrading

$npm install -g @webflow/webflow-cli@latest