Bolt client handoff
How to share a Bolt site with a client
Turn a compatible Bolt build into a stable client-review link, keep feedback on the page, and feed one clean revision prompt into the next build.
From build to client review
- 1
Export the source and run its build
Move the project into a local or repository workflow, install its pinned dependencies, and run the production build documented by the project.
- 2
Inspect the static output
Confirm index.html exists and test the built files in a clean browser. Watch for absolute asset paths and features that silently depend on the development server.
- 3
Create the review project
Zip the contents of the output directory and upload them. Add a project password when the preview should be limited to people who have the shared secret.
- 4
Ask for pinned feedback
Give the client a deadline and ask them to comment on the exact page elements they want changed. They do not need an account or browser extension.
- 5
Build the next round
Turn unresolved comments into a structured prompt, use it for the next Bolt iteration, and replace the reviewed version without changing the client URL.
Common questions
Can I upload my Bolt source folder directly?
Upload the built static output, not source files that still require a bundler or development server. The archive needs an index.html entry point.
Can clients comment without installing anything?
Yes. The review controls load on the hosted preview and reviewers identify themselves with a display name.
How do I avoid losing feedback between revisions?
Keep every upload in one PreviewSend project. Comments remain associated with their exact version while the client continues using the stable project URL.