How to Cancel Your Lovable Subscription
Cancelling Lovable means downgrading to Free, and the control lives at Settings → Plans & credit usage → Manage → Downgrade to free. Lovable states there is no separate cancel action and no email address to request one — you do it yourself, and your paid plan keeps running until the end of the current billing period. Export your code to GitHub before you click it, because Git sync is the one export route that survives on the Free plan.
By Hire Lovable Xperts · Last verified: 2026-08-08
What happens to my projects after I cancel?
Your projects are not deleted and your published app is not taken down. Lovable states that downgrading or cancelling does not disconnect your custom domains or unpublish your project, and workspace-private projects are included on the Free plan. What you lose is paid capability — editing code, downloading code, connecting new domains, credit rollover and top-ups — plus access to the subscription credits still sitting in your balance.
The credit outcome is the part worth reading twice, because Lovable describes it two ways in two places. Its cancellation FAQ says unused monthly plan credits and rollover credits expire at the end of your current billing period and are not refunded. Its downgrade note says those credits are frozen rather than destroyed — unusable while the workspace is on Free, but usable again at their original expiry date if you re-subscribe before then, a reading its pricing FAQ repeats. Top-up credits you bought and any bonus credits stay usable on Free until they expire.
One setting does not come back. Lovable keeps most configuration so features resume automatically if you upgrade again, but plan-dependent workspace defaults — default project visibility and publishing permissions — reset to the new plan's defaults and are not restored by a later upgrade. If you have deliberately tightened either, record the values before you downgrade.
A backend you own is a separate account and a separate bill. If your app runs on your own Supabase project, cancelling Lovable does not touch its database, auth, or storage. If it runs on Lovable Cloud, the backend is credit-funded: Lovable documents that built-in backend services pause shortly after a workspace runs out of credits, and separately that a downgrade to Free freezes subscription credits. Check your balance before you downgrade rather than after.
| Item | On Pro / Business | After the downgrade takes effect |
|---|---|---|
| Timing | Plan active | Downgrade applies at the end of the current billing period, not immediately |
| Workspace-private projects | Included | Still included on Free |
| Git sync (GitHub and GitLab) | Included | Still included on Free — this is your durable export |
| Download code | Included | Not available on Free |
| Edit code | Included | Not available on Free |
| Custom domains | Connect new domains | Already-connected domains keep serving; you cannot connect new ones |
| Credit rollover and top-ups | Included | Not available on Free |
| Monthly + rollover credits | Spendable | Frozen on Free; usable again at their original expiry if you re-subscribe first |
| Top-up and bonus credits | Spendable | Still usable on Free until they expire |
| 'Edit with Lovable' badge | Can be hidden | Returns on your next publish, and the hide setting is switched off |
| Build credits | 5 per day, no monthly cap | 5 per day, capped at 30 per calendar month |
Related: how to recover a project that disappeared after a plan change
How do I export my Lovable project before cancelling?
Connect Git sync to GitHub before you downgrade, not after. Lovable lists github.com Git sync as available on all plans including Free, while Download codebase — the ZIP route in the Code editor — is a paid-plan feature you lose when the downgrade takes effect. Connect the project at Project settings → Git → GitHub and Lovable creates a private repository and starts two-way sync automatically.
Disconnecting is safe; deleting is not. Lovable states that when you disconnect a project from its repository, sync stops but the repository stays on GitHub intact with all history and files, and your code stays in Lovable too. What breaks the relationship irreversibly is deleting the repository, renaming your GitHub account or organisation, or transferring the repository elsewhere — renaming the repository itself is tracked automatically and is fine.
- Open Project settings → Git → GitHub, or use the + (plus) menu in the chat.
- Under Accounts, click Add account and install and authorise the Lovable GitHub app on the account or organisation you want the repository created in.
- Back in the project, click Connect next to that workspace connection. Lovable creates a new repository — private by default — and starts syncing.
- Confirm the repository status reads Connected and the branch picker shows your active branch.
- Copy a clone URL (HTTPS, SSH, or GitHub CLI) from the same panel and clone the repository locally so a copy exists off both platforms.
- Repeat for every project you want to preserve: each Lovable project connects to exactly one repository.
- While you still hold a paid plan, also take a ZIP: open the Code editor and click Download codebase at the bottom of the file-tree sidebar.
Can I get a refund when I cancel Lovable?
Not for credits. Lovable's pricing FAQ states credits are not refundable or redeemable for cash or any other value, and its cancellation FAQ adds that unused monthly plan credits and rollover credits expire at the end of your current billing period and are not refunded. Cancelling therefore returns nothing — it stops the next charge. A wrong or duplicate charge is a different conversation, and that one is worth having.
If you downgraded before your renewal date and were charged anyway, that is a billing error rather than a policy question. Lovable's own troubleshooting routes payment problems to support@lovable.dev, so raise it there with the date you downgraded and the date of the charge. Screenshot the plan card showing the downgrade before you close the tab — it is the only timestamped evidence the UI gives you.
What is the alternative to cancelling — should I migrate instead?
Cancelling and migrating solve different problems. Cancelling stops the bill and leaves the project inside Lovable on a Free plan that cannot edit code, download code, or connect a new domain. Migration moves the synced repository onto hosting you control, so the app keeps running and keeps being developable without a Lovable subscription at all. Choose by whether the project is finished or still changing.
Migration means taking the Git-synced repository and deploying it to a hosting provider like Vercel or Railway, with your existing Supabase backend untouched. The result is an identical app that runs independently of Lovable, with no per-prompt credit cost and no plan restrictions. A developer can migrate a Lovable project in one to three days.
The migration decision comes down to one question: is your app finished and just needs hosting, or does it still need active development? If development is ongoing, migration to a standard React codebase gives you a stable foundation — a human engineer makes precise, targeted changes rather than AI prompts that can touch dozens of files at once. See the Move Off Lovable guide for the full step-by-step process.
How do I confirm my cancellation actually went through?
Do not expect the plan card to say Free straight away — that is the single biggest source of 'did it work?' panic, and it is normal. Lovable applies downgrades at the end of the current billing period, so a successful cancellation looks like a still-paid plan with an end date attached. Confirm it in Settings → Plans & credit usage, not in your inbox.
- Re-open Settings → Plans & credit usage after completing the flow.
- Read the plan card: a completed downgrade shows the current plan remaining active until the end of the billing period.
- Note that date — it is when the workspace actually moves to Free, and when unused monthly and rollover credits stop being spendable.
- Screenshot the card. Lovable does not document a cancellation confirmation email, so this is your timestamped record.
- If you cancelled through the iOS App Store instead, confirm there: Settings → [Your name] → Subscriptions.
- If the card shows no pending downgrade at all, the flow did not complete — run it again, then contact support@lovable.dev if it still does not register.
Frequently asked questions
Is there a Cancel button on the Lovable billing page?
Will Lovable delete my projects if I cancel?
What if I am on an annual Lovable plan?
Can I pause my Lovable subscription instead of cancelling?
What happens to my Supabase data if I cancel Lovable?
How do I prove I cancelled if I get charged after cancelling?
Can a developer take over my Lovable project if I cancel?
What is the difference between Downgrade to Free and deleting my account?
How long before renewal should I cancel to avoid being charged again?
I cancelled but Plans & credit usage still shows my paid plan — is something wrong?
Talk to a senior engineer — not a salesperson.
Book a free 30-minute audit call. We'll diagnose what's wrong and tell you exactly what it costs to fix.