You have a Figma prototype open and a list of things that feel off: the primary button sits too close to the field above it, the empty state has placeholder copy, the modal closes when it should not. You need to send those notes to whoever builds this, and you need them specific enough that nobody replies asking which button you meant.
Figma plugins can annotate a file, but only if you have edit access. On a view-only share link you are stuck. Here is a way that works no matter your access level, because it captures what is on your screen rather than reaching into the file.
Step 1: Open the prototype and the capture tab
Open the Figma prototype in your browser and click through to the frame you want to critique. Put it in the state you want to comment on: hover a menu open, trigger the error message, scroll to the section that breaks. In a second tab, go to start a new review. Nothing to install, no extension, no signup. The outcome: two tabs, one holding the design and one ready to capture it.
Step 2: Capture the frame
In the review tab, click Capture screen. The browser asks which window or screen to share; pick the Figma tab. The current frame is drawn to a canvas. Drag a rectangle to crop it down to the frame itself, cutting out the Figma toolbar and layers panel so the receiver sees only the design. That crop is the one image edit available, and it is the one that matters: a tight still keeps attention on the thing you are talking about.
Each capture becomes an item in the review. Take one per frame or per state you want to discuss. A checkout with a valid form, an error state, and a success screen is three captures, three items.
Step 3: Pin the exact spot and add the comment
On a captured still, drop numbered pins on the specific spots you mean. Pin 1 on the button, pin 2 on the spacing above it, pin 3 on the placeholder text. Then write the comment for the item. In Chrome or Edge you can dictate it with the browser's built-in speech recognition and talk through what you see; on Firefox you type instead. Numbered pins paired with a comment referencing each number stop the guesswork, which is the whole point of numbered pins that make a developer read steps in order.
Be concrete. "Pin 2: the gap between the email field and the Continue button is too tight, needs about the same spacing as between the other fields" beats "button spacing weird." You can also add free-floating comments with no screenshot for notes that span the whole flow, like "the tone across these three screens shifts from friendly to formal."
Step 4: Publish and get the link
Click Publish. The review is saved and gets a short public URL like /r/your-slug. Anyone with that link can read it, no account needed on their end. Send it to the developer, the design lead, or the client. This is the payoff of a proper Figma review handoff: the receiver opens one link and sees every captured frame, its pins, and your comments in order.
Publishing without signing in is fine. An anonymous review is kept for 30 days, and if you sign in later you claim it permanently. Sign-in is a free Google login or an emailed magic link when you want the review to stick around.
Step 5: Hand off in the format the receiver needs
The same review serves whoever reads it. A person gets the public link, or you export the review as a PDF or a Word document to drop into an email or a ticket. If the build gets handed to an AI coding agent, the review is also available as plain markdown at /r/your-slug/markdown, which is the format an agent reads cleanly. One review, several outputs, no reformatting.
Because this captures a still of what your screen showed, it does not care whether you had edit rights in Figma. That is why a cropped still beats an annotated live page for handoff: it is frozen, it does not shift when someone else opens the file, and it travels as an image plus text anywhere.
Step 6: Close the loop on the notes
Anyone with the link can post a comment on any individual item, so the developer can reply "fixed in the latest build" right under the pin you dropped. As the owner, you mark each comment resolved as it gets handled. There is no board and no ticket workflow here, just a way to resolve review comments without a bug tracker when the job is a single pass, not an ongoing project.
The review also has an owner-facing analytics page showing visit counts and visitor geography, so you can see whether the developer actually opened it before your next call.
If your reviewers and builders are spread out, run the whole thing async: capture, publish, send, and let them work through a design review that ends in a shareable link on their own time. For the broader picture of critiquing designs against the built product, the design review use case walks through where this fits.
Next time a view-only Figma link lands in your inbox with a request for feedback, open a capture tab beside it and send back a link instead of a wall of vague comments.