Quickstart: DevLink Export
Quickstart: DevLink Export
In this guide, you’ll learn how to configure DevLink and export Webflow components to a React project. This guide uses Next.js, but you can export and use components in any React-based framework.
Prerequisites
Before running this quickstart, make sure you have:
- A Webflow account and Webflow site with components to export.
- A paid Workspace plan or a CMS, Business, or Ecommerce Site plan.
- Node.js v22 or higher and
npminstalled. @webflow/webflow-cliv1.19.0 or later (installed in step 2).- Basic familiarity with React.
1. Prepare your Webflow components
DevLink exports Components only, not every element on the canvas. If the elements you want to export aren’t components yet, convert them first:
- Select an element or group of elements.
- Right-click the elements and then click Create Component.
- Give the component a clear, descriptive name.

2. Set up your React project
3. Export your components
Run the export
From the root of your React project, run:
The first time you run it, the CLI authenticates you in your browser and walks you through a short setup. Accept the defaults to export every component into a ./webflow folder with style isolation enabled, or follow the prompts to filter by component name or group. Your answers are saved to webflow.json so future runs don’t prompt again — see Configuration options to tune them later.
The CLI populates the webflow/ folder with your React components, the generated stylesheets, a DevLinkProvider for runtime wiring, and the supporting modules they depend on. See What’s exported for the full breakdown.
Verify the exported code
Look for @warning tags that indicate that DevLink was not able to export an identifier, as described in Name changes.
4. Use the exported components
Configure import aliases
Add a webflow/* alias to the paths section of your tsconfig.json so you can import the exported components by name instead of using long relative paths:
With the alias in place, import { Button } from 'webflow/Button' resolves to your local ./webflow/Button file from anywhere in the app.
Add the global styles and provider
In your app/layout.tsx file, import the global CSS file generated by DevLink so all components have the styles and resets they expect. If your Webflow components have interactions, also wrap your app in the DevLinkProvider to enable them at runtime:
Use a component
Now you can import and use your Webflow components in your application. This particular example uses three components exported from Webflow via DevLink: Hero, Card, and Button:
Updating your components
When you make changes to your components in Webflow, run the export again to refresh them in your React project:
The command refreshes the files in webflow/. Your own application code outside that folder is untouched.
You can also run the export in CI by setting WEBFLOW_API_TOKEN in your CI environment and adding the --no-input flag:
Common issues and solutions
Authentication Error
If you encounter authentication issues:
-
Verify that your API token has the correct permissions
-
Verify that the token has access to the site whose ID is set in
webflow.json(a Site API token only authorizes that one site; a Workspace API token authorizes every site in the workspace) -
Ensure that your environment variables are properly loaded
-
Check that the
webflow.jsonfile is in the root directory of the React application -
If all else fails, force a fresh login to clear any stale credentials:
Missing Styles
If your components don’t look the same as in Webflow:
- Ensure that you’ve imported
css/global.cssin your application - Verify that the
DevLinkProviderelement is properly set up — it loads Google and Adobe fonts at runtime - Check for CSS conflicts with other styles in your project
Component Not Found
If a component isn’t available after exporting:
- Make sure it’s properly created as a component in Webflow
- Make sure that the rules in the
devlink-exportobject in thewebflow.jsonfile match it - Check that it uses only supported elements