You only need the Framer badge gone
Framer says the badge automatically disappears when you connect a custom domain or upgrade the site to a paid subscription. Republish the site with the Update button to apply the change.
Remove Made in Framer badge and own the website.
Remove Made in Framer badge through Framer by connecting a custom domain or upgrading the site, then republishing. If you also want the brand, codebase, and hosting under your control, use the Agentic Website Template to recreate the site as an editable Next.js project.
Decide how much website control you actually need.
The badge has a quick supported fix inside Framer. The bigger decision appears when your team also wants control over the source code, hosting, publishing workflow, and every branded detail around the site.
Use the templateYou want the whole brand under your control
Removing one badge still leaves the website inside Framer's managed publishing system. Full control means owning the codebase, choosing the hosting account, and deciding how every page is built and shipped.
You need the site to keep changing
A branded launch solves today's request. A reusable component system, documented design rules, and clear agent instructions help the next landing page look right and reach production faster.
Move beyond the badge with a website your team owns.
Use the Agentic Website Template when independent code and hosting are part of the goal. Your AI coding agent can recreate the Framer design, turn approved patterns into maintainable components, and carry the finished website into an owned Next.js repository.
See the three ways to use the templateRecreate the Framer design in detail.
Keep the brand
Use the published site as the visual reference for layouts, typography, breakpoints, interactions, and motion. Review the homepage at desktop, tablet, and mobile sizes before building the remaining pages.
- Match the existing visual identity
- Record hover, scroll, and transition behavior
- Review responsive details before scaling
Put the website in your Next.js repository.
Own the foundation
Pages, reusable components, design tokens, content, and configuration live in code your team controls. Deploy through your own account and choose the services that fit the business.
- Keep the source code in your repository
- Choose your deployment account
- Change integrations as the company grows
Give coding agents the brand and project context.
Keep editing
Claude Code, Codex, or Cursor can read the goals, brand voice, design rules, reusable components, and launch instructions stored beside the website. Each new request starts with shared context.
- Store design and brand guidance with the code
- Reuse approved page patterns
- Review every update as working code
Publish pages web crawlers can read clearly.
Stay discoverable
Important copy and links render in the page HTML. Metadata, structured data, clear navigation, sitemaps, and AI crawler guidance help search engines and answer engines understand the website.
- Render important content in HTML
- Keep routes and navigation easy to follow
- Include SEO and GEO foundations
Check the complete website before changing the domain.
Move with care
Test pages, redirects, forms, analytics, responsive layouts, motion, search files, and production settings in preview. Move the domain after the new website passes review.
- Check every important public route
- Test forms and tracking
- Review production settings before launch
How to remove the badge or take full control.
Start with the smallest change that meets your goal. Stay in Framer for a supported badge removal. Use the template when your team is ready to own the complete website and its publishing workflow.
Start with the Agentic Website Template- 01
Use Framer's supported badge setting
Connect a custom domain or upgrade the site to a paid subscription, then click Update to republish. Framer says the badge disappears after this publish step.
- 02
Choose migration for deeper ownership
List the control you need over source code, hosting, content, integrations, and future edits. Choose the Next.js path when these goals matter beyond the badge itself.
- 03
Recreate and review the homepage
Clone the Agentic Website Template and ask your coding agent to study the live Framer site. Rebuild one complete page, then review its design, motion, and responsive behavior.
- 04
Move the website and switch the domain
Build the remaining pages, move CMS content, reconnect forms and analytics, map redirects, and run launch checks. Point the domain to the approved deployment when everything works.
What full website ownership gives your team.
Your brand appears on its own terms
The finished website keeps the visual character people recognize, with every public detail under your team's control.
The code and hosting belong to your workflow
Your team controls the repository, deployment account, integrations, and the rules used to publish each change.
The next page is easier to launch
Reusable components and written guidance give coding agents a reliable starting point for campaigns, content, and site updates.
Made in Framer badge questions.
Direct answers about Framer's supported badge removal and the path to an independently hosted Next.js website.
How do I remove the Made in Framer badge?
Framer's current help guide says the badge automatically disappears after you connect a custom domain or upgrade the site to a paid subscription. Click Update to republish the site after making the change.
Do I need to migrate my website to remove the badge?
No. Use Framer's supported custom domain or paid subscription route when badge removal is your only goal. Consider migration when you also want ownership of the source code, hosting, components, and publishing workflow.
Can an owned Next.js site keep my Framer design and animations?
Yes. Record the layouts, breakpoints, type styles, hover states, scroll effects, and page transitions that define the site. Recreate them with reusable React components and Motion, then review each screen size and interaction.
What else moves when I leave Framer hosting?
Move the pages, CMS content, forms, webhooks, fonts, scripts, redirects, localization, analytics, metadata, structured data, sitemap, and important interactions. Test each part before pointing the domain to the new deployment.