How to remove the "Made in Framer" badge

The "Made in Framer" badge appears on sites published on Framer's free plan, and the standard way to remove it is to put the site on a paid Framer site plan. That is how Framer intends it to work, and it's the simplest route if you're happy to keep hosting on Framer. The other route is to own the site's code: if you convert your published site to a project you host yourself, there's no Framer hosting involved and no badge, though you take on hosting and maintenance in exchange.

This post explains both options fairly, since the right one depends on whether you want to stay on Framer.

What the badge is

When you publish a site on Framer's free plan, a small "Made in Framer" label sits in the corner of the page. It's part of the free tier: Framer lets you publish a site without paying, and in return the site carries a mark pointing back to Framer. Nothing is broken or wrong with your site; it's a normal part of how the plan works.

Visitors sometimes read the badge as a sign of an unfinished or low-budget site, which is why people look for ways to remove it. That's a branding judgment for you to make, not a technical fault.

Option 1: upgrade the site plan on Framer

On Framer, publishing on a paid site plan removes the badge. This is the intended, supported way, and it comes with whatever else the paid plan includes. Framer has several plans, and what each one includes (page limits, CMS limits, bandwidth, locales and so on) changes over time, so check Framer's pricing page for the current options. We deliberately don't quote prices here, because they would go out of date.

How it works in practice:

1. Open the project in Framer and go to the publish or site settings.
2. Choose a site plan that fits your site's needs.
3. Publish again, and the badge is gone from the live site.

If you're weighing whether the plan is worth it, the useful questions are what you get for the money (hosting, CDN, CMS, forms, analytics, the editor) and what you'd have to build or buy elsewhere. Our post Framer hosting vs self-hosting costs works through that comparison, and the answer for many sites is to stay on Framer. If you do, upgrading is the right fix.

What not to do: hiding it with CSS

Some guides suggest hiding the badge with custom CSS or an injected script. We don't recommend it, for three reasons:

• It works against the plan's terms. The badge is a condition of the free tier. Framer's terms are the authority on what's allowed, so read them before trying anything that circumvents it.
• It's fragile. The badge is inserted by Framer's code, and a change on Framer's side can bring it back without warning.
• It can reflect badly on a client site. If you're building for someone else, a workaround is a poor thing to leave behind.

If you want the badge gone, pay for the plan or own the code. Those are the two honest routes.

Option 2: own the code

Framer has no code export; its help center says it does not offer HTML export for self-hosting (Framer Help). What you can do is convert the published site into a project you own. Deframer reads the pages your published site serves and writes a TypeScript project for Next.js (the default), TanStack Start, Astro, React Router or Vite. The project has no Framer runtime, and it's hosted by you, wherever you choose, so Framer's free-plan badge isn't part of it.

Check this yourself rather than taking our word for it: run the project locally with npm run dev, open it, and look at every page. Search the code for the word "Framer" and confirm that nothing draws the badge. You're the one who ends up responsible for the site, so you should see it.

What you take on

Owning the code is not just removing the badge. It changes who runs the site:

• Hosting. You pick and pay for a host. Next.js deploys to Vercel, Netlify, Cloudflare or a container; Vite builds a fully static site that any static host serves, including GitHub Pages. See deploying a converted Framer site and hosting on GitHub Pages.
• Editing. You edit code instead of the Framer canvas, or keep designing in Framer and convert again after each republish. Maintaining a converted Framer site with Git describes the workflow.
• Forms. Native Framer forms become routes in your project, or, in a Vite project, posts to a form service. Forms after leaving Framer covers it.
• CMS. Collections become JSON files. For frequent editing by non-developers, you may want a headless CMS (adding one).
• Fidelity. The converted site is meant to match the original, but you should compare them and fix any differences. See common conversion issues.

It's a good trade if you wanted to own the site anyway: you control hosting, can put the project in Git and can build on it. It's a poor trade if the badge is the only thing bothering you, since a Framer plan does that for less effort.

Questions to ask before you decide

• Is the site on a custom domain already? If it's going to need a paid plan anyway for the domain, the badge question may answer itself.
• How often does it change? A site edited weekly by designers is easier to keep on Framer. A site that rarely changes is easier to own as code.
• Who maintains it? Owning code only makes sense if someone on your side, or a developer you trust, will look after hosting and updates.
• Is it your site? Only convert a site you own or have permission for, and don't remove branding from a site that isn't yours to change.
• Do you need it today? A Framer plan takes minutes. A conversion, review and migration takes longer, and a careful one includes an audit of the old and new sites.

How to choose

• You're happy on Framer and want a clean look: upgrade the site plan. Done.
• You want your own hosting, Git and code review, or the freedom to leave Framer: convert, review and host it yourself. The badge issue goes away as a side effect.
• You're not sure: read before you cancel your Framer plan and Framer vs Next.js for growing sites. Leaving isn't automatically better.

What converting costs

Converting is free. Downloading the project costs 1 credit if you verify ownership, or 10 credits without verification. Packs are $10 for 1 credit, $25 for 5 and $100 for 30, credits never expire, and the $397 lifetime deal makes every verified download free. Full details are on the pricing page.

To download, you verify that you own the site. Deframer shows a one-line meta tag; you add it in Framer's custom code settings, publish and click Check again. Verifying Framer site ownership has the steps. Deframer is only for your own site, or one whose owner gave permission and published your verification tag. If you build sites for clients, the affiliates program pays 50% on each sale you refer.

Deframer is an independent tool and isn't affiliated with Framer.