Out of Lovable credits? How they work and how to keep building without them

How Lovable credits work

Lovable uses one credit balance for everything: building your app, chatting with Lovable, hosting and the built-in backend (Lovable Cloud), AI features inside your deployed app and paid connectors.

Credits come from two places. First, grants for one type of usage. Lovable always spends these first.

Lovable says the monthly grants are temporary and can change.

Second, general credits: your monthly plan credits (Pro and Business), top-ups you buy (Pro and Business) and bonus credits from referrals or promotions. When a grant runs out, the usage it covered moves to your general credits. Lovable spends the ones closest to expiry first.

What one message costs

Plan mode costs 1 credit per message, plus any research its subagents do. In Build mode the cost depends on how much work Lovable does. Lovable gives these examples:

So the 5 free daily credits are about ten small style changes, or two and a half landing pages. Real projects cost more, because Lovable has to read more code.

Chat has its own pricing, usually a fraction of a credit per message. It comes out of the daily chat allowance first, then the daily build credits, then general credits. Lovable says this pricing applies through 31 October 2026, so check it again after that date.

To see what a reply cost, open the More options menu under it and look at Credits used. On long Build mode runs, Lovable stops and asks you once a message reaches 20 credits. You can change that number in your account settings.

When do Lovable credits reset?

The daily chat allowance and the 5 daily build credits reset every day at 00:00 UTC. They do not roll over.

On Free there is a catch. Daily build credits stop after 30 in a calendar month and come back on the 1st of the next month. Pro and Business have no such cap.

Monthly plan credits roll over while your subscription is active, but not forever. On monthly plans they expire 2 months after they were issued. On annual plans they expire 1 month after the annual period ends. Top-ups and referral credits expire 12 months after you get them.

What a credit costs

Pro starts at $25 a month for 100 credits and goes up to $2,250 a month for 10,000. That is 25 cents a credit on the smallest tier and 22.5 cents on the biggest. Business costs double for the same credits ($50 for 100). Annual billing gives you two months free. Free cannot buy top-ups at all.

Prices checked on 20 October 2026.

What stops when you hit zero

• Building stops. Lovable shows a blocking dialog until you have credits again.
• Chat keeps working while the daily chat allowance lasts. After that, it pauses until you add credits or the allowance resets at 00:00 UTC.
• A reply in progress pauses. You get a card where you add credits or pick Finish up.
• AI features in your deployed app stop working.
• Lovable Cloud pauses shortly after: the database, file storage and logins.

That last one is the one people miss. Lovable says the data stays safe, but you cannot reach it until the services run again. Adding credits may not wake them up on its own. Then open More, Cloud, Overview in the project and click Wake up.

Your code does not use credits

This is straight from Lovable's docs. Editing and saving code yourself does not use credits. Editing and committing code on your own computer does not use credits either. Credits are spent only when Lovable's AI does the work.

On Free the code editor inside Lovable is read-only, and downloading the code is a paid feature. But Git sync (GitHub, GitLab and Bitbucket) is on every plan, Free too. So GitHub is your way out, whatever plan you are on.

The sync goes both ways. Lovable pushes its changes to your repository, and commits that reach the synced branch show up back in Lovable. So you can work in Claude Code today, while you have no credits, and continue in Lovable when your credits reset. Same project, nothing lost.

One cost does not go away. If the app on your computer calls Lovable Cloud or the Lovable AI Gateway, those calls count as Cloud and AI usage, the same as calls from your published app.

Keep building in Claude Code

• If the app uses Lovable Cloud, back up the database first, while the backend still runs.
• Connect the project to GitHub: Project settings, Git, GitHub, then Connect next to your workspace connection. Lovable creates a private repository and starts the sync.
• Get the repository onto your computer, start the app and open the folder in Claude Code. The step-by-step guide above walks you through it.
• Lovable suggests making your changes on a separate branch and merging it into the synced branch (usually main) when you are done.

Pushing to GitHub does not change your published app. When you are back in Lovable, publish again. Lovable also suggests telling it what you changed, with a prompt like this one:

I changed [files] outside Lovable to [describe the change]. Keep [behavior or constraint] when making further edits. Now [describe the next change you want].

Do not edit in Lovable and on your computer at the same time. If both sides get commits the other does not have, Lovable pushes its own changes to a lovable-sync branch, and the next sync from GitHub replaces Lovable's version with the GitHub one.

Claude Code, Codex or Cursor

Claude Code is not the only option. All three work on the same GitHub repository.

For scale, the $20 for Claude Pro buys 80 Lovable credits on the smallest Pro tier. Claude Pro has usage limits too. But editing your own code in Claude Code does not touch your Lovable balance, and you keep the same project in both places.

When buying more credits is the better call

If you never want to open a terminal or touch Git, buy credits. That is fine. Lovable is built for people who do not want to see the code, and the steps above take 15 minutes to an hour the first time.

Keep in mind that Free has no top-ups. On Free and out of daily credits, your choices are waiting for 00:00 UTC (or the 1st of the month, if you used your 30), upgrading to Pro or moving the work to GitHub as above.

Sources

1. Lovable docs: Credits and usage
2. Lovable docs: Subscription plans
3. Lovable docs: View and edit your code
4. Lovable docs: Git sync
5. Lovable docs: GitHub integration
6. Claude: Pricing
7. Codex docs: Pricing
8. Cursor: Pricing

• Lovable to Claude Code
• Back up the database of a Lovable app
• Keep Lovable in sync when you edit in another tool
• Should you leave Lovable for Claude Code?
• Lovable pricing
• Lovable migration checklist