How do you annotate a product screenshot well?

Label what the screen means rather than naming the element -- "everything overdue, across every project" instead of "filter bar". The test is whether the label would still be useful to someone who could not see the image.

How many callouts should a screenshot have?

Three at most. Beyond that the eye has nowhere to start. Crop or zoom into the relevant region rather than shrinking a full dashboard, which becomes a grey rectangle at blog width.

When should I use a demo instead of annotated screenshots?

Whenever the thing is a sequence. Four numbered annotated screenshots ask the reader to assemble a flow mentally; a demo lets them move through it. A numbered series of screenshots is a demo with extra steps.

← Back to blog

Annotated Screenshots That Actually Explain Something

August 22, 2026

An annotated screenshot is a product image with callouts explaining what a viewer is looking at. They appear on landing pages, in documentation, in proposals and in app store listings.

Most of them fail the same way: they label what things are rather than what they do for the reader.

Label the meaning, not the element

"Navigation menu" and "Filter bar" tell a reader what they can already see. "Everything overdue, across every project" tells them why the screen matters.

The test is whether the label would still be useful to someone who could not see the image. If not, it is decoration.

Practical rules

Three callouts maximum per screenshot. More and the eye has nowhere to start.
Crop or zoom rather than shrink. A full dashboard at blog width is a grey rectangle.
Keep contrast high -- pale grey on a pale interface disappears on a phone.
Use invented data. A screenshot on a public page is public, including the customer name in the header.
Do not number them unless order matters. Numbers imply a sequence and create one that is not there.

Where annotated screenshots beat a demo

In anything printed or exported, in email where interactive content is stripped, in an app store listing that only accepts images, and anywhere the reader is scanning rather than watching.

They also load instantly, which matters above the fold where an embed would be the slowest thing on the page.

Where a demo is the better answer

Anything that is a sequence. A flow explained as four annotated screenshots is four images a reader has to assemble mentally; the same flow as a demo is something they move through.

If you find yourself making a numbered series of annotated screenshots, that is a demo with extra steps.

Frequently asked questions

How do you annotate a product screenshot well?: Label what the screen means rather than naming the element -- "everything overdue, across every project" instead of "filter bar". The test is whether the label would still be useful to someone who could not see the image.
How many callouts should a screenshot have?: Three at most. Beyond that the eye has nowhere to start. Crop or zoom into the relevant region rather than shrinking a full dashboard, which becomes a grey rectangle at blog width.
When should I use a demo instead of annotated screenshots?: Whenever the thing is a sequence. Four numbered annotated screenshots ask the reader to assemble a flow mentally; a demo lets them move through it. A numbered series of screenshots is a demo with extra steps.

Keep reading

This is what Demorta does

Click through it — the same kind of demo you can record of your own product.

Try it on your own product

Record your first interactive demo free.

Five demos on the free plan, forever. No credit card, no trial countdown, no sales call. Install the Chrome extension, click through your product once, and you have a shareable link in about ten minutes.

Start free →