DEV Community

Israr Kundi
Israr Kundi

Posted on Originally published at israr-kundi.web.app

Lovable Credits Ran Out? Why Your Live App Stopped Working

Lovable credits ran out is the first thing to check when your Lovable app breaks and you changed nothing. One credit balance pays for building your app and for running it, so when that balance hits zero, parts of your live app stop working — while the pages themselves stay up.

The problem: "I changed nothing, and the app broke"

Your homepage still loads. But the AI chat feature returns an error or nothing at all. Login stops working. Data will not load. Nothing was edited, nothing was published, and the app worked yesterday.

That mix — pages up, features dead — is the signature of an empty credit balance. Lovable's own docs say AI features in deployed apps fail with an error when the credits run out, and Lovable shows no message for the failed calls themselves. Your visitors see a broken product, not an offline one, and you get no clear error pointing at the cause.

The cause: one balance pays for building and running

Since June 2026, Lovable has run on a single credit balance. Building in the editor, the built-in backend (Lovable Cloud), AI features inside your published app, and managed connectors all draw from the same pool. Before that, build credits and the Cloud and AI balances were separate pots.

Each month starts with small grants — 20 credits for Cloud usage and 4 for AI usage — and then your general credits pay for the rest, closest to expiry first. The part that catches people out is that visitors spend your credits too. Every AI call and every database read in the live app draws from the same balance you build with. A busy week can drain it even if you barely touched the editor.

When the balance hits zero, Lovable's docs list what stops:

  • Building stops, and work in progress pauses.
  • AI features in your deployed app stop working.
  • The built-in backend pauses: database, storage, and authentication. Your data stays safe, but you cannot access or export it until the services run again.
  • Your published pages keep serving, and chat keeps working while the daily chat allowance lasts.

Lovable does warn you first. Workspace admins and owners get an email when credits are likely to run out before the monthly refill, showing the expected run-out date and the refill date, plus banners on the Plans & credit usage page and the Database, Users, and Storage views. But the email goes only to admins and owners, and it is easy to miss one email among many.

The minimum fix: Lovable credits ran out

  1. Check the balance first. Go to Workspace settings, then Plans & credit usage. Look for the out-of-credits banner and the expected run-out and refill dates. If the balance is zero, you have found the cause.
  2. Add credits. On Pro and Business, a workspace admin or owner can buy top-up credits. On the Free plan, daily build credits refill each day, or upgrade to a paid plan.
  3. Resume what paused. Select Resume on any paused build work, and Wake up on the paused backend. AI features in your app start working again within a few seconds once credits are available.
  4. Test the live app yourself. Try the AI feature and the login before you tell users it is fixed. The pages loading does not prove the features work.
  5. Stop it happening again. On paid plans, set usage limits that warn you or block further spend when a threshold is reached. Turn on auto top-up if the app serves real users. Check the usage dashboard once a week — it breaks spend down by project, and by building versus running the app.

What NOT to do: do not rebuild or republish the app. The code is not broken, and republishing spends more credits. Do not keep asking the chat to fix it either — each message spends credits from the same empty balance. And do not take "the site loads" as proof the app works. Static pages stay up at zero credits; the features behind them do not.

When to get help instead of fixing it yourself

Get help when the balance looks fine and the app still fails — then the cause is somewhere else, and guessing costs more credits. Get help too when credits drain faster than you can explain, or when the app serves paying customers and this has happened more than once. A developer can trace which project and which feature is eating the balance, add error messages so users see something useful instead of a silent failure, or move the backend and AI calls somewhere they are billed on their own.

If this is your app, contact me through https://israr-kundi.web.app

Top comments (0)