# Lovable Templates: Where to Find Them & How to Use Them

- Tool: Lovable
- Difficulty: Beginner
- Fix time: ~10 min to remix, ~15 min to set up a workspace design template
- Compatibility: Design templates: Business and Enterprise plans. Remixing: available on all plans, but requires the source owner's Public remixing setting
- Last updated: September 2026

## TL;DR

Lovable templates come in two forms: workspace design templates, a Business and Enterprise feature for reusable internal starting points, and remixing, which copies any project whose owner has turned on Public remixing. There is no free-tier gallery of prebuilt niche app templates — most usable 'templates' are either remixed public projects or your own saved starting points, plus a smaller pool of official templates that survived the April 2026 privacy change.

## Why Lovable doesn't have one simple template gallery

Unlike page builders with a large curated gallery of prebuilt niche templates, Lovable's templating story is split across two genuinely different features. Design templates let a Business or Enterprise workspace save a full project as a reusable starting point for the team — share a project with the workspace, then flip the 'Use as a template' toggle in project settings. When creating a new project, anyone in that workspace can choose Design, then Use a template, and get a fully independent copy of the saved project to build from.

Remixing works differently and is not tied to a paid plan on the copying side. Any public project with a shareable URL can, in theory, be remixed by clicking the Remix button or using the three-dot menu — but only if the source project's owner has turned on 'Public remixing' in Project settings under Sharing, which is off by default. A remix produces an independent copy of the code, but secrets, Supabase data, and GitHub connections are never copied over, so a remixed project always needs its own setup pass before it is usable.

The pool of remixable community projects is also smaller than it used to be. After the April 2026 platform incident, Lovable converted all public projects to private by default, except official templates, which remain remixable. Third-party directories like madewithlovable.com still list 510+ community projects for browsing and inspiration, but most of what's listed there is private again and not actually remixable — treat it as a showcase, not a template marketplace.

- Design templates (Business and Enterprise plans) let a workspace save a full project as a reusable internal starting point
- Remixing copies a public project's code, but only if the owner has explicitly enabled Public remixing, which is off by default
- Secrets, Supabase data, and GitHub connections never carry over in a remix — every remixed project needs its own setup
- After the April 2026 incident, all public projects went private by default except official templates, shrinking the pool of remixable community projects

## Before you start

- A Business or Enterprise plan for saving and reusing a workspace design template
- A public project URL with Public remixing enabled, if remixing someone else's work
- A GitHub account and any required API keys ready to reconnect after a remix
- Enough understanding of the source project's schema to safely build on top of it

## How to fix it

### 1. Understand the two template systems before you look for one

*They solve different problems and require different plans*

Design templates are for a team that wants to reuse its own internal starting point across multiple client or product builds — that requires Business or Enterprise. Remixing is for copying any public project (yours or someone else's) that has Public remixing turned on — that works on any plan, but depends entirely on the source owner's setting.

**Expected result:** You know which system applies before searching Lovable's settings for a feature that doesn't match what you actually need.

### 2. Set up a workspace design template on Business or Enterprise

*This is the right tool for a team that repeats the same project shape across multiple builds*

Share the project you want to reuse with your workspace, then open its project settings and enable 'Use as a template.' A workspace can have one default template set at a time. When starting a new project, choose Design, then Use a template, to base the new build on it. The resulting project is fully independent — changes to the new project never affect the original template.

**Expected result:** New projects in the workspace can be created from your saved template instead of a blank prompt, saving setup time on recurring project shapes.

### 3. Remix a public project step by step

*This is the most common way non-Business users reuse someone else's Lovable project as a starting point*

Open the public project's URL and look for the Remix button, or use the three-dot menu and choose Remix. This only works if the owner has enabled Public remixing in their Project settings under Sharing — if you don't see a Remix option, that setting is likely off. After remixing, you get an independent copy of the code, but you'll need to reconnect GitHub, re-add any Secrets, and set up your own Supabase or Lovable Cloud data from scratch, since none of that copies over.

**Expected result:** A new project with the remixed project's code, ready for you to reconnect services and continue building independently.

### 4. Know why fewer public projects are remixable than before

*This avoids frustration when a project you expected to remix turns out to be private*

Following the April 2026 platform incident, Lovable converted all public projects to private by default, with official templates as the exception. That means the community remix pool shrank significantly. Third-party directories like madewithlovable.com still showcase 510+ projects across 25+ categories, but treat that as a source of inspiration and ideas, not a guarantee that any given listed project is still remixable — check its own sharing settings first.

**Expected result:** You stop assuming every showcased project is remixable and check its Public remixing setting before relying on it as a starting point.

### 5. Decide: template, remix, or prompt from scratch

*Forcing a mismatched template often costs more time than starting clean*

Templates and remixes save real time when your project matches a common shape closely — a SaaS dashboard, a landing page, a booking flow. For anything with unique business logic or an unusual data model, starting from a clear, well-scoped prompt (ideally backed by an AGENTS.md describing your architecture) tends to produce cleaner code than adapting an ill-fitting template. If you're evaluating whether a specific template or remix is a good foundation for a client project, RapidDev's engineers can audit a candidate project's schema, auth flow, and code quality before you commit hours to building on top of it.

**Expected result:** A deliberate choice between templating, remixing, and building from scratch, based on how closely the available option actually fits your project.

## Complete code example

File: `TEMPLATE-CHECKLIST.md`

```markdown
# Post-Remix Checklist

Run through this immediately after remixing any Lovable project, before treating it as your own.

## Reconnect Services
- [ ] Connect GitHub (or GitLab) two-way sync — remixes do not carry over the original connection
- [ ] Re-add every Secret the project needs (API keys, third-party credentials)
- [ ] Set up Lovable Cloud or your own Supabase project — data and schema do not copy over

## Audit Before Building On Top
- [ ] Review the database schema and confirm RLS policies are enabled on every table
- [ ] Check the auth flow (providers, redirect URLs) matches your own domain, not the original owner's
- [ ] Read through any AGENTS.md or code comments left by the original project for context you're missing

## Housekeeping
- [ ] Rename the project so it's clearly distinguished from the source
- [ ] Remove any content, branding, or copy that belonged to the original owner
- [ ] Set your own Public remixing preference in Project settings under Sharing
```

## Best practices

- Turn on Public remixing deliberately, project by project — it is off by default since the April 2026 incident
- Immediately after remixing, reconnect GitHub, re-add Secrets, and re-check RLS policies — none of that copies over automatically
- Save your own workspace design template (Business+) once you've built a pattern you reuse across multiple client projects
- Treat madewithlovable.com as inspiration, not a source of guaranteed remixable code — most listed projects are private again
- Do not remix a project you don't fully understand — audit the database schema and auth flow before building on top of it
- Prefer prompting from a clear brief over forcing a mismatched template — cleanup often costs more time than a fresh build
- Keep one workspace default template per recurring project pattern rather than letting several stale ones accumulate

## Frequently asked questions

### Does Lovable have free templates?

Not a dedicated free-tier gallery of prebuilt templates. What exists is remixing (available on any plan, but dependent on the source owner enabling Public remixing) and workspace design templates, which are a Business and Enterprise feature.

### Can I use someone else's Lovable project as a template?

Only if the owner has turned on Public remixing in their Project settings under Sharing, which is off by default. If enabled, click Remix on the public project to get an independent code copy — though Secrets, Supabase data, and GitHub connections never carry over.

### What happened to public Lovable projects in 2026?

After a platform incident in April 2026 exposed chat history and code on public projects, Lovable converted all public projects to private by default, with official templates as the exception. This significantly shrank the pool of remixable community projects.

### How do I save my own template in Lovable?

On a Business or Enterprise plan, share the project with your workspace and enable 'Use as a template' in its project settings. New projects can then be created from Design, then Use a template.

### Are Lovable templates really free code I can just take?

Remixing does copy the code, but it excludes secrets, database data, and service connections, so you still need to reconnect and configure everything yourself. It's a starting point, not a finished, ready-to-run app.

### Is madewithlovable.com an official template marketplace?

No, it's a third-party community directory showcasing 510+ projects across 25+ categories for inspiration. It is not run by Lovable, and most listed projects are private again post-April-2026, so treat it as a gallery, not a source of remixable code.

### What if I'm not sure a template or remix is a good foundation for my project?

RapidDev's engineers can audit a candidate template or remix's schema, auth flow, and code quality before you invest hours building on top of it, so you know upfront whether it's a shortcut or a liability.

---

Source: https://www.rapidevelopers.com/lovable-issues/lovable-templates-guide
© RapidDev — https://www.rapidevelopers.com/lovable-issues/lovable-templates-guide