Embedding in Webflow

Use the app’s Embed action to copy the loader script for Webflow. When hosted publish is enabled, those assets are served from Cloudflare R2 over the Cloudflare edge network (same CDN family as Webflow) for strong compatibility and fast delivery. Deployed asset URLs follow the service pattern https://ssscript.dev/<username>/<project>/..., such as https://ssscript.dev/valla.federico/t1/app.css.

Where to paste

• Site-wide: Webflow → Site settings → Custom code → Head code.
• Per page: Page settings → Custom code → Head.

Paste the single loader script — it handles both JS (app.js) and CSS (app.css) loading.

What the loader does

The loader is a single <script> block that:

1. On production (non-.webflow.io domains) — loads JS and CSS directly from your deployed URL. Fastest path, no dev-server overhead.
2. On .webflow.io staging — preloads deployed assets as fallback, tries the local dev server (http://127.0.0.1:6454) first, and falls back to deployed if the dev server is not running.

This means you can paste the same snippet once and it works for both development and production without changing it.

Automatic apply

If your project has a Webflow site linked and the Webflow MCP is connected, you can click Apply loader to Webflow in the Embed modal to inject the script via the Custom Code API — no manual paste needed.

Logged-out vs logged-in behavior

• If you are logged out, the loader points to local-dev URLs only. Sign in and publish at least once to get deployed fallback URLs.
• If you are logged in and have published, the loader is generated from your user/project publish namespace with full dev→deploy fallback.

After updates

When you publish a newer build, keep the same Webflow placement — the loader URLs stay the same. Republish the Webflow site to pick up updated assets.