Lovable credits, explained for operators

Lovable defines a credit as "the unit Lovable uses to measure and pay for usage across your workspace." One balance covers five kinds of usage:

In the usage screens, build and chat appear together as Build credits, and Cloud, AI gateway and connector usage as Run credits. These are reporting views, not separate balances.

Two points operators tend to miss:

• Credits belong to the workspace, not the person. Everyone you invite shares the pool. Lovable doesn't charge per seat: workspaces allow unlimited members on every plan, so adding people changes how fast credits go, not the subscription price.
• A credit isn't worth the same on every plan. Lovable's pricing page says the value of a credit and the rate at which credits are used "depend on your subscription plan and the feature used." Its docs give a plan credit rate of $0.25 a credit on Pro and $0.50 on Business. For Cloud and AI gateway usage, Business deducts fewer credits for the same usage, so the dollar cost is the same on both plans. Lovable doesn't say whether Plan or Build mode messages cost fewer credits on Business: its build examples give one figure, with no split by plan.

Every workspace gets some free, use-it-or-lose-it grants. Paid plans add a monthly credit balance on top.

Included grants (all except Enterprise)

Lovable doesn't publish the size of the daily chat allowance. It calls the Cloud, AI and connector grants, and the current chat pricing, temporary and subject to change. Chat pricing is stated to apply through October 31, 2026. Enterprise plans get none of these grants; their credit terms are set by contract.

The 30-a-month cap is easy to misread. Lovable's docs give the example: on Free you get daily build credits "for the first 6 days each month (6 × 5 = 30), then none until the next month starts." Five a day doesn't mean five every day.

On a paid plan the daily credits add up, if the docs' no-cap rule applies to you (see the note on regional plans above). On Pro, if you build on every day of a 30-day month, the daily grant gives you 5 × 30 = 150 build credits on top of your monthly balance (155 in a 31-day month). Daily credits are granted every day but expire at the end of the day, so they only count toward work on days you build.

For how Lovable's free plan compares with other builders, see free plans compared.

Reset times

• Daily build credits and the daily chat allowance: every day at 00:00 UTC.
• Free plan monthly grants and the Free 30-credit cap: the 1st of each calendar month at 00:00 UTC.
• Paid monthly plan credits: at the start of each billing period, on the same date each month that your subscription started.
• Paid Cloud, AI and connector grants: with your billing cycle.
• Member credit limits and the auto top-up spend limit: the 1st of each calendar month at 00:00 UTC, whatever your billing date.

Do unused credits roll over?

Monthly plan credits do, on paid plans. Unused monthly credits carry over at the end of each billing cycle as long as your subscription stays active. They keep their original expiry date, so rollover buys time, not permanence.

Grants don't. Daily build credits, the daily chat allowance and the monthly Cloud, AI and connector grants expire on their own schedule. Free plans have no rollover.

When credits expire

Lovable spends usage-specific grants first, then the general credits closest to expiry.

If you cancel, you keep using remaining credits until the end of the billing period, then drop to Free. Unused paid credits reactivate if you re-subscribe before they expire. Credits aren't refundable.

There's no official per-app figure. There are two kinds of number around, and they disagree.

What Lovable says

• Plan mode: 1 credit per message, plus the cost of any subagent research Lovable runs while planning, so a message that needs deep research costs more than 1 credit. Plan mode never changes your code.
• Build mode: depends on the complexity of the request and the work done. Lovable's examples:

The landing-page figure differs between Lovable's own pages. The docs give 2.00 credits for "Build a landing page with images"; the pricing page gives 1.70 for "Build me a landing page, use images" (3 generated images, a theme and 5 sections). We can't tell which is more current. The docs call all of these figures illustrative.

• Chat mode and Chats: priced per message, "typically a fraction of a credit," and covered first by the daily chat allowance.
• Goals: a Build mode message set with the /goal command "costs noticeably more" than a regular build message, because Lovable keeps working until the goal is met.
• Stopped requests are charged for the work done so far. Stopping before any change is made costs nothing.

What users report

User reports from r/lovable, not facts confirmed by Lovable:

• In a thread asking how much people have spent building apps, users give per-app totals such as 80, 400, around 900 and 1,510 credits (some posters say “tokens”).
• In a thread asking how many credits people spend, reports run from about 300 to 3,000 credits per project.
• One user's write-up of their experience says most requests cost 3 to 5 credits. It also describes the free plan as 30 credits a month (5 a day), which matches Lovable's docs, and a 100-credit pack for EUR 25.

These run well above Lovable's examples, which start at half a credit for a small edit. The reports don't establish what was built or which plan it was on, we couldn't confirm when each was written, and Lovable moved hosting and AI usage onto the same credit balance in 2026 (June 1 at the earliest). Treat them as a rough range, not a quote.

Why estimates vary so much

• Fix loops. A change that breaks something costs a second prompt to repair, and sometimes a third.
• Scope changes. Adding a feature halfway through often means reworking screens you'd already built.
• Exploration. Lovable says requests that need more codebase exploration, verification, browser checks, web search or image generation cost more.
• Long runs. A single Build mode message can run for up to 10 hours.

All of these are in Lovable's docs:

1. Per message: open the More options (three-dot) menu under any Lovable reply. It shows Credits used, even while Lovable is still working.
2. Balance at a glance: click your workspace name at the top of the sidebar, on the dashboard or in the editor. The credit bar shows what's left, not what's used.
3. Full breakdown: Workspace settings → Plans & credit usage → Usage details. Filter by credit type (All, Build or Run credits) and by project, over the last 30 days, 90 days, all time, or a custom range of up to 90 days. The person and group filters only work when viewing Build credits: admins and owners can filter by member (others see only their own usage), and group filtering is limited to admins and owners on Business and Enterprise.
4. Expiry dates: on Pro and Business (not Enterprise), the Breakdown tab of the credit balance details lists each general credit grant with its expiry date. The History tab (Pro, Business and Enterprise) shows up to 12 months of credit activity, recorded from March 8, 2026.
5. Ask Lovable in the project chat, for example "How many credits did this workspace use this month?" This uses credits itself.

Usage data can lag by about a minute; new Run credit usage can take up to 24 hours to appear.

Lovable gives paid workspaces several controls. Set them before you invite a team, not after the balance runs out.

• Workspace, project, group and member limits: Workspace settings → Usage limits & alerts. Each limit can send an alert or block usage at the threshold. Available on all paid plans.
• Per-member limit, quick route: Workspace settings → People → three-dot menu on the member's row → Set credit limit. Member limits cover Build credits (build, chat, image and video generation), not Run credits (hosting, AI features, connectors).
• Long-run check-ins: by default, Lovable pauses a Build mode message each time it crosses 20 credits and asks whether to continue. You can set the level anywhere from 20 to 100,000 credits. It's a prompt, not a hard cap, and it's in beta.
• Auto top-up spend limit: if you turn on auto top-up, set a monthly spend limit. The default is 400 credits; "No limit" is an option, so check the setting.

What happens at zero: building stops and work in progress pauses. Your published site stays live, but AI features in the app stop working and the built-in backend can pause. Adding credits may not restart the backend on its own; you may need to open More → Cloud → Overview and select Wake up. For a tool your team relies on, that's the strongest argument for alerts and a top-up plan.

Top-ups are only available on Pro and Business. Free workspaces have to upgrade.

• One-time top-up: Add credits → Buy once, from 50 to 10,000 credits. Credits arrive instantly and last 12 months.
• Auto top-up: buys credits when your balance falls to a threshold (25, 50 or 100 credits), up to the monthly spend limit you set.

Top-ups cost more per credit than subscription credits: $0.30 against $0.25 at Pro's lowest tiers. Lovable says that if you consistently need more each month, upgrading is usually better value. Upgrading from Pro to Business pauses auto top-up until you confirm the higher price.

This is a way to plan, not a prediction. All prices are the vendor figures above; the per-prompt and per-app figures are the vendor examples and the user reports already labelled.

Step 1: List the changes. Write down each screen and each change you expect to ask for: "add a table of open deals", "add a filter by owner", "add login". Count them. Add a line for fixes: a change that breaks something costs another prompt to repair.

Step 2: Price each change two ways.

• Vendor low end: Lovable's examples, 0.50 to 2.00 credits per Build mode message, plus 1 credit per Plan mode message (more if Lovable runs subagent research while planning).
• User-reported high end: 3 to 5 credits per request.

Budget to the high end. The gap between the two is your uncertainty.

Step 3: Compare with your allowance. Here is the arithmetic, using the per-app totals users report (80 credits at the low end of the threads above, 3,000 at the high end):

Two things stand out. Free is fine for trying Lovable but too small for a real internal tool at the user-reported rates. And on Pro, a bigger tier beats topping up a small one: 400 credits cost $100 on the Pro 400 tier against $115 as Pro 100 plus top-ups.

Step 4: Add running costs. Building is the burst; Run credits are ongoing. Lovable says hosting for "most users with smaller or new apps" is minimal and covered by the included grant. Apps with significant traffic or size start drawing on your balance. If your tool calls AI models, the AI grant is 4 credits a month, so check usage after the first week.

Step 5: Spread it out. Paid monthly credits roll over until they expire (2 months after issue on monthly billing), and daily credits only count on days you build. A build spread across several weeks uses more of the free daily credits than the same build crammed into a weekend.

• Plan before you build. A Plan mode message costs 1 credit, plus any subagent research Lovable runs while planning, and never changes code. Agree the plan, then build it.
• One change per prompt. Lovable says small, focused edits usually cost less than large, multi-step requests.
• Write a short spec first. Screens, fields, who uses it. Fewer surprises means fewer fix loops and fewer scope changes.
• Ask questions in Chat mode. Chat messages are typically a fraction of a credit and use the daily chat allowance first (pricing stated as temporary through October 31, 2026).
• Stop runs that go wrong. You pay only for the work done so far.
• Be careful with /goal. Lovable says a goal costs noticeably more than a regular build message.
• Build a little every day. Daily build credits don't roll over, so a day without building wastes them.

A Lovable credit is defined by Lovable's own pricing, and Lovable says credits aren't even equal in value across its own plans, so don't assume it matches a credit on another platform. Our tracker lists the other builders we follow. For Lovable against specific alternatives, see Lovable vs Base44, Lovable vs Replit and Lovable vs Bolt.new. For the full picture on Lovable, including plans, hosting and fit for non-coders, read our Lovable review. For how we rate tools, see how we test.

How many free credits does Lovable give?

The free plan gives 5 build credits a day, capped at 30 a month, plus a daily chat allowance and monthly grants of 20 Cloud credits, 4 AI credits and 1 connector credit. Once you hit 30, daily build credits stop until the 1st of the next month at 00:00 UTC.

How much do Lovable credits cost?

Pro starts at $25 a month for 100 credits, or $0.25 a credit. Business starts at $50 for 100 credits, or $0.50 a credit. Tiers from 1,200 credits up cost slightly less per credit. Top-ups cost $0.30 a credit on Pro and $0.60 on Business.

How many credits does it take to build an app in Lovable?

There's no official figure. Lovable's illustrative examples range from 0.50 credits for a small edit to 2.00 for a landing page (its pricing page says 1.70 for a similar prompt), and Plan mode costs 1 credit per message plus any subagent research Lovable runs while planning. In r/lovable threads, users report most requests costing 3 to 5 credits and totals from about 80 to 3,000 credits per app or project.

When do Lovable credits reset?

Daily build credits and the daily chat allowance reset every day at 00:00 UTC. Paid monthly plan credits arrive at the start of each billing period. Free plan monthly grants and the 30-credit monthly cap reset on the 1st of each calendar month at 00:00 UTC.

Do Lovable credits roll over or expire?

Paid monthly plan credits roll over while your subscription is active, but still expire 2 months after issue on monthly billing, or 1 month after the annual period ends on annual billing. Top-up credits last 12 months. Daily credits and monthly grants don't roll over.

How do I see how many Lovable credits I've used?

Open the More options menu under any Lovable reply to see that message's credits used. For totals, go to Workspace settings, then Plans & credit usage, then Usage details, where you can filter by credit type, project and time range. When viewing Build credits, admins and owners can also filter by member.

Can I buy more Lovable credits?

Yes, on Pro and Business. You can buy a one-time top-up of 50 to 10,000 credits or set up auto top-up with a monthly spend limit. Pro top-ups cost $15 per 50 credits and Business top-ups $30 per 50. Free workspaces need to upgrade first.

Can I stop one team member using up all the credits?

Yes, on paid plans. Workspace owners and admins can set monthly credit limits for each member, group, project or the whole workspace under Usage limits & alerts, either as alerts or hard blocks. Member limits reset on the 1st of each month at 00:00 UTC.

Full profile: Lovable review. Comparisons: Lovable vs Base44, Lovable vs Replit, Lovable vs Bolt.new, Lovable vs v0, Lovable vs Cursor.

All tools side by side: the tool tracker or the full guide index.