Practical guide
Review the Whole Screenshot Before Sending It
Share the part that explains the problem without exposing unrelated messages, account details, or other people.
Name the single thing the image must show
A screenshot can answer a support question quickly, but it often captures more than the problem. Before taking one, decide what the recipient needs to see. Perhaps it is an error message, a missing button, or a layout issue. A full account dashboard may be unnecessary. In a hypothetical report about a broken search field, private conversations visible beside the field do not help explain the bug. Start with the smallest relevant area rather than making a broad capture and hoping nobody reads the rest.
Check the margins as carefully as the center
The eye naturally goes to the error you are trying to show. Deliberately inspect the surrounding areas: account names, browser content, message previews, profile images, and any document open behind the page. Look for codes or private links as well as obvious personal details. A screenshot does not inherit the privacy boundary of the original conversation once you send it elsewhere. eSafety describes screen capture as a way to save and share what appears on a screen, which is why context matters.
Protect other people's part of the conversation
If a report requires a conversation excerpt, include only the relevant portion and use the platform's appropriate reporting channel. Do not post another person's private messages publicly just to demonstrate that your account has a problem. Ask permission before sharing an ordinary conversation for a different purpose, unless you are using an appropriate safety-reporting process. The useful distinction is between giving a responsible reviewer necessary context and broadcasting material to an audience that was never part of the exchange.
Inspect the final attachment, not the editing screen
After preparing a limited or redacted image, open the actual file you intend to attach and review it again. Confirm that it still explains the problem and does not reveal the information you meant to exclude. Avoid naming the file with unnecessary private details. If the screenshot cannot be made suitably narrow, a written description may be better. The finished task is not simply Screenshot taken; it is Relevant evidence shared with the right recipient and no avoidable extra disclosure.
Sources checked
Linked reference pages checked on 2026-09-09. Product details can change. No paid-membership test or sponsorship is implied.
eSafety: screen capture and sharing ↗