How to share a support screenshot without exposing secrets
A good support screenshot shows the error and enough context to understand it. It does not need to include your whole desktop, account menu or credentials.
Keep what helps diagnose the problem
Usually the error wording, relevant control and non-sensitive settings help more than a full screen. Reproduce the issue with fictional data or a test account when practical. Tell support what you clicked and what you expected in the ticket text.
Look beyond the main error
- Address bars: URLs may contain email addresses, document IDs, invitation links or temporary access tokens.
- Developer tools and terminals: review API keys, authorization headers, cookies, passwords and connection strings.
- Account menus and file paths: usernames, workspace names and folder names can identify people or clients.
- Background windows, browser tabs and notifications: check messages and unrelated records.
- QR codes, recovery codes and private keys: cover the full value or block, not just a few characters.
A useful before-and-after example
In a fictional “Connection failed” screenshot, keep the error message and selected connection type. Cover the credential field, private host details and account email. If support needs a diagnostic ID, provide it through their verified ticket system rather than posting it publicly.
Review before you attach
- Use opaque masks across complete secrets, including wrapped lines.
- Manually review unlabeled values; automatic text checks can miss them.
- Open the exported PNG and check the corners, title bar and every visible terminal line.
- Verify the recipient and attach the exported copy, not the original.
If a credential has already been exposed, covering a later screenshot does not invalidate it. Revoke or rotate it with the service provider and follow the incident process that applies. GitHub’s sensitive-data guidance likewise prioritizes revoking or rotating leaked secrets.
See also removing repeated email addresses and why blur is not enough.
Open your screenshot in the free checker, cover secrets manually as needed, and inspect the exported copy before attaching it to a ticket.
Open the free screenshot checker
Examples use fictional data. Text checks can miss information; no result certifies an image as safe to share. Privacy and limitations
Reviewed with the local build on 17 September 2026. Advertising and affiliate links are disabled. Public-site measurement is disabled.