You have a staging URL open, ten things you want fixed, and a developer who will not read a video. You want a single document with screenshots and comments, in markdown, that you can paste into a ticket or hand to a coding agent. Here is the exact sequence, start to finish, with no install and no signup.
Step 1: Open a new review in a browser tab
Go to start a new review. The page loads in any modern browser. You do not install anything, you do not add an extension, and you do not have to sign in. If you want the review tied to an account later, sign in afterward and it gets claimed permanently; otherwise the anonymous review stays live for 30 days.
Outcome: an empty review is ready in one tab. Keep the site you are reviewing open in another tab or window.
Step 2: Capture the first screen
Click Capture screen. The browser shows its standard picker asking which window, tab, or full screen to share. Pick the tab with the page you want to review. The current frame is grabbed to a canvas. If the screenshot includes a browser chrome you do not want, drag a rectangle on the still to crop it down. That crop is the only edit you make to the image. There is no drawing of arrows or labels on top, by design, so the screenshot stays clean.
Outcome: one item now exists in the review, holding a cropped screenshot.
Step 3: Pin the spot you are talking about
If your comment is about a specific element, drop a numbered pin on it. Pins are how you tell the receiver "this button, not that one" without scribbling on the image. A screenshot can carry several pins if you have several points about the same view.
Outcome: the screenshot has numbered markers that your comment text can refer to as 1, 2, 3.
Step 4: Add a comment by voice or by typing
On Chrome or Edge, click the microphone and talk. The browser's built-in speech recognition transcribes what you say into the comment field. On Firefox, dictation is not available, so type instead. Say what is wrong and what you want instead. "Pin 1 is the primary CTA. The contrast against the hero image fails AA. Use the dark variant on this section only." Specific verbs and specific outcomes are what make the markdown actionable later.
Outcome: the item now has a clear written comment attached to its pins.
Step 5: Repeat for the rest of the issues
Click Capture screen again for the next view. Crop, pin, comment, move on. If a thought is not about any particular screen ("the whole flow needs a progress indicator"), skip the capture and add a free-floating comment item instead. Order the items in the sequence you want the reader to follow, since that order is the order the markdown will use.
Outcome: a tidy list of items, each either a captioned screenshot or a standalone note.
Step 6: Publish the review
Click Publish. The review is saved and gets a short URL of the form /r/<slug>. Anyone with that link can open the review in a browser, no login needed. They can also leave a comment on any individual item, which you can mark resolved from your side later.
Outcome: a public link you can paste into Slack, email, or a ticket.
Step 7: Grab the markdown
Append /markdown to the review URL, so /r/<slug>/markdown, and you get the same review as plain-text markdown: a heading per item, the screenshot referenced inline, the pins listed, and your comment text underneath. This is the format the screen capture to markdown workflow is built around, and it is what a coding agent reads cleanly. If you would rather hand a human a polished document, export the same review as a PDF or a Word file from the review page.
Outcome: one source review, three deliverables: a link for people who want to click around, a PDF or Word doc for stakeholders, and markdown for developers and agents.
Step 8: Hand it off
For a developer, paste the markdown into the ticket body, or attach the PDF. For an AI coding agent, paste the markdown straight into the prompt. Cursor, Claude Code, and similar tools parse the headings, image references, and pin lists without complaint. If you want more on that handoff specifically, the guides on markdown screenshots and structured feedback for LLMs cover what to keep and what to cut.
Outcome: the receiver, human or agent, has something they can act on without watching a video or guessing what you meant.
What to do when feedback comes back
Open the review URL. Each item shows any comments the receiver left. Mark them resolved as you confirm fixes on the live site. The analytics page on your side shows visit counts and visitor geography, which is useful when you want to know whether the client actually opened the link before the status meeting.
If your next review is a staging pass before launch or a design check on the built product, the same eight steps apply. Open a fresh review, capture, comment, publish, export. That is the whole loop.