Can my testers leave comments on a Bolt app without a Bolt account?

Not through Bolt's own share feature — Viewer access requires a Bolt invite, and there's no comment layer in viewer mode anyway. Deploy your app to a live URL first, then share that URL through a review tool that supports guest commenting. Testers open the link in any browser and pin notes to the exact element without creating any account.

What is the difference between Bolt's Share and Publish?

Publish deploys your app to a hosted URL on Netlify or a custom domain — anyone can open it, and it runs with your environment variables intact. Share creates a Bolt-internal invite that lets another person view or edit your project inside the Bolt editor. For feedback from non-builders, Publish plus a review link is the right path; Share is for collaborators who are also Bolt users.

Why do some features break when I share my Bolt app with testers?

Bolt's viewer share mode doesn't pass through your environment variables — API keys, auth tokens, and any backend integrations are unavailable to viewers. So if your app calls an external API or has a login flow, those features appear broken in viewer mode. The fix is to use your deployed (published) URL, where the environment variables run normally.

How do I collect feedback from multiple testers on a Bolt app?

Send everyone the same review link on your deployed URL rather than separate messages. All their comments land in one place, pinned to the same screens. You're not reconciling four text threads describing the same button — you see one set of anchored notes and can reply or resolve each one.

Can I get feedback on a Bolt app that isn't deployed yet?

Bolt's live preview inside the editor is not shareable without giving someone a Bolt account. If your app isn't ready to deploy, share a screen recording of you clicking through it and ask specific questions. For anything interactive, the fastest move is to deploy to Netlify from inside Bolt — it takes one click and creates a public URL you can send for review.

How do I turn tester feedback into Bolt prompts?

Group comments by screen or flow before you prompt. "The onboarding screen has three notes: the Continue button is hard to find, the copy is too long, and the back arrow is missing" becomes one focused Bolt prompt instead of three separate iterations. If you use a review tool with threaded comments, you can copy the whole thread and paste it directly into Bolt's prompt box — it reads the context well.

drafty

How to get feedback on a Bolt app

Quick answer

To get feedback on a Bolt.new app, deploy or publish it first to get a live URL, then share that URL through a review tool so testers can leave pinned comments on the exact screen they mean — no Bolt account required. Bolt's own share feature lets people view your project, but it has no commenting layer, so testers can only message you separately about what they saw.

Step 1

Deploy your Bolt app and share the live URL for review

Bolt gives every project a live preview URL the moment you build it, and you can publish to Netlify or a custom domain from inside Bolt. That URL is what you share for feedback — not the Bolt editor link, which requires the reviewer to have a Bolt account. Once your app is live at a public URL, paste it into a review tool (Drafty, Markup.io, or Ruttl all support live URLs). Send the review link instead of the raw URL. Your tester opens it in their browser on desktop or phone, clicks the exact button or screen they mean, and leaves a note anchored right there. No Bolt account, no install, no screenshot guessing. The gotcha most bolt builders hit: Bolt's built-in share creates a viewer link into your project, not a standalone hosted URL — if your app relies on environment variables (API keys, auth tokens), the viewer sees broken features in that mode. Use the deployed app URL instead.

Step 2

Use Bolt's share feature for collaborators who have Bolt accounts

If your reviewers are other builders or teammates already on Bolt, the built-in share is the right tool. Click Share in the top right, choose Viewer or Editor, and send them the invite link or email. Viewers can explore the preview and duplicate the project, but they cannot edit your code or prompt Bolt further. Editors can read and change code. Neither role has a comment layer inside Bolt — there's no way for a viewer to pin a note to a specific element and have it show up in your inbox. For structured feedback from people inside Bolt, you still need an external step: ask them to message you with screen-specific notes, or pair the Bolt share with a review link on your deployed URL. Co-owner access (full editing + publishing) requires a Teams plan. Personal plan users can only share Viewer or Editor access.

Step 3

Walk through it on a screen share, then prompt Bolt in real time

A 30-minute screen share with your tester is the fastest way to catch flow problems a deployed link might miss. Open your Bolt app (the live URL, not the editor), share your screen on Zoom or Google Meet, and resist the urge to explain what each screen does before your tester reacts. Ask "what would you tap first here?" before pointing out the primary action — their first instinct is the data. One thing builders don't expect: you can keep Bolt open in another tab and prompt fixes live during the call. Your tester watches the change appear in the preview while you're still on the call. This is the fastest feedback loop in vibe coding — a round-trip from "this button is confusing" to a fixed version in under two minutes, while the tester is still looking at the screen. Take notes during the call; send the list back as a Bolt prompt summary when you're done.

Step 4

Send screen-specific questions, not an open link

"What do you think?" returns "looks cool." Screen-specific questions return usable answers. Before you send the link, write one question per main screen: "On the onboarding screen, is it clear what the app does before you sign up?" or "Can you find the settings page without me showing you?" You can add these as a short Typeform or even a plain text message alongside the review link. Cap it at five questions — anything longer kills completion rates from people doing you a favour. Pair the questions with a review link so testers can pin the thing they're reacting to rather than describing it in text. The combination — pinned comments on the live URL plus screen-specific questions — gives you both the precise location of the problem and the reasoning behind it.

The faster way

Bolt builds the app; it doesn't give your testers a way to mark it up. Drop your deployed Bolt URL into Drafty and send the review link — testers tap the exact screen or button they mean and leave a note pinned right there, no Bolt account or login required. Every comment lands in one thread. You fix it in Bolt, re-deploy, and mark it resolved.

Open a live demo

Questions

Can my testers leave comments on a Bolt app without a Bolt account?: Not through Bolt's own share feature — Viewer access requires a Bolt invite, and there's no comment layer in viewer mode anyway. Deploy your app to a live URL first, then share that URL through a review tool that supports guest commenting. Testers open the link in any browser and pin notes to the exact element without creating any account.
What is the difference between Bolt's Share and Publish?: Publish deploys your app to a hosted URL on Netlify or a custom domain — anyone can open it, and it runs with your environment variables intact. Share creates a Bolt-internal invite that lets another person view or edit your project inside the Bolt editor. For feedback from non-builders, Publish plus a review link is the right path; Share is for collaborators who are also Bolt users.
Why do some features break when I share my Bolt app with testers?: Bolt's viewer share mode doesn't pass through your environment variables — API keys, auth tokens, and any backend integrations are unavailable to viewers. So if your app calls an external API or has a login flow, those features appear broken in viewer mode. The fix is to use your deployed (published) URL, where the environment variables run normally.
How do I collect feedback from multiple testers on a Bolt app?: Send everyone the same review link on your deployed URL rather than separate messages. All their comments land in one place, pinned to the same screens. You're not reconciling four text threads describing the same button — you see one set of anchored notes and can reply or resolve each one.
Can I get feedback on a Bolt app that isn't deployed yet?: Bolt's live preview inside the editor is not shareable without giving someone a Bolt account. If your app isn't ready to deploy, share a screen recording of you clicking through it and ask specific questions. For anything interactive, the fastest move is to deploy to Netlify from inside Bolt — it takes one click and creates a public URL you can send for review.
How do I turn tester feedback into Bolt prompts?: Group comments by screen or flow before you prompt. "The onboarding screen has three notes: the Continue button is hard to find, the copy is too long, and the back arrow is missing" becomes one focused Bolt prompt instead of three separate iterations. If you use a review tool with threaded comments, you can copy the whole thread and paste it directly into Bolt's prompt box — it reads the context well.

Keep exploring

How to get feedback on an app How to get feedback on a website How to get feedback on a web design Design feedback tool

Stop emailing files back and forth.

Share one link. They comment on the exact spot — no account, always the current version.

Open a live demo