# How to Remove the "Edit with Lovable" Badge - Tool: Lovable - Difficulty: Beginner - Fix time: ~2 min - Compatibility: Hide Lovable badge toggle: Pro, Business, and Enterprise plans. Manual code removal: any exported, self-hosted project. - Last updated: September 2026 ## TL;DR Remove the Lovable badge by going to Project settings, then Publishing, and toggling Hide Lovable badge — it applies to your live site immediately and requires a paid plan (Pro or Business and above). On the Free plan there is no official removal option, only an unofficial CSS workaround, and the badge returns automatically if you downgrade and republish. ## Why the badge exists and how removal actually works The 'Edit with Lovable' badge is attribution shown on projects built and published without a paid plan, similar to the small branding many builders and free-tier platforms attach to output made with their free tools. It doubles as light marketing, since anyone who sees the badge on a live site knows what built it. The removal mechanism is intentionally simple and specific: a single per-project toggle, Hide Lovable badge, located in Project settings then Publishing, gated to Pro, Business, and Enterprise plans. The part people miss is that the setting is not permanent independent of your plan. It is tied to your subscription status at the moment of publishing, not a one-time unlock. Downgrade to Free, and the badge stays hidden only until your next publish — then it returns and the toggle itself resets to off. This trips people up on client projects that get handed off and later downgraded, where the badge quietly reappears weeks or months later with no obvious trigger from the client's perspective. - The badge is attribution/marketing shown on projects published without a paid plan - Hide Lovable badge is a per-project toggle in Project settings then Publishing, not a workspace-wide setting - It requires Pro, Business, or Enterprise — there is no official removal option on Free - Downgrading to Free resets the toggle and brings the badge back at the next publish, not immediately but not permanently avoided either ## Error messages you might see **Hide Lovable badge toggle appears greyed out or locked** This means the workspace is on the Free plan. The toggle only becomes interactive once the workspace is upgraded to Pro, Business, or Enterprise — there is no code-level workaround available from inside the standard editor on Free. **Badge still shows after toggling Hide Lovable badge on** Usually a caching issue, not a setting failure. Check the live site in a fresh incognito window rather than a tab that already loaded the page, and confirm you toggled the setting on the exact project you are viewing, especially in workspaces with several similarly named projects. ## Before you start - A Lovable project that has been published at least once - A Pro, Business, or Enterprise plan for the official toggle - Access to the project's exported code if you plan to remove the badge manually from a self-hosted build ## How to fix it ### 1. Open Project settings and find the Publishing section *The badge toggle lives specifically under Publishing, not the general project or workspace settings* Open your project in the Lovable editor and navigate to Project settings. Look for the Publishing section, which also holds your custom domain and publish history settings. This is where the badge control lives, separate from Cloud, Secrets, or workspace-level settings. **Expected result:** You are looking at the Publishing panel for this specific project, with the domain and badge options visible together. ### 2. Toggle Hide Lovable badge *This is the one official switch that controls badge visibility, and it is per-project* Inside Publishing, find the Hide Lovable badge toggle and switch it on. This setting is only available on Pro, Business, and Enterprise plans — on Free, the control is either absent or shown as locked behind an upgrade prompt. Confirm the toggle stays on after leaving and returning to the page, since a failed save is the most common reason people think the badge removal 'did not work.' **Expected result:** The toggle shows as enabled, and confirming it persists after a page refresh. ### 3. Verify the badge is gone on the live site *The setting takes effect immediately, so you can confirm it worked without waiting for a new deployment* Open your published site's live URL in a fresh incognito window (to avoid a cached version) and check the corner where the 'Edit with Lovable' badge normally appears. It should be gone right away, since this setting applies without requiring you to republish. If it still shows, double-check you toggled it on the correct project, especially if your workspace has several similar projects. **Expected result:** The badge no longer appears anywhere on the live, published version of your site. ### 4. Know what happens if you downgrade later *Losing track of this causes the badge to unexpectedly reappear on a site that previously looked clean* If your workspace downgrades to Free after the badge was hidden, the badge stays hidden until the next time the site is published. At that next publish, it reappears and the Hide Lovable badge setting itself turns back off. If you are planning to downgrade a client or portfolio project to Free after delivery, warn whoever owns it that the badge will return the next time they publish any change, so it does not look like a surprise regression. **Expected result:** You know exactly when and why the badge would come back, instead of being caught off guard by it on a future publish. ### 5. For exported projects: locate and remove the badge manually *Once code is exported, the official in-editor toggle no longer applies, since the project is running outside Lovable's publishing pipeline* If you have exported the project's code (via GitHub/GitLab sync or a ZIP download) and are self-hosting it, the badge exists as a component or injected script in the codebase. Search the project for the badge's component name or related script reference and remove it, then redeploy through your own host. This only makes sense for fully exported, self-hosted projects — for anything still managed inside Lovable, use the official Hide Lovable badge toggle instead, since a manual removal in the editor risks being reintroduced by a future AI-driven code change. For client handoffs where badge removal, white-labeling, and custom branding all need to be handled cleanly, RapidDev's engineers manage exactly this kind of Lovable publishing cleanup as part of standard $13K-$25K engagements. **Expected result:** The badge is permanently gone from the self-hosted, exported version of the app, independent of any Lovable plan setting. ## Best practices - Use the official Hide Lovable badge toggle in Project settings then Publishing rather than a manual code edit, since manual edits can be reintroduced by future AI-driven changes - Check the badge on a fresh incognito tab after toggling, since a cached page can make it look like the setting failed - Warn clients or teammates before downgrading a project to Free — the badge returns at the next publish, not instantly - Remember the setting is per-project — toggle it individually on every project in a workspace that needs the badge hidden - Only attempt manual badge removal in code for fully exported, self-hosted projects, not ones still actively managed in Lovable - Avoid relying on unofficial CSS workarounds for anything client-facing, since they are not guaranteed to keep working after platform updates ## Frequently asked questions ### How do I remove the Lovable badge from my published site? Go to Project settings, then Publishing, and toggle Hide Lovable badge. It takes effect on your live site immediately without needing to republish. This option requires a paid plan — Pro or Business and above. ### Can I remove the badge on the Free plan? Not through the official setting. The badge toggle is a Pro/Business+ feature. A CSS-based workaround exists in the community (hiding the badge element with a custom style rule), but it is unofficial, not guaranteed to keep working after updates, and worth knowing is a workaround rather than a supported feature. ### Does removing the badge require republishing my site? No. Once you toggle Hide Lovable badge in Publishing settings, it applies to your live site right away. You do not need to trigger a new deployment for the badge to disappear. ### If I downgrade my plan later, does the badge come back? Yes. On downgrade to Free, the badge stays hidden until the next time the site is published, and then it reappears and the Hide Lovable badge setting turns off. If you plan to stay on Free long-term, expect the badge to return the next time you publish any change. ### Is the badge setting per-project or workspace-wide? Per-project. Hiding the badge on one project does not automatically hide it on every other project in the same workspace — each project's Publishing settings need the toggle switched individually. ### Why does Lovable show the badge at all? It functions as attribution and light marketing on projects built with the free tier, similar to how many app builders and website platforms brand free-tier output. Paying customers get the option to remove it because a client-facing or production app usually should not carry a third-party builder's badge. ### Can I remove the badge by editing the code directly instead of using the setting? Technically, since you own the exported code, you can locate the badge component or script and remove it manually if you export the project. For a project still managed inside Lovable, using the official Hide Lovable badge toggle is simpler and safer than fighting with regenerated code on every future prompt, since a manual code edit can get reverted or reintroduced by future AI-driven changes. ### What if I can't fix this myself? If the badge is still showing after toggling the setting, or you are trying to remove branding from an exported project outside Lovable, RapidDev's engineers handle Lovable publishing and white-labeling issues as part of standard $13K-$25K project engagements. --- Source: https://www.rapidevelopers.com/lovable-issues/removing-the-lovable-badge © RapidDev — https://www.rapidevelopers.com/lovable-issues/removing-the-lovable-badge