Fix guide · updated 2026-11-11
Lovable remix blocked: why you can't remix a project and how to fix it
can't remix a project · Remix missing · the link says the project is private · Projects with payments cannot be remixed
You want a copy of a Lovable project (your own, a teammate's, or one someone shared with you), but Remix doesn't work: the option isn't there, or the link only says the project is private. Lovable's docs list six cases where remixing is blocked. Find yours below. Most are cleared with one change by the project's owner or a workspace admin.
Not logged in?
When you open a remix link without being logged in to Lovable, you see a preview of the app and a Remix button. Clicking it opens Log in to remix. After you log in or create an account, Lovable brings you back to the same page. Click Remix again: the first click only logged you in.
The six blocks and how to clear each one
- Public remixing is off. It is off by default. Then only people with access to the project can remix it, and anyone else who opens the link sees a message that the project is private. The owner turns it on in Project settings → Sharing → Public remixing. It doesn't exist in Enterprise workspaces.
- The project uses its own Supabase project (an external Supabase connection, not Lovable's built-in backend). Only people with edit access to the source project can remix it. Ask the owner for edit access. To move it to an account that has none, the owner disconnects Supabase first and reconnects it after the move.
- Enterprise workspace, copy going to another workspace. That needs transfer permission. Workspace admins and owners always have it. Editors have it only when the workspace's Editor project transfers setting is on, so ask an admin.
- Payments are enabled. Lovable's docs are flat on this: once payments are enabled, the project cannot be remixed, and the docs offer no way around it. If you plan to reuse a project as a starting point, remix it before you turn payments on.
- A Shopify store is connected. Disconnect the store (Lovable's Shopify docs show how), then remix.
- The project sends emails from its own domain (a custom sender for app and login emails). The FAQ lists this block without a fix. Disconnect from this project, on the sender row in Project → Settings → Domains, clears the project's email setup and keeps the sender in the workspace, so try the remix after that. Meanwhile the live app's login emails come from Lovable's default sender. The domain stays with the original: setting it up again in the copy fails with a message that the domain is already in use.
Moving a project to another Lovable account
Remixing is how Lovable moves a project between two accounts, for example to a new email address:
- If the project is connected to an external Supabase project, disconnect it first. You can reconnect it after the move.
- In the old account, turn on Public remixing in Project settings → Sharing and copy the project's link.
- Log in to the new account and open the link. The project opens as a preview with a Remix button.
- Click Remix and choose the workspace. The copy won't include the chat history or the Files tab, because the new account has no edit access to the original.
- Turn Public remixing off again in the old account if you want the original private.
If you want the one existing project somewhere else rather than a copy, transfer it instead: Project settings → Transfer ownership (new owner) or Move workspace (another workspace).
The copy worked, but things are missing
That is by design. A remix copies the code and leaves behind what belongs to the original:
- The database is empty. Tables, functions and triggers come over, the records in them don't. Bring data across yourself if you need it.
- Secrets have names but no values. Open Secrets in the copy and enter each value again, or anything that calls an outside service fails.
- No domain, no Git sync, no connectors, no collaborators, and the copy starts unpublished. Reconnect what you need and publish it.
- Chat history, Files tab and project instructions come only if you switch them on in the Remix dialog, and the first two only when you have edit access to the original.
- Plan features carry over only if the new workspace's plan includes them.
The copy is a snapshot. Changes to the original never reach it, and changes to the copy never touch the original. If the copy builds but breaks when published, see Lovable published site not working.
Sources: Lovable docs, Remix a project (including "Why can't I remix a project?"), Payments (Limitations), Shopify, Custom emails and Project access.
Other Lovable app problems? See Fix a Lovable app.