1 · 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.
Compare
Hosted editors, Webflow's own tools, proxies and a plain local server. Find the workflow you use today and see the same job with Stagepass, side by side.
A hosted code editor for Webflow with AI help, staging and production files.
Fits when you prefer a hosted editor with AI help.
See the comparisonWebflow's official bridge between Webflow components and React code. A different job than swapping scripts.
Fits when you build React components and want them in the Designer.
See the comparisonPaste code into the head and body fields or a Code Embed, then publish to the webflow.io staging domain to test.
Fits when you add a few lines of code.
See the comparisonPoint a script tag at localhost, or put your dev server on a public tunnel URL such as ngrok.
Fits when you test on a staging copy anyway.
See the comparisonAn open source CLI that proxies your webflow.io site locally with Vite and can publish custom code to Webflow.
Fits when you want one tool that also publishes to Webflow.
See the comparisonAn open source Bun and Vite starter that proxies your Webflow staging site through localhost.
Fits when you start a new project.
See the comparisonAt a glance
| Tool | Type | Where code runs while you test |
|---|---|---|
| SpStagepassthis site | Open source CLI and loader | Your real live URLYour real Webflow URL, only in a browser with an active ?stagepass= session. Visitors keep getting production.1 |
| SlSlater | Hosted editor | webflow.io stagingStaging files on your webflow.io domain, production files on your custom domain.2 |
| DLWebflow DevLink | Component sync | 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 |
| CCWebflow custom code and staging | Built into Webflow | Preview or stagingTurn on custom code in preview, or publish to the webflow.io staging subdomain, since some scripts only run on a published site.4 |
| DSLocal dev server and tunnel | Do it yourself | Wherever the tag is publishedWherever the script tag is published. From Chrome 142, a public page that requests a local or loopback address triggers a Local Network Access permission prompt, also for scripts.5 |
| wfwfkit | Open source CLI | localhost proxyA local proxy of your published webflow.io site, with your local Vite scripts injected.6 |
| VfViteflow | Open source starter | localhost proxyIts dev server proxies your Webflow staging site through localhost and injects the local script.7 |
The Stagepass way
1 · Write
Link a project folder once. It is served at https://my-project.sp with SSL, so you keep your files, Git and build step.
2 · Test
Open the live site with ?stagepass=. Only your browser loads the local files, every visitor keeps production.
3 · Go live
Upload the build to your hosting or CDN and bump data-stagepass-v. No extra publish step for testing.
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 any of the tools compared here. Tools change over time. If something here is out of date or unfair, open an issue.