How do I get feedback on a Figma mockup from a client without an account?

Figma requires a free account login to leave comments, even on a view-only link — this is a persistent friction point for non-designer clients on one-off projects. The workaround is to export the frame as a PNG or PDF and mark it up yourself before sharing, or use a separate review tool (Markup.io, Drafty) that supports guest commenting on an uploaded design without any account.

What is the best way to get client feedback on a design mockup?

A shared review link where the client clicks the exact element they mean and pins a note is the method that produces the most specific, actionable feedback — because it removes the step where they have to describe a position in words. For complex projects, combine it with a 30-minute screen share early in the review phase; async comments come in more focused after the client has seen the full design once.

How do I get useful feedback on a mockup instead of vague comments?

Attach specific questions to each section of the mockup before you share it. "Does the pricing section make the difference between plans clear?" produces a more useful answer than "let me know your thoughts." Clients default to vague praise when they don't know what you're asking them to evaluate. Visual annotation — where they click the spot instead of describing it — also narrows the scope automatically.

How do I collect mockup feedback from multiple stakeholders without it turning into chaos?

Send everyone the same link rather than separate email threads. A single shared artifact means all comments land in one place, visible to every reviewer — no reconciling four different annotated PDFs or chasing reply-all email chains. If stakeholders need to leave separate feedback before influencing each other, you can share the link sequentially rather than all at once.

Can I get feedback on a mockup that's not in Figma?

Yes. Any PNG, JPEG, or PDF export works with most review tools. If the mockup was built in Sketch, Framer, v0, or even a scanned whiteboard sketch, export it as a PNG and share it through a link-based review tool — the review experience is the same regardless of what created the file.

How do I track which mockup feedback has been addressed?

Resolve comments as you ship each fix rather than keeping a separate spreadsheet. Most link-based review tools (including Drafty and Markup.io) support marking comments as resolved while keeping the thread visible in a closed state — so you and the client both have a clear record of what changed between rounds. This beats re-annotating a new file export for each revision.

drafty

How to get feedback on a mockup

Quick answer

To get client feedback on a mockup, share it in a format they can actually react to — not an email that forces them to describe a spot by its rough position on the screen. A Figma view link with comments, an exported PDF, a 30-minute screen share, or a shared review link they click to pin notes directly on the design all work. The method that produces the most useful feedback is whichever removes the translation layer between what they see and what they're trying to say.

Step 1

Share a Figma view link with comments enabled

In Figma, click Share → set permission to 'Can view' → copy the link. Recipients can open it in any browser without a paid account. To leave a comment, they click the speech bubble icon in the toolbar — but Figma requires a free account login to submit comments. This is still the right call when your client is already a Figma user or when they need to inspect spacing, toggle between component states, or compare frames side by side. It's less ideal for a one-off client who has never opened Figma: the account step creates real drop-off, and first-time commenters often miss how to pin a note to a specific element. Walk them through it in a quick Loom or on a call the first time.

Step 2

Export as PNG or PDF and send for markup

Export the frame from Figma (⌘ Shift E → PNG at 2x, or File → Save As → PDF) and email it. Your client opens it in Preview on Mac or Edge on Windows and marks it up with the built-in annotation tools. For a PDF, Acrobat's Comment panel lets them pin sticky notes anywhere. This works for clients who will never open a web tool — but every round of revisions means re-exporting, re-sending, and reconciling markup across different versions of the same file. By round three, you're comparing annotated PDFs with different names and no clear sequence. Keep a dated version number in the filename (logo-v3-2026-06-20.pdf) so the history stays legible. This method falls apart on teams with multiple stakeholders — one person's annotations live in their copy, invisible to everyone else.

Step 3

Walk through it on a screen share

A 30-minute call where you share your screen and click through the mockup section by section is often faster than two weeks of async email. The discipline that makes it useful: don't explain what you were trying to achieve before your client reacts. Let them form a first impression, then ask "what's happening on this screen from your perspective?" before you frame it. Use Zoom, Google Meet, or Around — record it with the host's built-in recorder or Descript for a transcript you can turn into action items after. Keep a running doc open alongside the call and paste comments in real time with the section they apply to. Send the doc back within an hour while the conversation is still fresh. Screen shares produce the densest feedback per minute of any method, but the notes don't persist unless you capture them yourself.

Step 4

Share a review link they annotate without signing up

Drop the exported design into a shared review tool, generate a link, and send it. Your client opens it in any browser — on their phone or desktop — clicks the exact button, heading, or image they mean, and types a note pinned right to that spot. No Figma account, no PDF reader, no downloaded file. The specific feedback this produces is genuinely different from what email generates: "the CTA in the hero feels too small" pinned to the actual button beats "the button near the top" written in a message. Tools that support no-account guest commenting include Markup.io, Drafty, and Ruttl. The honest tradeoff: they're seeing a flat or embedded view of the design, not the live Figma file, so this doesn't replace a Figma link when clients need to inspect layer-level details. For sign-off and revision rounds, it's the lowest-friction option.

The faster way

If your client keeps leaving feedback that says "the bit on the left" — drop your exported design into Drafty and send the link instead. They click the exact element on the mockup and leave a note pinned right there, no account required. Every comment is threaded and anchored to the spot; you resolve each one when the revision ships. Works on PNG exports, Figma embeds, and PDF uploads, on desktop or phone.

Open a live demo

Questions

How do I get feedback on a Figma mockup from a client without an account?: Figma requires a free account login to leave comments, even on a view-only link — this is a persistent friction point for non-designer clients on one-off projects. The workaround is to export the frame as a PNG or PDF and mark it up yourself before sharing, or use a separate review tool (Markup.io, Drafty) that supports guest commenting on an uploaded design without any account.
What is the best way to get client feedback on a design mockup?: A shared review link where the client clicks the exact element they mean and pins a note is the method that produces the most specific, actionable feedback — because it removes the step where they have to describe a position in words. For complex projects, combine it with a 30-minute screen share early in the review phase; async comments come in more focused after the client has seen the full design once.
How do I get useful feedback on a mockup instead of vague comments?: Attach specific questions to each section of the mockup before you share it. "Does the pricing section make the difference between plans clear?" produces a more useful answer than "let me know your thoughts." Clients default to vague praise when they don't know what you're asking them to evaluate. Visual annotation — where they click the spot instead of describing it — also narrows the scope automatically.
How do I collect mockup feedback from multiple stakeholders without it turning into chaos?: Send everyone the same link rather than separate email threads. A single shared artifact means all comments land in one place, visible to every reviewer — no reconciling four different annotated PDFs or chasing reply-all email chains. If stakeholders need to leave separate feedback before influencing each other, you can share the link sequentially rather than all at once.
Can I get feedback on a mockup that's not in Figma?: Yes. Any PNG, JPEG, or PDF export works with most review tools. If the mockup was built in Sketch, Framer, v0, or even a scanned whiteboard sketch, export it as a PNG and share it through a link-based review tool — the review experience is the same regardless of what created the file.
How do I track which mockup feedback has been addressed?: Resolve comments as you ship each fix rather than keeping a separate spreadsheet. Most link-based review tools (including Drafty and Markup.io) support marking comments as resolved while keeping the thread visible in a closed state — so you and the client both have a clear record of what changed between rounds. This beats re-annotating a new file export for each revision.

Keep exploring

How to annotate a mockup How to get feedback on a website Design feedback tool Feedback on Figma designs

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