Lovable Credits Explained (2026): What a Message Costs and When Credits Die

Nothing generates more confusion, or more angry Reddit threads, than Lovable's credit system, and almost none of the confusion survives contact with the two official pages that define it: the pricing FAQ and the credits and usage docs. This is the whole system from those sources, with the arithmetic done.

What a credit is

Lovable's docs put it in one line: a credit is "the unit Lovable uses to measure and pay for usage across your workspace", and one balance covers three types of usage:

That unification is recent and matters: hosting and in-app AI are not separate bills, they are the same pool your prompts drain. An app with real traffic and AI features consumes credits while you sleep, which surprises everyone exactly once.

What messages actually cost

Build messages are priced by complexity, and Lovable publishes the anchor points on its pricing page:

Chatting to plan costs on the low end; generation and multi-file changes cost the high end. The per-message price is visible after the fact: hover the three dots on any message in history. That visibility is the underrated feature here; a week of checking it teaches you your personal burn rate better than any guide.

The expiry rules

Credits are perishable, on four different clocks, all from the official FAQ:

Spending order softens this: "Lovable always uses usage-specific grants before general credits. After usage-specific grants run out, Lovable uses the general credits closest to expiry first." Translation: the system burns your most perishable credits first, which is the order you would choose yourself.

Also from the FAQ: credits are not refundable; cancelling keeps your remaining credits alive until the billing period ends, then the workspace drops to Free; and unused paid credits reactivate if you resubscribe.

What each plan really gives you

Yearly billing is two months free. EU visitors see the same numbers in EUR with VAT included (25 and 50), per the live page. And the seat policy that changes the team math: "Workspaces support unlimited members on all plans, and plans are priced by the credits they include, not by seats", with per-member credit limits available to stop one heavy user draining the pool. How that compares to Bolt's per-member $30 is half the Lovable vs Bolt story.

How far do 100 credits go?

Using Lovable's own three price points as the scale: 100 credits is roughly 200 small tweaks, or about 110 mid-size edits, or just under 60 auth-grade features, and in practice a mix. A realistic solo month, one new feature plus fixes per working day at an average around 1 credit per message, lands near 20 to 25 credits a week: tight but workable on Pro if your prompts land first time, impossible if every feature takes three corrections. Which is the actual argument for prompt discipline; the prompting guide is, financially speaking, a companion to this page.

Remember the same pool also feeds Cloud and in-app AI once you have users; a launched app's baseline consumption comes off the top before you type anything.

Keeping burn down

• Specify once: the corrective message costs the same as the one that would have been right.
• Plan in chat, build on approval: planning conversation is the cheap end of the meter.
• Batch same-view micro-edits into one message.
• Watch the history costs weekly and learn which of your habits are expensive.
• Move backend weight to your own Supabase if Cloud consumption is eating the balance.
• Top up rather than upgrade for a one-off heavy month; top-ups keep twelve-month validity.

FAQ

What is a credit? Lovable's usage unit; one balance covers Build, Cloud and AI gateway usage.

Per-message cost? 0.50 to 1.70 credits in Lovable's published examples, visible per message in history.

Rollover? Yes on paid plans, with two-month (monthly) and one-month (annual) expiries; top-ups last a year; daily free grants die same-day.

Free plan? 5 build credits a day, up to 30 a month, plus 20 Cloud credits.

Spending order? Grants first, then general credits closest to expiry.

Refunds and cancelling? No refunds; credits live to period end; paid leftovers reactivate on resubscribe.

Team cost? Unlimited members, shared pool, per-member limits available.

Extra credits? Top-ups (12-month validity) or the yearly plan's two free months.

Where this meter fits among all the others (tokens, dollar allowances, time windows) is the coding-agent pricing comparison; the card with alternatives is in the tools directory.