How do I share a Figma prototype for client feedback without them needing a Figma account?

Set the share link to 'Anyone with the link can view' in Figma's presentation mode — clients can click through the prototype in any browser without an account. They can't leave comments on Figma without a free account, though. For no-account written feedback, export the key frames as PNGs and share them through a review tool like Drafty or Markup.io, where clients pin notes as a guest.

What kind of feedback should I ask for on a prototype?

Ask about the task, not the aesthetics. 'Can you find the pricing page from this screen?' is more useful than 'what do you think?' For visual review rounds, specific questions per frame — 'does the empty state make it obvious what to do next?' — produce more actionable notes than open-ended prompts. Colour and typography feedback is usually better deferred until the interaction is approved.

How do I get client feedback on a prototype without a live meeting?

Three async methods work: share the Figma prototype link with a short Loom walkthrough attached so they understand the intended flow before clicking; export frames as PNGs and share a review link where they annotate inline; or record yourself clicking through the prototype with narration and ask them to timestamp their comments in a reply. Of these, the annotated review link produces the most specific, location-anchored feedback without a call.

How do I collect prototype feedback from multiple stakeholders without missing anything?

Send everyone the same link rather than separate emails. A single shared artifact means all comments land in one thread, visible to everyone — no reconciling three annotated screenshots or chasing a reply-all chain where one stakeholder replied only to you. If they need to review independently before influencing each other, share the link sequentially rather than in a group.

How do I know when to do a usability session versus async review?

Usability sessions are worth it when you're testing whether people can complete a flow at all — navigation, checkout, onboarding — and when their hesitation is as informative as their words. Async review links are better for visual and copy sign-off once the flow is approved, or when stakeholders are in different time zones. Most projects benefit from one early usability session and then async review links for subsequent revision rounds.

My client keeps giving vague feedback on the prototype. What helps?

Two things: specific questions attached to specific frames ('does this screen make the next step obvious?'), and a format where they click the spot instead of describing it. Vague feedback ('it feels a bit off') usually means the client is reacting to a general impression but can't locate it in words — a visual annotation tool forces them to point first, which narrows what they're talking about before they type.

drafty

How to get feedback on a prototype

Quick answer

To get client feedback on a prototype, share it in a way that lets clients react to the right thing — the interaction, the flow, or the visual — not just the idea of it. A Figma share link lets them click through the prototype live. A recorded walkthrough removes the "I couldn't figure out how to navigate it" problem. A short usability call produces the densest notes. And a shared review link lets them pin written comments to the exact frame or element without a Figma account. The method that produces the most actionable feedback is usually the one with the least friction for your specific client.

Step 1

Share a Figma prototype link they can click through

In Figma, open your prototype flow and click Present (the play button, top-right). From presentation mode, click Share prototype and set access to 'Anyone with the link can view.' The recipient clicks through the prototype in their browser — transitions, overlays, hover states — without downloading anything or touching the design file. The catch: leaving a comment on a Figma prototype still requires a free Figma account. Clients who don't have one face a signup wall before they can type a note, and new-to-Figma users rarely know where the comment tool lives inside the presentation view. Walk them through it on a short call the first time, or use a Loom to show them. This method is best when the client is already a Figma user, when you need them to test a specific flow by clicking through it, or when the interaction fidelity itself is what you want them to react to — not just a static frame.

Step 2

Export key frames and ask for notes on them

If the prototype is for visual and layout sign-off rather than interaction testing, export the frames you need feedback on as PNGs (Figma: ⌘ Shift E → select frames → Export) and share them directly. Your client opens them in Photos, Preview, or a browser and tells you what they think. This sidesteps the 'I got confused clicking around' problem that high-fidelity prototypes create when clients explore in an unintended direction — you control exactly what they see. The tradeoff is that static exports can't demonstrate flows, animations, or responsive behaviour, and feedback comes back as email prose rather than anchored annotations. Clients will write 'the second screen' when they mean the modal that appears when you tap the cart icon. You end up translating their words back to coordinates. For screens where the interaction is the point — a swipe gesture, a transition, a state change — export a short screen recording instead of a still.

Step 3

Run a short usability session over a call

A 30-minute call where your client clicks through the prototype while you watch produces the most honest feedback of any method — you see where they hesitate, where they click the wrong thing, and what they say out loud before they self-edit. The discipline that makes it useful: don't explain the flow first. Say 'you're a new customer who just landed on the checkout page — show me what you'd do.' Let them try to complete a realistic task. Only explain after they've formed a first impression. Tools: share your Figma prototype in presentation mode and let them control their own mouse (Zoom remote control, Google Meet screen share with handoff, or just ask them to open the link themselves). Record with Zoom's built-in recorder or Loom. Use Descript after to get a transcript and clip the moments where they said 'wait, I'd expect this to...' — those moments are the design brief for your next revision. Usability sessions require scheduling, so they don't scale to five stakeholders reviewing async, but for a critical flow like a payment step or an onboarding sequence they're worth the calendar time.

Step 4

Share a review link they annotate without signing up

Export the key prototype frames as PNGs and drop them into a link-based review tool. Your client opens the link on any device — their phone, work laptop, an iPad — clicks the exact button, heading, or section they mean, and leaves a note pinned right to it. No Figma account, no downloaded file. The feedback you get back is different in kind from email: 'the CTA in the checkout frame feels too small' pinned to the actual button beats 'the button near the bottom of screen 3' in a reply-all thread. This method works well for visual review of individual frames, layout and copy sign-off, and collecting notes from multiple stakeholders in one place — they all see each other's comments, which cuts the 'one person flagged this already' duplication. It doesn't replace a live click-through for testing interactions, but it's the right format for the revision rounds after the flow has been approved. Tools that support guest commenting without a required account: Markup.io, Drafty, Ruttl. Honest tradeoff: you're sharing flat exports, not a live interactive flow, so this works for visual and copy feedback, not for interaction testing.

The faster way

If your client keeps saying 'the thing on the right side of that screen' — drop your exported prototype frames into Drafty and send the link. They click the exact element on the frame and leave a note pinned right there, no Figma account, no signup. Comments are threaded and anchored to the spot; resolve each one when the revision ships. Works on PNG exports from Figma, Sketch, or Framer, on desktop or phone.

Open a live demo

Questions

How do I share a Figma prototype for client feedback without them needing a Figma account?: Set the share link to 'Anyone with the link can view' in Figma's presentation mode — clients can click through the prototype in any browser without an account. They can't leave comments on Figma without a free account, though. For no-account written feedback, export the key frames as PNGs and share them through a review tool like Drafty or Markup.io, where clients pin notes as a guest.
What kind of feedback should I ask for on a prototype?: Ask about the task, not the aesthetics. 'Can you find the pricing page from this screen?' is more useful than 'what do you think?' For visual review rounds, specific questions per frame — 'does the empty state make it obvious what to do next?' — produce more actionable notes than open-ended prompts. Colour and typography feedback is usually better deferred until the interaction is approved.
How do I get client feedback on a prototype without a live meeting?: Three async methods work: share the Figma prototype link with a short Loom walkthrough attached so they understand the intended flow before clicking; export frames as PNGs and share a review link where they annotate inline; or record yourself clicking through the prototype with narration and ask them to timestamp their comments in a reply. Of these, the annotated review link produces the most specific, location-anchored feedback without a call.
How do I collect prototype feedback from multiple stakeholders without missing anything?: Send everyone the same link rather than separate emails. A single shared artifact means all comments land in one thread, visible to everyone — no reconciling three annotated screenshots or chasing a reply-all chain where one stakeholder replied only to you. If they need to review independently before influencing each other, share the link sequentially rather than in a group.
How do I know when to do a usability session versus async review?: Usability sessions are worth it when you're testing whether people can complete a flow at all — navigation, checkout, onboarding — and when their hesitation is as informative as their words. Async review links are better for visual and copy sign-off once the flow is approved, or when stakeholders are in different time zones. Most projects benefit from one early usability session and then async review links for subsequent revision rounds.
My client keeps giving vague feedback on the prototype. What helps?: Two things: specific questions attached to specific frames ('does this screen make the next step obvious?'), and a format where they click the spot instead of describing it. Vague feedback ('it feels a bit off') usually means the client is reacting to a general impression but can't locate it in words — a visual annotation tool forces them to point first, which narrows what they're talking about before they type.

Keep exploring

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