How to annotate screenshots for support docs

Create clearer support screenshots with arrows, labels, emphasis, and privacy-safe markup.

Support screenshots should reduce confusion, not add decoration. Good annotation makes the next action obvious and removes irrelevant noise.

Step 1: Start from the cleanest screenshot

Before adding arrows or labels, make sure the screenshot already shows the right state. If it contains private data, clean that first with Screenshot Redactor.

Step 2: Choose the one thing each screenshot needs to explain

One screenshot should usually support one instruction. If the image needs to explain too much, split it into two or three steps instead of adding more markup.

Step 3: Add only the annotation types you need

Open Screenshot Annotator and use simple markup such as:

arrows for direction
boxes for regions
short labels for action names
highlights for emphasis

Avoid mixing every annotation style in one frame.

Step 4: Keep labels short

Labels should support the main instruction text, not replace it. Short notes like "Open settings" or "Select billing" work better than full sentences on the image.

Step 5: Check scan order

A viewer should understand where to look first, second, and third. If the arrow flow feels unclear, simplify the screenshot or reduce the number of marked areas.

Best pairing for support teams

Use Screenshot Highlighter when simple emphasis is enough. Use Screenshot Annotator when the screenshot needs explanation. Use both with redaction when the image comes from a real customer account.

Final test

Pretend you know nothing about the product and view the screenshot alone. If the intended action is not obvious in a few seconds, revise the annotation.