Webflow Release Notes

The translatable parameter introduced on July 27 couldn't express the workflow it was built for, so its shape has changed.

Why it changed

A translation integration reads the primary locale to get the source text, translates it, then writes the result to a secondary locale. As originally shipped, translatable=true resolved exclusion rules against the same localeId used to select the content, which left no way to do that first step correctly:

• Requesting the primary locale returned the right content, but only matched exclusion rules scoped to "all languages" — rules scoped to a specific language were silently ignored, so you could receive content the site owner had excluded for the language you were translating into.
• Requesting a secondary locale scoped the rules correctly, but returned content that was already translated rather than the source text.

What changed

translatable now takes the id of the secondary locale you're translating into, independent of localeId:

?localeId={primary locale id}&translatable={target locale id}

• translatable=true and translatable=false now return a 400. Pass a locale id, or omit the parameter entirely.
• The value must be the id of one of the site's secondary locales. The primary locale id, or any other value, returns a 400.
• localeId is optional. Omitting it returns the primary locale's content, filtered for the target locale — the common case for a translation integration. …

Site owners can exclude specific fields, properties, or canvas content from AI translation using the Localization panel in the Designer. These endpoints now expose those exclusion rules through a new translatable query parameter. Translation pipeline integrations can fetch exactly the content that should be translated, without tracking exclusion rules themselves.

New parameter

Pass translatable=true along with a secondary locale to return only content that hasn't been excluded from translation for that locale:

• Get page content: returns only page fields not excluded for the requested locale.
• Get component content and get component properties: return only canvas content and properties not excluded for the requested locale.
• List and get collection items, including their live counterparts: return only collection fields not excluded for the requested locale. …

Site owners can exclude specific fields, properties, or canvas content from AI translation using the Localization panel in the Designer. These endpoints now expose those exclusion rules through a new translatable query parameter. Translation pipeline integrations can fetch exactly the content that should be translated, without tracking exclusion rules themselves.

New parameter

Pass translatable=true along with a secondary locale to return only content that hasn't been excluded from translation for that locale:

• Get page content: returns only page fields not excluded for the requested locale.
• Get component content and get component properties: return only canvas content and properties not excluded for the requested locale.
• List and get collection items, including their live counterparts: return only collection fields not excluded for the requested locale. …

A minor (maintenance) release to improve how the Webflow MCP works with Claude. Three groups of actions moved out of two large tools into focused tools of their own. The actions themselves are unchanged (same inputs, same behavior).

• Element settings. data_element_settings_tool takes over element settings and data bindings from data_element_tool: reading and writing settings, discovering bindable sources, and setting an element's tag, visibility, and DOM id (static or bound).

• Component props. data_component_props_tool takes over prop work from data_component_tool: creating, updating, and removing prop definitions, reading an instance's props, setting prop values, and resetting all props to their defaults.

• Component variants. data_component_variants_tool takes over variant work from data_component_tool: creating, duplicating, deleting, reordering, and renaming variants, and reading or setting per-variant styles.

Skills based on earlier versions of Webflow MCP may need to be updated. The skill migration guide covers the updated tools and actions.

MCP 2.0 changes what agents can do in Webflow and how. Most element, component, style, and variable operations no longer require a Designer session. This release also adds five new areas of functionality, expands several existing tools, and enforces your workspace's permissions and audit logging across every agent action. Some tools and actions were renamed or relocated; see Migrating from an earlier version below.

Build without a Designer session

In earlier versions, working with elements, components, styles, and variables required an active Designer session through the Webflow MCP Bridge App. In 2.0, those capabilities work on their own:

• Query and edit the element tree: text, styles, links, images, attributes, tags, settings, visibility, and display names, plus moving and removing elements.
• Create, transform, and manage components, including instances, props, and variants.
• Create, update, rename, and remove styles (classes and combo classes), and manage per-style variable modes.
• Create, update, rename, and delete variables (color, font family, number, percentage, size), and build and reorder collections and modes.
• Build elements on a page from a schema, insert component instances (including nested trees), and insert elements from HTML and CSS.

None of these need a Designer session anymore.

New capabilities …

DevLink Export supports a new opt-in camelCaseVariantNames setting in webflow.json that converts Style Variant names into camelCase values for the exported variant prop.

What changed

• New camelCaseVariantNames option under devlink-export in webflow.json. It's off by default, so existing exports are unaffected.
• When turned on, a Style Variant named Papaya With Whip exports as papayaWithWhip instead of the raw display name. Names that would collide, or that would otherwise produce an invalid value (a number-only name, or a JavaScript reserved word), fall back to safe, deduplicated values.

To use

Set "camelCaseVariantNames": true under devlink-export in webflow.json, then re-run webflow devlink export.

For more information, see Configuration options.

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 flag

Replaces

Available on

-n, --app-name

--project-name

cloud init, cloud deploy

-a, --app-id

-p, --project-id

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

{
  "cloud": {
    "app_id": "<Your App ID>",
    "framework": "astro"
  }
}

See the configuration reference for details. …

The new workspace_settings event allows auditors to track when AI features are enabled or disabled on a Webflow Workspace. Currently, this event is triggered only when the AI enablement setting changes, not on any other Workspace setting changes.

Here is an example API request that retrieves matching events:

curl -G https://api.webflow.com/v2/workspaces/hitchhikers-workspace/audit_logs \
     -H "Authorization: Bearer <token>" \
     -d limit=100 \
     -d offset=0 \
     -d eventType=workspace_settings \
     --data-urlencode from=2025-06-22T16:00:31Z \
     --data-urlencode to=2025-07-22T16:00:31Z

Here is an example response:

{
  "eventSubType": "setting_updated",
  "eventType": "workspace_setting",
  "timestamp": "2026-03-03T08:07:18.358Z",
  "actor": {
    "id": "62c730cfe7412b1cf86caa4d",
    "email": "alena.messmer@webflow.com"
  },
  "workspace": {
    "id": "685c583b3b9dd5e04b2f82d3",
    "slug": "cms-fga"
  },
  "payload": {
    "setting": "ai_toggle",
    "previousValue": "false",
    "value": "true",
    "method": "dashboard"
  }
}