How to use Lovable, in short: describe the app you want in plain words, let it build a first version, fix it one change at a time and click Publish. Lovable is an AI app builder from Stockholm that grew out of GPT Engineer, an open source tool built by its CEO Anton Osika. Lovable says a first app takes about ten minutes and needs nothing installed. (Lovable Docs: Quick start (opens in a new tab); TechCrunch (opens in a new tab))

The catch is credits. Every build costs some, the free plan gets only a few a day, and an October 2026 review says vague prompts and repeated fixes burn through them quickly. This guide covers what you get for free, the steps to a first published app, and prompts that keep the cost down. (Lovable Docs: Plans and credits (opens in a new tab); AppLaunchpad: Lovable review (opens in a new tab))

Lovable free plan, credits and prices

The free plan includes 5 build credits a day, up to 30 a month. Once you hit 30, daily credits stop for the rest of the calendar month and come back on the 1st. Daily credits refresh at midnight UTC and do not roll over. Free users also get small monthly grants for Lovable Cloud, its backend, and for AI features inside the apps they build. (Lovable Docs: Plans and credits (opens in a new tab); Lovable Docs: Subscription plans (opens in a new tab))

Build mode is priced by the work done. Lovable's own examples: a color change costs about 0.50 credits, removing a footer about 0.90, adding user login about 1.20 and a landing page with images about 2.00. Plan mode, where Lovable thinks with you before writing code, costs 1 credit per message. If you stop a build, you pay only for the work it finished. (Lovable Docs: Plans and credits (opens in a new tab))

Pro starts at $25 a month for 100 credits, plus the 5 daily build credits with no monthly cap. It adds code editing and download, custom domains, removal of the Edit with Lovable badge and rollover of unused monthly credits. Business starts at $50 a month and adds team features such as single sign-on and role-based access. Students and teachers can get 50 percent off Pro for up to 12 months. (Lovable Docs: Subscription plans (opens in a new tab))

On the free plan you cannot edit or download the code and cannot use your own domain, but Git sync with GitHub, GitLab or Bitbucket is included. Publishing is free on every plan. (Lovable Docs: Subscription plans (opens in a new tab); Lovable Docs: Quick start (opens in a new tab))

How to use Lovable: your first app, step by step

1. Create an account

Sign up with email, Google, GitHub or Apple. You can also type your idea on the homepage first; Lovable keeps the prompt and asks you to sign up when you submit it.

2. Describe your app in Build mode

Type in the prompt box with Build selected in the mode picker. Any language works. Be concrete: what the app is, who it is for and which sections or screens it needs. You can also attach a sketch, a design or a screenshot as a visual reference, start from a template, or build from a link.

3. Watch the first version appear

The first build takes a few minutes. The editor has the project chat on the left and a live preview on the right.

4. Change one thing at a time

Ask for a single change, then check the preview before the next one. Every change is saved as a version you can restore, so a bad edit does not break the app for good.

5. Point at what you want changed

For small fixes, use the preview toolbar to select an element and describe the change. For text, use Edit text inline and type straight onto the page. Lovable's own docs recommend this over writing a new prompt for small fixes.

6. Test it on a phone screen

Click every button and link, then use the device toggle to switch to Mobile view. Most people will open your link on a phone.

7. Publish

Click Publish in the top right. Lovable suggests a lovable.app address that you can edit. The live site is a snapshot: later edits show up in the preview right away, but reach the live site only when you click Publish again and choose Publish changes.

Lovable prompts that save credits

Lovable's prompting guide suggests building in a fixed order: the foundation (the product, the audience and the one key action), then the design direction, then one component at a time with real text, and finally a clear limit on what each change may touch. It also suggests saving your design rules in the project instructions so they carry across prompts. (Lovable Docs: Prompting best practices (opens in a new tab))

Prompt 1: The foundation

Build a one-page website for [product], made for [audience]. The one thing visitors should do is [key action, for example book a table]. Sections: [list of sections]. No login or database yet.

Prompt 2: Plan before building (use Plan mode)

I want to add [feature] to this app. [Describe how it should work in two or three sentences.] Ask me any questions you need in order to fully understand what I want from this feature and how I envision it.

Prompt 3: A scoped change

Only change the [page or section name]. [Describe the change.] Keep the existing styling and leave the rest of the app unchanged.

Prompt 4: A clear design direction

Use a [calm, bold or premium] design: [colors], [type of fonts], rounded corners and generous spacing. Apply it to the whole site without changing any text or layout.

Tip: Use real headlines and button text instead of placeholder text. The docs say placeholder copy hides layout problems that real words reveal. Specific words work better than vague ones: "bold, saturated colors" beats "colorful", and "replace" or "adjust" beats "make this better".

What Lovable is bad at

An AppLaunchpad review published on October 20, 2026 called Lovable one of the strongest tools for turning an idea into a working first version quickly. It also named credit burn as a major weakness, said some users need several prompts to fix a single bug, and said bigger, more complex projects still need manual fixing. Its advice: for a real production app, knowledge of React and backend code becomes much more valuable. (AppLaunchpad: Lovable review (opens in a new tab))

That matches how the credit system works. Each round of fixes costs credits, so a loop of failed fixes is expensive on any plan. If a fix does not work after one or two tries, describe the problem more precisely, or restore an earlier version, instead of repeating the same request.

Tip: Lovable's docs suggest bookmarking milestones in version history and previewing the current version before a risky redesign, so you know which version to return to.

When to pay for Lovable

The free plan is enough to test an idea, build a simple landing page or a small internal tool and publish it on a lovable.app address. Pay for Pro when you need your own domain, want to edit or download the code, or keep running out of daily credits halfway through a project. Teams that need sign-in controls and shared workspaces are who Business is for.