Client feedback on Vercel and Netlify preview deployments
Vercel and Netlify both build a preview for every change, and both let people comment right on it. That is handy for your team. For a client, it usually means making an account first. This guide covers how Vercel preview comments and Netlify's Drawer handle client access, what deployment protection does to your preview links, and the options when a client shouldn't need an account. Every Vercel and Netlify fact below is from their own docs and pricing pages, checked 18 November 2026.
How preview links work
A preview deployment is a copy of your site built from one branch or pull request, at its own address, separate from your live site.
- Vercel gives each preview two kinds of link: a branch link that always shows the latest commit on that branch, and a commit link that stays fixed on one commit. Vercel's Share button defaults to the branch link, which is the one to send a client so they don't need a new address after every push.
- Netlify builds a Deploy Preview for each pull request, at an address like
deploy-preview-42--mysitename.netlify.app. Every deploy also has a permalink that starts with the deploy ID, and its contents never change.
Whether a client can open that link depends on protection settings, which are covered below. Whether they can comment depends on accounts.
At a glance
| Vercel Comments | Netlify Drawer | |
|---|---|---|
| Where it lives | The Vercel Toolbar on preview deployments | The Netlify Drawer on Deploy Previews and branch deploys |
| Price | Free on all plans | Reviewer accounts are free |
| Client needs an account to comment | Yes, a Vercel account | Yes, a Netlify Reviewer account |
| Approval step | Invite, access request, or a Shareable Link | A Developer on your team approves each reviewer |
| Preview locked by default | Yes, Vercel Authentication | Private by default for teams created on or after 28 July 2026 on credit-based plans |
| Password option | Pro, $20 a month per protected project; not on Hobby | Pro on credit-based plans; not on Free or Personal |
| Extras | Slack threads, email notifications, CLI | Screenshots, video, links to project trackers |
From vercel.com and docs.netlify.com, their docs and pricing pages, on 18 November 2026.
Vercel Comments: who can comment
Comments are part of the Vercel Toolbar and are switched on for every preview deployment, on every plan, free of charge. Vercel's docs are clear about the catch: everyone who comments must have a Vercel account.
Anyone on your Vercel team with access to the project can comment by default. For people outside the team, Vercel gives you three ways in, all from the Share button in the toolbar or dashboard:
- Invite them by email. Vercel recommends this for external collaborators. They are not added to your team, but they log in to their Vercel account to comment, and to view the preview if it is protected. Hobby accounts can have one external collaborator at a time.
- Accept an access request. If someone without access logs in to the toolbar, they can press Request Access, and you get an email to approve or deny it.
- Set access to Anyone, or Anyone with the link. Without protection, Anyone lets any visitor who logs in with a Vercel account leave comments. With protection on, Anyone with the link creates a Shareable Link that gets past the login, and people with it can log in to the toolbar and comment.
In every case, a client who wants to comment ends up creating a Vercel account. For a developer or a product team that is no trouble. For a client who just wants to say the headline is wrong, it is one more step that can delay a round.
Vercel Comments do a lot well: threads can link to Slack, pull request owners get an email for each new comment, and a popup tells people when a newer preview is ready.
The Netlify Drawer: who can comment
On Netlify, feedback happens in the Netlify Drawer, a panel on your Deploy Previews and branch deploys. Reviewers can leave comments, take screenshots and video, and send feedback to your team's project tracker.
A client using it goes through these steps, from Netlify's reviewer quickstart:
- Open the deploy link and choose to collaborate on the Deploy Preview.
- Select Create a free account to set up a Netlify Reviewer account with your team, then confirm their email from the invite.
- Wait for a Developer on your team to approve the request.
- Log in to the Drawer with those Reviewer credentials.
The Reviewer role is free for the client and for your team, and Netlify's docs present the Drawer as a current feature. It still means a sign-up and an approval before the first comment.
Deployment protection: can the client even open the link?
Before accounts come into it, check the preview opens at all. Both hosts now lock previews by default in many setups.
Vercel
Vercel's own guide says Vercel Authentication is on by default for deployments. Visitors to a protected preview are sent to a Vercel login, and only people with access get through. Your options, all in the project's Deployment Protection settings:
- Vercel Authentication: included on all plans. Only logged-in team or project members, people you've granted access, and holders of a Shareable Link can view.
- Shareable Links: included on all plans, but Hobby accounts get one link in total. The link uses a query string to get past protection, and you can revoke it.
- Password Protection: $20 a month per protected project on Pro, included on Enterprise, not available on Hobby. Existing Pro teams on the legacy Advanced Deployment Protection package pay $150 a month for the whole team.
- Protection Bypass for Automation: a secret for tools such as test runners, included on all plans.
- Turn protection off for the project, so anyone with the link can view the preview.
For reference, Vercel Hobby is free and Pro starts at $20 a month, with unlimited viewer seats on Pro.
Netlify
On Netlify's credit-based plans, each project has a visibility setting, with separate choices for production and previews. A project can be public, private (behind Netlify login, for your team and people you invite) or password protected. Teams created on or after 28 July 2026 start with new projects private, and previews stay private unless you change the preview setting. Older teams default to public.
- Free ($0) and Personal ($9 a month): no password protection. A private project can only be seen by the Team Owner.
- Pro ($20 a month, unlimited members): a shared password, which you can apply to previews only and leave production open.
- Enterprise and legacy plans use the older Password Protection settings, including team login on Enterprise.
So on a newer Free or Personal Netlify team, your client can't open a preview at all until you make it public.
Options for clients who shouldn't need an account
If the client is senior, busy, or just allergic to sign-up forms, here are the realistic routes, from least to most change:
- Let them view, and collect comments some other way. An unprotected preview or a Vercel Shareable Link lets them see the site without an account. The feedback then arrives by email or a call, without the context of where on the page it belongs.
- Use a review tool that doesn't need an account. Make the preview public for the review round, paste it into a tool that wraps the page with comments, and send that review link. Several tools work this way; we compare them in feedback tools where clients don't need an account.
- Skip the host and upload the built file. For a single page, build it and upload the HTML file to a review tool, so the preview's protection doesn't matter. For other ways to turn a file into a link, see how to share an HTML file as a link.
Step by step: a no-account review round with HTMLAnnotate
This is how the second and third routes work with HTMLAnnotate.
- Pick the stable link. On Vercel, copy the branch link from Share. On Netlify, use the Deploy Preview address.
- Open it in a private browser window. If you see a Vercel login, a Netlify login or a password page, HTMLAnnotate will hit the same wall. It can't import a page behind a password prompt or a sign-in.
- Open it up for the round. On Vercel, change the project's Deployment Protection so previews are public, then turn it back on after sign-off. On Netlify, set preview visibility to public. If you can't do either, build the page and upload the HTML file instead: up to 1 MB on Free, 10 MB on Pro and Team.
- Share it. Paste the link at htmlannotate.com/new, or upload the file, and copy the review link.
- Send the review link with a short note on what to check. Your client opens it in any browser, gives their name and email once, and clicks any heading, button or image to leave a comment pinned to it. No account, nothing to install.
- Check phone and tablet. Reviewers can switch views, and desktop, tablet and phone comments are kept apart, so a note about the phone menu doesn't land on the desktop layout.
- Ship the next version. Push your fixes, let the host build a new preview, and share it again. For an uploaded file, publish a new version on the same review link; earlier versions keep their comments.
A deployed site runs live on the review copy, with its scripts and menus, and reviewers can move between pages, each with its own comments. Forms don't submit on the review copy. Review links are private: only people with the link can open them, and search engines don't index them. Free covers 1 active project with unlimited reviewers, and links last up to 14 days; Pro is $15 a month and Team is $40, with links that never expire.
If your site came out of Cursor and you want the agent to read the comments and make the fixes, follow getting client feedback on a site built with Cursor, which covers that MCP loop end to end. For v0, Lovable or Bolt prototypes, see reviewing AI prototypes with stakeholders, and for staging sites in general, the staging links page.
Which should you use?
- Use Vercel Comments when the reviewers are your own team, or a client already comfortable with developer tools. It's free, sits on the real preview, and links to Slack.
- Use the Netlify Drawer when your team is on Netlify and wants screenshots, video and feedback sent to a tracker, and reviewers don't mind a free Reviewer account.
- Use a no-account review link when the client won't sign up, when several stakeholders need to comment, or when you want phone and desktop feedback kept apart. Make sure the preview opens without a login for the round, or upload the HTML file.
Questions
Do clients need a Vercel account to comment on a preview?
Yes. Vercel's docs say Comments are free on all plans, and the only requirement is that every user has a Vercel account. A client can view an unprotected preview without an account, but needs one to open the toolbar and comment. Checked 18 November 2026.
Do clients need a Netlify account to use the Netlify Drawer?
Yes. They create a free Netlify Reviewer account with your team, and a Developer on your team approves the request before they can sign in to the Drawer. The Reviewer role costs nothing for them or for you. Checked 18 November 2026.
Why does my Vercel preview ask for a login?
Vercel Authentication is on by default, so preview URLs send visitors to a Vercel login. You can change it in the project's Deployment Protection settings, invite the person, approve their access request, or share a Shareable Link.
How much does password protection cost on Vercel and Netlify?
On Vercel, Password Protection is $20 a month per protected project on Pro, included on Enterprise, and not available on Hobby. On Netlify's credit-based plans, a shared password is a Pro feature; Pro is $20 a month with unlimited members. Checked 18 November 2026.
Can HTMLAnnotate open a password-protected preview?
No. HTMLAnnotate can't import a page behind a password prompt or a sign-in page, so the preview has to open in a private browser window with no login. If you can't open it up, upload the built HTML file instead.
Should I stop using Vercel Comments or the Netlify Drawer?
No need. They work well for your own team, who already have accounts. Many teams keep them for internal review and use a no-account link only for clients.
Paste your preview link or upload the built HTML file. Free, and your client never needs an account.
Start a free review