The "Made in Framer" badge appears on every site published through Framer's free and lower-tier plans. It sits in the corner of your page — and for client work or professional portfolios, it doesn't belong there.
You have two ways to remove it: upgrade to a paid Framer hosting plan, or export your site as static HTML and self-host it elsewhere. This article covers both options, what each actually costs, and walks through the export route in full.
The Quick Answer
Framer's built-in option: Upgrade to a paid Framer plan (Mini or above). The badge disappears on Framer-hosted sites.
The export route: Export your site to static HTML/CSS/JS using a tool like PullPage, then host it on Netlify, Vercel, Cloudflare Pages, or your own server. The watermark is stripped automatically during export.
Which is cheaper long-term: For agencies managing multiple client sites, the export route saves significantly more. For a single personal site, upgrading Framer's plan is the path of least resistance.
Now let's walk through each option with specifics.
Option 1: Upgrade Your Framer Plan
Framer ties watermark removal directly to its hosting plans. On the free plan, the badge appears and there's no setting in the editor to remove it — upgrading is the only option Framer gives you.
A paid Framer hosting plan removes the badge on that specific site for as long as you keep paying. That's fine if you're running one site and already happy with Framer's hosting.
The problem shows up when you're managing multiple client sites. Each one needs its own paid plan, and those costs stack up fast.
Option 2: Export Your Framer Site and Self-Host It
This is where most freelancers and agencies land once they're managing more than two or three client sites.
The logic is straightforward: export your Framer site as a static HTML/CSS/JS bundle, deploy it to a host of your choice, and pay that host's rates instead of Framer's per-site fees. The "Made in Framer" badge doesn't exist in the exported code — it's a Framer-injected script, and a proper export strips it entirely.
What "Export" Actually Means Here
Framer doesn't offer a native export-to-HTML feature. You design and publish inside Framer, but getting the static files requires a third-party tool that reads your published Framer URL and generates a clean static bundle.
PullPage is purpose-built for this. You paste your published Framer URL, it generates a static ZIP containing HTML, CSS, JavaScript, and all your assets, and you download it in around 24 seconds. The export automatically removes the "Made in Framer" badge and strips Framer's editor scripts from the output.
For a fuller breakdown of how the process works, see Can You Export a Framer Website in 2026?
Step-by-Step: Removing the Watermark via Export
Publish your Framer site to get a live Framer URL — the export requires it
Go to pull.page and paste your published Framer URL
Generate the static export — PullPage strips the badge and Framer scripts automatically
Download the ZIP or sync directly to a GitHub repo (paid plans)
Deploy to Netlify, Vercel, Cloudflare Pages, GitHub Pages, or your own server
No manual code editing. No hunting through HTML to find and delete the badge script yourself.
What Gets Preserved in the Export
The common concern: will the exported site still look and behave like the Framer original?
In practice, yes. PullPage's rendering engine is built specifically for Framer sites, which matters because generic HTML scrapers tend to break Framer Motion animations and scroll transitions. Hover effects, scroll-triggered animations, and Framer Motion interactions all carry over into the static output.
On paid plans, the export also bundles all local assets — images, videos, fonts, 3D models, audio, documents — so your site isn't quietly loading assets from Framer's CDN after deployment. Everything lives in your own hosting environment.
The Cost Comparison
This is where the export route makes a real financial argument.
Managing 10 client sites on Framer hosting means paying for 10 separate plans. With PullPage's Agency plan, you export and self-host all of them — and your hosting costs drop to whatever Netlify, Vercel, or Cloudflare charges, which for most static sites is near zero on their free tiers.
One agency user reported saving over $1,200 after switching to the export workflow. That's what happens when you stop paying per-site hosting fees for sites that don't need dynamic server infrastructure.
What the Badge Actually Is (And Why You Can't Delete It in the Editor)
The "Made in Framer" badge isn't a design element you placed on the canvas — it's a script Framer injects at the hosting level. You won't find it in your Framer editor. You can't select it and delete it.
That's why upgrading your plan or exporting the site are the only real options. Trying to hide it with CSS is fragile and technically violates Framer's terms of service.
The export route is clean because the injected script simply doesn't exist in the static HTML output. There's nothing to hide — it was never written into the files.
SEO Implications of Removing the Badge and Self-Hosting
Removing the badge itself has no direct SEO impact. But self-hosting your Framer export often improves your Core Web Vitals scores because you control the hosting environment, CDN configuration, and asset delivery.
When you deploy a PullPage export to Cloudflare Pages or Netlify, you can configure caching headers, enable compression, and serve assets from edge nodes close to your users. Framer's hosting handles some of this automatically — self-hosting gives you direct control over all of it.
If SEO matters for your Framer site, the export route is worth taking seriously beyond just the watermark question. The complete guide to improving SEO for Framer websites covers what to configure once you're self-hosting.
Which Option Should You Choose in 2026?
Upgrade Framer's plan if: You run one or two sites, you want zero configuration overhead, and Framer's hosting costs work for your budget.
Export and self-host if: You manage multiple client sites, you want full control over hosting infrastructure, or you want to eliminate per-site recurring fees.
The export route takes more setup the first time. After that, PullPage's GitHub Sync means you update the design in Framer, push to your repo, and the host redeploys automatically. The workflow gets fast quickly.
FAQs
Can I remove the "Made in Framer" badge without paying for anything?
Not through Framer's platform. The free plan always shows the badge, and there's no setting to hide it without upgrading. PullPage does have a free plan that generates a static export and removes the badge — though paid plans unlock full asset bundling and SEO features.
Is hiding the badge with CSS against Framer's terms?
Yes. Framer's terms of service prohibit hiding or obscuring the badge on free plans using CSS or other workarounds. The compliant options are upgrading your Framer plan or exporting the site to self-host it.
Does exporting the site break Framer animations?
Not with a purpose-built Framer export tool. PullPage's rendering engine is built specifically for Framer and preserves Framer Motion effects, hover states, and scroll transitions in the static output. Generic HTML scrapers often break these — which is why the tool you use matters.
Do I need to republish in Framer every time I make a change?
Yes. The export workflow requires you to publish in Framer first, then re-export. With GitHub Sync on paid PullPage plans, re-exporting commits directly to your repo and triggers an automatic redeployment on your host — so the only manual step left is publishing in Framer.
What hosting platforms work with a PullPage export?
Any platform that serves static files. Netlify, Vercel, Cloudflare Pages, and GitHub Pages all work well. You can also deploy to your own server or any VPS. The exported ZIP is standard HTML/CSS/JS with no platform-specific dependencies.
Will removing the badge and self-hosting affect my site's SEO?
Removing the badge has no SEO effect. Self-hosting can improve your Core Web Vitals scores because you control caching, CDN configuration, and asset delivery directly. PullPage's paid plan exports also preserve your Framer SEO settings and generate sitemaps, so your metadata carries over correctly.
Can I export a Framer CMS site and remove the badge?
Yes. PullPage supports full Framer CMS exports, including sites with 100+ pages and 500+ MB of content on paid plans. CMS content, page slugs, and SEO metadata all carry over into the static export.