Can a client leave comments on a mockup without a Figma account?

Not in Figma itself — Figma requires a signed-in account to post comments, even on view-only shared links. This has been an open request on the Figma forum since 2021. The practical solution most designers use is to export frames as PNG or PDF and share via a review tool — clients pin notes directly on the design in their browser, no Figma account or extension required.

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

A shared review link outperforms email attachments for multi-round projects. With a file you reconcile annotated PDFs and interpret vague location descriptions. With a link, every note is pinned to the exact element in one thread — and the URL stays the same when you push revisions.

How do I share a mockup from Figma for feedback?

Share a view link (Share → Anyone with the link can view) for clients who just need to see it. For clients who need to comment, export frames as PNG and share via a review tool — Figma's built-in commenting requires a Figma account, which most clients don't have.

How do I keep client mockup feedback organized across rounds?

Share one URL per mockup rather than sending new files. When all feedback lands on the same artifact, you mark threads resolved as you address them, and revision-3 notes sit in context with the original ask. File-based workflows lose that thread by round two.

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

Two things help: a tool where clients click the exact element (rather than describing it in prose), and a specific question attached to the areas you're unsure about. 'Does the pricing table make the difference between plans clear?' gets a pinned note. 'Thoughts?' gets 'looks great!'

drafty

How to share a mockup for feedback

Quick answer

To share a mockup for feedback, export the design as a PNG or PDF and send the file, share a Figma view link, or — best for client review — generate a public URL clients open in their browser, click to pin notes on the exact element, and reply without creating an account. The third method is the one most designers land on after one too many emails describing a button as 'the blue thing near the top.'

Step 1

Share a Figma view link (free, but no client comments)

Open the file in Figma, click Share in the top-right corner, set permissions to 'Anyone with the link can view', and paste the URL into Slack or email. Your client sees the live design in their browser without a Figma account. The problem: view-only means no commenting. Figma only allows pinned notes from signed-in accounts, so you still get back a separate email: 'The pricing section — font bigger? Also the CTA.' You're translating prose into design coordinates every round. If your client has a Figma account and is comfortable in it, press C to comment is genuinely fast. If they're not — and most clients aren't — this becomes a bottleneck by the second revision.

Step 2

Export as PNG or PDF and share the file

From Figma: select the frames, open the Design panel, scroll to Export, choose PNG (2×) or PDF, click Export. Drop it into email, Google Drive, or a shared Dropbox folder. Your client downloads it, opens it in Preview or Acrobat, and marks it up with sticky notes. The friction lands on you: every round means re-exporting with a new name and reconciling feedback from a file called homepage-v4-FINAL_revised-JanFeedback.png. The most common mistake is skipping the naming convention — 'homepage-r2-2026-06-20.png' is unambiguous; 'homepage_FINAL.png' is a lie you'll regret in two weeks. Use this for a single round of low-stakes feedback. Once you're on round three, the file-bouncing cost adds up fast.

Step 3

Share a public review link — client pins notes, no account needed

Export the frame from Figma as a PNG, upload it to a review tool that supports guest commenting, and paste the URL in your message. Your client opens it in Chrome, Safari, or their phone browser — no account, no extension — clicks the element they mean, and the note lands pinned to that spot. You see it in one thread, reply, and mark it resolved. One thing that makes this work: send a sentence with the link. 'Click anywhere to pin a note — no account needed.' Without it, clients who've never used a review tool open the URL, scroll around, and email you separately anyway. That sentence cuts one full round. Tools that support guest commenting on uploaded designs include Drafty, Markup.io, and Ruttl.

The faster way

If you're already exporting a PNG to share, the extra step is just where you drop it. Upload to Drafty and share the link — your client clicks the exact button or heading they mean and leaves a note anchored to that spot, no Figma account, nothing to download. Push a revised version and every comment stays on the same URL. No re-emailing files, no tracking which PDF is newest.

Open a live demo

Questions

Can a client leave comments on a mockup without a Figma account?: Not in Figma itself — Figma requires a signed-in account to post comments, even on view-only shared links. This has been an open request on the Figma forum since 2021. The practical solution most designers use is to export frames as PNG or PDF and share via a review tool — clients pin notes directly on the design in their browser, no Figma account or extension required.
What is the best way to share a design mockup for client feedback?: A shared review link outperforms email attachments for multi-round projects. With a file you reconcile annotated PDFs and interpret vague location descriptions. With a link, every note is pinned to the exact element in one thread — and the URL stays the same when you push revisions.
How do I share a mockup from Figma for feedback?: Share a view link (Share → Anyone with the link can view) for clients who just need to see it. For clients who need to comment, export frames as PNG and share via a review tool — Figma's built-in commenting requires a Figma account, which most clients don't have.
How do I keep client mockup feedback organized across rounds?: Share one URL per mockup rather than sending new files. When all feedback lands on the same artifact, you mark threads resolved as you address them, and revision-3 notes sit in context with the original ask. File-based workflows lose that thread by round two.
How do I get specific feedback on a mockup instead of vague comments?: Two things help: a tool where clients click the exact element (rather than describing it in prose), and a specific question attached to the areas you're unsure about. 'Does the pricing table make the difference between plans clear?' gets a pinned note. 'Thoughts?' gets 'looks great!'

Keep exploring

How to comment on a mockup Get feedback on a mockup How to review a mockup 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