How do I stop clients from giving visual feedback on a wireframe?

Frame it in writing before they look. A single line — 'the grey boxes and placeholder text are intentional; what I need you to evaluate is the order of steps and whether anything's missing, not the colour or font' — cuts visual feedback in half. Asking specific structural questions per section ('does this checkout flow match how you'd expect to proceed?') gives clients something concrete to react to instead of reaching for aesthetic impressions.

Does my client need a Figma account to leave comments on a wireframe?

Yes — Figma requires a free login to submit comments, even on a view-only link. If your client is unlikely to create an account for a one-off review, export the frames as PNGs and use a link-based review tool (Markup.io, Drafty, Ruttl) that accepts guest comments without signup. They get the same pinned-to-the-spot experience without the account wall.

What's the right level of detail to ask for feedback on at the wireframe stage?

Structure, sequence, and completeness — not visual design. Does the page hierarchy make sense? Is anything missing? Does the flow of steps match how the user would actually think? Leave colour, typography, and imagery out of scope explicitly. If you don't say so upfront, clients will give you design feedback, because that's what a 'review' means to most people who aren't designers.

How do I get wireframe feedback from multiple stakeholders without losing track of it?

Send everyone the same link, not separate files. A shared review link means every comment lands in one place visible to all reviewers — no reconciling three annotated PDFs or chasing a reply-all thread. If stakeholders need to form independent opinions before influencing each other, send the link sequentially rather than in a group message.

How do I share a low-fidelity wireframe with a client who doesn't understand what they're looking at?

Include a short walk-through. A 90-second Loom recording where you click through the wireframe and narrate — 'this box will be a photo of the product, this section is the pricing table' — sets expectations before they form the wrong ones. Without it, clients often read placeholder Latin text literally or assume the grey boxes mean the design is unfinished in a bad way.

Can I collect wireframe feedback without scheduling a meeting?

Yes. Export frames as PNGs, attach specific questions to each one, and share a review link where clients annotate inline at their own pace. Async review works particularly well for visual sign-off rounds once the structure has been discussed. Where async breaks down: when the client is new to reviewing wireframes and needs orienting, or when the feedback you need is about a multi-step flow that's hard to convey in static frames. In those cases, a single short call first pays for itself in the quality of the async feedback that follows.

drafty

How to get feedback on a wireframe

Quick answer

To get useful feedback on a wireframe, share it in a way that focuses your client on structure and flow — not colour, font choice, or visual polish those boxes don't represent yet. A Figma view link, an exported PDF with your questions annotated in, a 30-minute walkthrough call, or a shared review link they click to pin notes to the exact spot all work. The method that generates the most useful feedback is whichever stops them from saying 'can you make it more modern' when you haven't shown them a colour yet.

Step 1

Share a Figma view link with specific questions attached

In Figma, click Share → set to 'Anyone with the link can view' → copy. Recipients open it in any browser without a paid account. To leave a comment, they'll need a free Figma login — that's a known friction point for clients who've never opened Figma before. What makes this method work despite that: attach specific questions per frame in your comments before you share. 'Does the order of these three steps match how you'd actually think about it?' is a real question anchored to a real frame; 'let me know your thoughts' produces vague praise or premature visual critique. Include a short Loom or a one-paragraph message explaining that the grey boxes and placeholder text are intentional — wireframes represent layout and structure, not the final look. Without that framing, half of all wireframe reviews turn into a conversation about font choices and colour that can't be decided yet. This method is best when the client is already a Figma user or when you need them to navigate between frames to understand a multi-screen flow.

Step 2

Export as PDF and annotate your own questions before sending

Export the wireframe as a PDF (in Figma: File → Export frames as PDF, or use a plugin like PDF Export). Before you send it, open it in Preview on Mac or Acrobat and add sticky-note comments next to each section with the specific question you want answered. 'Is this the right order for these steps?' beats a blank frame that invites 'it looks a bit plain.' Your client marks up the PDF in Preview, Edge, or Acrobat — built-in tools, no extra software. The problem with PDF rounds: every revision means re-exporting, re-annotating with questions, and re-sending. By revision three you're reconciling three PDFs with different names, each with some comments in the file and some in the email thread. Keep a strict version number in the filename (checkout-flow-v2-2026-06-20.pdf) and send a summary email listing exactly what changed between versions — otherwise clients respond to an old version, which is a reliable source of confusion on every long project.

Step 3

Walk through it on a call with a concrete task script

A 30-minute call where you share your screen and walk through the wireframe section by section is often faster than two weeks of async back-and-forth. The technique that makes it produce useful feedback rather than polite reactions: open with a task, not an explanation. 'You're a first-time customer who just clicked our ad — what do you expect to happen on this screen?' is more productive than 'so what we've designed here is...' because it gives the client a concrete frame for their reaction before you've filled in the answer for them. Don't explain what each section is trying to achieve until after they've reacted. Record the call in Zoom or Google Meet and use Descript to pull a transcript. Paste timestamped notes into a running doc during the call and send it back within an hour. The limitation: you're capturing notes yourself; if you miss something the client said, it's gone unless you scrub back through the video. And you need to schedule it, so it doesn't scale to five stakeholders reviewing independently.

Step 4

Share a review link they pin notes on without signing up

Export the wireframe frames as PNGs (Figma: ⌘ Shift E → PNG at 1x or 2x) and drop them into a link-based review tool. Send your client the link. They open it in any browser — on their phone or laptop — click the exact box, label, or section they're commenting on, and leave a note pinned right to that spot. No Figma account. No PDF reader. No downloaded file. The feedback is structurally different from what email produces: 'this step label is confusing' pinned to the actual label beats 'some of the text in the middle section feels unclear' in a reply thread. The honest limitation of this method: your client is seeing flat PNG frames, not a clickable flow. For a multi-screen flow where the sequence is what you want them to evaluate, either walk them through the sequence in your message or export frames in order and number them. Tools that support guest commenting without an account: Markup.io, Drafty, Ruttl. Worth knowing: even clients who usually respond with three-word emails tend to give more specific feedback when they're clicking the exact thing they mean instead of describing it in words.

The faster way

If your client keeps giving you 'it feels a bit plain' feedback on a wireframe — drop your PNG exports into Drafty and share the link. They click the exact label, box, or section they mean and leave a note pinned right there, no account required. You can add guiding questions as your own comments before you share the link, so they arrive knowing what to focus on. Every comment is threaded and anchored; resolve each one when the revision ships.

Open a live demo

Questions

How do I stop clients from giving visual feedback on a wireframe?: Frame it in writing before they look. A single line — 'the grey boxes and placeholder text are intentional; what I need you to evaluate is the order of steps and whether anything's missing, not the colour or font' — cuts visual feedback in half. Asking specific structural questions per section ('does this checkout flow match how you'd expect to proceed?') gives clients something concrete to react to instead of reaching for aesthetic impressions.
Does my client need a Figma account to leave comments on a wireframe?: Yes — Figma requires a free login to submit comments, even on a view-only link. If your client is unlikely to create an account for a one-off review, export the frames as PNGs and use a link-based review tool (Markup.io, Drafty, Ruttl) that accepts guest comments without signup. They get the same pinned-to-the-spot experience without the account wall.
What's the right level of detail to ask for feedback on at the wireframe stage?: Structure, sequence, and completeness — not visual design. Does the page hierarchy make sense? Is anything missing? Does the flow of steps match how the user would actually think? Leave colour, typography, and imagery out of scope explicitly. If you don't say so upfront, clients will give you design feedback, because that's what a 'review' means to most people who aren't designers.
How do I get wireframe feedback from multiple stakeholders without losing track of it?: Send everyone the same link, not separate files. A shared review link means every comment lands in one place visible to all reviewers — no reconciling three annotated PDFs or chasing a reply-all thread. If stakeholders need to form independent opinions before influencing each other, send the link sequentially rather than in a group message.
How do I share a low-fidelity wireframe with a client who doesn't understand what they're looking at?: Include a short walk-through. A 90-second Loom recording where you click through the wireframe and narrate — 'this box will be a photo of the product, this section is the pricing table' — sets expectations before they form the wrong ones. Without it, clients often read placeholder Latin text literally or assume the grey boxes mean the design is unfinished in a bad way.
Can I collect wireframe feedback without scheduling a meeting?: Yes. Export frames as PNGs, attach specific questions to each one, and share a review link where clients annotate inline at their own pace. Async review works particularly well for visual sign-off rounds once the structure has been discussed. Where async breaks down: when the client is new to reviewing wireframes and needs orienting, or when the feedback you need is about a multi-step flow that's hard to convey in static frames. In those cases, a single short call first pays for itself in the quality of the async feedback that follows.

Keep exploring

How to get feedback on a mockup How to get feedback on a prototype How to get feedback on a Figma 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