Home/Answers/Screenshot privacy
SHOT LAB / Screenshot privacy

Screenshot privacy Failed? Troubleshooting

When Screenshot privacy fails, troubleshoot in order: file/format, permission/lock, output settings, another tool.

Updated 2026-10-31About 3 minLocal test
Quick answer

When Screenshot privacy fails, troubleshoot in order: file/format, permission/lock, output settings, another tool. Crop or mask accounts/notifications/paths/tokens; compression is not redaction.

Why it matters

Start with the most common and cheapest causes to narrow it down fast.

Mask beyond the edges to avoid leftovers.

Step by step

  1. Crop sidebars, empty space and unrelated windows first.
  2. Prefer PNG/WebP for text; use JPEG around 85% for photo-like screenshots.
  3. Export at the actual display width instead of uploading a 4K screenshot.
  4. Zoom in after compressing to check text/UI edges.
  5. Keep the original; use the compressed copy only for publishing.

Common mistakes

  • Compressing code screenshots to 50% JPEG and blurring text.
  • Uploading a 4K screenshot displayed only 800px wide.
  • Recompressing and dirtying the edges.
  • Converting transparent UI to JPEG, turning the background white/black.

Checklist

  • Sensitive areas cropped/masked.
  • Text screenshot not saved as low-quality JPEG.
  • Dimensions match the actual display width.
  • Zoomed in on the target page.
  • Original kept.

Key facts

  • Mask beyond the edges to avoid leftovers.
  • Screenshots may carry software/time metadata.

FAQ

How do I troubleshoot a failed Screenshot privacy task?

When Screenshot privacy fails, troubleshoot in order: file/format, permission/lock, output settings, another tool. Crop or mask accounts/notifications/paths/tokens; compression is not redaction.

How long does it take?

Usually 1-3 minutes; for intermittent issues, run 30 seconds and retest elsewhere.

Is data uploaded?

Runs locally and does not upload video/audio; extensions may still read the page.

Source: FTC privacy