wfkit1 · Write
Start a Vite project
Create a project with the CLI and run the dev script in your own editor.1
Compare · Open source CLI
Stagepass vs. wfkit.
wfkit and Stagepass are both open source CLIs for local Webflow development. wfkit proxies the site to localhost and can publish code for you. Stagepass loads local files on the real URL.
The short answer
wfwfkit
Open source CLI Made for One tool that also publishes your code to Webflow, on macOS, Linux or Windows.1
SpStagepass
CLI and loader Made for Testing on the real live URL while you keep your own deploy, on macOS.
Workflow
The same job, step by step.
If you work with wfkit today, its steps are your usual flow. Next to each one is the same job with Stagepass.
wfWith wfkit
SpWith Stagepass
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.5
wfkit2 · Test
Open the local proxy
The proxy serves your published webflow.io site on localhost and injects your local Vite scripts.1
Stagepass2 · Test
Test on your real URL
Open the live site with ?stagepass=. Only your browser loads the local files, every visitor keeps production.2
wfkit3 · Go live
Publish with one command
The publish command builds, pushes to GitHub, updates the Webflow custom code and republishes the site.1
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.3
Point by point
Side by side.
| Topic | wfkit | Stagepassthis site |
|---|---|---|
| What it is | CLI and proxyA CLI for Webflow custom code development with Vite, local proxy and publishing commands.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.6 |
| Where you write codeSame on both | Your own editorYour own editor, in a Vite project.1 | Your own editorYour own editor. The folder you link is served at https://<name>.sp with SSL.5 |
| Where code runs while you test | localhost proxyA local proxy of your published webflow.io site, with your local Vite scripts injected.1 | Your real live URLYour real Webflow URL, only in a browser with an active ?stagepass= session. Visitors keep getting production.2 |
| Setup on the Webflow site | CLI, browser cookiesInstall the CLI. It reads your browser cookies to authenticate with Webflow.1 | 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.7 |
| Where production files live | jsDelivr or inlinejsDelivr through a GitHub repository by default, or inline in Webflow.1 | Your hosting or CDNYour own hosting or CDN. The production URL stays in data-src. Stagepass hosts nothing.7 |
| Going live | Publish commandA publish command builds, pushes to GitHub, updates the Webflow custom code and republishes the site.1 | Your usual deployUpload your build as usual and bump data-stagepass-v so browsers fetch the new file.3 |
| Requirements | macOS, Linux, WindowsNative binaries for macOS, Linux and Windows.1 | macOSmacOS, Node.js 18 or newer and Homebrew. Setup installs Caddy, PHP and Dnsmasq.4 |
| License and cost | GPL-3.0, freeOpen source under GPL-3.0-only.1 | MIT, freeOpen source under the MIT license, free to use.8 |
When each one fits
Pick the tool for the job.
wfPick wfkit if
- You want one tool that also publishes to Webflow
- You work on Linux or Windows
- A local proxy of the published site is enough for testing1
SpPick Stagepass if
- You test on the real live URL
- You keep your own deploy and hosting
- You work on macOS
Switching
Moving from wfkit to Stagepass.
Your Vite project can stay as it is. Stagepass only needs the folder with the built files.
- 1Link the build output folder with
stagepass link. - 2Host the production files yourself and put their URL in
data-src. - 3Replace the managed script tags in Webflow with tagged tags and the Stagepass loader.
Status and sources Checked on · 8 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 wfkit. Tools change over time. If something here is out of date or unfair, open an issue.
- 1 wfkit README wfkit github.com
- 2 Stagepass README, dev mode Stagepass github.com
- 3 Stagepass MIGRATION.md Stagepass github.com
- 4 Stagepass setup.js Stagepass github.com
- 5 Stagepass CLI README Stagepass github.com
- 6 Stagepass README Stagepass github.com
- 8 Stagepass LICENSE Stagepass github.com