How I clean private information from screenshots before sharing them

Screenshots are easy to share too quickly. The problem is that a screenshot often contains more information than the one thing I wanted to show.

It may include:

• names;
• emails;
• tokens;
• URLs;
• browser tabs;
• file paths;
• terminal commands;
• customer data;
• internal project names.

The Screenshot Privacy Cleaner helps cover or pixelate sensitive parts before the image leaves my machine.

The simple idea

Before sharing a screenshot, I ask:

What can someone learn from everything visible in this image?

Not only the center of the image. Everything.

The dangerous part is often in the edges: browser tabs, sidebars, terminal prompts, bookmarks, account names, or notification previews.

Step 1: look at the whole screenshot

Open the screenshot and scan it slowly.

Check:

• top bar;
• browser tabs;
• address bar;
• sidebars;
• usernames;
• emails;
• IDs;
• logs;
• tokens;
• timestamps;
• background windows.

Do this before editing. If the screenshot contains too much, it may be better to crop it first.

Step 2: crop when possible

The safest information is the information not included at all.

If you only need to show one small area, crop the image so the rest is removed.

Cropping is better than hiding because there is nothing left to recover from the removed area.

After cropping, inspect the image again. Cropping can still leave sensitive details inside the remaining area.

Step 3: choose blackout for secrets

For secrets, tokens, passwords, API keys, session IDs, and private URLs, I prefer a solid blackout.

Pixelation can sometimes leave patterns or text lengths visible. A black rectangle is boring, but boring is good for secrets.

Examples of things I black out:

• access tokens;
• API keys;
• passwords;
• private email addresses;
• customer names;
• invoice numbers;
• internal hostnames if sensitive.

Step 4: use pixelation for low-risk context

Pixelation is useful when I want to show that something exists but hide the exact text.

For example:

• a list of user names;
• a sidebar with project names;
• a paragraph that is not the focus;
• part of a UI that gives context.

For highly sensitive data, use blackout instead.

Step 5: cover enough area

Do not cover only the exact letters. Cover a little extra around the sensitive area.

Why?

• text can have shadows or antialiasing;
• the shape of remaining letters can leak clues;
• nearby labels may reveal what was hidden;
• small uncovered edges can still be readable.

When hiding secrets, I would rather cover too much than too little.

Step 6: check URLs carefully

URLs can contain sensitive information in query parameters.

Example:

https://example.com/reset?token=abc123

Even if the page content is harmless, the address bar may expose a token.

Before sharing browser screenshots, I check the address bar and tabs carefully.

Step 7: check terminal screenshots carefully

Terminal screenshots often reveal:

• usernames;
• hostnames;
• current directories;
• environment variables;
• IP addresses;
• command history;
• secrets printed by mistake.

If I only need to share command output, I may copy the text into a clean example instead of sharing the raw terminal screenshot.

Step 8: download and inspect the cleaned image

After editing in Screenshot Privacy Cleaner, download the cleaned image.

Open the downloaded file and inspect it again at normal size and zoomed in.

Check:

• did every sensitive area stay covered?
• did the export include the edits?
• did I accidentally download the original instead?
• is the image still clear enough for the intended point?

Step 9: remember that redaction should be permanent

A real redaction should change the pixels in the exported image. It should not be an editable overlay that someone can remove later.

For public sharing, export a flattened image such as PNG or JPEG from the tool. Do not share an editable design file with hidden layers unless you know exactly what is inside it.

My screenshot checklist

Before sharing a screenshot, I check:

1. Can I crop instead of hiding?
2. Are browser tabs safe?
3. Is the address bar safe?
4. Are names, emails, and IDs safe?
5. Are tokens or secrets visible?
6. Are sidebars and background windows safe?
7. Should I use blackout instead of pixelation?
8. Did I inspect the exported image, not only the editor preview?

Screenshots are useful because they show context. The risk is that they show too much context. Clean the image until it shows only what the recipient needs.