How do I share a Bolt project for feedback?

Download the project, build it, and upload the output folder as a Comma Website — reviewers get the running app with a comment layer on top. For a single page, ask Bolt for one self-contained HTML file and paste it into Comma instead.

Why not share the Bolt project link?

A project link opens the editor, the file tree and the chat, which is a lot of workspace to hand someone who only needs to look at a screen. A deployed Bolt site is cleaner, but it has nowhere for the reader to leave a comment on a specific element.

Does the WebContainer preview URL work for other people?

Treat it as yours. The in-browser preview runs inside your tab, so it depends on your session and disappears when the tab does. It is a development server, not a share link.

What does the reviewer need?

For a single-page report, only the link — no Bolt, StackBlitz or Comma account, and you choose whether it is public, password-protected, invite-only or limited to an email domain. A full app uploaded as a Comma Website starts private; invite reviewers as commenters or make it public with comments on.

Yes. Unlimited reports and unlimited commenters on the free plan.

Share what Bolt built

Bolt's trick is that the whole stack — Node, the dev server, the package install — runs in your browser tab. That makes the build loop feel instant. It also means the running app is, in a very literal sense, yours: it lives in your tab.

Three links, none of them a review

The preview. It is served by a WebContainer inside your browser. It works for you and stops when you close the tab. Nobody else can open it.

The project link. Opens the editor. Your reviewer wanted a screen and got a file tree, a terminal and your prompt history.

The deployed site. The right thing to demo. Still no way for the reader to put a comment on the thing they mean, so feedback arrives as prose describing where to look.

Review the running app

Download the project from Bolt (or push it to GitHub).
Build it: npm install && npm run build. Most Bolt projects are Vite, so output goes to dist/.
Zip the output folder and upload it on the Websites tab in Comma.

The build is hosted on an isolated deployment, not in anyone's browser tab, and the comment layer sits on top of every page. Reviewers click any element and write — the comment keeps the page path and what they clicked. While Websites is new, uploads carry text files only, so point images at absolute URLs; anything that needs a server at runtime needs to be hosted somewhere that runs one.

Review one page

For a landing page or a single screen:

Ask Bolt: "Output this page as one self-contained HTML file, Tailwind via CDN, JavaScript inline, no imports."
Paste into Comma, or check it in the free HTML viewer first.
Send the link.

Scripts run in a sandboxed iframe and libraries load from jsDelivr, unpkg, cdnjs and esm.sh — commenting on HTML covers what reviewers can do.

Feed the review back

Back in Bolt, paste the comment list and ask for the fixes. If you have moved the project into Claude Code or Cursor, the agent can fetch the comments itself over MCP (list_website_comments), with the element each one refers to, and resolve them as it goes. Publish the revision to the same report or Website so the original link shows the fix.

Try it

Publish your Bolt page →