Do Unused Lovable Credits Roll Over?

Do unused Lovable credits roll over to next month?

Yes, on paid plans — with a two-month clock attached. Lovable states that all unused monthly plan credits automatically roll over at the end of each billing cycle as long as your subscription remains active, and that those credits expire two months after they are issued. Rollover is a named credit type in your balance: open Settings → Plans & credit usage → Details and Rollover credits appear as their own line in the Breakdown tab.

Which bucket you mean decides the answer. Lovable splits credits into general credits — the monthly plan allocation, rollover, bonus, and purchased top-ups — and usage-specific grants, which are the daily build credits and the monthly Cloud and AI grants. General credits roll over. Usage-specific grants do not: Lovable states plainly that unused usage-specific grants do not roll over, and daily build credits refresh every day at 00:00 UTC.

The two-month window is the part most founders miss. Credits issued in January are spendable in February and March and expire after that if unused — so rollover smooths a quiet month or two, but it will not let you stockpile a year of allocation for one large build. Lovable spends the general credits closest to expiry first, which is why a balance that looks stable can still be losing its oldest grant every month.

Two edge cases change the outcome entirely. Cancelling: unused monthly plan credits and rollover credits expire at the end of your current billing period and are not refunded. Downgrading to Free: those same credits are frozen rather than spent — unusable while the workspace is on Free, but available again at their original expiry date if you re-subscribe before then. Purchased top-up credits and bonus credits are the exception to both and stay usable on Free until they expire.

Verify before you act on any of this. Lovable's credit policy changes with product updates; the figures here were confirmed against lovable.dev/pricing and Lovable's credits documentation on 2026-08-08, and your own dashboard is the authority for your workspace.

Does rollover differ between Free, Pro, Business, and Enterprise?

Yes — rollover is a paid feature, not a universal one. Lovable's plan comparison lists Credit rollovers as available on Pro and Business only; Free has no monthly subscription credits to roll, and Enterprise terms vary by contract. So the honest per-plan answer is that Free users have nothing to carry forward, and Pro and Business users carry forward everything unused, subject to the two-month expiry.

The Free plan runs on grants, not a balance. It receives 5 daily build credits, capped at 30 per calendar month — Lovable spells out the consequence: you receive daily build credits for the first six days of each month, then none until the next month starts. Free also gets a 20-credit monthly Cloud grant and a 4-credit monthly AI grant. None of those roll over, because usage-specific grants never do.

Pro and Business start at 100 monthly credits at $25 and $50 per month respectively, and both add the two features Free lacks for this question: credit rollover and on-demand top-ups. Both scale by credit volume above that entry tier, so if you are sizing a plan around rollover it is worth reading what each Pro and Business tier actually costs before you commit. Both also still receive the 5 daily build credits, without the Free plan's 30-per-month cap. Because the allocation carries forward, an occasional light month is not wasted — but a long gap still loses value once credits pass the expiry window, and the larger your plan relative to real usage, the more you risk letting expire.

Annual billing changes the expiry math and the ceiling. Monthly plan credits on an annual plan are still issued monthly, but they expire one month after the annual billing period ends rather than two months after issue, and Lovable states annual billing carries higher rollover limits for unused credits alongside its discounted monthly rate.

How does the two-month expiry affect sporadic users?

Sporadic users lose whatever falls outside a rolling two-month window, not everything unused each month — which is a far smaller loss than a hard reset, and a far larger one than 'credits roll over' implies. Two Lovable behaviours soften it: it spends the general credits closest to expiry first, and it can surface a chat nudge when rollover or top-up credits are nearing expiry. Neither helps across a genuinely dormant quarter.

A concrete way to think about it: credits issued in a given month are spendable that month and for the next two, so a heavy build week followed by a couple of quiet weeks rarely wastes anything. What wastes credits is a long dormant stretch — for example, building hard in January, then not touching the app again until May. By then the January–February allocation has expired, even though your subscription kept renewing.

You can watch it happen rather than guess. The Breakdown tab in Settings → Plans & credit usage → Details lists every general credit grant with its type, expiry date, and remaining amount, soonest expiry first, and the History tab records 'Monthly credits expired' as its own event type. If you want to know whether your plan is oversized, that log answers it directly — no estimation required. And if the drain turns out to be a stuck bug rather than a quiet month, our Lovable credit burn calculator prices what repeated Fix clicks on a single error have already cost you.

If your usage is genuinely infrequent — one short project a year rather than continuous building — a always-on monthly subscription may be the wrong shape regardless of rollover, because you keep paying for an allocation that expires before you return. In that case, a lower base plan plus purchased top-up credits (which last about twelve months) during active phases can be more economical. Check your plan's top-up options before assuming the subscription is the cheapest path.

These trade-offs depend on your actual plan cost and usage pattern; the point is to plan active work to fall inside the rollover window rather than discovering expired credits later. Track your consumption for a couple of cycles and you will see quickly whether you are sized correctly.

What should you do with unused credits before they expire?

Spend surplus credits on work that cannot break the app, and check the expiry date before you spend anything. Documentation, comments, and isolated refactors are the safe category; broad structural changes to a working codebase are the expensive one, because a regression introduced in the last days of a cycle costs the new cycle's credits to undo. Manufacturing tasks purely to consume capacity is how a stable app becomes a rescue ticket.

Useful ways to spend surplus credits near cycle-end: Documentation tasks — have Lovable generate inline code comments, README sections, or API documentation for parts of your codebase that are light on documentation. This is low-risk (documentation changes do not affect app behavior) and genuinely useful. Refactoring lower-priority components that are working but messy — consolidating duplicate code, cleaning up unused imports, standardizing component patterns. Exploring a speculative feature or design direction that you have been curious about but have not prioritized. If the exploration does not pan out, reverting is easy and you have not spent credits on a failed debugging loop.

What not to do with surplus credits: Do not prompt Lovable to make broad structural changes to a working stable codebase just to use up credits. Broad structural changes on a stable app are the most likely source of new breakage, and introducing a bug in the last days of a billing cycle means you start the new cycle dealing with a regression rather than fresh capacity. Stability is more valuable than using up your allocation.

An alternative to spend-down: if your usage is consistently well below your monthly allocation and you see no change to that pattern, consider whether you are on the right plan. Downgrading to a lower tier or moving to a different billing frequency may be more economical than maintaining an allocation you consistently under-use. Check Lovable's plan options and any restrictions on mid-cycle downgrades before making changes.

Does annual billing change the rollover situation?

Yes, in three ways at once. Monthly plan credits on an annual plan are still issued monthly, but they expire one month after the annual billing period ends rather than two months after issue — effectively the whole term to draw them down. Lovable also states annual billing carries higher rollover limits for unused credits, and a discounted monthly rate. You switch it at Settings → Plans & credit usage → turn on Annual.

The discount is published, so you can price it exactly rather than estimate. Lovable's tier table lists the 100-credit Pro plan at $25 per month on monthly billing versus $250 per year, which it states as $21 per month — and the annual toggle on the pricing page is labelled '2 months free'. The 100-credit Business plan is $50 monthly versus $500 annually ($42 per month) on the same basis. Higher tiers follow the same two-months-free shape.

The risk of annual billing is committing twelve months of subscription cost to a tool you may stop using. Note also what a switch does not do: it does not convert your existing expiry dates retroactively, since Lovable grants the credits monthly either way. Before switching, assess honestly whether you expect to be actively building with Lovable for most of the next year — if you are exploring, monthly billing preserves flexibility at a higher per-month cost.

How do competitor tools handle credit rollover?

Compare on the shape of the model, not on a rate you read once. Lovable's shape is a subscription balance that rolls over with a two-month expiry, plus separate use-it-or-lose-it daily grants, plus top-ups at $0.30 per credit on Pro and $0.60 on Business. Any competitor is either that shape, a hard monthly reset, or pay-as-you-go — and which one wins depends entirely on whether your usage is steady or bursty.

Pay-as-you-go models — where you buy credits that stay valid until used, with no monthly reset — are structurally better for sporadic users than a subscription with a hard reset. The trade is a higher per-credit rate than the effective subscription rate a heavy user gets. Lovable sits between the two: rollover softens a quiet month, the two-month expiry stops it becoming a bank, and top-ups exist for spikes.

For migration-minded users — those considering moving their app off Lovable's managed environment to their own hosting — this rollover question is part of a broader TCO calculation. An app running on your own Vercel + Supabase stack has zero ongoing AI credit costs after the migration; you pay for hosting (typically $20–$100 per month for an early-stage app) rather than a credit-based subscription. Whether that is more or less than your current Lovable plan depends on how heavily you use Lovable for ongoing development versus initial build.

Is the credit rollover policy a reason to migrate off Lovable?

The credit rollover policy alone is not typically a sufficient reason to migrate off Lovable — the migration costs and effort should be weighed against the credit loss value for your specific usage pattern. However, if you are simultaneously concerned about rollover costs, platform lock-in, ongoing credit dependency, and total cost of ownership, those factors together may add up to a migration case worth evaluating seriously.

The strongest migration case is when you find yourself paying for Lovable credits primarily for maintenance and small feature changes on an app that is substantially complete. In that scenario, an owned codebase on Vercel and your own Supabase instance would incur only hosting costs — no per-prompt charges, no credit limits, no rollover concerns. The migration cost is typically $3,000–$10,000 depending on complexity; the ongoing cost saving depends on how much you currently spend on credits for maintenance work.

A free scoping call can help you assess whether the TCO math points toward migration. We review your app, estimate the migration cost, and compare it against your current monthly credit spend on maintenance and feature work to give you an honest break-even calculation. There is no obligation to proceed, and the calculation itself is often informative even if you decide to stay on Lovable.