Lovable's Free plan includes a daily grant of 5 build credits, but you can use no more than 30 build credits in a month. It also includes 20 Cloud credits a month and 4 monthly credits for AI features inside your live apps. Daily build grants expire at the end of the day and do not roll over.
Reviewed for material changes on August 13, 2026
The free plan in one clean list
As of August 12, 2026, a new personal workspace starts on Lovable's Free plan. The build allowance is five credits on a day when credits are available, with a hard ceiling of 30 build credits for the month. It is not five credits every day for a 150-credit month. Once the monthly maximum is gone, tomorrow's reset does not create another five.
Lovable now describes three kinds of free capacity. Build credits pay for work done while making the project. A monthly grant of 20 Cloud credits covers some hosting and backend usage. Free workspaces also receive 4 credits a month for AI features used inside a deployed app. Those balances pay for different work, so twenty Cloud credits cannot be treated as twenty extra build prompts.
- Build: 5 daily credits, up to 30 in a month.
- Cloud: 20 credits per month for running Lovable Cloud services.
- In-app AI: 4 credits per month for AI features used by the app's visitors.
- Daily build grants expire each day; unused daily credits do not roll over.
A credit is not the same thing as a prompt
In Default Mode, Lovable charges according to the complexity of the work. A small style change can use less than a credit; a broader request can use more. Lovable's pricing page gives examples, but they are illustrations rather than a fixed menu. The cost shown in your own message history is the useful number.
Plan Mode is simpler: every message costs one credit and does not change the code. That can be worthwhile for a thorny architectural decision. It is an expensive place to think out loud about button labels, colours or ideas that could have been settled in a note before opening Lovable.
How to get a useful first version from 30 build credits
Do the cheap thinking outside the builder. Decide who the page is for, the one action it should drive, the sections it needs and three visual references. Then give Lovable a bounded first brief. Vague prompts tend to produce vague work followed by a long correction loop.
After the first build, group related changes. Ask for the mobile header, spacing and type scale in one deliberate pass instead of sending three messages while you notice them. Check the preview before the next request, and keep a short punch list so you do not ask it to undo something you asked for ten minutes earlier.
- Write the page outline and real copy before the first build prompt.
- Name the must-keep parts when asking for a revision.
- Batch changes that touch the same component or screen.
- Test forms, links and mobile layouts yourself before spending a credit on polish.
- Use Plan Mode for decisions that genuinely need investigation, not casual brainstorming.
Free credits, referrals and coupon-page folklore
The dependable free allowance is the one shown in your workspace. Lovable's dashboard documentation also says a user can earn 100 credits when a referred person becomes a paid customer; that referral programme is not available on Enterprise plans. Treat it as a referral reward, not a coupon that appears just because somebody clicked a link.
Search results are full of old invite codes and screenshots from earlier pricing systems. Lovable changed its billing model in June 2026, bringing build, Cloud and in-app AI usage into a clearer credit system. If a third-party page disagrees with the Plans and credit usage screen in your account, believe the account screen. Do not open extra accounts or buy questionable credits to work around limits; that is a poor foundation for a project you intend to keep.
When paying makes more sense than rationing prompts
Stay free while you are testing the product and can wait for the allowance to refresh. Pay when the cap is changing the way you work: you are postponing customer fixes, stripping useful detail from requests or losing time rebuilding context after every pause. The right comparison is the subscription against the cost of delay, not against zero.
Before upgrading, read the live pricing page and check the workspace-level details. Lovable plans and credits belong to a workspace, and the members and projects in that workspace share them. A team should decide who can spend the balance and set member limits before inviting everybody into the same pool.
If the free plan is the wrong shape, change the tool
Lovable is strongest when you can describe an app or site and keep steering it in chat. Replit's free Starter plan is useful when you want a code-and-runtime workspace, although it limits Agent to Lite build and its free published app goes down after 30 days. Wix and Framer make more sense when you want a hosted visual editor and are happy to publish on a branded subdomain while testing.
Copycat solves a different first step. It starts from a reference website you own or have permission to use and produces an editable Next.js first draft. That route is paid, not a free-credit workaround. It is worth comparing when recreating an approved design is the job and a blank prompt would simply make you describe a site that already exists.
Sources and checks
Product limits and prices came from the companies themselves:
- Lovable pricing
- Lovable documentation: Create an account
- Lovable documentation: Plan Mode
- Lovable documentation: Workspaces
- Lovable documentation: Dashboard overview
- Lovable announcement: Simplifying billing
Plans move. We date every check so you know when to verify again.