Add project details or files (optional)
I could use help with Optional

I usually reply within one or two business days to discuss the scope and next step.

PITCHWAVE®
HomeInsightsGuide

Guide

How to Annotate Product Screenshots in a Presentation

In a sales presentation, a full-screen product capture can leave the buyer searching for the feature you are explaining. I start with the detail the buyer needs to see, then crop and annotate the screen around it. The test is whether the image supports the slide’s point without a tour of every menu.

by Seva Latin · 4 min read ·

In this guide
01 / Guide

Show the detail that supports the headline

Consider a request-management product being introduced to a workplace team. The draft slide is titled “Our platform” and shows the entire workspace: navigation, several requests and an updates panel. The presenter wants to explain how a coordinator can identify the reviewer and review status for a particular request.

The revised headline is “Each request shows its reviewer and review status”. The image is cropped to the relevant request, keeping its name and the column headings. Two labels point to the reviewer and the status. The example below shows the actual change in emphasis.

The revised image explains what information appears together. It does not establish that reviews are faster or that the product reduces missed requests. Those claims would need separate evidence.

Illustrative example

Keep the request. Enlarge the reviewer and status.

Before · whole workspace

Our platform

WorkspaceOverviewRequestsReportsSettings
Requests · all requests
RequestReviewerReview status
Access badgeReception teamAwaiting review
Room setupWorkplace teamReady
Visitor listEvents teamDraft
Recent updatesRoom setup updatedVisitor list created
After · one request, two useful details

Each request shows its reviewer and review status

Request
Access badge
1 Reviewer
Reception team
2 Review status
Awaiting review

1The reviewer stays attached to the request.

2The status remains readable, with its heading.

Original interface mockup for a fictional request-management product. The layouts demonstrate a crop and annotation choice, not a real product, client project or measured result.
02 / Guide

Keep enough context to interpret the crop

A reviewer’s name beside “Awaiting review” means little if the reader cannot tell what is being reviewed. Keep the request name, relevant headings and any scope label needed to understand the view. Remove unrelated navigation and panels before shrinking the useful content.

If the point is about where a feature sits in the wider interface, keep a small overview beside an enlarged detail. Mark the same area in both views so the reader can connect them. If the point is about what the feature shows, as it is here, a single crop is enough.

Keep filters, dates or account labels when they change the meaning of the evidence. A view filtered to completed work must not be presented as the whole workload. Cropping should remove distraction while preserving the qualifications that matter.

03 / Guide

Make annotations explain the interface

Place callouts outside the important content. A short label such as “Reviewer” can identify a field; a longer explanation belongs beside the image or in the speaker’s account. Use matching numbered markers when labels cannot sit close to their targets.

Do not place a bright arrow on every control. In this example, the reviewer and status are the two details needed to support the headline. Highlighting search, navigation and export would introduce other topics without helping explain this one.

Keep added labels visually distinct from the product interface. If you redraw the screen as a schematic, label it as a mockup and retain the actual product’s meaning. A proposed design should not look like evidence of a feature that already exists.

04 / Guide

Check the slide in the file you will send

Review the exported slide at the size your audience will read it. If the important text is still too small, tighten the crop or use a separate detail slide. Enlarging a low-resolution capture will not restore missing detail; take a clearer capture when needed.

For a real product, use a safe demonstration account or a suitably prepared image before inserting it. Microsoft notes that normal cropping hides image areas while retaining them in the Office file. A crop or a shape placed over private information is not a substitute for removing it from the image you share.

  • In desktop PowerPoint, Microsoft documents Picture Format → Compress Pictures → Delete cropped areas of pictures. Save and check the distribution copy after making the change.
  • PowerPoint for the web can crop an image, but Microsoft says deleting the cropped areas requires a desktop app. Prepare a safe image separately if you are working only in the browser.

Send me your screenshot slide and the point you need a buyer to understand.

Sources and technical guidance

Have a case to make?

Tell me what you’re working on. A rough idea or an existing deck is enough to start.

Start a conversation ↗