How do I share a web design with a client for feedback?

The simplest approach: share a link they can open without installing anything. That means a Figma prototype link (requires a free Figma login to comment), a staging URL with a specific set of questions, or a review link from a tool like Drafty where they pin comments without signing up. The key is matching the format to the client — non-technical clients fare much better with a plain URL than with a Figma file share.

Do clients need an account to leave feedback on a design?

Not always. Figma requires a free account to comment. Most dedicated review tools — including Drafty — let clients comment as guests on a public link, with no signup. That removes the single biggest reason clients default back to emailing vague notes.

What is the best way to get feedback on a web design before launch?

Before launch, sharing the staging site as a review link (rather than a screenshot) gives clients the most realistic experience and the most specific reactions. It also catches viewport and mobile issues that a static screenshot misses. Ask three or four specific questions alongside the link rather than an open "let me know what you think" prompt, which tends to produce vague replies.

How do I stop design feedback from being scattered across email and messages?

Share one link and direct all feedback there. When the design lives at a single URL and reviewers can comment on the page itself, there is no reason to take a screenshot and describe it in iMessage. If you are still getting feedback over email, it usually means the review tool has friction — the client needs an account, or the interface feels unfamiliar. Removing that friction (a one-click guest comment on a public link) is the most reliable fix.

Can I get feedback on a live website, not just a design file?

Yes. Tools like Drafty and Ruttl let you paste a live URL and generate a review board where visitors comment on the exact element. This works on the real rendered site — not a screenshot or export — so the client sees the actual fonts, spacing, and responsiveness.

How many review rounds should I budget for a web design project?

Two structured rounds is the standard. The first covers overall direction and layout; the second covers copy, color, and detail. Unstructured rounds — where the scope of feedback is undefined — tend to run to four or five. Running the review on a shared link (rather than emailed files) tends to compress the cycle because feedback is specific and anchored, not open-ended.

drafty

How to get feedback on a web design

Quick answer

To get feedback on a web design, share something the client can open and react to directly — a Figma prototype, a live staging link, or a review link where they can pin comments on the exact element. The method that works best is the one that requires the least from the client: no account, no extension, just a URL they can tap on their phone and leave a note on the specific part they mean.

Step 1

Share a Figma prototype (fastest for design-stage work)

In Figma, click Share → Copy prototype link and paste it into an email or message. Anyone with the link can open it in a browser and leave comments — they do need a free Figma account to comment, which is worth flagging to the client first. One common mistake: sharing the design file URL instead of the prototype link, which shows the editor rather than the finished layout and tends to distract clients with layer names and components they don't understand. Use Present mode (the play icon) and share that URL.

Step 2

Send the staging URL and ask for specific reactions

If the site is already built on a staging server, send the URL with a short brief: which pages to look at and which questions you want answered. Open-ended prompts get vague replies; specific ones get useful answers. For example: "Does the pricing section feel clear?" or "What would you expect to happen when you tap the main button?" Screenshot annotations — the classic approach — work in a pinch, but they multiply fast: by the third round you are decoding red circles drawn on a compressed JPEG, trying to map them back to the original layout. Structured prompts cut that cycle in half.

Step 3

Export a static image and mark it up together on a call

Export the design as a PNG or PDF and annotate it in a screen-share call using your tool of choice — Preview on Mac (Shift ⌘ A for the markup toolbar), or Figma's own pen tool on a shared file. The advantage of doing this live is you can probe vague feedback in real time: when a client says "it feels heavy", you can ask exactly which section they mean and draw the boundary together. The limitation: the annotations live in the call recording or a one-off file that quickly falls out of sync with revisions. You need a source-of-truth for the feedback, not just the call notes.

Step 4

Share a review link so they comment on the exact spot

The cleanest workflow for client sign-off is a URL that opens the design — mockup, screenshot, or live site — and lets the client click any element and leave a note pinned right there. No account, no extension. Tools in this category (Markup.io, BugHerd, Drafty) all work this way: you paste the URL or upload the file, share the review link, and every comment lands anchored to the element the client meant. The feedback is in one place, not split across an iMessage thread, a follow-up email, and a Zoom recording. Markup.io removed their free plan in 2025, so check current pricing; BugHerd is more geared toward dev/QA than design sign-off; Drafty lets anyone comment as a guest on any artifact type.

The faster way

If the client needs to comment on a live web design — not just a static export — drop the URL into Drafty. It creates a review link your client opens in any browser, taps the exact element they mean, and pins a note right there. No account, no extension, works on their phone. You see the feedback anchored to the spot, reply in the thread, and share a revised version on the same link. The scattered-email-and-screenshot cycle ends at step one.

Open a live demo

Questions

How do I share a web design with a client for feedback?: The simplest approach: share a link they can open without installing anything. That means a Figma prototype link (requires a free Figma login to comment), a staging URL with a specific set of questions, or a review link from a tool like Drafty where they pin comments without signing up. The key is matching the format to the client — non-technical clients fare much better with a plain URL than with a Figma file share.
Do clients need an account to leave feedback on a design?: Not always. Figma requires a free account to comment. Most dedicated review tools — including Drafty — let clients comment as guests on a public link, with no signup. That removes the single biggest reason clients default back to emailing vague notes.
What is the best way to get feedback on a web design before launch?: Before launch, sharing the staging site as a review link (rather than a screenshot) gives clients the most realistic experience and the most specific reactions. It also catches viewport and mobile issues that a static screenshot misses. Ask three or four specific questions alongside the link rather than an open "let me know what you think" prompt, which tends to produce vague replies.
How do I stop design feedback from being scattered across email and messages?: Share one link and direct all feedback there. When the design lives at a single URL and reviewers can comment on the page itself, there is no reason to take a screenshot and describe it in iMessage. If you are still getting feedback over email, it usually means the review tool has friction — the client needs an account, or the interface feels unfamiliar. Removing that friction (a one-click guest comment on a public link) is the most reliable fix.
Can I get feedback on a live website, not just a design file?: Yes. Tools like Drafty and Ruttl let you paste a live URL and generate a review board where visitors comment on the exact element. This works on the real rendered site — not a screenshot or export — so the client sees the actual fonts, spacing, and responsiveness.
How many review rounds should I budget for a web design project?: Two structured rounds is the standard. The first covers overall direction and layout; the second covers copy, color, and detail. Unstructured rounds — where the scope of feedback is undefined — tend to run to four or five. Running the review on a shared link (rather than emailed files) tends to compress the cycle because feedback is specific and anchored, not open-ended.

Keep exploring

Review a website Website feedback tool Annotate a PDF BugHerd alternative

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