How do I get feedback on something I built in v0?

For a single screen or landing page, ask v0 for one self-contained HTML file, paste it into Comma and send the link — reviewers pin comments to the headline, the pricing card or the button they have an opinion about, with no account. For a multi-page app, build it and upload the output folder to a Comma Website, which puts the same comment layer on the live site.

Why not just send the v0 share link or the Vercel deployment?

Both are fine for showing the work. Neither gives the reader anywhere to say what they think about a specific element, so the feedback arrives as a Slack message describing where on the page the problem is. A v0 chat also keeps changing as you prompt, so the link does not pin the version you asked about.

v0 produced a React component. Can Comma render it?

Not as a component — Comma renders HTML documents. Ask v0 to 'rewrite this as one self-contained HTML file using the Tailwind CDN build and inline JavaScript'. For review purposes the static version is usually what you want anyway: it shows the layout and copy without needing a running Next.js app.

Will Tailwind, icons and charts still work?

Yes, if they load from a CDN. Comma renders the page in a sandboxed iframe with scripts on and allows jsDelivr, unpkg, cdnjs and esm.sh, so the Tailwind CDN build, Lucide from unpkg and Chart.js all work. Local imports from a components folder do not, which is why the self-contained rewrite matters.

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

Share what v0 built

v0 is fast at the part that used to need a designer and a sprint: "a pricing page with three tiers and a comparison table", "an onboarding screen for the mobile app", "a dashboard for these metrics". In ten minutes it looks real. Then it needs to go past a founder, a PM or a client, and the review is where the time goes.

Why the feedback comes back vague

The chat link shows the latest state of a conversation, not the version you meant. If you keep prompting after sending it, the reviewer comments on something that no longer exists.

The deployment URL is a real site, which is the point, and it has no place for the reader to write. So you get "the second card feels off" in a DM, and a round of "which second card?"

A screenshot loses hover states, the mobile layout and everything below the fold, and nobody can quote the copy back to you.

What you want is the page, frozen at the version you chose, with a comment thread attached to each thing someone points at.

One screen or a landing page

In v0, ask: "Rewrite this as one self-contained HTML file. Use the Tailwind CDN build, inline all JavaScript, and replace imported components with plain markup."
Copy the file. Check it renders in the free HTML viewer if you want to be sure.
Paste it into Comma and send the link.

Reviewers select the headline, the tier name or the CTA and leave a comment pinned to it — commenting on HTML. No Vercel account, no v0 account, no Comma account.

The page runs in a sandbox with scripts on, so toggles, tabs and carousels still work. Libraries load from jsDelivr, unpkg, cdnjs and esm.sh. What will not work is anything that called your API — the static copy has no backend, which for a design review is usually what you want.

A multi-page app

When the thing under review is the flow, not one screen, use a Website instead of a report. Build the project (npm run build), zip the output folder (dist/, out/ or build/), and upload it on the Websites tab. Comma hosts it on an isolated deployment and puts the same anchored comment layer over the live pages.

Two limits worth knowing while the feature is new: the upload carries text files only, so reference images by absolute URL rather than bundling them, and anything that needs a server at runtime (API routes, server actions) needs to be deployed somewhere that runs a server.

The comments are also readable by an agent. The MCP tool list_website_comments returns each comment with the page path and the element it was left on, so a coding agent can work through the review and mark each one resolved as it fixes it.

Who can see it

A report can be a public link, password-protected, invite-only, or limited to your team or email domain — sharing options. A Website starts private; invite reviewers as commenters or make it public with comments on. Either way a client can review a prototype without it being indexed or forwarded around.

The second round

Take the comments back to v0, get the revision, and update the same report. The link you already sent now shows the new version, the previous one stays in the revision history, and open threads carry over so the person who raised a point can check it and resolve it.

Try it

Publish your v0 page →