How to Share Your Lovable Projects With Other People

Choose the sharing method that matches your goal: publish a live app for visitors, share a preview for feedback, invite collaborators to work on the project, or enable public remixing so others can make independent copies. These options do not grant the same access.

What you will learn and need

You will learn how to avoid confusing website visitors with project editors and how to test a sharing link. You need a project you control and a clear audience. Join Lovable if you still need to create a project.

1. Decide what the recipient should be able to do

Before generating a link, choose the intended outcome. A customer usually needs the live website. A reviewer may need only a preview. A teammate may need project access. A builder who wants their own version needs remix permission, not access to edit your original.

2. Share a live website with visitors

Publish the app, review website-access settings and copy its live URL. A live URL does not automatically permit remixing. Test private app pages with a signed-out session if your app includes accounts.

3. Use a preview for feedback

Use the available shared-preview option for review-only access to work in progress. A preview is not the same as a production launch or an editor invitation. Check the displayed access and availability settings before sending it to people outside your team.

4. Invite collaborators deliberately

Use Share → Invite people and review the role. Available roles depend on the plan. Invite links also add collaborators; do not send an editing invitation when you only want someone to review the app. Use the lowest level of access that meets the goal.

5. Enable remixing only if you want copies

Public remixing is disabled by default and is unavailable in Enterprise workspaces according to the remix documentation. When enabled, recipients can preview the latest app and create their own copy after signing in. They do not become editors of the original, but a remix includes the project’s code: do not enable it for code you intend to keep private.

Review this project for safe public sharing without changing settings. Identify private app data, unfinished workflows and configuration that should not be exposed. Explain the differences between publishing the website, sharing a preview, inviting collaborators and enabling public remixing. Recommend the minimum access needed for customer feedback.

How to verify the link

Open it in a fresh signed-out browser. Confirm the recipient sees the intended app or preview, not an unexpected editor invitation. For an authorised teammate, verify the actual permitted actions. For remix sharing, test that a copy is independent and that private original data is not presented as copied content.

Common errors

• Reviewer receives edit access: use a review-only preview instead of a collaborator invitation.
• Live website has no Remix option: publication and public remixing are separate settings.
• Private page is visible to everyone: review app permissions as well as website-access settings.
• Old link is used after access changes: retest the exact link you intend to distribute.

Frequently asked questions

Does sharing the live URL expose the project editor?

Not by itself. Website access and project access are separate.

Do remixers become collaborators?

No. They create an independent project.

Can I share an unfinished app for feedback?

Use a suitable preview link and review access before sending it.

Official sources and next steps

Share a project, Publish and Remix a project. Next, read what happens when a project is remixed.