Lovable · Setup guide
How to set up Lovable
Build a small full-stack web slice from a browser prompt, review the preview and generated code, then connect GitHub before any serious team or production work.
Lovable
browser · checked August 14, 2026
The “Open Lovable” link goes to the vendor site. It is not an affiliate-tracked link on this page — no commission is claimed for that click. Affiliate disclosure.
Before you begin
- A Lovable account and a modern browser.
- A small product brief with explicit boundaries for data, auth, and deployment.
- A GitHub account if you want an owned repository and two-way sync.
Authentication
Lovable account sign-in and optional GitHub/GitLab OAuth
Account: Lovable account; GitHub or GitLab for repository sync
Git sync grants Lovable permissions to manage the new repository it creates. Review scope before approving.
Install or open it
1. Get the harness ready
These steps are written for beginners. On Mac, Terminal is the black/white text window where you type commands. On Windows, use PowerShell or Terminal. Use the OS tabs to hide steps that are not for your computer, then copy one command at a time.
- 01
Open Lovable in your browser
You do not install Lovable on your computer for the standard workflow. Open Chrome, Safari, or Edge, go to lovable.dev, and create an account or sign in.
Lovable welcome - 02
Create a project
Start a new project from the home screen and describe a small, concrete first page in plain language.
Lovable welcome - 03
Preview in the browser first
Use in-app Preview as staging. It is not a production publish. Check the generated page at desktop and mobile widths before you treat anything as live.
Lovable deployment - 04
Publish only when you intend to go live
Publish creates a permanent *.lovable.app snapshot. Do not click Publish just to share a draft — Preview is the staging step. Auth/RLS can differ between preview and the published snapshot.
Lovable deployment - 05
Connect GitHub (creates a new repo)
Open Project settings → Git and connect GitHub. A workspace owner/admin must authorise the Lovable GitHub App; project linking is a narrower repository scope than org-wide access. Lovable creates a new repository for the project — it does not import an existing repo as the primary path. GitLab is also supported. Review the permission screen carefully.
Lovable GitHub integration
Repository or project
2. Start in the right place
Keep the first repository small, clean, and easy to roll back while you learn the harness’s permissions and context model.
- 01
Start with a constrained brief
Describe one page or workflow, its acceptance criteria, and what should remain out of scope.
Lovable welcome - 02
Publish, then sync to a new Git repo
Publish to *.lovable.app first. Then connect Git so Lovable can create/sync a repository — do not expect to attach an existing production monorepo as the first step.
Lovable Git sync overview
First run
Prototype a read-only page
Use this task to test the workflow before handing over a larger repository or production responsibility.
- 01Ask Lovable to build a static page with a small, explicit acceptance checklist.
- 02Review the generated code and test the in-app preview at desktop and mobile widths.
- 03Publish to *.lovable.app, then connect Git only after the preview is correct.
Why this is safe: A read-only prototype exercises prompt-to-code quality without introducing credentials, payments, or destructive data operations.
Stop and review if
- The generated app asks for secrets or payment credentials before the static slice works.
- The preview hides errors or introduces an unrequested backend integration.
- Git permissions are broader than the repository you intended to create.
The operating boundary
Privacy, data, and cost
The setup is incomplete until you know what the harness can see, what account pays for it, and who approves a risky action.
Privacy
Lovable processes prompts and generated apps in its cloud. From 2026-09-09, Free/Pro customer data may be used for AI training unless you opt out (Account settings → AI model training → disable Use my Lovable content for model training). Business/Enterprise workspace data stays excluded by default. GitHub/GitLab and backend connections expand the data boundary.
Training on code: tier dependent
Check current Lovable workspace, enterprise, and connected-provider terms for your region and plan.
Sensitive repos: Before 2026-09-09, set Free/Pro training opt-out in Account settings → AI model training if the project is confidential; start non-sensitive, review generated code before adding secrets, and restrict SCM access to the selected repository.
Pricing
Workspace credits (not seats): Free includes limited daily build credits (commonly 5/day, ~30/mo cap); Pro/Business add larger credit pools shared by unlimited members.
Model: usage based
Watch out: Credits cover build + Cloud + AI gateway. Hosting/runtime after grants and external deployments can be separate. Shipped apps often have weak or missing Row Level Security — scan policies before publish.
When setup goes wrong
The generated page looks right but the app does not work after refresh.
Test the preview as a new visitor, inspect routing and data-loading errors, and ask for a reproduction-specific fix rather than a rewrite.
You expected to import an existing GitHub repo.
Lovable Git typically creates a new repository for the project. Export/sync outward, then migrate code into an existing monorepo manually if needed.
Auth or data works in preview but fails after Publish.
Compare preview vs production env vars and Row Level Security / backend rules; republish after fixing policies rather than rewriting the UI.
An external deployment returns a blank page or 404.
Check the platform’s build command, output directory, environment variables, and SPA fallback rules against the current Lovable deployment guidance.
Tables look empty or auth works in preview but fails after Publish.
Compare preview vs production env vars and Row Level Security policies. Independent audits still find weak/missing RLS on generated apps — fix policies before treating Publish as production.
The UI goes blank after an edit.
Use version history / undo in Lovable, reproduce in a fresh preview tab, and ask for a minimal fix rather than a full rewrite.
Next steps
After the first successful run
Keep the pilot small, then compare surfaces and budget before a team rollout.
Setup details change quickly. The page was checked August 14, 2026; use the official source below before installing in a managed or production environment.