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

No — Figma requires an account to comment. A client without an account can open a 'can view' prototype link and see the design, but the comment icon is locked. Guest commenting has been Figma's most-requested feature since 2021 and as of 2026 still isn't available. The workaround: export the frames and share them via a tool that lets clients annotate without signing up.

What is the best way to share a Figma file for client review?

From presentation mode (not the editor), click Share and set it to 'Anyone with the link → can view'. Test the link in an incognito window first — this shows you exactly what your client sees before they tell you. If you need their comments anchored to specific elements, exporting the frames and sharing a review link outside Figma gets more usable feedback than asking them to create an account.

How do I get specific feedback on a Figma design instead of vague notes?

Vague feedback ('make it pop', 'something's off') comes from clients who can't point at what they mean. Email and screenshots force them to describe — descriptions are imprecise. Give them a way to click the exact element and leave a note tied to that spot. Also helps: send two specific questions with the review link ('Does the button copy match what you'd expect to happen next?' / 'Is the hierarchy clear at a glance on your phone?'). Specific questions replace one round of follow-up.

How do I review a Figma prototype before sharing it with a client?

Open the prototype in presentation mode (⌘\ to clear the panels, then ▶). Walk every flow as a first-time user — click what they'd click, not the correct path you know. Check that every screen is legible in under three seconds, every hotspot is wired, and every CTA is visually heavier than surrounding elements. Run a contrast check (Contrast plugin by Stark) on every button and text-on-colour. That covers the most common client feedback before it lands.

How many rounds does a Figma client review usually take?

One to two rounds when the client can annotate directly on the design — because element-pinned comments eliminate the back-and-forth needed to locate what they meant. Email-based review adds rounds: 'the section near the top' requires at least one clarification exchange before you know what to fix. Running your own review pass before the client sees the file removes the most predictable round entirely.

Should I share the Figma editor link or the prototype link with a client?

The prototype link. The editor link exposes every layer, component, and page in your file — including frames you haven't finished. From the prototype link set to 'can view', the client sees only the flows you've wired. Always test it in an incognito window first so you see exactly what they open. Don't share from the editor Share panel — that controls file permissions, not prototype permissions.

drafty

How to review a Figma file (and get a client to sign off on it)

Quick answer

To review a Figma file, work through it in two passes. First, a self-check: view as prototype (not editor), squint for visual hierarchy, check contrast on interactive elements, and walk every flow from the client's entry point. Then share with the client: use 'Anyone with the link → can view' from presentation mode, or export the frames — clients without a Figma account hit a login wall when trying to comment, so a review link outside Figma often gets more usable feedback back.

Step 1

Switch to presentation view before you review your own file

Press ⌘\ (Mac) or Ctrl+\ (Windows) to hide the left and right panels, then hit ▶ to open the prototype in presentation mode. This is the first thing most designers skip — reviewing a file in the editor is like proofreading a document while watching the tracked-changes markup. You see layer names, constraints, and component boundaries that your client never sees. Presentation mode shows exactly what they'll open. Look for three things: (1) Does the entry frame make the purpose of the screen legible in two seconds without you explaining it? (2) Are the primary actions visually heavier than secondary ones? (3) Does every interactive element look tappable — does it have a cursor or an obvious affordance? If you spot a hierarchy miss here, it's far easier to fix than after the client has already formed an impression.

Step 2

Walk every flow as a first-time user, not as the designer

In the prototype, disable your own mental model. Click only what a first-time user would click, in the order they would click it. The mistake designers make here: they already know the correct path, so they take it efficiently. A new user scans, mis-taps, and tries things that aren't linked. In Figma, if a hotspot isn't wired up, the screen flashes — that flash is what your client will see, and they'll either think it's broken or stop clicking. On a real project: a common missed wire is a secondary CTA on the hero that the designer mentally parked as 'not the main flow' but that users click immediately because it's in prime position. Walk the full prototype with a timer. Any screen that takes longer than three seconds to understand what to do next is a screen the client will flag — catch it first.

Step 3

Run a contrast check on every interactive element

In Figma, install the free Contrast plugin (Figma Community, by Stark). Run it on your primary CTA, all body text on coloured backgrounds, and any disabled-state elements. The two thresholds: 4.5:1 for normal text, 3:1 for large text and UI components (buttons, inputs). Why this matters specifically in Figma reviews: design files often use opacity layers or colour blend modes that look fine on a white artboard but fail when the file is exported or rendered against a real background. The Contrast plugin evaluates the computed colour, not the layer settings — so it catches what your eyes don't. This is the single check that eliminates the most predictable round of client feedback: 'the button text looks a little light on mobile.'

Step 4

Share with the client — and avoid the Figma login wall

This is where most Figma review workflows break. If you share an editor link, the client lands in the full file with all layers exposed. If you share a prototype link set to 'can view', they can view it — but to comment, they need a Figma account. Figma's guest commenting has been the platform's most upvoted feature request since 2021 and still isn't available. The result: clients without an account either create one (adds friction before they've seen a pixel), fall back to email ('can you change the thing near the top?'), or WhatsApp you a photo of their screen. None of those give you a comment anchored to the element they mean. The workaround that actually gets annotated feedback back: export the frames you want reviewed, share a link the client opens in their browser, and let them click the exact element and pin a note — no Figma account required.

The faster way

If the client feedback part is the bottleneck — not your own review — export the frames from Figma and drop them into Drafty. Share the link. Your client opens it in their browser, clicks the button or the headline they want to flag, and leaves a threaded note anchored to that element. No Figma account, no 'which part near the top?'. When you push a revised export, the same URL updates. The client marks threads resolved. The loop that used to span iMessage, email, and two more calls stays on one link.

Open a live demo

Questions

Can a client comment on a Figma file without a Figma account?: No — Figma requires an account to comment. A client without an account can open a 'can view' prototype link and see the design, but the comment icon is locked. Guest commenting has been Figma's most-requested feature since 2021 and as of 2026 still isn't available. The workaround: export the frames and share them via a tool that lets clients annotate without signing up.
What is the best way to share a Figma file for client review?: From presentation mode (not the editor), click Share and set it to 'Anyone with the link → can view'. Test the link in an incognito window first — this shows you exactly what your client sees before they tell you. If you need their comments anchored to specific elements, exporting the frames and sharing a review link outside Figma gets more usable feedback than asking them to create an account.
How do I get specific feedback on a Figma design instead of vague notes?: Vague feedback ('make it pop', 'something's off') comes from clients who can't point at what they mean. Email and screenshots force them to describe — descriptions are imprecise. Give them a way to click the exact element and leave a note tied to that spot. Also helps: send two specific questions with the review link ('Does the button copy match what you'd expect to happen next?' / 'Is the hierarchy clear at a glance on your phone?'). Specific questions replace one round of follow-up.
How do I review a Figma prototype before sharing it with a client?: Open the prototype in presentation mode (⌘\ to clear the panels, then ▶). Walk every flow as a first-time user — click what they'd click, not the correct path you know. Check that every screen is legible in under three seconds, every hotspot is wired, and every CTA is visually heavier than surrounding elements. Run a contrast check (Contrast plugin by Stark) on every button and text-on-colour. That covers the most common client feedback before it lands.
How many rounds does a Figma client review usually take?: One to two rounds when the client can annotate directly on the design — because element-pinned comments eliminate the back-and-forth needed to locate what they meant. Email-based review adds rounds: 'the section near the top' requires at least one clarification exchange before you know what to fix. Running your own review pass before the client sees the file removes the most predictable round entirely.
Should I share the Figma editor link or the prototype link with a client?: The prototype link. The editor link exposes every layer, component, and page in your file — including frames you haven't finished. From the prototype link set to 'can view', the client sees only the flows you've wired. Always test it in an incognito window first so you see exactly what they open. Don't share from the editor Share panel — that controls file permissions, not prototype permissions.

Keep exploring

How to annotate a Figma file How to review a design Design feedback tool BugHerd alternative

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