Stagepass
GitHub

Compare · Component sync

Stagepass vs. Webflow DevLink.

DevLink and Stagepass do different jobs. DevLink moves components between Webflow and React. Stagepass loads your own scripts and styles on a Webflow site while you test.

The short answer
DLWebflow DevLink
Component sync

Made for React developers who want their components in the Webflow Designer, or Webflow components inside a React app.1

SpStagepass
CLI and loader

Made for Developers who write plain scripts and styles for a Webflow site and test them on the live URL.

  • What moves DevLinkReact components, in both directions1 StagepassYour own scripts and styles2
  • Where it runs DevLinkDesigner library or your React app3 StagepassYour real live URL, only for you4
  • Setup DevLinkWebflow CLI with token or OAuth5 StagepassOne loader script and attributes6

See both workflows side by side

Workflow

The same job, step by step.

If you work with DevLink today, its steps are your usual flow. Next to each one is the same job with Stagepass.

DLWith DevLink
SpWith Stagepass

DevLink1 · Write

Build components in React

Work in your own React project. Exported Webflow components land in ./webflow by default.7

Stagepass1 · Write

Code in your own editor

Link a project folder once. It is served at https://my-project.sp with SSL, so you keep your files, Git and build step.8

DevLink2 · Test

Share them as a library

Code components are bundled and shared as a Workspace library, then installed through the Libraries panel.9

Stagepass2 · Test

Test on your real URL

Open the live site with ?stagepass=. Only your browser loads the local files, every visitor keeps production.4

DevLink3 · Go live

Import again, then publish

After changes, import the library again and publish the Webflow site.3

Stagepass3 · Go live

Ship with your usual deploy

Upload the build to your hosting or CDN and bump data-stagepass-v. No extra publish step for testing.10

Point by point

Side by side.

TopicDevLinkStagepassthis site
What it is Component bridgeOfficial Webflow tooling to import React components into Webflow as code components, and to export Webflow components to React code.1 CLI and loaderAn open source CLI and browser loader. Tagged scripts and styles on your Webflow site load from a folder on your Mac, only in your browser.2
Where you write code Your React projectIn your own React project. Exported Webflow components land in a local folder, ./webflow by default.7 Your own editorYour own editor. The folder you link is served at https://<name>.sp with SSL.8
Where code runs while you test Designer or React appImported code components are used in the Webflow Designer from a shared Workspace library. Exported components run in your own React app.3 Your real live URLYour real Webflow URL, only in a browser with an active ?stagepass= session. Visitors keep getting production.4
Setup on the Webflow site Webflow CLIAuthenticate the Webflow CLI with a token or OAuth, then import or export components. The old sync command was removed.5 One script and attributesOne loader script in the head code, plus data-stagepass and data-src or data-href on the tags you want to swap.6
Where production files live Workspace libraryImported code components are bundled with Webpack and shared as a Workspace library, installed through the Libraries panel.9 Your hosting or CDNYour own hosting or CDN. The production URL stays in data-src. Stagepass hosts nothing.6
Going live Import, then publishImport the library again after changes, then publish the Webflow site. Exported React code ships with your own app.3 Your usual deployUpload your build as usual and bump data-stagepass-v so browsers fetch the new file.10
Requirements Node.js 22 or newerComponent export needs Node.js 22 or newer and Webflow CLI 1.19.0 or newer.7 macOSmacOS, Node.js 18 or newer and Homebrew. Setup installs Caddy, PHP and Dnsmasq.11
License and cost Paid planComponent export needs a paid Workspace plan, or a CMS, Business or Ecommerce Site plan.7 MIT, freeOpen source under the MIT license, free to use.12

When each one fits

Pick the tool for the job.

DLPick DevLink if

  • You build React components and want them in the Designer
  • You want Webflow components inside a React app
  • You want to stay within official Webflow tooling1

SpPick Stagepass if

  • You write plain scripts and styles, no React needed
  • You test on the live URL from your own editor
  • You keep your own hosting and deploy

Switching

Using both side by side.

The two tools do not compete for the same files, so many projects can use both.

  1. 1Keep your React components in DevLink as they are.
  2. 2Put page scripts and styles in a project folder and run stagepass link.
  3. 3Add the Stagepass loader and tag those script and style tags with data-stagepass.
Getting started How sessions stay private Webflow custom code in VS Code

More comparisons

Other ways to work.

Status and sources Checked on · 12 sources

We check every statement on this page against its public source once a month. Each small number in the text points to a source below, with a link to the original page and, where one exists, an archived copy on the Internet Archive.

Stagepass is not affiliated with Webflow DevLink. Tools change over time. If something here is out of date or unfair, open an issue.

  1. 1 Webflow developer docs, DevLink overview DevLink developers.webflow.com Archived 23 Oct 2026
  2. 2 Stagepass README Stagepass github.com
  3. 3 Code components quick start DevLink developers.webflow.com
  4. 4 Stagepass README, dev mode Stagepass github.com
  5. 5 Webflow CLI reference DevLink developers.webflow.com Archived 15 Jul 2026
  6. 6 Stagepass README, tagging scripts Stagepass github.com
  7. 7 DevLink export quick start DevLink developers.webflow.com Archived 15 Jul 2026
  8. 8 Stagepass CLI README Stagepass github.com
  9. 9 Code components, bundling and import DevLink developers.webflow.com Archived 4 Sep 2026
  10. 10 Stagepass MIGRATION.md Stagepass github.com
  11. 11 Stagepass setup.js Stagepass github.com
  12. 12 Stagepass LICENSE Stagepass github.com