Changelog

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.

The base variable mode — the default set of values that variables fall back to — is now first-class in the Designer API. It has the reserved ID "base" and, by default, the name "Base mode".

You can now work with the base mode like any other mode:

• Rename it with mode.setName(). Its ID stays "base" even after it’s renamed.
• Retrieve it by ID with collection.getVariableModeById("base"), or by its (default or renamed) name with collection.getVariableModeByName().

The Analyze API lets you read a site’s analytics. Five reports are available now:

Analyze

• Traffic: a daily time series of sessions, users, or page views over a chosen window.
• Top pages: the most-visited pages, ranked by sessions, users, or page views, with an optional per-page time series.
• Top dimensions: the top values for a dimension you choose, such as country, device, traffic source, or audience.
• Top events: the most-fired events, ranked by how often they fire, with an optional daily time series per event.
• Time on page: the average time spent on a page, as a single value or bucketed by day or week.

The Analyze API (beta) lets you read a site’s analytics. Five reports are available now:

Analyze

• Traffic — a daily time series of sessions, users, or pageviews over a chosen window.
• Top pages — the most-visited pages, ranked by sessions, users, or pageviews, with an optional per-page timeseries.
• Top dimensions — the top values for a dimension you choose, such as country, device, traffic source, or audience.
• Top events — the most-fired events, ranked by how often they fire, with an optional daily timeseries per event.
• Time on page — the average time spent on a page, as a single value or bucketed by day or week.

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

CLI 2.0 consolidates the webflow library command group into webflow devlink and raises the Node.js minimum version to 22.13.0. The commands from the previous version still work but emit deprecation warnings because they will be removed in a future version.

Breaking changes

Node.js minimum version raised to 22.13.0. Verify your Node.js version with node --version before upgrading.

DevLink Component Export now ships interactions built with the new GSAP-powered Interactions engine. Animations defined on a component, including triggers, timelines, and GSAP plugins, are exported and run in your React project with no extra setup.

What’s exported

For every component that has Interactions, DevLink now emits:

Version 1.3 of the Webflow MCP server adds over 30 new tools and actions across component authoring, branch management, styles, elements, and comments. If you are already using the MCP server, your agents and prompts automatically use this version. To start using the MCP server, see Getting started.

Components

The Data API now exposes endpoints for managing the JSON-LD schema markup attached to a page. Schema markup powers rich search results such as FAQ snippets, breadcrumbs, organization cards, and product listings. Previously, schema markup could be edited only one page at a time in the Designer.

New endpoints

Update Page Metadata no longer returns an error when the slug field can’t be applied. The request now returns 200 OK with the slug field silently ignored — all other fields in the update apply as expected.

What changed

• Home pages, collection template (detail) pages, and utility pages (e.g. 404, password, search) previously returned 400 Bad Request ("Slug of index pages can't be updated", "Collection Template page slugs cannot be updated", or "Utility page slugs cannot be updated") when a slug was included. They now return 200 OK with the slug ignored.
• Secondary locales on sites without the Advanced or Enterprise Localization add-on previously returned 403 Forbidden when a slug was included. They now return 200 OK with the slug ignored.

The Custom Fonts API adds seven new OAuth v2 endpoints under /v2/sites/{site_id}/custom_fonts. Apps can now manage a site’s custom fonts programmatically — uploading, listing, updating, replacing, and deleting fonts without any manual steps in the Webflow Designer.

For information on using custom fonts in sites, see Custom fonts.

You can now scope the List Assets endpoint (GET /v2/sites/{site_id}/assets) to return assets that are in a specified folder. In the same way, the response to this endpoint includes the folder that an asset is in.

New query parameter: folderId

Pass a folder’s ObjectId to receive only assets in that folder and all of its descendant folders. When folderId is omitted, the endpoint returns all assets on the site as before.

v1.21.0 adds a forms command group for reading form data and exporting submissions.

webflow forms list

Lists all forms on a site with their ID, display name, and slug. Supports --fields to customize columns and --json for machine-readable output.

$
webflow forms list --site <siteId>
$
webflow forms list --site <siteId> --json

v1.20.2 is a patch release with CMS UX improvements and a small auth output fix.

CMS error handling improvements

• Cleaner user errors — Invalid collection or item IDs now display a clean message and exit with code 1 instead of throwing a CLI error with a stack trace.
• Structured API error bodies — When the Webflow API returns an error, the full structured error body from the response is now included in the output, not just the HTTP status code.
• Next-steps hint after collections create — After successfully creating a collection, the CLI now prints a hint showing how to add fields to it:

  $
  webflow cms collections create --site <siteId> --name "Blog Posts"
  $
  # ✔ Collection created: Blog Posts (id: abc123)
  $
  # → Add fields: webflow cms fields create --collection abc123 --name <name> --type <type>

The Webflow AI Assistant can now generate and modify code components based on plain-language prompts. You can use the AI Assistant to generate visual and interactive components for your site, like custom sliders, pricing menus, calculators, The AI Assistant can access the styles and CMS collections from the current site and can make changes with further prompts.

v1.20.1 is a patch release with two improvements.

cloud init updated to use devlink export

The webflow cloud init command now scaffolds projects using the new webflow devlink export command. The Astro and Next.js scaffold templates have been updated to take advantage of the latest DevLink features.

v1.19.0 adds webflow devlink export, a new command that generates a static, self-contained DevLink bundle of your Webflow components as local React code that runs without a build-time connection to Webflow.

webflow devlink export

$
webflow devlink export

Key features

v1.20.0 introduces global session storage so a single webflow auth login covers all CLI commands, plus two new commands for inspecting and clearing your session.

Global session storage

Running webflow auth login now saves your credentials in two places:

• Global session file — ~/.config/webflow/auth.json on macOS/Linux or %APPDATA%\webflow\auth.json on Windows. This is shared across all projects and survives outside any specific project directory.
• Project .env file — WEBFLOW_API_TOKEN continues to be written for compatibility with existing 1.x workflows.