How do I get clients to comment on a mockup instead of emailing?

Send the link with a one-sentence instruction: 'Click any spot to pin a note directly on the design — easier than describing it in an email.' Most clients default to email because it's familiar, not because they prefer it. Give them one explicit alternative and they'll usually use it. If they still email feedback, reply with the link and ask them to pin the notes there — 'so I can see exactly which element you mean' is the framing that works.

Can a client comment on a mockup without a Figma account?

No. Figma requires a signed-in account to leave a comment, even on a view-only shared link. This has been a persistent complaint since at least 2021. The standard workaround: export the mockup as a PNG and share it via a tool that supports guest commenting — the client opens the link in a browser, no account, and clicks the spot they mean.

How do I get more useful feedback on a mockup?

Ask a specific question, not an open one. 'Does the pricing table make the difference between plans clear?' gets a yes or no and a note on the table. 'Let me know your thoughts' gets a general reaction that isn't actionable. Pin your question as a comment on the section you want evaluated — clients who open the link and see a specific question already know where to start.

What is the best format to share a mockup for client feedback?

A browser-openable link beats an email attachment in almost every scenario. An attachment forces the client into whatever software opens PNG or PDF files on their machine, they mark it up there, and you receive an annotated copy you have to interpret. A review link means both of you are looking at the same artifact in the same thread, and the client's notes are pinned to the exact element — not described in text.

How do I handle conflicting feedback from multiple stakeholders on a mockup?

Share one link with all stakeholders, not individual copies. When every reviewer comments on the same artifact, they can see each other's notes — which surfaces conflicts before they reach you. If two stakeholders disagree on the header treatment, that's a conversation they have in the thread rather than two contradictory instructions you receive separately. For final approval, still identify one decision-maker whose call resolves conflicts.

How many rounds of mockup feedback is normal?

Two focused rounds is the professional standard for most freelance projects. Round one covers major direction — layout, hierarchy, content gaps. Round two catches details after those are resolved. If you're consistently hitting four or five rounds, the cause is usually one of three things: feedback is arriving on the wrong version, the review ask was too open-ended, or the right decision-maker isn't reviewing until late. Fixing the feedback format (a review link with a specific question) usually cuts rounds without requiring a difficult conversation about scope.

drafty

How to get client comments on a mockup

Quick answer

To get client comments on a mockup, share a browser-openable link — not a file attachment — and ask one specific question alongside it. Attachments produce vague email replies ('the thing on the left'); a link where clients click the exact element and pin a note produces comments tied to a specific spot. Most designers who find client feedback hard to work with are sending the wrong format, not dealing with a difficult client.

Step 1

Export a flat image — don't send the Figma link

The instinct is to share the Figma view-only URL. The problem: Figma requires a free account before a client can leave a single comment, even on a view-only link. On the Figma forum, one thread titled 'Guest comments for clients without an account' has run to 97+ replies since 2021 with no resolution. Clients who hit the login wall don't push through — they email you a description of what they meant instead. Export the mockup as a PNG at 2x (Figma: ⌘Shift E → PNG → Export) and share it in a tool that accepts guest comments with no account. Clients open the URL in any browser — on their phone, on a work laptop they can't install software on — and click directly on what they mean. You get a pinned note on the exact element, not a paragraph describing its approximate location.

Step 2

Frame the ask — one specific question, not 'any thoughts?'

The most common reason client comments are vague is the ask was vague. 'Let me know what you think' returns 'Looks great!' or 'Can you make it pop?' — neither is actionable. Before sending the link, identify the one thing you actually want a decision on. Send the link with a one-liner: 'The main thing I'd like your eyes on is the header hierarchy — does the primary action stand out clearly, or does it compete with the navigation?' Clients who receive a specific question answer the specific question. Pin that question as a comment on the relevant section so it's visible when they open the link — the context makes it obvious where to start. This also cuts the rounds of revision: a pointed round one gives you usable direction; an open-ended round one gives you a second round of clarification.

Step 3

Share one link for the whole review — not a file per round

When a client emails 'a few more tweaks' on round three and you can't find which version they're referring to, the problem started at round one. Email attachments — even well-named ones — scatter across inboxes, local Downloads folders, and Slack DMs. By round three, someone is commenting on v2 thinking it's v3. A single review link fixes this: every round of feedback lives on the same URL. When you revise the mockup, you replace the file on the same link; the client opens the same URL they bookmarked, sees the updated version, and their previous notes are still in the thread — resolved ones marked closed, open ones still visible. Send the revision as a reply to the original email thread: 'Updated — same link, all your round-1 notes are addressed in the thread.' The client has one place for the whole conversation, not a folder of versioned PNG files.

Step 4

Set a deadline and tell them exactly how to comment

Two things kill a feedback round: no deadline ('whenever you get a chance') and no instruction ('let me know if you have questions'). Clients treat open-ended review requests as non-urgent. A short sentence covers both: 'Click any spot on the mockup to pin a note — no account needed. I need your feedback by Thursday so I can incorporate it before our Friday build hand-off.' Most people who have never used a visual review tool will instinctively open the link, scroll around, and then email you a separate message. That one instruction sentence — 'click any spot to pin a note' — cuts a full round of back-and-forth in half. If you get an email anyway, reply with the link and a single ask: 'Can you pin those notes directly on the mockup? It helps me find exactly which element you mean.'

The faster way

The part of this workflow that takes longest is the version-chasing — figuring out which round of the mockup a client's email is referring to. Drop the mockup into Drafty and share the link: your client clicks exactly where they mean and pins a note, no account needed. When you update the design, push the revision to the same link. The thread carries over — every round's comments visible, resolved ones closed. You see at a glance what's addressed and what isn't before you reply.

Open a live demo

Questions

How do I get clients to comment on a mockup instead of emailing?: Send the link with a one-sentence instruction: 'Click any spot to pin a note directly on the design — easier than describing it in an email.' Most clients default to email because it's familiar, not because they prefer it. Give them one explicit alternative and they'll usually use it. If they still email feedback, reply with the link and ask them to pin the notes there — 'so I can see exactly which element you mean' is the framing that works.
Can a client comment on a mockup without a Figma account?: No. Figma requires a signed-in account to leave a comment, even on a view-only shared link. This has been a persistent complaint since at least 2021. The standard workaround: export the mockup as a PNG and share it via a tool that supports guest commenting — the client opens the link in a browser, no account, and clicks the spot they mean.
How do I get more useful feedback on a mockup?: Ask a specific question, not an open one. 'Does the pricing table make the difference between plans clear?' gets a yes or no and a note on the table. 'Let me know your thoughts' gets a general reaction that isn't actionable. Pin your question as a comment on the section you want evaluated — clients who open the link and see a specific question already know where to start.
What is the best format to share a mockup for client feedback?: A browser-openable link beats an email attachment in almost every scenario. An attachment forces the client into whatever software opens PNG or PDF files on their machine, they mark it up there, and you receive an annotated copy you have to interpret. A review link means both of you are looking at the same artifact in the same thread, and the client's notes are pinned to the exact element — not described in text.
How do I handle conflicting feedback from multiple stakeholders on a mockup?: Share one link with all stakeholders, not individual copies. When every reviewer comments on the same artifact, they can see each other's notes — which surfaces conflicts before they reach you. If two stakeholders disagree on the header treatment, that's a conversation they have in the thread rather than two contradictory instructions you receive separately. For final approval, still identify one decision-maker whose call resolves conflicts.
How many rounds of mockup feedback is normal?: Two focused rounds is the professional standard for most freelance projects. Round one covers major direction — layout, hierarchy, content gaps. Round two catches details after those are resolved. If you're consistently hitting four or five rounds, the cause is usually one of three things: feedback is arriving on the wrong version, the review ask was too open-ended, or the right decision-maker isn't reviewing until late. Fixing the feedback format (a review link with a specific question) usually cuts rounds without requiring a difficult conversation about scope.

Keep exploring

How to comment on a mockup How to get client sign-off Share a design for feedback Get feedback on a mockup

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