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 setting in Project settings → Sharing controls whether people outside your project can make their own copy of it from its link. It is disabled by default, and it is not available in Enterprise workspaces.- Disabled: Only people with access to your project can remix it. Anyone else who opens the link sees a message that the project is private.
- Enabled: Anyone with the project link can see a preview of the latest version of your app and make their own copy of it. Nobody gains access to your project itself.
Who can see and remix your project
Public remixing does not add people as collaborators and does not give them access to the Lovable editor, your project chat history, your code, or your files. It gives everyone with the project link a preview of the app and the option to make their own copy. What a visitor sees depends on whether they are logged in to Lovable.How to remix
You can start a remix from four 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.
- On lovable.dev/templates or the dashboard’s Lovable templates tab, open a template card’s ⋯ menu and select Remix. Preview in the same menu opens the template app in a preview window with a Use template button, which starts the same remix.
The Remix dialog
The dialog shows these fields:- Project name: The name of the copy, pre-filled as “Remix of” followed by 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 project 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, including their collections. 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 instructions. This option only appears when the project has project instructions. You can enable either switch, both, or neither. The dialog shows neither switch when you remix a Lovable template.
What carries over
A remix copies what you need to keep building and leaves behind everything tied to the original’s identity, such as its live URL, its collaborators, its secret values, and its app users. Carries over to the copy:- Your project’s code
- Database structure: tables and the rest of the schema, including database functions and triggers, without the records in them
- Edge functions, which Lovable deploys in the copy’s own backend
- 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
- Project instructions, if Include custom knowledge is enabled
- The names of the secrets you added, without their values
- Database data
- Version history, unless Include project history is enabled
- Secret values
- Custom domains
- Publish state: the copy starts unpublished
- Collaborators
- Service connections (Git sync and connectors)
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:- 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.
- In the source account, enable Public remixing in Project settings → Sharing and copy the project’s link.
- Log in to the destination account and open the link. The project opens as a preview with a Remix button.
- Click Remix and choose the destination workspace. The copy does not include project chat history or files from the Files tab because the destination account has no edit access to the original project.
- Disable Public remixing again in the source account if you want the original private.
FAQ
How do I duplicate a project?
How do I duplicate a project?
What is the difference between remixing and transferring a project?
What is the difference between remixing and transferring a project?
Does the copy stay in sync with the original?
Does the copy stay in sync with the original?
Can I remix a deleted project?
Can I remix a deleted project?
Do people need a Lovable account to open my remixable project link?
Do people need a Lovable account to open my remixable project link?
Can people with the link see my code or project chat history?
Can people with the link see my code or project chat history?
Why can't I remix a project?
Why can't I remix a project?
- 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 from its link.
- The project is in an Enterprise workspace and you don’t have permission to remix it into another workspace.
- The project has payments enabled.
- The project has a connected Shopify store. Disconnect the store to remix the project.
- The project sends emails from its own domain.
What does a remix copy from my project's backend?
What does a remix copy from my project's backend?
Can a remix reach my production services?
Can a remix reach my production services?
- Lovable usually deploys the copied edge functions while it creates the remix, and leaves any it could not to the next time it works on the project.
- Keys or production URLs written into your code still work.
- Database triggers and functions are copied, and they run as soon as the new app uses the database.
- Secret values are not copied, so code that reads a project secret fails until you add it.
Can I remix a project without the built-in backend and connect my own Supabase?
Can I remix a project without the built-in backend and connect my own Supabase?