Comments and Mentions in Figma are collaboration features that help designers, developers, product managers, testers, and other team members communicate directly inside a design file. Instead of using separate messages or documents for every design discussion, team members can leave comments on specific areas of a design, reply to existing comments, mention teammates, ask questions, provide feedback, and track design decisions.
Comments are especially useful during UI/UX reviews, design handoff, usability testing, client feedback, design-system discussions, and team collaboration. Mentions make communication faster by notifying a specific teammate when their attention or response is required.
For professional Figma learning, explore JustAcademy Figma Training and Register for Figma Course Demo.
A comment is a message attached to a particular location or object within a Figma design. It allows a team member to provide feedback without changing the actual design immediately.
For example, a designer may receive a comment such as “Increase the spacing between these buttons” directly on a mobile app screen. The designer can review the feedback, make the required change, and reply to the comment.
Designer:
"Can we increase the spacing between these two buttons?"
Developer:
"Updated. The spacing is now 16px."
Designer:
"Looks good. Thank you!"
A mention is a way to specifically notify another person inside a comment or collaboration message. A teammate can generally be mentioned using the @ symbol followed by their name.
Mentions are useful when feedback requires action from a particular person.
@Rahul Please review the checkout screen.
@Priya Can you confirm the final color?
@Amit Please check the developer handoff details.
Select Design Area
↓
Open Comment Tool
↓
Place Comment
↓
Write Feedback
↓
Mention Team Member if Required
↓
Team Member Receives Notification
↓
Reply / Make Changes
↓
Resolve Comment
To add feedback to a design, use Figma's comment functionality and place the comment near the relevant layer, frame, component, or area of the canvas.
A good comment should be clear, specific, actionable, and connected to the design element being discussed.
This looks wrong.The button feels too close to the input field.
Can we increase the vertical spacing to improve readability?
Comments become more useful when they are attached to the exact area that needs attention. Instead of saying “Fix the login page,” identify the particular element.
Login Page
├── Logo
├── Email Input
├── Password Input
├── Forgot Password Link
├── Login Button
└── Social Login Buttons
For example, a reviewer can place a comment specifically on the Login Button rather than creating a general comment for the entire screen.
Mentions are useful when feedback is intended for a particular person. Start typing the @ symbol and select the relevant teammate from the available suggestions.
@Designer Please check the spacing.
@Developer Please confirm whether this interaction is possible.
@ProductManager Please confirm the final requirement.
Comments can become conversation threads. A team member can reply to an existing comment instead of creating a separate comment for the same topic.
Comment:
"The card needs more spacing."
Reply:
"Should we use 16px or 24px?"
Reply:
"Let's use 24px for desktop."
Reply:
"Done. Updated the component."
A comment thread groups the original comment and its replies together. This keeps related communication organized and makes it easier to understand the history of a design discussion.
| Thread Element | Purpose |
|---|---|
| Original Comment | Starts the discussion. |
| Reply | Responds to the comment. |
| Mention | Notifies a specific teammate. |
| Resolution | Indicates that the issue has been addressed. |
After a comment has been addressed, the thread can be resolved. Resolving a comment helps separate completed discussions from active issues.
Issue identified
↓
Comment added
↓
Designer reviews feedback
↓
Design updated
↓
Reviewer confirms change
↓
Comment resolved
| Unresolved Comment | Resolved Comment |
|---|---|
| Requires attention | Issue has been addressed |
| Usually part of active review | Usually part of completed review |
| Needs follow-up | Does not normally require further action |
Comments are extremely useful during design review sessions. Reviewers can identify problems directly on the design instead of describing the location separately.
UI designers can use comments to discuss visual improvements.
Example:
"The heading hierarchy is not strong enough.
Can we increase the heading size or font weight?"
"Please align the CTA with the content container."
"The card radius is different from the design system."
Comments can also be used to discuss user experience problems rather than only visual issues.
"What happens when the user enters an invalid email?"
"Should the user receive confirmation after submitting the form?"
"Can we provide a loading state here?"
Comments can provide useful implementation context during developer handoff. Designers can clarify interactions, states, responsive behavior, or special requirements.
Developer Note:
"The mobile navigation opens as a drawer."
"Use the disabled button state when required fields are empty."
"Show the error message below the input field."
Comments make it easier for clients or stakeholders to provide feedback directly on the relevant design screen.
Client:
"Can we use the brand blue for this button?"
Designer:
"Yes. I will update the primary CTA."
Client:
"Approved."
Comments can also support approval workflows. Stakeholders can communicate whether a particular design direction is accepted or requires changes.
Review:
"Homepage layout approved."
"Pricing section needs revision."
"Mobile version approved after spacing update."
When a design decision involves several people, multiple relevant team members can be mentioned. However, mentions should be used carefully so that only people who genuinely need to participate are notified.
@Designer Please update the component.
@Developer Please confirm implementation feasibility.
@ProductManager Please confirm the requirement.
Do not mention large groups of people when the comment only requires one person's attention. Excessive mentions can create notification noise and reduce productivity.
@Amit Can you verify the API state for this screen?@Everyone @Everyone @Everyone Please check this.Comments can help identify inconsistencies in components, typography, spacing, colors, and other design-system elements.
Comment:
"This button uses 12px radius, but the primary button
component uses 8px. Should we use the shared component?"
Component-related comments can help teams identify problems with reusable UI elements.
When working with Auto Layout, reviewers can leave comments about spacing, padding, alignment, sizing, and responsive behavior.
Example:
"The horizontal padding should be 24px."
"Please check whether the content expands correctly
when the text becomes longer."
During prototype reviews, comments can identify interaction and navigation issues.
"The button should navigate to the checkout screen."
"The back interaction is missing."
"Please add a loading state before showing the result."
Designs usually go through multiple iterations. Comments provide a record of feedback and help teams understand why certain changes were requested.
Version 1
↓
Review Comments
↓
Design Update
↓
Version 2
↓
Additional Comments
↓
Final Design
During usability testing, observations can be recorded directly on the relevant screen or interaction.
Observation:
"Three users failed to notice the filter button."
Design Feedback:
"Consider increasing the visual prominence of the filter control."
Accessibility issues can be documented through comments so designers can correct them during the design process.
| Bad Comment | Good Comment |
|---|---|
| This is bad. | The heading needs stronger visual hierarchy. |
| Fix this. | Please align this field with the form container. |
| Wrong color. | Can we use the primary brand color defined in the design system? |
| Doesn't work. | The prototype does not navigate when the CTA is selected. |
Use professional and neutral language when communicating with team members. A comment should focus on the design problem rather than the person.
"The spacing appears inconsistent with the design system.""You made the spacing wrong."Designers can mention product managers when a design decision depends on business requirements, product behavior, or feature priorities.
@ProductManager
Can you confirm whether users should be able to edit
their address after placing an order?
Developers can be mentioned when a design requires technical validation.
@Developer
Can we support this animation on the current platform?
@Developer
Please confirm whether this empty state is required by the API.
Designers can use comments to discuss visual consistency, component usage, layout decisions, and design-system rules.
@Designer
Should this use the existing Card component?
@Designer
Can we keep the same spacing as the dashboard layout?
Comments and mentions can generate notifications depending on the collaboration and notification settings of the Figma workspace. Team members should review their notification preferences so important feedback is not missed while unnecessary notifications are minimized.
1. Open Design
2. Review Unresolved Comments
3. Understand Each Issue
4. Make Required Changes
5. Reply to Important Comments
6. Request Confirmation
7. Resolve Completed Comments
Comments create a shared communication layer between designers, developers, product managers, researchers, testers, and stakeholders. This makes collaboration more contextual because discussions remain connected to the actual design.
Comment threads can provide useful context about previous decisions. Before changing an important design element, reviewing related discussions can help understand why the original decision was made.
During handoff, comments can clarify implementation details that may not be obvious from the visual design alone.
| Area | Example Comment |
|---|---|
| Spacing | Use 16px spacing between fields. |
| Interaction | Open the dropdown when the field is selected. |
| State | Show the disabled state when the form is incomplete. |
| Responsive | Stack the cards on smaller screens. |
Suppose a team is designing an e-commerce checkout page.
Comment 1:
"Please make the shipping address section easier to scan."
Mention:
@UXDesigner
Comment 2:
"Can we show an inline validation message for invalid postal codes?"
Mention:
@Developer
Comment 3:
"Please confirm whether guest checkout is required."
Mention:
@ProductManager
Comment:
"The transfer button is too close to the bottom edge.
Please verify the mobile touch area."
Mention:
@UXDesigner @AccessibilityReviewer
Comment:
"The chart labels are difficult to read at smaller sizes.
Can we improve the hierarchy or provide tooltips?"
Mention:
@Designer @Developer
Review Meeting
↓
Team Opens Figma File
↓
Reviewer Adds Comments
↓
Relevant Members Are Mentioned
↓
Designer Updates Design
↓
Team Reviews Changes
↓
Comments Are Resolved
Comments are collaboration messages attached to a design or specific location that allow team members to provide feedback, ask questions, and discuss design decisions.
A mention is used to specifically notify or involve another team member in a comment or collaboration discussion.
They keep feedback connected to the actual design and make design reviews, communication, and issue tracking more organized.
Comment threads keep related questions, responses, and decisions together instead of scattering the discussion across multiple comments.
A teammate should be mentioned when their input, approval, technical validation, or action is specifically required.
Resolving completed comments keeps the workspace organized and makes it easier to identify active issues.
Comments can clarify interactions, responsive behavior, component states, spacing, validation rules, and other implementation details.
A good comment is specific, concise, respectful, contextual, and actionable.
Comments and Mentions are essential collaboration features for professional Figma workflows. They allow teams to communicate directly within the design context, provide precise feedback, ask questions, request approvals, clarify implementation details, and document design decisions. By using clear comments, relevant mentions, organized threads, and proper resolution practices, teams can make design reviews faster, reduce communication gaps, and improve the overall quality of the final product.
For structured learning and practical Figma training, visit JustAcademy Figma Training and Register for Figma Course Demo.
