v0 · AI tool

Get feedback on apps and pages built with v0

Publish your v0 project to its vercel.app address and paste the link into HTMLAnnotate. Clients and teammates comment on the real running app, and the brief goes straight back into the v0 chat.

Free for 3 projects. Reviewers never need an account. Or upload an HTML file.

Why v0 users use HTMLAnnotate

v0 builds real Next.js apps, with many files, components and routes. That makes an uploaded HTML file the wrong tool for feedback, and screenshots worse: they miss menus, dialogs, hover states and how the layout reflows on a phone. The useful thing to review is the running app at its published address, and the people who need to review it are often clients or stakeholders who are not on your Vercel team.

Vercel has its own comments on preview deployments, and they work well for your team. Every commenter needs a Vercel account, though, and inviting outside people to a preview is a Pro and Enterprise feature. Many clients will not create an account for one review. So feedback comes back as an email with five bullet points and no context, and you translate it into a v0 prompt, hoping you picked the right component.

With HTMLAnnotate, you paste the published URL and reviewers comment without any account, clicking the exact button, card or heading in the Desktop, Tablet or Mobile view. Every page of the app keeps its own comments. Copy for AI then gives you one brief listing each element, its CSS selector, page path, view and suggested wording, which you paste into the v0 chat as the next prompt.

How it works with v0

Three steps, about a minute.

Publish from v0

Select Publish in the chat header and publish to production. Confirm the provided vercel.app domain and pick a visibility that lets anyone open the app without signing in.

Paste the link

Paste the production URL into HTMLAnnotate. The app runs live with its own scripts, so navigation, dialogs and menus work for reviewers.

Feed it back

When comments are in, press Copy for AI and paste the brief into the v0 chat. Publish Changes, and the same review link loads the update.

A full review round, start to finish

What a typical round looks like on v0.

Publish to production
In the v0 chat, select Publish. On first publish, confirm the Vercel project, choose visibility, and keep the provided vercel.app domain or pick a custom one. Use the stable production address, not a long per-deployment URL, so the review always loads the latest build.
Make sure it opens without a sign-in
Open the URL in a private window. If you see a Vercel login or password page, change visibility under Project menu, Settings, Vercel Project, or adjust Deployment Protection in the Vercel dashboard for the length of the round. Pages behind a sign-in form cannot be imported.
Create the review link
Paste the URL into HTMLAnnotate. Sign in so the link lasts: 1 day without an account, up to 14 days on Free, forever on Pro and Team. Click through the main routes yourself so you know each page loads and keeps its own comments.
Brief the reviewers
Send the link with the flows you want tested, such as sign-up screen layout or pricing page copy. Reviewers give a name and email once, use Browse mode to move around the app, and switch to Comment mode to pin notes. Forms will not submit on the reviewed copy.
Triage in one place
Label comments Bug, Copy, Design, Question or Idea and set priority. Each comment records browser, OS and screen size, which helps with layout bugs. Preview suggested text on the page and Accept what you want. Tag teammates by @mention or email for anything they own.
Prompt v0 with the brief
Press Copy for AI and paste the brief into the v0 chat. The CSS selectors and page paths point v0 at the right components. Review the new version, then Publish Changes. Reopen the review link to check fixes against each comment, resolve them, and collect Approve clicks.

v0 and Vercel's own tools and HTMLAnnotate

Use both. Here is what each is good at.

What you need	v0 and Vercel	HTMLAnnotate
Comment on a running app	Vercel Comments via the toolbar on preview deployments	Pinned comments on the published app
Reviewer accounts	Every commenter needs a Vercel account	No account, name and email once
Outside reviewers	Inviting external users needs Pro or Enterprise	Anyone with the review link
Notes per screen size	Comments on the page as viewed	Separate Desktop, Tablet and Mobile comments
Visual tweaks	Design Mode edits styles and writes them to code	Not offered, edits happen in v0
Turn feedback into a v0 prompt	You collect and rewrite it	Copy for AI with selectors and page paths

What works

Reviews the running app, with menus, dialogs and routes working
Clients comment without a Vercel or v0 account
Each page of the app keeps its own comments
Separate Desktop, Tablet and Mobile notes
Browser, OS and screen size recorded with every comment
Copy for AI turns the round into one v0 prompt

Good to know

v0 projects are multi-file apps, so publish and paste the URL. Uploading the code or a ZIP will not work.
Vercel's default Standard Protection puts preview and generated deployment URLs behind Vercel Authentication. Use the production domain, which stays public unless you protect all deployments.
Screens behind your app's own login cannot be reached by reviewers, and forms on the reviewed copy cannot be submitted.
There is no direct connection to v0. You paste the Copy for AI brief into the chat.

Tips for better v0 reviews

Use the stable production URL

Every Vercel project has a stable production address that updates when you Publish Changes. Review that one. Individual deployment URLs are protected by default and also freeze on one build.

Add a demo state for logged-in screens

Reviewers cannot get past a sign-in form. If a dashboard matters, ask v0 to add a public demo route with sample data for the round, then remove it before launch.

Look at Tailwind breakpoints

v0 builds with Tailwind, where layouts often change at the md and lg breakpoints. Ask reviewers to check Desktop, Tablet and Mobile, since a card grid can look fine in one and broken in another.

Pair it with Design Mode

Small spacing and color notes can be quicker to fix in v0's Design Mode than by prompt. Use Copy for AI for the bigger items, then resolve the small ones as you apply them.

Questions about v0

Can I upload a v0 project as a file?

No. v0 makes multi-file Next.js apps, and HTMLAnnotate takes only single self-contained HTML files (up to 1 MB on Free, 10 MB on Pro and Team). Publish the project and paste the vercel.app link instead.

Why does my vercel.app link ask reviewers to log in?

Vercel Deployment Protection is on. Standard Protection covers preview and generated deployment URLs, so share the production domain. If you chose to protect all deployments, change visibility for the round, since sign-in pages cannot be imported.

How is this different from Vercel Comments?

Vercel Comments live in the Vercel Toolbar on preview deployments and every commenter needs a Vercel account. HTMLAnnotate works on the published app with no reviewer accounts, separates notes by screen size, and exports a brief for v0.

Will buttons and menus work?

Yes. The app runs live with its own scripts, so navigation, dialogs, tabs and menus work. Forms on the reviewed copy cannot be submitted, so no test data reaches your backend.

Do I need a new review link after I publish changes?

No. The review is fetched fresh each time it opens, so after Publish Changes the same link shows the update, and you can check each fix against its comment.

Do reviewers need a Vercel account?

No. They open the review link in any browser and give a name and email the first time they comment. They never need access to your v0 chat or Vercel team.

Other AI tools

HTMLAnnotate works with any page anyone can open in a browser.

Claude ChatGPT Gemini Lovable Bolt Cursor Replit +See all