How to hide sensitive information in a screenshot before sharing

Start with what the recipient actually needs

Keep the context needed to understand the issue, not every detail that happened to be on the page. A full-page capture may include private content far below the area you wanted to discuss. Review sidebars, tables, page headers, footers and repeated account information as well as the main content.

• People and contact details: names, email addresses, phone numbers, profile pictures and delivery addresses.
• Account and customer information: account numbers, order references, balances, customer records and internal identifiers.
• Private work: messages, unpublished copy, confidential filenames, internal links and project details.
• Security secrets: passwords, access tokens, API keys and recovery codes. Prefer a demo or sanitised page rather than capturing these at all.

Covering one name does not necessarily make the rest anonymous. A photo, unique reference or nearby description may still identify the person. If you cannot safely share the remaining context, do not send the screenshot.

Cover sensitive webpage details in five steps

1. Prepare the page. Use demonstration data, hide unnecessary panels or remove private details from view where practical. Follow your organisation's sharing rules.
2. Capture. Open the webpage in desktop Chrome and click Fully's toolbar button. The capture opens in the mark-up preview. See the full-page screenshot guide for supported page types and capture limits.
3. Cover. Select Cover and drag over the complete private detail. Leave a small margin so no letters or digits remain visible around the edges. Add a separate cover wherever that information appears again.
4. Inspect. Review the entire preview, not only the marked issue. If a cover is misplaced, use Undo and draw it again. Highlight draws attention; it does not hide information.
5. Copy and paste. Copy the finished PNG to your clipboard. Paste it into your chosen chat, email, ticket or document and inspect the attached image before submitting or sending.

Fully works on the captured webpage. It is not an editor for importing an existing photo, PDF or screenshot file.

Cover is not Highlight, blur or automatic redaction

Fully's Cover is a solid charcoal rectangle, not blur or pixelation. When you copy, the cover is drawn into the finished image and replaces the selected output pixels. The copied PNG has no editable annotation layers that a recipient can remove to reveal those pixels.

Highlight is translucent and intended to show where to look. An arrow, note or partial scribble is also not a substitute for a complete cover. Fully does not scan for names, recognise secrets or decide what is safe to share.

The ICO's image-redaction guidance describes solid colour masking followed by a simple image format without layers or edit history, and warns that blur or pixelation may be reversible. This is general guidance, not an endorsement or compliance guarantee for Fully.

Example: show an order-page problem without customer details

Suppose you need help with a misaligned button on an order page. Keep the button, its surrounding layout and the relevant error message visible. Cover the customer's name, email, address and order reference, including any repeated values in the sidebar or lower table. Then add an arrow to the button and a note describing the problem.

Add the change request as a note on the screenshot before copying:

Do not put the covered details back into your message, annotation or attachment name. For a fuller change request, read how to give clear website feedback with an annotated screenshot.

A final check before you share

• Have you checked the full page, including repeated details outside the main issue?
• Does each cover completely hide the text or image, with no visible edges?
• Could the remaining context still identify someone or reveal confidential work?
• Did your new notes or accompanying message reintroduce anything you covered?
• Are you attaching the finished covered PNG rather than an earlier uncensored copy?
• Is this recipient or service an appropriate destination for everything still visible?

Inspect the actual attachment where possible, rather than trusting a small thumbnail. If the destination cannot show it clearly enough to check, do not submit it until you can verify the image elsewhere.