This is an overview of the changes to the Webflow APIs and related tools. To filter the list, select one or more tags.
Updates to DevLink Export
DevLink Export ships a major upgrade. A new webflow devlink export command replaces webflow devlink sync and walks you through setup the first time you run it. Exported components are fully-typed TSX by default, and the generated CSS is now isolated to your DevLink components via CSS @scope so it won’t leak into the rest of your app. Webflow’s native Slot element replaces DevLink Slots (with an in-canvas Convert action), and the new Attributes prop replaces Runtime Props (auto-conversion coming soon).
DevLink Export requires @webflow/webflow-cli v1.19.0 or later, on Node.js v22+.
New export workflow
- New
webflow devlink exportcommand replaceswebflow devlink sync. See Quickstart: DevLink Export. - The first run walks you through an interactive setup and saves your settings to
webflow.json, so subsequent runs — manual or in CI — execute without prompts. - New
componentsandcomponentGroupsregex filters inwebflow.jsonlet you scope the export to a subset of your library. See Configuration options. - The
webflow devlink exportcommand now requires the DevLink Export read permission on OAuth and Site API tokens.
TypeScript by default
- Exported components ship as fully-typed
.tsxfiles with JSDoc comments. Setts: falseinwebflow.jsonto opt out and emit.jsxinstead.
Style isolation and CSS structure
- New
cssScopesoption (enabled by default) wraps the exported styles in a CSS@scoperule tied to each component’s wrapper, so DevLink styles can’t leak into the rest of your app. - Categorized CSS files (
normalize,defaults,variables,tags,classes,fonts) are imported from a singleglobal.cssyou load once at your app root.
New Designer primitives
- DevLink Export now supports Webflow’s native Slot element — the recommended replacement for DevLink Slots. Existing DevLink Slots continue to work but show a deprecation warning in the Designer; use the in-canvas Convert action to migrate. See Slots.
- DevLink Export now supports the new Attributes prop — the recommended replacement for Runtime Props. Existing Runtime Props will be automatically converted soon. See Attributes.
- New supported elements: Iframe, Inline Code, and Code Block. See Supported elements.
Broader component coverage
- Nested components and any library components they depend on are automatically included in the export.
- Conditional visibility settings on elements are compiled into the exported React code (Boolean, Enum, Number, Text, and Style Variant conditions).
Defaults and cleanup
- The default export folder is now
webflow/at the root of the project (wasdevlink/). - The following options are no longer supported:
cssModules,skipTagSelectors,envVariables,overwriteModule,fileExtensions.
Migration
Existing DevLink Sync projects can upgrade by following the Migrating to DevLink Export guide. It walks through the CLI bump, .env rename, webflow.json restructure, tsconfig and import-path updates, and the Designer-side migration of Runtime Props and DevLink Slots.