Lovable credits: understand them and save

A credit is the unit that measures your Lovable usage. Your plan sets how many you receive, and each paid action uses some of them.

The number of credits a request uses depends on task complexity. Lovable does not publish a fixed rate per action, so it is better to think in working habits than to count every credit.

• Build and change requests sent to the agent.
• Cloud hosting of the app: database, authentication, storage.
• Built-in AI features your users trigger inside your app.

• Free: 5 credits per day, up to 30 a month.
• Pro and Business: 100 credits a month at the first tier.
• Pro and Business: 5 extra daily credits, with no monthly cap.
• Free, Pro and Business: 20 Cloud credits and 4 AI credits a month.
• Unused monthly credits: rolled over while the subscription is active.
• Top-ups: $15 per 50 credits on Pro, $30 on Business, valid for 12 months.
• Tiers: up to 10,000 credits a month, for $2,250 on Pro and $4,300 on Business.

1. 01

   Frame before you prompt.

   Write down the problem, the users, the screens and the data first. A precise first message avoids a string of fixes.

2. 02

   Split your requests.

   One feature per message. A request mixing three topics produces three half-finished jobs.

3. 03

   Think in chat mode.

   Use chat mode to explore an approach, ask questions and validate a plan before touching the code.

4. 04

   Fix precisely instead of regenerating everything.

   Name the screen, the element and the expected behaviour. “The Save button on the client record does not store the email” beats “it doesn’t work”.

5. 05

   Give context once.

   Put lasting rules (brand, vocabulary, constraints) in the project knowledge instead of repeating them in every message.

6. 06

   Check the preview before moving on.

   A bug spotted right away takes one message to fix. Spotted three features later, it is tangled with everything else.

7. 07

   Roll back instead of stacking fixes.

   If a change goes the wrong way, restore the previous version and rephrase the request.