Webflow · free forever · no signup

Free Webflow widgets, ready for Code Embed

Webflow is behind hundreds of thousands of production sites, and every one of those sites has the same problem: adding a small piece of live data — how many people are reading, which countries visit, where people click — usually means installing an app you'll have to maintain, update and trust.

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. Every widget below is one snippet, pasted in once. Pick one and the page tells you the exact menu path for Webflow, the gotchas, and what to do if you're on an older theme or a page builder.

Why Code Embed beats an app for small widgets

Webflow sites are usually built with care for design and speed, so adding a heavy third-party app for a small counter or badge feels wrong. A FeedPulse widget is one async script you paste into a Code Embed element or the site's custom code fields. It carries no jQuery of its own, so it doesn't clash with the copy Webflow already loads.

Where the snippet goes in Webflow

Sitewide tools such as the heatmap go into Site settings → Custom code, in the Head or Footer code box. Widgets that belong in a specific spot go into a Code Embed element on the canvas. For something that should appear on every page, like a footer counter, put the Code Embed inside your footer component so you only place it once. For blog posts, add it to the Collection page template.

All 18 free widgets for Webflow, and where each one goes

Free website heatmap tool for Webflow

Goes in Site settings → Custom code → Head code, because it has to load on every page before your clicks happen, and it renders nothing visible.

Free hit counter for website for Webflow

Goes in Site settings → Custom code → Footer code, because an all-time total is a footer artefact — nobody scrolls up to check it.

Free live weather widget for Webflow

Goes in a Code Embed element inside a global component, because local conditions are a glanceable sidebar item, not a content block.

Free crypto ticker widget for Webflow

Goes in a Code Embed element inside a global component, because a ticker reads best as a persistent strip beside the content.

Free stock ticker widget for Webflow

Goes in a Code Embed element inside a global component, because quotes are reference data — visible, but never competing with the article.

Free countdown widget for Webflow

Goes in a Code Embed element on the canvas, because a countdown works above the fold on the page that's actually selling the thing.

Live visitor tracker — world map widget for Webflow

Goes in a Code Embed element on the canvas, because it's the most visual widget you have, so it earns a spot in the content rather than the chrome.

Free comments widget for Webflow

Goes in a Code Embed in the Blog Posts Collection page template, because it belongs directly under the article body, which means the blog-post template rather than a global widget area.

Trust badge & social proof widget for Webflow

Goes in Site settings → Custom code → Footer code, because trust badges are read at the moment of hesitation, which is usually the footer.

YouTube live widget for website for Webflow

Goes in a Code Embed element inside a global component, because a live pill is only useful if it's visible before the visitor decides to leave.

Free Twitch live widget for website for Webflow

Goes in a Code Embed element inside a global component, because the whole point is catching someone while you're actually live.

Free GitHub stars badge for Webflow

Goes in 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.

Free npm downloads badge for Webflow

Goes in a Code Embed element on the canvas, because it belongs beside the install command, in the post or docs page that teaches it.

Free Discord live-members widget for Webflow

Goes in a Code Embed element inside a global component, because a live member count is a standing invitation, so it should follow the reader down every page.

Free AI chat widget for your site for Webflow

Goes in Site settings → Custom code → Footer code, because it's a floating bubble, so it only needs to exist once per page and should load last.

Free page speed badge for Webflow

Goes in Site settings → Custom code → Head code, because one paste in the head gives every page its own score — the badge auto-detects which page it's on.

Free flag counter for Webflow

Goes in Site settings → Custom code → Footer code, because a ranked country list belongs at the bottom, where its lazy-loaded flags stay below the fold.

Free online-now counter for Webflow

Goes in a Code Embed element on the canvas, because a live count only changes behaviour when it sits in the same line of sight as the price or the button.

Publish to test

The Designer shows a grey placeholder for Code Embeds and doesn't run site-level code on the canvas. Preview isn't reliable for third-party scripts either. Publish the site, then check the live domain in a normal browser tab. Remember to publish to your custom domain as well as the webflow.io address if you use both.

Which widgets suit Webflow sites

Webflow is popular with agencies, startups and designers. The page speed badge is a natural fit for agencies that sell fast sites, the GitHub stars and npm downloads badges suit developer-tool landing pages, the heatmap helps test new landing page designs, and the visitor globe works on About pages for remote-first teams.

Keeping custom code tidy

Webflow limits how much code you can put in each custom code field, and several third-party tags in one place quickly become hard to manage. Give each widget its own clearly named Code Embed or a comment line in the custom code box, so anyone editing the site later knows what each script does and can remove it safely.

Widgets on CMS-driven pages

If a widget should appear on every blog post or every item in a CMS collection, add the Code Embed to the Collection page template once rather than to each item. Inside a Collection template you can also insert CMS fields into the embed, for example to show a different GitHub repository on each project page. Keep a copy of the snippet in a note so it is easy to restore if a template change removes it.

Removing a widget

Delete the Code Embed element or the line in your custom code settings and republish. Nothing else on the site depends on it.

Webflow plan 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.