How do I remove the Made in Webflow badge?

Turn the badge off in Site settings

By default, Webflow branding can appear on a published site. The visible piece is the Made in Webflow badge. Other references can also appear in the site's HTML. Both are controlled under Site settings, not on the canvas. Deleting a footer you built does not remove this badge. It is a site setting.

Open Site settings, then the General tab, then Webflow branding. Turn off Display Made in Webflow badge. Save. The branding article says this setting is on by default when you create a site on Workspace plans other than Growth, Agency, and Enterprise. When it is on, the badge shows on the published staging subdomain, such as yoursite.webflow.io, and on the custom domain.

If you already had a Growth, Agency, or Enterprise Workspace when you created the site, Webflow says the setting is off by default. A site that never showed a badge may already be in that state. Read the toggle before you look for a class on the canvas.

Example: a client site on a paid Site plan still shows the badge at the corner of the homepage and on the staging link you send for review. Turn the badge off in Webflow branding and save. The Designer does not need a layout change. The next publish is what updates both hosts.

Publish before you judge the live site

Webflow says changes to branding settings do not take effect until the site is published. Save alone leaves the previous publish in place. Publish to the domain you are checking. If you use both the staging subdomain and the custom domain, publish the one you have open in the browser, then check the other if it is also public.

Reload the page after the publish finishes. A tab that was already open can keep the old badge until you refresh. Look at the homepage and one inner page. The badge is a site setting, so it is not tied to one page.

If the badge remains after a reload, confirm you saved Webflow branding and published this site. An exported copy does not read the toggle until you update that copy too.

Check the plan that allows the change

You can hide the badge if you have a Growth, Agency, or Enterprise Workspace plan, or a paid Site plan. Webflow states that one of those is required to remove Webflow branding. A new site on another Workspace plan keeps the badge setting on.

There is a further limit when the staging subdomain is used outside Webflow. The branding article names the Pages plugin for WordPress and a reverse proxy. In those setups, turning the badge off is not enough while the public site still uses yoursite.webflow.io. Webflow says you need to purchase a Site plan, add a custom domain or subdomain, and use that custom domain in the plugin or proxy setup.

The custom domain you already connected for a normal Webflow site is a different case. There, the badge follows the branding toggle on both the staging subdomain and the custom domain, once the plan allows it and you publish. You do not have to remove the staging subdomain to hide the badge on www.

Upgrading does not publish the site. Turn the badge off if it is still on, save, and publish.

Hide branding in the HTML when you export

Display Webflow branding in HTML is a second setting in the same Webflow branding group. It is on by default. You can turn it off on a Growth, Agency, or Enterprise Workspace, or on a paid Site plan, the same plan requirement as the badge.

When that setting is off, Webflow removes the comment at the top of the site HTML. An export made after the toggle is off also renames two files. webflow.js becomes your-site-name.js. webflow.css becomes components.css. Turning off only the badge does not do that rename. Use the HTML control when the export's file names and that comment are the problem.

Webflow says this toggle does not remove every Webflow-specific term. Some references may need to be removed by hand. Even on a Growth, Agency, or Enterprise Workspace, exported code may still contain class names that start with w-. The branding article says you can manually change class names, metadata, and site and page IDs. It also says changes to exported code are done at your own risk and are outside Webflow support.

For a site that stays hosted on Webflow, the badge toggle plus a publish is what visitors see. The HTML toggle matters for the source comment and the names inside an export. Leave exported class names alone unless you accept that those edits are unsupported.

Confirm the badge is gone on the live domain

Open the custom domain in a browser after you publish. Scroll the homepage. The Made in Webflow badge should be gone from the corner. Open the staging subdomain in a second tab if people still use that link. It should match, because the setting applies to both when the site is published there.

If the staging link is embedded in WordPress or a proxy and the badge remains, follow the branding article: use a custom domain on a Site plan inside that setup, rather than the webflow.io host. Republishing the staging subdomain alone does not meet that requirement.

If the badge is gone and an export still contains webflow.js, you turned off the badge and left HTML branding on. Turn off Display Webflow branding in HTML, save, and export again if the renamed files are what you need. Expect some w- class names to remain. The help article does not describe a toggle that strips those.

Check once more after the next full-site publish. Branding is saved with the site settings, and a later publish should keep the badge off as long as the toggle stays off and the plan still allows it.