Figma and design tools · Beginner · 11 min
Share a Figma file and collect comments
By Padding · Updated 18 Nov 2026
Figma (web) · November 2026
You will run one complete feedback round on a single Figma screen, from writing the question you need answered to sharing a link to that frame, sorting the comments and resolving every one.
On this page
Most feedback on a design is not wrong, it is aimed at the wrong thing. You wanted to know whether people understand the flow, and you get five comments about the shade of a button. That happens when a file is shared with "thoughts?" and nothing else. The reviewer has to guess what stage the work is at and what kind of comment would help, so they comment on whatever they notice first.
This tutorial runs one feedback round on one screen and treats the request as part of the design work. You write down the question you need answered, prepare the screen so reviewers land on it, share the file with the right access, send a link that opens on that exact frame, and then sort, answer and resolve what comes back. The sharing mechanics take a few minutes. The ask, and what you do with the replies, decide whether the round was worth running.
Pick one screen you are working on now. A screen with an open decision on it, such as a form whose field order you are unsure of, works best.
Step 1 · Write down the feedback you need
Before you touch the Share button, open a note and answer four questions about the screen. Keep each answer to one line.
- Stage. Is this a rough layout, a near-final design, or something about to go to developers? This tells reviewers how much is still allowed to change.
- The question. What decision do you need help with? Make it something a reviewer can answer from the screen alone, such as "Is it clear which fields are optional?" rather than "Does this work?"
- Out of scope. What should reviewers ignore because it is placeholder or already decided? Colours, copy and icons are common ones at early stages.
- Deadline. When do you need comments by? A round with no end date never closes.
Then choose your reviewers by what the question needs. A question about whether a form is understandable needs someone who has not seen it before. A question about whether a layout can be built needs a developer. A question about whether the content is correct needs the person who owns that content. Two or three people is enough for one screen.
Check it worked
Your note has four lines (stage, question, out of scope, deadline) and a list of named reviewers, each with the reason they are on it. The question ends with a question mark and can be answered without reading anything else.
Step 2 · Prepare the screen so reviewers land in the right place
Reviewers open a file and start looking around. Make the screen they should look at easy to find and hard to confuse with older versions.
- Give the frame a clear name in the layers panel, for example
Sign up – v3 for review. A version number stops people commenting on an old copy. - Move earlier versions of the screen out of the way, onto another page or into a clearly named section, so there is only one candidate on the canvas.
- Add a short text layer above the frame with your ask from the previous step: the stage, the question and what to ignore. People read text on the canvas before they read an email.
If the file has several pages, make sure the page holding the review frame has a plain name such as For review, so the page list in the left sidebar makes sense to someone who has never opened it.
Check it worked
On the review page there is one frame for this screen, its name includes a version, and a text block above it states the stage, the question and what to ignore. Zoom out to fit the page and you can still find the frame in a second.
Step 3 · Invite reviewers with the right access
Click Share in the toolbar at the top right of the file. In the share dialog, type each reviewer's email address and set their access level before you send the invite.
- Can view lets the person open the file and add comments. They cannot move or change anything. This is the right level for almost every reviewer.
- Can edit lets the person change the design. Give it only to someone who will work on the file with you, not to someone you want an opinion from. On paid plans, edit access can also count towards your team's paid seats, so check with whoever manages your Figma account before handing it out.
Look at the link access setting in the same dialog as well. It controls who can open the file using only the link, and the options you see depend on your plan and on any rules your organisation's admin has set. For a review with named people, keep it so that only invited people can open the file. That way a forwarded link does not widen the audience without you knowing.
Check it worked
Open the share dialog again. Every reviewer from your list appears with "can view" (or "can edit" only for a co-designer you chose on purpose), and the link access setting shows the restricted option you picked.
Step 4 · Copy a link that opens on the screen
A link to the whole file drops the reviewer wherever the file was last saved, which may be a different page. Link to the frame instead.
Select the review frame on the canvas, right-click it, and use the menu option to copy a link to the selection (it sits in the copy and paste group of the right-click menu). Paste the link somewhere you can read it.
A link that points to a frame carries that frame's ID in the address, after node-id=. A link to the whole file does not.
Check it worked
The link you pasted contains node-id= followed by a number pair. Open it in a private browser window while signed in as yourself: the file opens on the review page, zoomed to your frame.
Step 5 · Send the request and leave the ask in the file
Send the link in whatever channel your reviewers read: email, chat or the project tracker. Put the ask in the message, not only the link. A template you can adapt:
Sign up screen, v3 – feedback by Thursday 5pm please.
Stage: layout and flow. Colours and icons are placeholder, please skip them.
Question: is it clear which fields are optional, and would you know what to do after pressing Create account?
Link (opens on the screen): <paste your frame link here>
Comment straight on the screen: press C, click where your point applies, type. Start with Q if it is a question, or Change if you are suggesting a change.The prefixes are optional, but they make the next step much faster, because you can tell a question from a request without reading the whole thread.
Now go back to the file and leave the same ask as the first comment. Press C (or choose the comment tool in the toolbar), click on the frame's top edge, write the question and the deadline, and @mention each reviewer. A mention notifies them inside Figma as well as in your message, and the comment pin sits on the frame, so anyone who opens the file sees the ask first.
Check it worked
Your message has been sent to every reviewer with the frame link in it. In the file, a comment pin sits on the review frame, and opening it shows your question, the deadline and each reviewer's name as a mention.
Step 6 · Sort the comments as they arrive
When comments come in, open the comments list in the right sidebar to see them all in one place. Clicking a comment in the list takes you to its pin on the canvas.
Read each one and decide which of three groups it falls into. Reply in the thread so the reviewer can see your decision:
- Answer. A question you can answer now. Reply with the answer. If the question shows that the screen itself was unclear, treat it as a change too.
- Change. Something you will act on in this round. Reply with what you will do, for example "Moving the optional label next to the field name".
- Park. A fair point that is out of scope for this round, such as a colour comment at the layout stage. Reply saying where it is noted and when you will come back to it, and copy it into your note from step 1.
Do not argue in threads. If two reviewers disagree, reply to both with the decision you are making and why, and move on. Comments that agree with each other are a strong signal; one comment alone is an opinion worth weighing.
Check it worked
Every comment on the frame has at least one reply from you, and each reply makes clear whether it is an answer, a change or parked. Your note from step 1 now has a "Parked" list with anything you deferred.
Step 7 · Make the changes and resolve the threads
Work through the threads you marked as changes. Edit the design, then go back to each thread and resolve it with the check mark on the comment. A resolved comment disappears from the canvas but is not deleted, so the record of what was asked and what you did stays in the file.
Resolve answered and parked threads too, once your reply is in. An unresolved comment should always mean "something still needs doing".
When the list is empty, close the round:
- Rename the frame to drop "for review", for example
Sign up – v3, or duplicate it as v4 if the changes were large enough that you want to keep both. - Reply to your own ask comment with a short summary: how many comments, what changed, what was parked. Then resolve it.
- In the comments list in the right sidebar, switch on the option to show resolved comments, and scan them once to confirm nothing was resolved by mistake.
Check it worked
With resolved comments hidden, the review frame has no comment pins on it. With resolved comments shown, every thread is there with your reply, and your first comment ends with a summary of the round. The changes you replied about are visible in the design.
Next steps
You have run a feedback round on one screen with a written question, a frame link, sorted replies and nothing left open. The same pattern works for a whole flow; send one question per screen rather than one for the file.
- When the conversation needs to happen live with a group, run a design critique in FigJam.
- If your files are getting hard for reviewers to find their way around, organise a Figma file with pages, frames and layers.
- When reviewed screens turn into shared components, publish and update a Figma team library so changes reach every file that uses them.
Part of these paths
Related tutorials
- Run a design critique in FigJamYou will set up a FigJam board for one critique, run it in 30 minutes with a silent review before any discussion, and leave with a sorted list of agreed changes, each tied to the goal it serves.
- Publish a team library and push updates to other filesYou will have the Larkfield Clinic components in their own library file, used by the booking app file, with one published change reviewed and accepted on the other side.
- Organise a Figma file with pages, frames and layersYou will have a Figma file for the Larkfield Clinic booking app with a cover, a page for each stage of work, named mobile and desktop frames for all six screens, and sections that group them.
Need this done for you?
Padding does this work for growing companies, from the first diagnosis to a system that keeps working.
Get new tutorials