This guide shows how to add a github stars badge for Webflow in about a minute, with no app: you paste one snippet into a Code Embed element on the canvas, because it's social proof for a specific project, so it goes inline next to what it's vouching for. 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.
What this github stars badge for Webflow shows
The GitHub stars badge shows the live star count of a public repository as a small pill that links to the repo. It's social proof for open-source projects: a docs site, a project landing page or a developer's portfolio can show at a glance that people use and follow the project.
How to add a GitHub stars badge to Webflow
- Step 1
- Open the page in the Designer and click Add (+) → Code Embed.
- Step 2
- Drag it exactly where the widget should appear — under a heading, beside a product, above the footer.
- Step 3
- Paste the snippet into the code editor and click Save & Close. The Designer shows a placeholder, not the widget.
- Step 4
- Publish, then open the live URL to see it render.
- On a free webflow.io staging site?
- Code Embeds render inline, not in an iframe, so the widget inherits your Webflow styles and sizes itself — no fixed height to manage, unlike iframe-based builders.
Where it works best on a Webflow site
On Webflow, the right spot is a Code Embed element on the canvas. A star count vouches for one specific project, so put it inline, right next to that project's name or install instructions, rather than in a sitewide footer.
Webflow plan and editor requirements
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.
Three things that trip people up on Webflow
- Custom code fields need a paid plan
- 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.
- The Designer never runs your code
- 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.
- Don't add a second jQuery, and watch the 50k cap
- 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.
Honest limits
It works for public repositories only. Stars show interest, not quality or how many people actively use the project.
Webflow questions
- Do I need an app to add a GitHub stars badge to Webflow?
- 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.
- Where exactly does the snippet go on Webflow?
- A Code Embed element on the canvas, because it's social proof for a specific project, so it goes inline next to what it's vouching for.
- Will it slow my Webflow site down?
- 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.
- Does it work with page builders like Webflow Designer?
- 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.
- Does the GitHub badge work for private repositories?
- No. It reads the public star count, so the repository has to be public.