Lovable subscription and billing: cancellation, credits and invoices
A useful subscription review ends with a clear decision: keep building, choose a different plan, or pause with a documented handover. Start with the workspace that owns the project and the person responsible for its bill. An account with several workspaces needs more care than a single personal experiment.
This guide covers Pro and Business subscriptions bought on lovable.dev. App Store purchases and Enterprise contracts have different billing arrangements. We reviewed the official documentation on 21 October 2026; we did not buy, cancel or change a subscription to test these instructions. Check the terms shown in your own workspace before confirming a change.
The new cost worksheet compares the cash commitment for your planned project length. It accepts your own quotes and separate-service budgets; it does not forecast how many credits an app or prompt will consume.
By The Lovable Club editorial team · Reviewed 21 October 2026
First published . Use the subscription cost worksheet.
Quick verdict
Record the renewal, credit balance and services the live project depends on before making a plan change. Keep the confirmation and check the project again afterward.
Target topics covered
Compare a monthly plan with an annual commitment
Enter quotes for the same plan and credit tier. Use one currency and the same tax treatment throughout. Annual means the full year’s charge paid upfront; a monthly equivalent is not a monthly payment. These calculations stay in your browser.
Top-ups and separately billed services are budgets you supply, not predictions. Count Lovable credit purchases once: do not add Cloud or AI usage again if it is already funded by those credits. External provider charges belong in the separate-services field.
Enter your quotes, then choose Compare my inputs. Changing an input clears the previous result.
Formula: monthly route = months × (monthly fee + top-up budget + separate services). Annual route = full annual fee + months × (top-up budget + separate services). Assumption: identical extra budgets and no refund, price change or discount during the comparison.
Readable example: Lovable’s documentation lists Pro with 100 monthly credits at USD 25 monthly or USD 250 annually, checked 21 October 2026. With zero extra purchases assumed, 12 monthly payments total USD 300 versus USD 250 upfront. For a three-month project the monthly fees total USD 75; the full annual fee is still USD 250. Taxes and other charges must be checked separately.
Source: official subscription tiers and billing cycles. Confirm current checkout terms; the example is not a purchase recommendation or a promise that 100 credits will cover your work.
At a glance
Documented plan-change effects for web subscriptions. Check your workspace’s confirmation before proceeding.
| When it applies | Effect on existing subscription credits | |
|---|---|---|
| Upgrade a paid tier | Immediately after completion. | You receive the allocation difference; existing credits retain their expiry. |
| Downgrade to a lower paid tier | At the end of the billing period. | Unused plan and rollover credits remain usable until their original expiry. |
| Cancel by moving to Free | At the end of the billing period. | Unexpired plan and rollover credits freeze while on Free; purchased top-up and bonus credits remain usable until expiry. |
Official sources checked
Added a transparent cost worksheet, a documented Pro billing example and guidance to avoid counting credit-funded services twice.
How to cancel a web subscription
An owner or admin can open Workspace settings → Plans & credit usage → Manage → Downgrade to free and complete the flow. The paid plan continues until the billing period ends. A lower paid tier is a different choice from Free.
Published apps stay live after cancellation, subject to Lovable’s inactivity policy. That is not a promise that every paid feature remains available. Review the official plan-change details before confirming.
Choose comparable quotes before using the worksheet
Use the same plan, monthly credit tier, currency and tax basis in both quotes. Pro and Business are different feature sets; a cheaper quote for a different tier is not a like-for-like annual discount. Enterprise terms are contract-specific. The official plan table is the source for features and current tier choices.
Write down when you collected each quote and whether tax is included. Keep your plan fee separate from optional top-ups and services billed by another provider. A Cloud or AI charge paid from the Lovable credit balance should not also be entered as a separate provider bill. Start with observed invoices or a clearly labelled budget, then revisit the assumptions after real usage.
Compare the full commitment before renewing
Pro and Business offer monthly or annual billing. Annual plans are paid for the year, while the subscription credits are still issued monthly. Compare the total charge and the features your project needs; an advertised monthly equivalent is not a monthly payment schedule.
Write down the next useful release before considering a longer commitment. A founder validating one workflow and an agency maintaining several client products have different reasons to pay. For either, a lower displayed monthly equivalent does not establish value. Use the current pricing page for the exact tier, currency, taxes and checkout terms offered to you.
Read the credit balance as well as the plan name
Lovable’s current documentation describes one workspace credit balance covering building, chat, Cloud hosting and backend usage, deployed AI features, and managed connector requests. Build and Run are reporting views, not separate balances. Usage-specific grants are spent before general credits.
Monthly subscription credits expire two months after issue on monthly plans. On annual plans they remain valid until one month after the annual period ends. Purchased top-ups expire after twelve months. Inspect Credit balance details for the actual grants and expiry dates in your workspace.
Do not estimate runway from one total alone. Record the balance, its expiry dates and the recent work it funded. A burst of prototyping may not resemble the usage of an app serving real customers. Review the usage breakdown before choosing a larger recurring commitment.
Where to find invoices and payment details
For web purchases, open Workspace settings → Plans & credit usage → Manage → Invoices & payments. This opens the Stripe billing portal, where you can download past invoices and receipts and manage payment methods. Manage → Edit billing information opens the billing-name, address and tax-details controls. Owners and admins manage billing.
Enterprise contract invoices come from the account team; Apple handles receipts and refunds for purchases made inside the iOS app. Identify the purchase channel before looking for a missing receipt.
For your records, keep the invoice identifier, billing period, currency, amount and payment status together. If a charge is unfamiliar, first match it to the workspace and purchase rather than assuming a successful bank transaction proves which service it paid for.
Distinguish an alert from a usage block
On paid plans, workspace owners and admins can configure Usage limits & alerts. A usage rule can notify, block, or do both when its credit threshold is reached. A low-balance alert only notifies. Blocking can stop building or pause Cloud, AI and metered connector use in deployed apps, depending on the selected scope and credit type.
Before choosing a rule, write down the intended outcome: receive an early warning, constrain an experiment, or stop a particular category of usage. For a live customer product, identify who will respond and what the customer would experience if the rule blocks activity. Review the current settings with the owner; a notification is useful only if somebody can act on it.
A practical renewal record
Keep a short record where the project owner can find it. The following is an editorial checklist, not a form required by Lovable. Avoid copying payment-card details or secrets into a shared document.
- Workspace and project names, with a named billing owner.
- Current plan, billing interval and next renewal shown in the account.
- Full expected charge, currency and the invoice or checkout that supports it.
- Credit balance, expiry dates and recent usage observations.
- The next release or maintenance work that justifies another period.
- Separate providers, domains and services, with their owners and renewal dates.
- Decision, confirmation reference and a date to verify the result.
An illustrative project-pause handover
Imagine an agency finishing a client portal. The client wants the portal to remain available but has no feature work scheduled for the next month. This is an example decision process, not a tested subscription outcome.
First, agree who owns the application and its ongoing support. List the live URL, repository, data storage, sign-in, email, payments and any external services. Record where each item is managed and who has legitimate access. Confirm the recovery material is usable without sharing credentials in the handover document.
Next, compare the intended plan with the features the portal actually uses. Have the billing owner review the proposed change and its effective date. Keep a copy of the confirmation. Changing a Lovable plan does not replace reviewing a separate provider’s account and terms.
After the change takes effect, open the live URL and test the agreed user journeys with test accounts and data. Check sign-in, the main client task and the support route. Record the observed result and assign any follow-up. Do not tell a client that continuity is guaranteed merely because the billing page accepted a change.
Choose the next period from evidence
Keep the subscription when there is a defined outcome and someone responsible for checking it. If work is uncertain, use a short review interval and write down what would justify continuing. If the project is pausing, a careful inventory and handover are more useful than a rushed cancellation. Revisit the decision when usage or the product’s needs change.
Build the next version
Try this workflow inside Lovable
If this guide matches what you want to build, the most useful next step is to open Lovable and turn the brief into a working first version. Start focused, test the main workflow, then improve one screen or state at a time.
Related Lovable guides
Explore more Lovable resources
Use these hubs to move between related Lovable guides, tutorials, prompts, integrations, and comparison pages.
FAQ
Frequently asked questions
Does the cost worksheet predict how many Lovable credits my app needs?
No. It compares amounts you enter. Credit use varies with building, chat, Cloud, deployed AI and connector work. Use actual usage records and keep any future top-up amount labelled as a budget.
Does a yearly plan issue all credits at once?
No. Pro and Business annual plans still issue subscription credits monthly. Compare the full annual charge with your expected work.
Does a low-balance alert stop app usage?
No. It notifies. A usage rule can block activity when configured to do so; check its scope and action.
What should I keep after a billing change?
Keep the confirmation, effective date, billing owner and a short record of the live checks performed afterward.
Was this cancellation process tested with a purchase?
No. This is a dated review of official documentation, with an illustrative handover checklist. We did not make a purchase or change an account.
Build faster with a better Lovable prompt
Turn the strategy from this guide into a structured Lovable prompt with pages, user roles, data, states, and acceptance criteria.