Please note that some of the terms or concepts mentioned below are only available with the paid plan.
What it is: The homepage or main file of your app. It’s usually the first screen users see.
Example: If you have a blog, /index might list your most recent posts.
As shown in the screenshot below, you'll need to click on the small icon to the right of the top bar. Then, an extra column will appear, containing a list of all the files used for your applications.
.jpg)
What it is: A tool that connects Lovable with Figma and Builder.io so you can turn visual designs into real, working code.
Why it’s helpful: Skip hand-coding UI. Then export from Figma → import into Lovable → build your app visually.
What it is: An interactive assistant mode where Lovable becomes more than a code generator. It’s like working with an intelligent co-pilot or assistant.
What it does: You can ask questions, brainstorm features, get debugging help, or generate content.
Example:
You: “Add a login form to my app.”
Lovable: "Done! Here's the code. Want to add email validation?"
What it is: A side-by-side comparison of two versions of code or files, showing what changed.
Why it's useful: Helpful when reviewing edits or debugging a bug caused by recent changes.
What it is: The place where you make changes to your project — content, layout, or code.
Think of it as: Your design/coding workspace in Lovable.
What it is: A tool for making visual edits to your project using Tailwind-style controls (like padding, color, layout), powered by AI.
Why it’s useful: You don’t need to write CSS manually. You can tweak things visually and Lovable handles the code.
What it is: A timeline of everything you’ve changed in your project.
Why it matters: You can undo, redo, or review changes just like in Google Docs or Git.
Example:
"Oops, I broke the header layout."
Go to History → revert to the last working version.
.jpg)
What it is: A living document where you explain what your app does, who it's for, what features it has, and any other notes.
Why it helps: Lovable uses this to understand your project better and provide more informed suggestions.
What it is: An area where Lovable experiments with new or beta features.
Important: Lab features might be unstable or disappear, but you can use them to try cool new things before they're officially released.
What it is: A way to clone an existing project (yours or public) and use it as a base for a new idea.
Why it's powerful: You can fork someone’s app, test a feature, or create a variation. This without touching the original.
Example:
See a cool public app? Remix it → customise → launch your version.
Note: You can’t remix a project if Supabase is connected.
What it is: A way to view your app as a user would, without publishing it.
Why use it: Test layout, functionality, and user experience live before going public.
If you're using Lovable to build projects faster, this glossary should help you feel confident navigating the platform’s core features.
