Advanced

How do I write a good Lovable prompt?

Describe one concrete outcome, give real content and constraints, and say what NOT to touch. Plan first for anything non-trivial, then build in small steps.

How do I get Lovable to follow my design properly?

Give Lovable concrete references — a screenshot, a site to draw from, exact colours and fonts — and store them in Project knowledge so every prompt is checked against the same design rules.

How do I give Lovable a website to use as inspiration?

Paste the site's URL in your prompt and describe which parts to borrow — layout, spacing, tone — Lovable can't literally browse and clone it, so be specific about what you want copied.

How do I get Lovable to copy a design style without copying the website?

Ask for the underlying pattern — layout, spacing, type scale — in your own words and colours, not the site's actual assets, text or exact visual identity.

How do I upload images to Lovable?

Attach images directly in the chat message box — Lovable can use them as design references or as assets to place in your app (e.g. a logo or product photo).

How do I get Lovable to use my logo?

Attach your logo file in chat and tell Lovable exactly where to place it (header, favicon, footer) — it won't guess sizing or position from the file alone.

How do I give Lovable my brand colours?

Give exact hex codes in your prompt or Project knowledge, name which role each colour plays (primary, accent, background), and ask Lovable to apply them via the Tailwind/shadcn theme, not one-off styles.

How do I get Lovable to use a specific font?

Name the exact font (e.g. from Google Fonts) and tell Lovable to load it and apply it across the theme, not just the current page.

How do I make Lovable build one feature at a time?

Ask for one clearly-scoped feature per prompt and confirm it works in Preview before moving on — bundling several features into one message makes failures harder to isolate and revert.

How do I stop Lovable changing things I didn't ask it to change?

State explicitly what must stay unchanged in the same prompt, keep requests narrow, and check the diff/preview after each change so unintended edits are caught immediately.

How do I tell Lovable to only edit one section?

Name the exact page, component or element (or select it via the preview toolbar) and explicitly say the rest of the app should stay unchanged.

How do I get Lovable to plan a feature before building it?

Switch to Plan mode and describe the feature there — Lovable will ask questions and lay out a structured plan for you to approve before any code is written.

How do I get Lovable to review existing code before making changes?

Ask Lovable directly, ideally in Plan mode, to look at the relevant files or feature first and summarise how it currently works before proposing any changes.

How do I make Lovable ask me questions before building?

Use Plan mode and explicitly ask Lovable to raise questions or ambiguities before building — it's designed to clarify requirements first rather than guess.

How do I get better results from Lovable prompts?

Be specific and concrete, use real content, plan before building complex features, work in small steps, and review each result in Preview before prompting again.

Why does Lovable misunderstand my prompts?

Usually the prompt is ambiguous, references something that doesn't exist yet, or bundles too many changes at once — narrow it, add references, and split it up.

Should I use screenshots when prompting Lovable?

Yes, for layout and visual matching — a screenshot removes ambiguity that words leave open, especially for spacing, alignment and component styling.

How do I make Lovable match a screenshot?

Attach the screenshot, say precisely what to match (layout, spacing, colours, all of it), and iterate with follow-up prompts comparing Preview against the image side by side.

How do I undo a bad Lovable change?

Open Version history and revert to the version saved right before the bad change — every change Lovable makes is auto-saved as a version, so you can step back without losing later unrelated work.

How do I safely make large changes to a Lovable project?

Plan the change first, bookmark a known-good version before starting, break it into small ordered steps, and check Preview between each step so you can revert cleanly if one goes wrong.

How do I connect Lovable to GitHub?

Open your project's Settings, go to the GitHub/Git sync integration, authorise Lovable's GitHub app, and choose or create the repository to sync with — Lovable then keeps code in sync both ways automatically.

Should I connect my Lovable project to GitHub?

Yes for most real projects — it gives you a free, portable code backup and lets developers or other tools work on the code, with no real downside beyond one extra setup step.

When should I connect GitHub?

Connect it as soon as the project is more than a throwaway experiment — ideally at the start, and definitely before involving another developer, going to production, or relying on the app for a real business.

Does Lovable automatically sync with GitHub?

Yes — once connected, Git sync is automatic and two-way: changes made in Lovable push to GitHub, and commits pushed to GitHub pull back into Lovable, with no manual export step required.

Why isn't GitHub syncing with Lovable?

Usually a permissions/authorisation issue, a disconnected integration, or a conflicting edit on both sides at once — reconnect the GitHub app and check recent commits on both ends.

Can I edit Lovable code directly in GitHub?

Yes — once Git sync is connected, you (or a developer) can edit code directly in GitHub or your own IDE, and those changes sync back into Lovable automatically.

Will editing GitHub break my Lovable project?

Not inherently — Git sync is designed to handle two-way edits, but structural mistakes, conflicting simultaneous edits, or breaking the build can cause problems that show up back in Lovable.

How do I restore an older version?

Open Version history in your Lovable project, find the version you want, and revert to it — this restores the project's code (and, if bookmarked, is easy to find again) without needing GitHub.

How do I create a backup before making changes?

Bookmark the current Version history entry before you start, and connect GitHub if you haven't already — together they give you an in-app safety net and an independent copy of the code outside Lovable.

Can developers work on Lovable code outside Lovable?

Yes — once your project is synced to GitHub, developers can clone it, edit in their own IDE, run their own build/test tools, and push changes back, all of which sync into Lovable automatically.

Can I use Cursor with Lovable?

Yes. Use Git sync to push your Lovable project to GitHub, then clone that repo and open it in Cursor for local edits, which sync back to Lovable.

Can I host Lovable code somewhere else?

Yes. You can download your project's code or sync it to GitHub via Git sync, then deploy it to any host that supports a Node/Vite React app (Vercel, Netlify, your own server, and so on).