1. Decide what the recipient needs to see
Start with the question you're trying to answer. For a bug report, the relevant error and surrounding controls may matter. For a set of instructions, one highlighted button may be enough. Crop unrelated tabs, windows and conversations where possible.
2. Check the edges for private details
Look for names, email addresses, profile pictures, account identifiers, message previews, URLs with tokens, calendar entries and location information. Private details often appear in a sidebar or notification—not in the centre of the screenshot.
3. Remove the detail rather than just making it fuzzy
Use fully opaque coverage for information that should not be visible in the shared image. Blur can help reduce visual clutter, but it should not be your only protection for sensitive text. Read our comparison of blur and redaction for more context.
4. Annotate sparingly
One arrow pointing to the problem is often more useful than five colourful shapes. Keep labels short and choose colours with enough contrast against the image. Avoid marking over the information the recipient needs.
5. Inspect the exported file
Open the actual exported image, not only the canvas preview. Confirm the crop, redaction and labels are in the correct locations. Check that the file includes no information you intended to remove.
A practical example: asking for account help
Keep the error message and relevant controls, but crop unrelated tabs and conversations. Redact names, account numbers and tokens in the address bar wherever they appear. If support needs an identifier, send it through the recipient's appropriate private channel instead of exposing it in a public screenshot. A covered email address does not conceal the same address repeated in a sidebar.
Choose a format for the conversation
For technical support, follow the bug-report annotation workflow. For several steps, decide between one combined screenshot image and an image PDF. Check filenames as well as visible pixels before sharing, especially when batch outputs retain source-derived names.
Can the recipient understand the point? Are private areas fully covered? Have you checked the actual exported image? If yes, the screenshot is much more ready to share.
Use the ScreenReady screenshot editor to crop, resize, rotate and annotate locally in your browser, or open the redaction tool to cover private details. Apply all redactions, then download or copy the flattened result and inspect it before sharing. If you move to batch conversion, stitching or PDF, select that safely exported image: tools do not inherit another workspace's edits.