How to share a prototype for feedback
To share a prototype for feedback: send a presentation-mode link for interaction review, or flat PNG exports for visual sign-off. Set 'anyone with the link can view,' add one specific question per screen, and name the deadline. Vague feedback almost always means the client was asked to react to everything at once.
Send the right link for what you need reviewed
There are two kinds of prototype links and they produce different feedback. A live prototype link (Figma's 'Share prototype' in presentation mode, set to 'Anyone with the link can view') lets your client click through flows, transitions, and overlays — use this when the interaction itself is what's being reviewed. A flat export link (PNGs or a PDF dropped into a review tool) works better for layout, copy, and visual sign-off on individual frames, because the client can't wander into an unfinished screen or get stuck navigating. Mixing them up is the main reason prototype reviews go sideways: sending an interactive prototype when you only want a colour opinion means the client spends the session getting lost in the navigation, not looking at the button you asked about.
Write two lines of context before you send
The feedback quality you get back is almost entirely determined by what you write in the message alongside the link. Two things to include: what stage the design is at ('this is the first-pass layout, we haven't touched copy yet') and one specific question per screen you want them to look at ('on the checkout step — does the order summary make sense before you hit pay?'). Without this, clients review everything at the same time and give general impressions rather than located reactions. A good rule: if your client could paste their notes back and you'd still need to ask 'which screen?' — you didn't frame the ask tightly enough. For multiple screens, a numbered list works. One question per frame, not 'let me know your thoughts.'
Set a permissions level that matches the client relationship
In Figma, 'Anyone with the link' in presentation mode gives view-only access to the prototype — they see the flow, not the layers. For clients who aren't in Figma, this is cleaner than giving edit access to the file. One edge case most designers hit on the first round: Figma's free plan shares the prototype AND the file. On a paid plan you can share a prototype-only link (presentation mode, no access to the editor). If you're on the free plan and don't want the client in your layers, export the key frames as PNGs and share those via a link-based review tool instead — guests can annotate without touching your Figma file at all. For clients on a tight deadline, frame permissions as a feature: 'you don't need to make an account, just open the link.'
Collect notes in one place, not a reply-all chain
If you send the prototype link by email and ask for notes, feedback will come back as bullet points in a reply, a Word doc attachment, and a separate iMessage with the real opinion. One tool makes this considerably less painful: a review link where clients pin a comment to the exact frame and element they mean, visible to everyone in the thread. They click the spot, type the note, and you see it anchored to the pixel — no more 'the thing on the right-hand side of the second screen.' This matters more with multiple stakeholders: shared comments mean they see each other's notes, which cuts the duplicate feedback round and reveals disagreements early. Whatever tool you use — a Figma comment thread on an export, Markup.io, Ruttl, or Drafty — the principle is the same: one link, one place, comments on the artifact rather than next to it.
Confirm your client can actually open it before the review
Send a quick 'can you open this?' test link a day before the deadline, especially with new clients. Prototype links break in two common ways: the Figma file was moved or the sharing permissions got reset when you published a new version, and the previous link now redirects to a login screen. A version update in Figma replaces the content at the same URL, which is usually fine, but if you deleted the presentation and re-added it the URL changes — the link you sent last week now 404s. The fix is to version before sharing: in Figma, save a named version before you send the link so you have something stable to point clients at. A one-line test message saves a half-hour of 'I'm getting an error' on review day.
If your client keeps annotating the wrong screen or their feedback arrives as a vague voice note — export your key frames from Figma and drop them into Drafty. Send the link; they click the exact button or section and leave a note pinned right to it, no account. Every comment is threaded and anchored to the spot. Resolve each one when you've shipped the revision. Works on PNGs from Figma, Sketch, or Framer.
Open a live demoQuestions
- How do I share a Figma prototype without the client needing a Figma account?
- In presentation mode, set the link to 'Anyone with the link can view' — your client opens it in any browser without signing up. They can't leave comments in Figma without an account, though. For no-account written feedback on the frames, export the screens as PNGs and share via a review tool (Markup.io, Drafty, Ruttl) where guests annotate as a visitor.
- How do I get specific feedback on a prototype instead of vague replies?
- Ask one specific question per screen in the message you send alongside the link. 'Does the checkout summary give you enough information before you hit pay?' produces more useful notes than 'what do you think?' The other thing that helps: a format where they click the exact spot before they type — visual annotations force the client to locate their reaction before they put it into words, which catches 90% of the 'it feels off' responses.
- My prototype link keeps breaking when I update the design. What should I do?
- In Figma, save a named version before you share the link (File → Save to version history). That freezes the content at the URL you sent. If you need to share updated work, send a new link for the new version rather than replacing the old one — your client's notes live on the original URL and shouldn't mix with revision round 2.
- What's the best way to share a prototype for feedback from multiple stakeholders?
- Send everyone the same link rather than separate copies. A single artifact means all comments land in one thread where stakeholders can see each other's notes — this cuts duplicate feedback and surfaces disagreements before they become a revision round. If they need to review independently first, share the link sequentially and ask each person to leave their notes before reading the others.
- Should I share an interactive prototype or flat images for feedback?
- Interactive prototype for flow and navigation feedback — when you want to know if people can find what they're looking for or complete a sequence of steps. Flat images (PNG exports) for visual, layout, and copy feedback — when the question is about what something looks like, not how it behaves. The most common mistake is sending an interactive prototype for a colour or copy opinion: the client explores instead of reviewing, and you get 'I got a bit lost' rather than notes on what you asked.
- How do I share a prototype for feedback on mobile?
- Figma's presentation mode is mobile-responsive and works in a phone browser — set the link to 'Anyone with the link,' send it, and the client can click through the prototype on their phone. For a mobile design specifically, this is worth testing yourself first: on a phone, the comment toolbar in Figma can be awkward to trigger. If you need clean mobile feedback with no interface in the way, export the frames and share via a review tool that works on phone — clients annotate by tapping the element, not hunting for a comment icon.
Keep exploring
Stop emailing files back and forth.
Share one link. They comment on the exact spot — no account, always the current version.