You have a build, a staging site, or a competitor's page open, and you want to send someone specific notes about it. Not a wall of text, not a Loom they have to scrub through. Notes tied to what you saw. Here are the questions people ask the first time they do this with a browser-based feedback tool, answered directly.
Do I need to install anything or sign up?
No. There is no app, no desktop download, and no browser extension. You open a tab, capture the screen, and go. You do not need an account to publish, either. An anonymous review gets saved and given a public link that works right away, and it stays live for 30 days. If you sign in later (Google or an emailed magic link), that review becomes permanently yours. The whole thing is free, and you can check the details on the pricing page if you want the specifics.
How do I actually capture the screen?
Click Capture screen. Your browser prompts you to share a window, a tab, or the full screen, the same prompt you get for any screen share. The current frame is drawn onto a canvas. That is a still image, not a recording. You then drag a rectangle to crop to the part that matters, or keep the full frame. Cropping is the only edit to the image itself, so if you want to point at a specific spot, you use a numbered pin rather than drawing an arrow.
To start right now, go to start a new review and click Capture screen on the first item.
Can I record video instead?
No. It captures still frames only. That is deliberate. A still with a written comment is faster to read and easier to act on than a two-minute video where the fix is buried at 1:37. If you have been sending walkthroughs and wondering whether they land, the difference is spelled out in screen capture vs screen recording.
How do I add my comments to a screenshot?
Each screenshot becomes an item, and you add a comment to it by typing or by dictating. Dictation uses your browser's built-in speech recognition and works in Chrome and Edge. Firefox does not support it, so in Firefox you type. You can also add a numbered pin to a screenshot to point at an exact element, then reference the number in your comment ("pin 2, the total is wrong here"). And you can add a comment with no screenshot at all when the note is general, like "the whole checkout flow needs a progress indicator."
What do I send the other person once I'm done?
Click Publish. The review gets a short public URL at /r/<slug> that anyone with the link can open, no login on their end. From there you have options for the receiver:
- Send the link for someone to read in the browser and comment on.
- Export a PDF or a Word document for a client who wants a file.
- Point a developer or an AI agent at the markdown version at
/r/<slug>/markdown.
Same review, different formats. You do not rewrite anything. If you are sending to a client who should never have to learn a tool, the no-tool client feedback approach covers that case.
Can the person I send it to reply?
Yes. Anyone with the review link can post a comment on any individual item. You, as the owner, can mark each comment resolved as you work through them. This is not a project board with assignees and workflow columns; it is a review thread tied to specific screenshots. That is enough for most back-and-forth on a build.
Why would a developer or AI agent want the markdown version?
The markdown export is plain text with your comments and screenshot references in order, which is exactly what a coding agent can read and act on. You do not have to use one, but if your build was made with a tool like Cursor or another AI coding agent, handing over the markdown skips the step of describing your screenshots in words. For a person, the PDF or the link does the same job. Nobody is forced into the agent path.
Can I see if my review was opened?
Every review has an owner-facing analytics page showing visit counts and visitor geography. So you know whether the client actually opened the link before your follow-up call, instead of guessing.
What's a good first review to try?
Pick something small and real. Walk through a signup flow and note every friction point, or capture three screens of a page a client asked you to check. If you want a worked example to copy, the first-time reviewer walkthrough follows one from capture to send, and the product review use case shows what a full pass looks like. The fastest way to understand it is to capture one screen, type one comment, and publish.