Annotate Image
Annotate your images with freehand drawing, rectangles, arrows, circles, and text. Perfect for highlighting, marking up documents, or adding notes to photos.
Loading tool…
Why annotation beats description
Annotating an image means drawing explanatory marks onto it — arrows, boxes, circles, freehand highlights, numbered callouts, and short labels. It converts a picture that requires explanation into one that explains itself, which is why every bug report, support ticket, and piece of software documentation is full of them.
There is also a redaction dimension. Screenshots regularly contain things that should not travel with them: account numbers, email addresses, customer names, API keys in a terminal. A drawn box hides them visually, and because annotation tools export a flattened image, the covered pixels are genuinely replaced rather than merely hidden under a movable layer — unlike a rectangle placed over text in a PDF or a document, which can often be dragged aside by the recipient.
Why we built this tool
Support teams, QA engineers, designers giving feedback, and teachers building instructions all annotate constantly, usually many times a day.
The screenshots involved are full of internal systems, customer data, and credentials — exactly what you should not be uploading to an unfamiliar web editor. Our annotator draws on a canvas in your browser and exports locally, so the unredacted screenshot never leaves your machine. That is a meaningful difference when the whole point of the edit is to hide something: with a server-side tool, you would upload the sensitive version first and redact it afterwards.
Tips and common mistakes
- Cover sensitive text with a solid shape rather than a blur — solid shapes destroy the information outright.
- Number your callouts when explaining a sequence of steps; arrows alone do not convey order.
- Use a colour that does not appear in the interface you are marking up, so annotations are unmistakable.
- Export the flattened image and inspect it before sending, rather than trusting the editing view.
Quick start: using Annotate Image
- Load the screenshot or photograph you need to mark up.
- Pick a tool — arrow, rectangle, ellipse, freehand, or text.
- Draw over the areas that need pointing out, or cover anything sensitive with a solid shape.
- Use a colour that stands out against the background, such as red on a light interface.
- Export the flattened image and check the covered areas are fully hidden before sending it.
For plain captions use Add Text to Image; to blur a face or a detail instead of covering it, use Blur Image.
Why annotate instead of describe
Describing a location in words is slow and ambiguous: "the third icon from the left, near the top, the blue one." An arrow pointing straight at it removes all doubt. Annotation is faster to create and far faster to understand, which is why bug reports, tutorials, and design feedback lean on it so heavily.
Annotation that communicates clearly
- Use arrows to point, boxes to group. An arrow says "here"; a box says "all of this."
- Pick a color that stands out from the image — bright red or yellow over a mostly neutral screenshot.
- Number your steps when the annotation describes a sequence, so the viewer knows the order.
- Keep notes short. The image carries the context; the note just names the action.
- Do not clutter. Three clear marks beat ten overlapping ones.
Redact while you annotate
Screenshots often contain things that should not be shared — names, emails, account numbers, tokens. Cover them before sending. A solid box works, or use Blur Image for a softer redaction. Annotating and redacting usually happen in the same pass: point at what matters, hide what does not.
Common uses
- Bug reports showing exactly what is wrong.
- Tutorials and how-to guides.
- Design and document feedback.
- Instructions for a form or process.