Export Webflow components to your React codebase as production-ready code.
DevLink Export lets developers pull Webflow components directly into an external React codebase. Changes you make in Webflow stay in sync with your code, so your design system stays consistent across sites and apps. DevLink Export is set up and run through a Command Line Interface (CLI). This help page covers what DevLink Export supports, its limitations, and some additional info.
Visit the DevLink developer docs for detailed info on CLI setup, configuration options, code output structure, and TypeScript behavior.
Before you get started
DevLink Export requires a paid Workspace plan or a CMS, Business, or Ecommerce Site plan. Only Site Admins and Designers can use DevLink Export.
What DevLink Export supports
Use DevLink Export to export native Webflow components as React components, along with everything needed to render them correctly in your codebase. This includes:
-
Component properties — all properties defined on a component in Webflow are exported as React props, with full TypeScript coverage
-
Styles — global styles, variables, fonts, and component classes are included alongside your component code
-
Variable modes and collections — variable definitions export to CSS, including breakpoint overrides and element-level mode settings
-
Conditional visibility — visibility conditions set on elements are compiled into the exported React code
-
Native Component Slots — slots export as ReactNode props, letting you pass content into components from your React project
-
Nested library components — library components used inside an exported component are automatically included in the export
-
Component group filtering — export a subset of components by name or group, configured in your
webflow.json file
DevLink Export known limitations
The following aren't currently supported in DevLink Export:
-
CMS and Collection Lists — components with bound CMS content won't export fully; Collection List elements export as unsupported element placeholders
-
Interactions with GSAP — Classic Interactions are supported
-
Localization — secondary locales aren't included in exports
-
Code components — export as unsupported element placeholders
- Ecommerce, Lightbox, Lottie, Rive, and Spline elements
Migrating from the DevLink beta
If you've been using the previous DevLink beta (the devlink sync command), here's what to know:
-
Slots — DevLink Slots are deprecated and replaced by native Component Slots. Your existing DevLink Slots will continue to work but show a deprecation warning. To migrate, select the DevLink Slot element on the canvas, open the Settings panel, and click Convert.
-
Runtime props — DevLink Runtime props are being replaced by a new Attributes prop type. Existing Runtime props will be migrated automatically — no action needed.
For step-by-step migration instructions, see the DevLink migration guide in the developer docs.