Lovable Pricing in 2026: Plans, Credits & Costs

Lovable's price list looks simple until you try to predict a real monthly bill. The sticker is a plan with a pool of credits, but how fast that pool drains depends on what you ask the agent to do, and since mid-2026 the same pool also pays for your live app's hosting and AI calls. That second change is the one most pricing pages have not caught up with.

I ship production client MVPs on Lovable and Supabase, so I'm not pricing this from a blog post I skimmed. Below is every tier, how credits get spent, and three realistic monthly scenarios built from Lovable's own numbers, not guesses.

Lovable pricing at a glance (July 2026)

A naming note, since it trips people up: Lovable's own plan names are exactly Free, Pro, Business, and Enterprise. You'll see "Teams" used loosely in some third-party roundups. That's likely just a third-party label for Business, since no separate "Teams" plan appears on Lovable's own pricing or docs pages.

The full credit-tier ladder

Both Pro and Business let you pick how many monthly credits you want, and the price scales with the tier. Here's the complete official ladder:

Annual billing knocks the price down at both ends of that ladder I could verify directly (Pro: $21/mo at 100 credits, $1,875/mo at 10,000; Business: $42/mo at 100 credits, $3,584/mo at 10,000), and annual billing also raises the credit rollover limits. Lovable doesn't publish the exact annual price for every tier in between on the pages I checked, so I'm not going to interpolate and pretend those are official. Check the live pricing page for the exact number at your chosen tier.

One more thing worth knowing before you pick a tier: Pro offers a student discount, up to 50% off the base 100-credit tier or a flat $12.50/month off higher tiers, with university email verification, valid for up to 12 months.

How Lovable credits work

This is the part most pricing roundups get stale on fast, because it changed mid-2026.

There are two build modes, and they're priced differently. Plan mode is flat: every message costs exactly 1 credit, no matter what you ask. Build mode is variable, priced by what the AI actually has to do. Lovable's own illustrative examples:

• "Make the button gray" (a tiny style tweak): about 0.50 credits
• "Remove the footer": about 0.90 credits
• "Add authentication": about 1.20 credits
• "Build a landing page with images": about 2.00 credits

Lovable is explicit that these are illustrative, not a price list. Real cost varies with project complexity, how much of your codebase it has to explore, verification and browser checks it runs, web searches, and any image generation it performs. A one-line tweak on a small project and a "add a whole new authenticated dashboard section" request on a sprawling codebase are not the same credit spend even though both are "one message."

The June 18, 2026 change: credits now cover hosting and AI usage too. Before that date, Lovable Cloud usage (your app's database, storage, compute, network, realtime) and AI gateway usage (model calls your deployed app makes) were billed from separate dollar-denominated balances, distinct from your chat/build credits. As of a changelog entry titled "One credit balance and clearer usage insights," Lovable merged all of it. In their own words: "Lovable now uses one credit balance for building your app, hosting and running it with Lovable Cloud, and AI features your deployed app uses." And: "Cloud and AI usage now use credits instead of separate dollar balances, and any remaining Cloud or AI balance was converted into credits at your plan's credit rate." Practically, that means the credits you burn chatting with the builder and the credits your live app burns serving real users now come out of the exact same pool. One caveat worth flagging: Lovable's docs note this rollout is gradual, so a small number of workspaces may still be seeing the older, separate-balance experience while it finishes rolling out.

What burns credits fastest, given all this: heavier Build-mode requests (new features, anything touching images or web search, broad codebase changes) cost more per message than small edits, and once your app is live, its own database reads and writes, file storage, and any in-app AI features are drawing from the same balance around the clock, not just when you're actively chatting with Lovable.

Rollover, and its limits. On Pro and Business, unused monthly plan credits roll over automatically as long as your subscription stays active. That's not indefinite, though: rolled-over credits expire 2 months from issue on monthly billing, or 1 month after the annual billing period ends on annual billing. Top-up credits (available on Pro/Business) expire 12 months from purchase. The daily/Cloud/AI usage grants on Free, Pro, and Business are a different bucket entirely. They reset on a fixed schedule (build credits daily, Cloud and AI credits monthly) and simply vanish if unused; they never roll over. Free has no monthly subscription pool at all, so credit rollover as a concept only really applies once you're on Pro or Business.

What Lovable costs in the real world

These are scenarios built from the credit math above, not a published "typical spend" figure, since Lovable doesn't publish one. Your own mix of edits, features, and live traffic will move these.

Light builder, evenings and weekends on a prototype. Free's 30 monthly build credits only accrue in the first 6 days of the month (5/day, capped there), so it genuinely suits someone who tinkers in short bursts rather than every day. At the illustrative 0.50 to 2.00 credit range per Build-mode message, 30 credits is roughly 15 to 60 messages for the whole month, plenty for a small, low-traffic prototype, thin for anything you're iterating on daily. The moment you want to build most days or add a custom domain, the cheapest real headroom is Pro at 100 credits/month, $25/mo month-to-month or $21/mo billed annually.

Medium builder, an active side project or early MVP with a few real users. Once your app is live with auth and a database, Cloud usage is drawing from the same pool as your chat messages. Daily Build-mode sessions adding features (authentication, forms, small pages) at roughly 1 to 2 credits each, plus modest live-traffic Cloud draw, is a realistic fit for the 400 to 800 credit/month Pro tier, $100 to $200/month month-to-month. If a launch spike pushes you past that, the next rung up is 1,200 credits at $294/month.

Heavy builder, a production client app with a small team and real traffic. Multiple people building in parallel, the code editor and a custom domain in regular use, and a deployed app serving real users, meaning ongoing database, storage, and possibly in-app AI calls drawing on the same credit balance around the clock. That combination plausibly lands in the 2,000 to 4,000 credit/month range, $480 to $920/month on Pro, or $960 to $1,840/month on Business if you need role-based access, SSO, or priority support. This is arithmetic off the official tier table, not a guarantee.

A caveat worth naming directly: third-party guides (not Lovable's own numbers, I could not verify this against any primary Lovable source) commonly cite active builders spending somewhere in the $200 to $500-plus per month range once credit burn adds up. Given the tier table above, that's directionally plausible for a team past the base 100-credit tier, but treat it as an unverified estimate from outside Lovable, not a figure Lovable publishes.

Lovable Cloud and Supabase: what's included

Lovable Cloud is, in Lovable's own words, "a full-stack hosting platform with built-in database, authentication, storage, edge functions, and AI, no infrastructure setup required." Under the hood, it runs on Supabase's open-source foundation, so you get a production-ready backend from day one without configuring Supabase separately yourself.

Two things worth knowing if you're deciding how to set a project up. First, a given project uses either Lovable Cloud or an externally connected/self-managed Supabase project, not both at once, and if you already have an external Supabase integration, it keeps working unchanged. Second, since the June 2026 unification, Lovable Cloud usage draws from the same unified credit balance as your build messages and AI gateway calls, rather than the separate Cloud dollar balance it used to be billed from.

Developers who want direct database access and more portability outside the Lovable ecosystem often connect an external Supabase project instead of defaulting to Lovable Cloud. Either path is a legitimate choice; which one's right depends on whether you value the zero-setup convenience or the extra control.

Lovable vs Bolt, and vs coding tools like Claude Code

Lovable and Bolt get compared constantly because they're both AI app builders, but the pricing shape is similar at a glance and different underneath. As of mid-2026, both start with a free tier and a paid tier from about $25/month. Where they diverge is the billing model: Lovable is credit-based, and since June 2026 that single credit balance covers build messages, Cloud hosting, and AI usage together, while Bolt uses a different billing model entirely. I go deeper on the feature-by-feature differences, including code ownership, backend choices, and how Bolt's own pricing works, in Lovable vs Bolt.

It's also worth separating Lovable from developer-focused AI coding tools entirely, since people sometimes shop them against each other. Lovable is a hosted app builder: your credits pay for the build, the hosting, and the AI together, in one bundled product. Something like Claude Code is a CLI tool for developers who bring their own hosting and infrastructure, priced under a completely different model entirely. If you're weighing that path instead, or alongside Lovable, see my breakdown of Claude Code pricing and the free Claude Code cost calculator to run your own numbers.

Sources

All figures verified against Lovable's own pricing and documentation pages, accessed July 2026 (docs reflect the credit-system change rolled out June 18, 2026):

• lovable.dev/pricing
• docs.lovable.dev/introduction/subscription-plans
• docs.lovable.dev/introduction/plans-and-credits
• docs.lovable.dev/features/cloud
• docs.lovable.dev/features/custom-domain
• docs.lovable.dev/integrations/git-sync-overview
• docs.lovable.dev/changelog
• docs.lovable.dev/introduction/faq

Pricing changes. Check those pages directly before you commit to a tier.

If you'd rather have a production build shipped for you than figure out the credit math yourself, that's the job I do: full-stack MVPs on Lovable and Supabase, built to hold up once real users show up. Book a 30-minute call and we'll scope it against your real feature list, not a guess at your credit tier.