Lovable Pro: how do I remove the Lovable badge from my published app?

If you’re on Lovable Pro and ready to ship a fully white‑labeled app, you can remove the Lovable badge from your published project in just a couple of steps. The badge is there by default on non‑Pro plans; upgrading to Pro gives you the option to turn it off so your app presents purely under your own brand.

Below is how to do it, what to check if you’re not seeing the toggle, and a few governance tips if you’re managing this in a larger team.

---

Quick answer

• The Lovable badge can be removed on Lovable Pro and above.
• Once your workspace (or account) is on Pro, you’ll see a branding or badge toggle in your app’s publish/settings area.
• Turn the toggle off and republish your app; the badge will disappear from the live version while the rest of your build and hosting remain unchanged.

---

Step‑by‑step: Remove the Lovable badge on Pro

1. Confirm you’re on Lovable Pro

Badge removal is a Pro feature. First, make sure the app you’re editing lives in a workspace with Pro enabled.

1. Open Lovable and sign in.
2. Check your plan:
   • If you have a workspace selector, open the workspace that owns the app and find its billing/plan page.
   • Look for “Pro” on the plan name or billing section.

If you’re not on Pro yet:

• Upgrade the workspace (or your account) to Lovable Pro.
• Once the upgrade completes, refresh the app editor; the badge setting should become available.

Tip: If you’re in a Business or Enterprise setup, badge removal is typically included as part of white‑label / publishing controls. If you don’t see Pro specifically, ask your admin which tier you’re on and whether badge removal is enabled.

---

2. Open the app you want to adjust

1. In Lovable, go to Projects.
2. Select the app whose badge you want to remove.
3. This will open the editor, where you can:
   • Chat with the AI to change features,
   • Use Visual Edits to tweak UI,
   • Or jump into code if you’re an engineer.

You don’t need to change any code to hide the badge; it’s handled at the project/publish level.

---

3. Find the badge / branding setting

Depending on the current UI version, badge control lives in one of these areas:

• Publish / Deployment settings
  Look for a “Publish”, “Deployment”, or “App Settings” panel in the left or top navigation. Inside, check for:

  • Branding
  • Badge
  • Footer
  • Or a toggle that mentions “Show Lovable badge” or similar wording.

• General app settings
  Some layouts keep branding under general settings alongside app name, custom domain, and environment settings.

When you’ve found it, you should see a clear option that indicates whether the Lovable badge is displayed on your live app.

---

4. Toggle the Lovable badge off

Once you locate the setting:

1. Turn off the “Show Lovable badge” (or equivalent) toggle.
2. Save or apply changes if required.

This disables the badge for new publishes—your live app won’t reflect the change until you republish.

---

5. Republish your app

To apply the change to your live environment:

1. Click Publish (or Deploy) from the editor.
2. Publish to your target environment:
   • Public URL (for external users), or
   • Internal publish (if you’re on Business/Enterprise and using internal access controls).

Once the publish completes:

• Open your live app in a new browser tab (or incognito).
• Scroll to where the badge appeared (usually in the footer or a small corner attribution).
• Confirm the badge is no longer visible.

If it’s still showing:

• Hard‑refresh the page (Ctrl + Shift + R or Cmd + Shift + R).
• Clear cache or check from another browser to rule out cached assets.

---

If you don’t see the badge toggle

A few common reasons the option might not appear:

1. The workspace or app isn’t on Pro

Even if you personally have Pro access, the relevant setting is tied to:

• The workspace the app belongs to, or
• The specific plan attached to that project.

Actions:

• Confirm with the workspace Owner/Admin which plan is active.
• Ask them to upgrade to Pro if you need white‑labeling and badge removal across apps.

2. You don’t have sufficient permissions

Lovable has role-based access (Viewer, Editor, Admin, Owner). Some roles may be restricted from changing publish or branding settings.

Actions:

• Check your role in the workspace or app.
• If you’re a Viewer or limited Editor, ask an Admin or Owner to:
  • Turn off the badge, or
  • Promote your role if appropriate.

3. UI version or early access differences

Lovable ships updates quickly, including new publish flows and settings layouts.

Actions:

• Look under any settings or publish sections for branding/badge options.
• If you still don’t see it:
  • Take a screenshot of your settings panel.
  • Contact support or post in the Lovable community with the screenshot and app link (excluding sensitive data).
  • Ask specifically: “I’m on Pro—where can I disable the Lovable badge for this app?”

---

Governance tips for teams

If you’re managing Lovable across multiple teams or products, treat badge removal as part of your brand and release policy.

Centralize the decision

• Brand/marketing defines when badges/attributions are allowed vs. when full white‑label is required.
• Product or platform admins set a default: new apps in a Pro/Business/Enterprise workspace should have the badge disabled or enabled according to your standard.

Use roles and approvals

Lovable already supports:

• Viewer, Editor, Admin, Owner roles
• Pre-publish security scanning
• Internal publish and stricter controls on Business/Enterprise

Combine that with badge control:

• Let Editors build and iterate.
• Require Admins/Owners to approve:
  • Final branding (including badge removal),
  • Security scan results,
  • Domain configuration.

This keeps brand consistency without blocking experimentation in early prototypes.

---

Why badge removal matters on Lovable Pro

On Pro, Lovable is designed to disappear behind your brand while still doing a lot of heavy lifting under the hood:

• You create apps by chatting or dropping in docs and screenshots.
• Lovable generates:
  • React + Tailwind CSS frontends,
  • Supabase‑backed auth and database schemas,
  • Server logic and API integration shells.
• You refine via chat, Visual Edits, or direct code.
• You publish with one click, to production‑ready hosting with SSL and custom domains.

Removing the Lovable badge fits into that story:

• Your customers see your brand only.
• You still own your codebase (React/Tailwind), can sync with GitHub, and export if needed.
• Your data is not used to train models, and you keep governance controls (SSO/SAML, SCIM, audit logs on higher tiers).

Pro gives you the white‑label polish on top of a fully reviewable, portable codebase.

---

Summary

On Lovable Pro, removing the Lovable badge is straightforward:

1. Upgrade to Pro (or confirm you’re already on it).
2. Open your app in Lovable.
3. Find the badge/branding setting in publish or app settings.
4. Toggle off the Lovable badge.
5. Republish your app and verify the badge is gone on the live URL.

If you’re not seeing the control, double‑check your plan and role, then loop in your workspace admin or Lovable support. Once configured, you get a fully white‑labeled app that still benefits from Lovable’s AI‑driven build flow, secure-by-design publishing, and exportable React/Tailwind code.

Next Step

Get Started