Stagepass

Compare · Built into Webflow

Stagepass vs. Webflow custom code and staging.

The built in way needs no extra tool: paste code into Webflow and publish to staging to see it run. Stagepass adds a local workflow on top, for when your code grows.

The short answer
CCWebflow custom code and staging
Built into Webflow

Made for A few lines of code, nothing to install, and publishing to staging is quick enough for you.7

SpStagepass
CLI and loader

Made for Code that has outgrown the fields, with files, Git and a build step, tested without publishing.

  • Where you write Webflow custom codeWebflow code fields, up to 50,000 characters1 StagepassFiles in your own editor2
  • How you test Webflow custom codePreview, or publish to webflow.io staging3 StagepassLive URL, no publish needed4
  • Setup Webflow custom codeNothing to install5 StagepassA CLI on your Mac and one script6

See both workflows side by side

Workflow

The same job, step by step.

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

CCWith Webflow custom code
SpWith Stagepass

Webflow custom code1 · Write

Paste into a code field

Add HTML, CSS and JavaScript in Site settings, Page settings or a Code Embed element.71

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.2

Webflow custom code2 · Test

Publish to staging

Some scripts only run on a published site, so you publish to the webflow.io staging subdomain to test.35

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

Webflow custom code3 · Go live

Publish the site

Custom code goes live when you publish the site to your domain.7

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.8

Point by point

Side by side.

TopicWebflow custom codeStagepassthis site
What it is Built inCustom code fields in Site settings and Page settings for HTML, CSS and JavaScript, plus the Code Embed element.7 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.9
Where you write code Webflow fieldsIn the Webflow fields. Head and footer code are limited to 50,000 characters each, a Code Embed to 50,000 characters.1 Your own editorYour own editor. The folder you link is served at https://<name>.sp with SSL.2
Where code runs while you test 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.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 Nothing to installNothing to install. Every site has a webflow.io staging subdomain that can be published on its own.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.10
Where production files live Part of the siteThe code is part of the published Webflow site.7 Your hosting or CDNYour own hosting or CDN. The production URL stays in data-src. Stagepass hosts nothing.10
Going live PublishCustom code goes live when you publish the site.7 Your usual deployUpload your build as usual and bump data-stagepass-v so browsers fetch the new file.8
Requirements Paid site planCustom code needs a paid plan, as listed in the help article. Webflow support does not troubleshoot custom code.1 macOSmacOS, Node.js 18 or newer and Homebrew. Setup installs Caddy, PHP and Dnsmasq.6
License and cost IncludedIncluded in the Webflow plan. A custom or private staging domain is Enterprise only.5 MIT, freeOpen source under the MIT license, free to use.11

When each one fits

Pick the tool for the job.

CCPick Webflow custom code if

  • You add a few lines of code
  • You do not want to install anything
  • Publishing to staging is quick enough for you7

SpPick Stagepass if

  • Your code has outgrown the fields
  • You want files, Git and a build step
  • You want to test without publishing every change

Switching

Moving code out of the fields.

Start with the biggest script. The rest can stay in Webflow until you are ready.

  1. 1Move the code from the field into a file in a project folder and run stagepass link.
  2. 2Upload the production file to your hosting or CDN.
  3. 3Replace the pasted code with a tagged script tag and add the Stagepass loader to the head code.
Status and sources Checked on · 11 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 custom code and staging. Tools change over time. If something here is out of date or unfair, open an issue.

  1. 1 Webflow help, custom code limits and plans Webflow custom code help.webflow.com
  2. 2 Stagepass CLI README Stagepass github.com
  3. 3 Webflow University, previewing and testing custom code Webflow custom code university.webflow.com Archived 6 Jun 2026
  4. 4 Stagepass README, dev mode Stagepass github.com
  5. 5 Webflow help, staging subdomain Webflow custom code help.webflow.com Archived 28 May 2026
  6. 6 Stagepass setup.js Stagepass github.com
  7. 7 Webflow help, custom code in head and body Webflow custom code help.webflow.com Archived 9 Oct 2026
  8. 8 Stagepass MIGRATION.md Stagepass github.com
  9. 9 Stagepass README Stagepass github.com
  10. 10 Stagepass README, tagging scripts Stagepass github.com
  11. 11 Stagepass LICENSE Stagepass github.com