This page covers what happens when a Lovable workspace hits zero credits. Current pricing and credits-and-usage describe one balance; the same official docs say the 13 June 2026 unification is still rolling out. Plan prices stay on Lovable. Cross-builder coupling is on the deployment-limits matrix. This is not a migration tutorial.
If Lovable credits run out, does my published app go down?
Documented current model
Fact Current pricing and credits-and-usage describe one credit balance that can pay for build messages, Cloud hosting and the built-in backend, and AI features the deployed app calls.
Rollout applicability
Unknown — account_dependent Credits-and-usage: unification is rolling out gradually and some workspaces may still see the previous Cloud and AI balance. The 13 June 2026 billing blog: unmigrated workspaces keep their current two-balance setup until they move. Which model a given workspace is on is not published as a universal cutoff.
Published pages (unified model)
Fact On the credits-and-usage zero-credit FAQ: your published site stays live, and its pages keep serving. A live site does not consume credits on its own. Run credits cover work the app does while it runs.
Building (unified model)
Fact Building stops. A blocking dialog appears until credits are available. Work in progress pauses and can resume or wrap up after credits are added.
Cloud and in-app AI (unified model)
Fact AI features in deployed apps stop. Built-in backend services (database, storage, authentication) can pause shortly after the workspace has no available credits. Data stays safe while paused and is not exportable until services run again.
Last verified
Sep 10, 2026, 6:00 PM UTC
Official source conflict
Official sources disagree
Unknown — conflicting Whether every Lovable workspace currently uses one credit balance for build, Cloud, and deployed-app AI
Source A:Lovable pricing — The live pricing FAQ defines credits as one balance that can pay for building, hosting with Cloud, and AI features in user apps. Paid plan credits are added to that balance monthly and can be used flexibly across those uses.
Source B:Lovable credits and usage — Credits-and-usage describes the current model as one credit balance, and on the same page states the update is rolling out gradually. Some workspaces may still see the previous Cloud and AI balance experience. The 13 June 2026 billing blog says unmigrated workspaces keep their current two-balance setup until they move.
Applies to: Workspace-dependent during the 13 June 2026 unification rollout. Which model a given workspace is on is account_dependent.
Decision impact: Do not publish one-balance as unconditional Fact for every workspace. Zero-credit outcomes on credits-and-usage (pages stay live; building stops; Cloud/AI can pause) apply to the unified model. Unmigrated workspaces still have a separate Cloud and AI dollar balance until they migrate.
TraceCheck status: Unresolved — Derived outputs must not treat one side as settled Fact.
Current interpretation: TraceCheck records unified billing as the documented current model on pricing and credits-and-usage, and records the same credits-and-usage page plus the 13 June 2026 blog as official evidence that some workspaces have not migrated.
Last checked Sep 10, 2026, 10:00 PM UTC
Zero-credit outcomes
These zero-credit outcomes are quoted from current credits-and-usage for the unified model. They are not a Fact that every workspace has already migrated.
Surface
At zero credits
TraceCheck will not infer
Static published pages
Fact Keep serving.
That a specific visitor URL is currently reachable.
Builder chat
Fact Stops until credits are added, granted, or the next refresh arrives.
A hidden remaining build quota.
Deployed app AI
Fact Stops working.
Which model a specific app was calling.
Lovable Cloud backend
Fact Can pause; data is retained.
The exact number of minutes until pause. Official text is “shortly after.”
What this page does not do
It does not convert Lovable credits into Bolt tokens or v0 USD credits.
It does not treat one balance as settled Fact for every workspace while official docs still describe a gradual migration from two balances.
It does not treat the 20-credit Cloud grant as a visitor cap. Official hosting docs say the plan does not cap visitors, requests, or bandwidth.
It does not give legal advice about code ownership. Zip download is documented for paid plans; Git sync is documented on all plans. See Lovable.
TraceCheck maintainer: review when Lovable ends the unified-billing rollout, changes zero-credit outcomes, or changes Cloud/AI grant amounts. Do not treat one balance as Fact for every workspace while official docs still describe unmigrated Cloud and AI balances. Do not treat a paused backend as a taken-down static page.