Add a screenshot when an action or request alone cannot show the result. Screenshots are captured explicitly; Recorder does not create one for every action.

Capture the visible page

While recording, the in-page controls offer Capture for the visible viewport and Area for a selected region.

1. Bring the application tab and the relevant content into view.
2. Select Capture to capture the visible viewport.
3. After Stop, check the image in Screenshots & Attachments.

Despite the control’s label, this captures what is visible in the viewport. It does not scroll and stitch the whole document. To document content farther down the page, scroll to it and take another capture.

Capture an area

Select Area, then choose the region of the visible page you need. Inspect the resulting image in the Viewer to confirm it includes the finding and enough context.

Add an existing image

After Stop, open Screenshots & Attachments in the local Viewer. Use Paste image for a copied image or Upload image to choose a file. You can also drop images on that tab. If clipboard access fails, use the file route.

Record the origin of externally created images in your handoff. Their presence in a session does not establish when the pictured state occurred.

Explain a screenshot

In the local viewer, open Screenshots & Attachments, select an image, and choose Add note. Write what the image shows and the expected result, optionally mark it Important, then Save comment. The note belongs to the image itself; you do not need to annotate a nearby action instead. Use Notes → View evidence to return to it.

Review inclusion and timing

The Viewer marks images outside the stopped session’s retained interval. Review their inclusion controls before submitting a report; an image from outside the interval may still be useful if you explain its timing.

Local downloads include all available attachments, including images marked Exclude from report or Outside recorded period. Those labels do not remove files from the download. Inspect the downloaded screenshot folder and share only the images you intend to send. Save needed images before New recording, which clears local attachments.

Choose enough visual context

In the real sample, 002-full.png shows the card in Blocked. The later 003-area.png shows the retained badge but omits the lane heading. Use the recorded In progress action and final board response to establish the lane. For a new capture, include the destination lane heading with the card when that relationship is the finding.

Check the pixels

Screenshots are not automatically masked. Inspect account names, messages, tokens, and other sensitive information before sharing. Use a separately reviewed edited copy or retake the image with safe data when needed. Recorder does not provide a pixel-redaction editor.

Privacy preview lists available attachments and lets you enlarge them under Not sanitized → Screenshots. It also reports small clicked-image thumbnails stored with action evidence. Those thumbnails remain in the export and cannot be hidden from Privacy preview; open the action to inspect one, and repeat the recording with safe content if necessary.

Download session artifacts explains the screenshot files saved alongside other evidence.