⚡ AI Analyst
Lovable credits explained with live September 2026 pricing: what each message costs, the real Pro and Business ladders, and what an MVP burns.
Money Flock
Recommended Contents
Comments
MoneyFlock may earn a commission if you subscribe to a Lovable Business plan through links in this article, at no extra cost to you. TJ Alam is a certified Lovable Expert.
A monthly subscription is a bus pass. You pay once, you ride as often as you like, and the number printed on the ticket is the number you pay. Lovable is a taxi meter. The plan sets how many credits are loaded into the meter, and what you actually spend depends on how far you ask the car to drive.
That difference is why so many builders are surprised by their second invoice. Pro is not a flat $25 a month. Read live off the pricing page on 15 September 2026, Pro is a twelve-rung ladder that starts at 20 credits for $5 a month and ends at 10,000 credits for $2,250. Business runs a parallel ladder that costs twice as much per credit through most of its range.
Almost every credit explainer on the web stops at the definition. This one does the arithmetic. It uses Lovable's own published per-message costs, the two live plan ladders as they read today, and a real Pro account balance, to answer the only question that matters before you start: what does an MVP actually burn?
470 credits were spent across the author's Lovable workspace in the 30 days to 14 September 2026.
The Pro credit-tier dropdown on lovable.dev/pricing, opened and read on 15 September 2026.
Lovable's documentation defines a credit as the unit it uses to measure and pay for usage across your workspace. That usage falls into three buckets: build usage, which is the work of planning and editing your app; Cloud usage, which is hosting and the built-in backend; and AI gateway usage, which is the AI features running inside apps you have already deployed.
The part that trips people up is that credits do not arrive from one place. A paid workspace receives four separate grants, each with its own refresh cycle and its own expiry, and only one of them is the number advertised on the plan card.
Where your credits come from
| Credit type | Free | Pro | Business | Expiry |
|---|---|---|---|---|
| Monthly plan credits | None | 100 at $25, up to 10,000 | 100 at $50, up to 10,000 | Roll over while subscribed, then expire |
| Daily build credits | 5 per day, capped at 30 per month | 5 per day, no monthly cap | 5 per day, no monthly cap | End of day, reset at 00:00 UTC |
| Monthly Cloud grant | 20 | 20 | 20 | No rollover |
| Monthly AI grant | 4 | 4 | 4 | No rollover |
| Top-ups | Not available | $0.30 per credit | $0.60 per credit | 12 months from purchase |
Source: Lovable plans and credits documentation and lovable.dev/pricing, both read on 15 September 2026.
The free tier is the cheapest instrument you will ever have for measuring your own burn rate. Five build credits a day, capped at 30 a month, is not enough to ship anything serious, but it is enough to price your own habits before you commit a card. Start a project on the free plan and watch what your first twenty messages cost.
Most software pricing scales with people. Lovable's scales with work. Both Pro and Business advertise unlimited users, so a second developer costs nothing to add and everything to feed. Two people sharing a 100-credit month get roughly half a month each.
Two changes in late August 2026 made that more pronounced. On 26 August, Lovable extended how long it will keep working on a single build message to as much as ten hours, and stated plainly that build messages are billed on the work done, so a message that runs for hours costs more than a short one. On 30 August, goal mode arrived with the same warning attached: a goal costs noticeably more than a regular build message.
Up to 10 hours is how long one Lovable build message can now run, and the bill follows the work rather than the clock on your wall.
The practical consequence is that a vague instruction is now an expensive instruction. "Make the dashboard better" can commit the agent to hours of exploration. "Change the portfolio table header to sticky" cannot. The same discipline that makes a good ticket makes a cheap credit month.
There are two main modes, and they are priced on completely different logic. Knowing which one you are in is the single biggest lever you have over the bill.
Plan mode is for thinking. It investigates a problem, compares approaches and writes a plan, and it never modifies your code. Lovable charges 1 credit per plan message, plus the cost of any subagent research it runs while planning, so a message that triggers deep research costs more than a single credit. Since 3 August 2026, each revision of a plan is itself a plan message and costs a credit.
Build mode implements changes. Pricing is usage-based, and small focused edits cost less than multi-step changes or requests that force the agent to explore the codebase, run browser checks, search the web, or generate images and video. Lovable publishes worked examples rather than a rate card.
Lovable's own worked examples of Build-mode pricing, from its credits and usage documentation on 15 September 2026.
Those four rows are the most useful numbers Lovable publishes. A cosmetic tweak is half a credit. A real feature with logic behind it is a little over one. A whole generated page with images and a theme is two. Every estimate later in this article is built from that scale.
A message sent with the goal command is billed on the work done and costs noticeably more than a normal build message. Images and video generated while building draw on the same build credits, and since 10 September 2026 the usage chart splits build spend from media spend so you can see which is which. Messages sent through the Slack integration use the workspace's credits and are counted against the person who sent them.
Exporting a design from the Figma plugin is free, but building with that design uses credits like any other message. Asking Lovable in chat which plan your workspace is on also uses credits, because it is still a message. There is no free question.
Lovable does not publish an MVP price, so the table below is a MoneyFlock estimate, not a Lovable figure. It is built by applying the per-message costs in Lovable's own documentation to three build shapes, on the assumption that plan messages cost 1 credit and build messages average slightly above the documented "add authentication" example, because real projects include retries.
Estimated credit cost of three MVP shapes
| Build | Plan messages | Build messages | Estimated credits | Cheapest plan rung that covers it | Monthly cost |
|---|---|---|---|---|---|
| Weekend prototype, one screen, mock data | 10 | 40 at about 1.2 | about 58 | Pro 100 credits | $25 |
| Launchable MVP with auth, a database, payments and a custom domain | 25 | 150 at about 1.5 | about 250 | Pro 400 credits | $100 |
| Team-built internal tool with roles, SSO and a design system | 40 | 320 at about 1.6 | about 552 | Business 800 credits | $400 |
MoneyFlock estimate derived from Lovable's published per-message credit costs, 15 September 2026. Treat it as a planning range, not a quote.
Two things about that table are worth saying out loud. The first is that the cheapest honest answer to "what does an MVP cost" is one month of Pro at a rung you will only know after you have measured yourself. The second is that the credits are rarely the largest line. Lovable's own June 2026 costing guide put a small multi-tenant SaaS product at roughly $26 a month all in and under $400 in the first year, with the domain, the payment processor's fees and any external database sitting outside the credit ledger entirely.
$0.30 per credit is the Pro top-up rate, which puts a hard ceiling on what a bad week can cost you: 50 extra credits is $15.
If you are pricing a finance build specifically, the walkthrough in Lovable for finance apps shows where the credits go on a portfolio tracker, from the first prompt through to a working data layer.
Four mechanics account for most of the confused posts about Lovable billing. None of them are hidden, but three of them changed in August 2026 and the third-party guides have not caught up.
Since 17 August 2026, an account includes 10 free fixes, covering both the "Try to fix" button on build errors and the fixes offered by security scans. Each fix you use becomes available again 24 hours later. Past those ten, a fix runs as a normal chat message and uses credits like any other request. If you are debugging hard on a Tuesday, you are paying for it by Tuesday afternoon.
Also on 17 August, Lovable added credit check-ins in beta. When a single message crosses your check-in level, 20 credits by default, it pauses and shows what the message has cost so far. The threshold is adjustable from 20 up to 100,000 credits, or can be switched off entirely in account settings. Leaving it at 20 is the cheapest insurance policy on the platform.
Since 18 August 2026, a message that runs out of credits mid-flight pauses rather than ending, and you can add credits to resume from where it stopped. Your published site stays live and its pages keep serving. What does stop is AI features inside deployed apps, and apps leaning on the built-in Cloud backend can pause. For a live product, that distinction is the one to plan around.
Unused monthly plan credits roll over at the end of each billing cycle as long as the subscription stays active, but rollover is not permanent. The documentation puts monthly plan credits at two months from their issue date, and top-up credits at twelve months from purchase. The account page prints the expiry date on the balance, which is the number to trust.
The author's own Lovable plan page on 15 September 2026. Workspace and collaborator data is cropped out.
Pro at $25 buys 100 credits. Pro at $50 buys 200. The rungs climb to $920 for 4,000 and $2,250 for 10,000, with volume discounts starting at 2% on the 1,200 rung and reaching 10% at the top. Third-party pricing posts almost universally quote the $25 rung as though it were the plan. Open the dropdown yourself before you budget.
Every failed build attempt is billed on the work the agent did, and a loop can eat a day's credits before you notice. Switch to plan mode, which costs a flat credit, and ask it to diagnose the problem before you ask anything to touch the code.
At every rung from 100 to 5,000 credits, the Business ladder costs exactly twice what Pro costs for the same credits: $50 against $25 at 100, $100 against $50 at 200, $2,250 against $1,125 at 5,000. Lovable's own pricing FAQ explains that the higher price reflects the features Business adds rather than a difference in running cost, and notes that the cost of running an app is identical on both. Business is worth buying for the team workspace, role-based access, internal publish, SSO, the security center and design templates. It is a poor way to buy volume.
The five daily build credits reset at 00:00 UTC and expire at the end of the day. They are not savings. On the free plan they are also capped at 30 a month, which is the real ceiling on free usage, not the daily five.
A credit is the unit Lovable bills for build work, Cloud hosting and the AI features in deployed apps. Plan-mode messages cost a flat credit plus research; build-mode messages are priced on the work completed. Credits arrive as a monthly plan allowance, a daily build allowance, and small monthly Cloud and AI grants.
Unused monthly plan credits roll over at the end of each billing cycle while the subscription is active, then expire on a published schedule. Daily build credits never roll over. The Cloud and AI grants do not roll over either.
Yes. A plan-mode question costs one credit plus any research it triggers, and even asking which plan your workspace is on is charged as a message. There is no free chat lane.
Because build mode bills on work done, and a failing build makes the agent explore more of the codebase, run more checks and retry. The ten free fixes absorb the first wave; after that every attempt is a paid message.
Applying Lovable's published per-message costs, a single-screen prototype lands near 60 credits and a launchable MVP with auth, a database and payments lands near 250. Those are planning estimates, not quotes, and the only reliable number is your own first month.
A message in flight pauses instead of failing, and a blocking dialog appears when you try to continue building. Published pages keep serving, but AI features inside deployed apps stop and apps using the built-in backend can pause.
If you are measuring, stay on the free plan for a week and read your own usage chart before you pick a rung. If you already know your burn rate and you are working with other people, the Business plan is the one that adds the team workspace, role-based access, SSO and the security center that a shared build needs. You can compare the plans on Lovable's pricing page and open the credit dropdown yourself rather than trusting a table in a blog post.
If the build is worth more than the experiment, hiring help is the other route. The Lovable Partner Program explains how the Expert and Solution Partner tracks work and what certification actually means, and you can see a certified Expert's directory profile for an example of what a partner listing contains.
TJ Alam is a certified Lovable Expert (Website Builder track) and the founder of Digi Flock Enterprises. He built tjalam.com and cyberdance.in with Lovable, and the plan page shown above is his own working account.
MoneyFlock may earn a commission if you subscribe to a Lovable Business plan through links in this article, at no extra cost to you. TJ Alam is a certified Lovable Expert.