Arrows & shapes
Direct attention to the button, spacing issue or field you mean.
SHOW THE EXACT DETAIL
Annotate screenshots.
Point to the detail.
Give a screenshot enough context to stand on its own. Mark the issue before you send it, then collect review feedback beside the saved capture.
Text & highlights
Add a brief explanation and emphasize the relevant area.
Solid redaction
Cover confidential content before exporting or uploading.
Choose the mark that matches the message
Frame a broken layout with a box, draw a quick path through the interface, or label the expected behavior in text. Crop away unrelated content so a recipient starts with the right view. Annotations become part of the flattened exported image, so the visual explanation travels with it.
Image annotations and review comments do different jobs
An arrow or highlight is embedded in the image. A pinned comment belongs to the cloud review, can receive a response and can be marked resolved. Use both when handing work from a designer to a developer or reviewing a website with a client. Read about pinned comments →
A useful fit for QA and customer support
Show the issue at the viewport where it appears. Include a concise note about the expected result. Before sharing, inspect the screenshot for personal data, tokens or unrelated tabs. Local annotation is free; uploading the finished image uses workspace storage.
Continue exploring
A LITTLE MORE CLARITY
Frequently asked questions
Will annotation use my server render credits?
No. Editing an existing image is a local browser operation. A new screenshot generated from a website URL on the server consumes a render; signed image URL cache hits reuse the existing render.
Can viewers change the original annotation?
Exported edits are flattened into the image. Cloud comments are separate review records; this is not simultaneous multiplayer image editing.