Remove the ‘Made in Webflow’ badge
Why CSS hacks are a bad idea
Search results full of display: nonesnippets for the Webflow badge make it look like a simple fix. It isn't. Webflow's terms of service for the free plan explicitly require the badge to remain visible, and the badge element is re-injected at runtime — so the CSS rule has to win every time, on every page, in every browser, forever.
Worse, hiding it puts the site in violation of the plan it depends on, which means a takedown is one report away. The cost of being caught is the entire site disappearing — for a stake that's usually just “the page looks slightly cleaner.”
The legitimate options
There are exactly three:
- Buy a paid Site plan.Webflow's paid Site plans remove the badge as part of the plan. From ~$14/mo per site.
- Export the site and host elsewhere.The badge is injected by Webflow's hosting. Take the site off Webflow hosting and the badge is gone — by absence, not by hiding.
- Leave it visible. Honest, free, no terms violation. For internal tools, personal pages, and side projects, this is fine.
Cost comparison — paid plan vs export
| Approach | Upfront cost | Recurring cost | Notes |
|---|---|---|---|
| Webflow Site plan (Basic) | $0 | ~$14/mo per site | Badge removed; bandwidth + CMS items capped |
| Webflow Site plan (CMS) | $0 | ~$23/mo per site | Higher CMS limits; same hosting |
| Export + Netlify free | One export fee | $0 | Badge gone; static site only |
| Export + Cloudflare Pages | One export fee | $0 | Unlimited bandwidth; static site only |
| Export + Vercel Pro | One export fee | $20/mo per seat | Best if you'll grow into Next.js |
Pricing as of May 2026; check each host for current figures.
Remove the badge by exporting
- 1
Generate a Webflow API token
In Webflow: Site settings → Apps & Integrations → API access → generate read-only token. A free workspace can do this; no upgrade needed.
- 2
Run Webflow Export
Paste the token into Webflow Export, scan the site, download. The output has no badge in it — there's no Webflow hosting layer to inject one.
- 3
Deploy to a static host
Drag the folder onto Netlify Drop, or push it to a Cloudflare Pages project, or run
vercel --prod. See where to host an exported Webflow site for the per-host tradeoffs. - 4
Point your domain at the new host
Update DNS to point at the new host, set up the TLS certificate (every host above does this automatically), and the badge is gone for every visitor immediately after propagation.
- 5
Park or cancel the Webflow workspace
The exported site no longer needs the Webflow hosting relationship. Park the workspace as a backup or cancel it entirely — your content lives in the export folder now.
FAQ
- Is removing the badge by exporting allowed?
Yes. Webflow's terms cover hosting on Webflow's platform — the badge requirement is tied to the hosted free plan. Once a site is exported and hosted elsewhere, the badge requirement no longer applies because the hosting relationship is over.
- Can I just upgrade to a Site plan and skip this?
Absolutely — a paid Site plan removes the badge as part of the plan and gives you better bandwidth, custom code, and form submissions. The export route is better when you want to leave the platform entirely or pay $0/mo on hosting going forward.
- Does the export include the badge code anywhere?
No. The badge is injected by Webflow's hosting layer, not by the published HTML — so it isn't in the export at all.
- Are forms going to break?
The Webflow form handler doesn't follow the export. Wire forms to Netlify Forms, Formspree, or your own endpoint before you flip DNS. Everything else (interactions, animations, lightboxes) keeps working.
- Will my SEO be affected?
Not from the badge removal itself. Migration mistakes — broken redirects, missing sitemap, trailing-slash mismatches — are what hurt SEO during a Webflow move. Handle those before flipping DNS. See Webflow export vs hosting for the full SEO checklist.
Ready to try it?
Paste a Webflow API token, scan the site for free, and only pay when you download. Every page, asset, and CMS item is included.
Related
Last updated May 19, 2026