v0 client handoff
How to share a v0 site with a client
Separate production publishing from client approval with a stable review link, pinned feedback, an AI-ready change list, and exact-version sign-off.
From build to client review
- 1
Choose the build the client should review
Finish the v0 iteration and connect it to a project or repository. Treat the selected source revision as the candidate, not every intermediate chat preview.
- 2
Create and test a static export
Build a static output when the project supports it. Open the output in a clean browser and verify routes, images, fonts, and responsive behavior.
- 3
Upload the output as a version
Zip the built files with index.html at the root and upload them to one PreviewSend project. Each later upload becomes a new immutable review version.
- 4
Collect client comments
Send the stable link and ask the client to pin comments directly on the elements they mean. Keep email for scheduling, not scattered change requests.
- 5
Apply feedback and request sign-off
Paste the structured revision plan into v0, upload the revised build to the same URL, then send a named approver link for the final version.
Common questions
Why not send the v0 production URL?
That may be enough for an informal look. A dedicated review surface adds account-free pinned comments, version history, revision-plan export, and a separate approval record.
Can PreviewSend run a full Next.js application?
No. PreviewSend hosts static files. A site that needs server rendering, route handlers, runtime APIs, or secrets should remain on a compatible application host.
Will the client link change after revisions?
No. Upload each revised build to the same PreviewSend project and the stable project URL serves the current version.