Skip to main content
Remixing creates your own independent copy of a project. The copy is a new project that you own, and changes you make to it never affect the original.

​
Why remix a project

  • Duplicate your own work: Keep a safe copy before a big change, or spin off a variation of an app you already built.
  • Start from a public project: Use someone else’s remixable project, or a Lovable template, as a starting point instead of building from scratch.
  • Move work between workspaces or accounts: Remix a project into a different workspace, or use remixing to move projects to another account.

​
Control who can remix your project

The Public remixing toggle in Project settings → Sharing controls whether other people can remix your project via its link. It is disabled by default: until you enable it, your project is a starting point for yourself and your collaborators only. Public remixing is not available in Enterprise workspaces. When public remixing is enabled, anyone with your project’s link copies the latest version of the project. They can’t edit your project, and the original stays unchanged. Because a copy contains your code, people with the link can also view your project’s source code while public remixing is enabled. Someone who only has your project’s public link can’t copy your chat history or the files in its Files tab. You can disable it again at any time. Copies people already made stay theirs. See Project access.
Projects connected to an external Supabase project can only be remixed by people with edit access to the source project.

​
How to remix

You can start a remix from three places:
  • In the editor, open the sidebar, hover the project, and select Remix from its ⋯ menu.
  • In Project settings → Project actions, click Remix.
  • On the dashboard, open a project card’s menu and select Remix.

​
The Remix dialog

The dialog shows these fields:
  • Project name: The name of the copy, pre-filled with the original name.
  • Target workspace: Which workspace the copy is created in. This field only appears when you have more than one workspace. In Enterprise workspaces, remixing into a different workspace requires transfer permission: workspace admins and owners always have it, and editors have it when the workspace’s Editor project transfers setting is enabled.
  • Target folder: Optionally place the copy in a folder. Appears when the target workspace has folders.
  • Include project history: Copies the chat history, including files attached to chat messages, so the conversation context is preserved. The switch is disabled by default and appears only when you have edit access to the original project.
  • Copy project files to new project: Copies the files in the original project’s Files tab. The switch is disabled by default and appears only when you have edit access to the original project.
  • Include custom knowledge: Copies the project’s knowledge. This option only appears when the project has custom knowledge.
  • Region: For projects on the built-in backend (Cloud), the dialog also asks which region hosts the copy’s backend. The region is locked once chosen. See Region selection.
You can enable either switch, both, or neither. The dialog shows neither switch when you remix a Lovable template. Some templates ask you to confirm a security acknowledgment before remixing. In that case, the button reads Acknowledge and remix instead of Remix.

​
What carries over

A remix copies what you need to keep building and leaves behind everything tied to the original’s identity, like its live URL, its collaborators, its secrets, and its app users. Carries over to the copy:
  • Your project’s code
  • Database structure (tables and schema, not the records in them)
  • Chat history, including files attached to chat messages, if Include project history is enabled
  • The files in the project’s Files tab, if Copy project files to new project is enabled
  • Custom knowledge, if Include custom knowledge is enabled
Does not carry over:
  • Database data
  • Version history: the copy’s History panel starts fresh
  • Secrets
  • Custom domains
  • Publish state: the copy starts unpublished
  • Collaborators
  • Service connections (Git sync and connectors)
In practice this means the copy is your app’s code with a clean slate around it: it gets its own new API keys, and it isn’t connected to the original’s secrets, domains, Git repository, or other services. If your app relies on external services, reconnect them and add their credentials again in the copy before it can use them.
Remixed projects don’t carry over subscription-level features unless the target workspace’s plan also includes them.

​
Move a project to another account

Remixing is also the way to move a project between two Lovable accounts, for example when you want your projects under a new email address:
  1. If the project is connected to an external Supabase project, disconnect it first. The destination account has no edit access to the source project, so a connected project can’t be remixed from there. You can reconnect Supabase after the move.
  2. In the source account, enable Public remixing in Project settings → Sharing and copy the project’s link.
  3. Sign in to the destination account and open the link.
  4. Remix the project into the destination workspace. The copy does not include chat history or files from the Files tab because the destination account has no edit access to the original project.
  5. Disable Public remixing again in the source account if you want the original private.
The copy in the new account follows the normal remix rules: what carries over is the same, and subscription-level features apply only if the new workspace’s plan includes them.

​
FAQ

Remixing creates a second, independent copy and leaves the original untouched. Transferring moves the one existing project to a new owner (Project settings → Transfer ownership) or to another workspace (Project settings → Move workspace), so there is still only one project. Remix when you want a copy. Transfer when you want to hand over or relocate the original.
No. A remix is a snapshot of the project at the moment you remix it. Changes to the original never flow into the copy, and changes to the copy never affect the original.
No. Deleting a project is permanent, and there is no way to remix or otherwise recover it afterward. If you want a backup, remix the project before deleting it.
The most common reasons are:
  • The project is connected to an external Supabase project, and you don’t have edit access to the source project.
  • The owner disabled Public remixing in Project settings → Sharing, so it can’t be remixed via its link.
  • The project is in an Enterprise workspace and you don’t have permission to move projects out of it.