How to Give Design Feedback in Figma (2026 Guide)
Good design feedback is specific, in-context, and easy to act on. The problem with most Figma feedback is that it's a wall of text that loses your tone and takes forever to write. This guide covers every way to leave feedback in Figma — and when to use each — so your notes are clearer and your revisions faster.
Where do you give feedback in Figma?
You give feedback directly on the canvas in Figma. Click a frame or element and add a comment pinned to that spot. Comments support replies, reactions, and @mentions. For voice or video feedback, a widget like Murmur pins a recording to the same spot.
Keeping feedback on the design — rather than in a separate doc, email, or chat thread — is the single biggest thing you can do to make it clear. The reviewer points at the exact element, and the designer never has to guess what "the button at the top" refers to.
Method 1: Text comments (built into Figma)
Figma's native comments are pinned to the canvas and support threaded replies, reactions, and @mentions. They're perfect for quick, unambiguous notes like "increase spacing here" or "typo."
Best for: short, factual points. Weak for: nuance — text strips out tone, can read as blunt, and is slow to write for anything complex.
Method 2: Voice & screen-recorded feedback (with Murmur)
For anything beyond a quick note, voice and video are faster to give and clearer to receive. Murmur lets you record an audio note or your screen in a Chrome extension, then pins it as a playable note on the exact Figma element — with reactions and text replies, just like comments.
Best for: explaining the "why," walking through a flow, or delivering tricky feedback warmly. Your tone comes through, and a 30-second note often replaces three paragraphs.
How to give design feedback in Figma, step by step
- Select the exact element you're reviewing so your note is anchored to it.
- Pick the format — a quick text comment, or a voice/screen note for anything nuanced.
- For voice or video, record in the Murmur Chrome extension and pin it to the element.
- Be specific — explain the why, not just the what, and suggest a direction.
- Keep it a conversation — let teammates reply, react, or resolve the thread.
Best practices for giving great design feedback
- Be specific and anchored — tie every point to an element, not "the page in general."
- Explain the reasoning — "this CTA competes with the headline" beats "make it smaller."
- Separate must-fix from nitpick — tell the designer what's blocking vs. preference.
- Lead with intent, not just problems — voice makes encouragement land better than text.
- Keep it one conversation — feedback that lives on the design doesn't get lost in chat.
Text vs. voice/video feedback in Figma
| Voice / video (Murmur) | Text comments (Figma) | |
|---|---|---|
| Speed to give | Seconds — just talk | Slow for complex notes |
| Carries tone | Yes | No |
| Walk through a flow | Yes (screen recording) | No |
| Pinned to the element | Yes | Yes |
| Best for | Nuanced, in-depth feedback | Quick, factual notes |
FAQ
Does Figma have built-in feedback tools?
Yes — Figma has text comments you can pin to a frame or element, with replies, reactions, and @mentions. They're great for quick notes but text-only, so they can't carry tone or walk through a screen.
What's the best way to give feedback on a Figma design?
Use text comments for quick, simple points. For anything nuanced — explaining the "why," walking through a flow, or softening tough feedback — a voice or screen-recorded note is clearer and faster than typing.
Can you leave voice or video feedback in Figma?
Not with Figma's native comments, which are text-only. Murmur adds voice and screen-recorded feedback pinned to the element, played back right inside Figma. See voice comments in Figma.
Is Loom good for Figma feedback?
Loom is great for general video messages, but the recording lives behind an external link outside Figma. See our Loom alternative for Figma for an in-context option.