Lovable client handoff
How to share a Lovable site with a client
Export a compatible static build, put it behind one stable preview link, collect pinned comments, and send the revision list back to Lovable.
From build to client review
- 1
Export and build the project
Get the project into a local or Git-connected workspace, run its production build, and confirm the output folder contains an index.html file.
- 2
Test the output, not the editor preview
Open the built site locally and click every page. Check mobile layout, asset paths, forms, and any feature that may depend on a server.
- 3
Upload the static output
Zip the contents of the output folder so index.html is at the archive root, then upload it to a PreviewSend project.
- 4
Share one review link
Add a password when the work is sensitive, then send the stable preview URL. The client can comment on the page without creating an account.
- 5
Return the change list to Lovable
Resolve unclear notes with the client, generate an AI-ready revision plan, paste it into Lovable, and upload the next build to the same project URL.
Common questions
Can I share the Lovable preview link directly?
You can, but a separate client-review link is useful when you want one stable handoff, account-free pinned comments, version history, and final sign-off around the exported build.
Will every Lovable project work as a static ZIP?
No. Server functions, runtime authentication, databases, and other backend dependencies need a compatible deployed runtime. Test the production output before uploading it.
Does my client need a PreviewSend account?
No. Reviewers enter a display name on the preview. A named approver can also record a version-bound decision without creating an account.