Lovable pricing in 2026: plans, credits, and one real build cost
Free starts at $0, Pro at $25, and Business at $50 per month before top-ups. Use the calculator for a controlled Build-credit estimate, then compare it with one observed 2.50-credit response and the production work those credits did not finish.
2.50
Build credits recorded
3m 35s
One response work time
86
Tracked files in clean checkout
$0
Subscription, top-up, and test spend
Lovable starts at $0 Free, $25 Pro, or $50 Business per month.
The entry Pro and Business tiers include 100 monthly credits. Free includes up to 30 daily Build credits per calendar month; paid plans add 5 daily Build credits on active days. Extra 50-credit top-ups cost $15 on Pro or $30 on Business.
Prices were rechecked against Lovable's first-party documentation on August 17, 2026. Figures are monthly USD before tax and exclude Cloud, deployed AI, and foreign-exchange costs.
Lovable pricing answers, without the plan-page shorthand
How much does Lovable cost?
Lovable starts at $0 per month for Free, $25 per month for Pro, and $50 per month for Business before tax. Pro and Business each include 100 monthly plan credits; Cloud, deployed AI, and foreign-exchange costs are separate.
What is Lovable's pricing model?
Lovable combines a monthly plan with Build credits, daily Build grants, optional top-ups, Cloud usage, and deployed AI usage. It is not one flat per-app price, so a production estimate needs all applicable ledgers.
How much do Lovable credits cost?
A 50-credit top-up costs $15 on Pro and $30 on Business in the reviewed snapshot. Free does not offer top-ups. Build-mode usage varies with the complexity and work completed, so one observed 2.50-credit response is a reference unit rather than a universal rate.
Is Lovable Free really free?
Free has a $0 subscription price and up to 30 Build credits per calendar month, issued as 5 daily credits, but it does not offer credit top-ups or a custom domain. Production Cloud, deployed AI, tax, and foreign-exchange costs are not established by the $0 plan price.
One prompt bought a substantial first pass, not a finished production system
Requested in one Build message
- Responsive marketing page with an accessible hero
- Email/password authentication and a protected dashboard shell
- Three seeded evidence records plus one server action
- One environment-backed label and exact local handoff commands
Plan
Free
Prompts
1
Build
2.5 credits
Run
0 credits
Worked
3m 35s
Cash
$0
RECEIPT 01
Lovable reported the requested routes, seeded records, server action, environment fallback, and README in one Build response.
RECEIPT 02
The response worked for 3 minutes 35 seconds and the response menu recorded 2.50 credits used.
RECEIPT 03
The workspace usage page attributed 2.50 Build credits and 0 Run credits to the project over the last 30 days.
RECEIPT 04
A clean checkout contained 86 tracked files and passed its declared production build, but it had no lockfile and its declared preview command failed.
Free, Pro, and Business start with different reasons to pay
Prices and grants below were read from the authenticated plan screen and Lovable's public documentation on August 5. They are USD figures before tax and future pricing changes.
$0/ month
- Plan credits
- None
- Daily Build
- 5/day · 30/month cap
- Cloud grant
- 20/month
- AI grant
- 4/month
- 50-credit top-up
- Unavailable
Testing one bounded project before a recurring subscription.
Daily Build credits stop after 30 in a calendar month, and credit top-ups are unavailable.
$25/ month
- Plan credits
- 100
- Daily Build
- 5/day · no monthly cap
- Cloud grant
- 20/month
- AI grant
- 4/month
- 50-credit top-up
- $15
Repeated building that needs monthly credits, rollover, top-ups, or a custom domain.
The entry price buys capacity and product features; it does not cap Cloud or deployed-AI usage.
$50/ month
- Plan credits
- 100
- Daily Build
- 5/day · no monthly cap
- Cloud grant
- 20/month
- AI grant
- 4/month
- 50-credit top-up
- $30
Teams paying for governance, access controls, and business workspace features.
The entry tier starts with the same 100 monthly credits as Pro; the price difference is not cheaper generation.
Use the receipt as a reference unit, never as “credits per app”
Observed free Build response
2.50 credits ÷ 5-credit daily grant
50% of one day's included Build grant
Cash spend was $0 because the response used the Free workspace's included daily Build credits.
Free monthly Build ceiling
30-credit monthly cap ÷ 2.50
12 same-cost responses
This is an equivalence, not a forecast. Build-mode cost changes with request complexity and completed work.
Entry paid-plan capacity
100 monthly plan credits ÷ 2.50
40 same-cost responses
Paid plans also include daily Build grants, while general credits can cover Cloud and AI usage after specific grants run out.
One 50-credit top-up
50 top-up credits ÷ 2.50
20 same-cost responses
The same capacity costs $15 on Pro or $30 on Business, before tax and only after choosing a paid plan.
Lovable documents Plan mode as one credit per message, while Build-mode cost depends on complexity and completed work. The private 2.50-credit receipt must not be generalized into an average.
Build cost and operating cost are not the same meter
Build
Plan, generate, edit, and update
Build-mode cost varies with complexity and work completed.
Cloud
Database, storage, network, functions, and realtime
Usage begins to matter only after a deployed app runs.
AI gateway
Model choice, tokens, calls, and deployed AI features
This is separate from the Lovable agent that builds the app.
OBSERVED RUN
0
Run credits in the last-30-day project view. The private app was not published, so this is not a production cost sample.
Zero balance is an operating dependency
Lovable documents three separate effects at zero credits: building stops, deployed AI features stop working, and built-in backend services pause shortly afterward. A production budget therefore needs an observed Run ledger, not just an entry subscription price.
2.50 credits produced code, not a no-caveat handoff
Generated state
86 tracked files and a passing production build
Dependency graph
No committed lockfile; install resolved current ranges
Runtime configuration
A tracked environment file retained six configuration entries
Declared start
The documented preview path failed; the generated Worker path rendered
Upgrade for a measured constraint, not for a vague promise of “more AI”
Stay Free
One bounded project fits inside the 30-credit monthly daily-grant cap, and no custom domain or top-up is required.
Free is an evidence budget, not a guarantee that production runtime stays free.
Choose Pro
Repeated building needs monthly credits, rollovers, top-ups, collaboration, or a custom domain.
Buy it for recurring capacity and features, not because one successful response proves the whole project is production-ready.
Choose Business
The team needs governance, workspace controls, roles, or business security features.
The entry tier starts with the same 100 monthly credits as Pro and a higher top-up price.
What this ledger does not claim
One Build response is a concrete receipt, not an average credit cost for every prompt, project, or model change.
The project was not published, so its observed Run usage was zero. This does not establish production Cloud or AI cost.
Lovable's unified Build, Cloud, and AI credit balance was still rolling out gradually on the observation date.
Plan prices and grants are a dated USD snapshot before tax, foreign-exchange effects, or future pricing changes.
The 2.50-credit response generated a substantial first pass, but the clean checkout still exposed a missing lockfile, tracked runtime configuration, and a broken declared preview path.
No subscription, top-up, trial, affiliate URL, public deployment, or advertising spend was used for this evidence pass.
Measure the handoff before buying more generation capacity
The free checklist keeps repository control, independent build, runtime configuration, data recovery, and ongoing operation separate. It stores no project name, credit balance, or free text.
Need a pricing decision tied to search demand and a real buyer?
Useful Mint's fixed SEO Revenue Sprint maps purchase-intent queries, fixes the first technical blockers, and connects the page to a measurable conversion path. It is a service offer, not an affiliate recommendation.
Private usage readback plus current first-party rules
The usage receipt came from an existing private Free workspace, one completed response, the project usage breakdown, and the clean Git checkout. Public documents define current grants, plan tiers, top-ups, Cloud, AI, and external deployment.
No affiliate URL appears on this page. No account identifier, private prompt link, environment value, or repository URL is published.