This guide shows how to add a npm downloads badge for Webflow in about a minute, with no app: you paste one snippet into a Code Embed element on the canvas, because it belongs beside the install command, in the post or docs page that teaches it. Nothing to install. Webflow renders raw HTML and script tags inside a Code Embed element, so no third-party app sits between you and the widget.
The npm downloads badge shows how many times a package was downloaded in the last day, week or month, using npm's public download counts. It's for JavaScript library authors who want that number on their docs or landing page, not only on npmjs.com. Scoped packages are supported.
On Webflow, the right spot is a Code Embed element on the canvas. Put it next to the install command, in the docs page or post that teaches people to use the package. That's where a reader is deciding whether to run npm install.
Webflow's Code Embed element and its site-wide and page-level custom code fields only run on a paid Site plan or a paid Workspace. On a free webflow.io staging site the fields are visible but the code doesn't run on the published page, which looks exactly like a broken snippet. Custom code also doesn't run inside the Designer, so always test on the published site.
Site settings → Custom code and the page-level code fields are gated behind a paid Site plan or a paid Workspace. On a free webflow.io staging project they're visible but inert, which looks exactly like a broken snippet. The Code Embed element has no such gate, so free projects are not locked out — put the snippet on the canvas instead.
A Code Embed shows a grey placeholder in the Designer, and site-level code doesn't execute on the canvas at all. Preview is unreliable for third-party scripts too. Publish, then check the live domain in a normal tab. Most 'the widget doesn't work on Webflow' reports are an unpublished change.
Webflow already loads its own jQuery; importing another version breaks interactions site-wide. Our snippet has no jQuery dependency, so nothing to do here — but if you're pasting several third-party tags, that's the usual culprit. Each code field also caps at 50,000 characters; past that, host the file externally and link it.
Download counts include automated installs from CI systems and mirrors, so they overstate the number of people using a package. Use them as a relative signal, not a user count.
Nothing to install. Webflow renders raw HTML and script tags inside a Code Embed element, so no third-party app sits between you and the widget. Installing an app for this would mean another dependency and update cycle just to show one widget.
A Code Embed element on the canvas, because it belongs beside the install command, in the post or docs page that teaches it.
It adds one small script, loaded asynchronously, so it doesn't block your page from rendering. Any third-party script has some cost, so check your page speed before and after adding it. Webflow serves your site from its own CDN and the snippet is a single async tag, so it loads beside your content rather than in front of it. Put JavaScript in Footer code rather than Head code when you don't need it early — Webflow recommends the same thing. Nothing to purge; publishing replaces the page.
Webflow Designer: Add (+) → Code Embed. Page settings: paste inside the <head> tag or before </body> for one page. Site settings: Custom code → Head or Footer for every page. CMS Collection templates: drop a Code Embed into the template. Any builder with a raw-HTML or code block will render it.
No. They include automated installs from build servers and mirrors, so treat them as a rough popularity signal rather than a count of people.