KBAISE/ for lovable
Library
Docs

Remix a project

about 3 minFirst appchecked 7d agoOfficial page
The short version

Remixing creates a completely separate duplicate of an app that you can edit without affecting the original. The new copy keeps your code and database layout, but leaves behind actual database records, secret passwords, custom domains, and live connections.

Anyone who wants to duplicate their app safely before making big changes, start from a template, or move an app to a different workspace or account.

Do this, in order

  1. 1

    Open the project menu by clicking the three dots on your project card in the dashboard, or go to Project settings then Project actions, and select Remix.

    This starts creating an independent copy of your project.

  2. 2

    Enter a name for the new copy and choose the destination workspace and folder.

    This determines what the new app will be called and where it will live in your account.

  3. 3

    Toggle on 'Include project history', 'Copy project files to new project', or 'Include custom knowledge' if you want to keep your previous chat messages, uploaded files, and instructions.

    These options are turned off by default so copies start fresh unless you explicitly choose to carry them over.

  4. 4

    Click Remix to generate your new project.

    Lovable sets up the new app with its own backend and opens it for you.

  5. 5

    Go to Secrets in your new project settings and enter the actual values for any API keys or credentials.

    Lovable copies secret names so you remember what is needed, but secret values are never copied for security.

  6. 6

    Reconnect any third-party tools like Git, custom domains, or external databases.

    The new project starts completely detached from all live connections and publish states.

Paste this into your project

Scan the entire codebase of this remixed project for any hardcoded API keys, secrets, or external service URLs that were written directly into the code instead of being loaded from environment secrets. List any that you find so I can replace them safely.

Words decoded

Remix
Creating a brand new, independent clone of an existing app. Editing the clone never changes the original.
Database structure (schema)
The blueprint or skeleton of your database tables, columns, and rules, without any of the actual user rows or saved information.
Secrets
Private keys, passwords, or tokens used to connect securely to outside services.

Where people get stuck

  • Your database records and actual data are not copied over; only empty tables and their structure are duplicated.
  • Secret values (like API keys) do not carry over, so any integrations will fail until you enter those values again in the new copy.
  • If you wrote API keys or external service URLs directly into your code instead of using Secrets, your remixed copy will still talk to your original external services.
  • Public remixing exposes the full latest version of your app's code to anyone who copies it via the link, even if the app is unpublished.
  • Projects connected to an external Supabase database, Shopify store, payments, or custom email domains cannot be publicly remixed unless those features or connections are handled first.

The short version, steps, decoder and prompt on this page are written automatically from Lovable's own documentation and can lag or misread it. The official page is always the authority.