QQudo ツール

Redact Sensitive Information from Screenshots

Hide faces, accounts, emails, phone numbers, QR codes, API keys and other sensitive information before sharing a screenshot. Your image is processed locally and never uploaded.

Local ProcessingNo UploadsManual ReviewNo Watermark

Paste a screenshot, drop an image, or click to choose a file

Your image is read and processed only in this browser. It is never uploaded to Qudo or a third-party server.

Max 30MB. Supports PNG, JPG, WebP.

What is Screenshot Privacy Redaction?

Screenshots often contain sensitive information that should not be shared publicly. This tool helps you identify and permanently hide faces, email addresses, phone numbers, IP addresses, URLs, QR codes, API keys and other sensitive data before sharing your screenshots online.

What Information Should Be Hidden?

Before sharing any screenshot, check for: faces and profile photos, email addresses, phone numbers, physical addresses, account names and usernames, API keys and tokens, passwords and secrets, credit card numbers, QR codes containing personal data, GPS coordinates in image metadata, and any personally identifiable information.

Why Do Screenshots Leak Information?

Screenshots capture everything visible on screen, including notification previews, browser autofill suggestions, and background content you may not notice. Additionally, photos taken with cameras contain EXIF metadata including GPS location, device model, and timestamp.

Cover vs Mosaic vs Blur

Opaque cover completely replaces the area with a solid color, making recovery impossible. Mosaic pixelates the area which may still be partially readable. Blur softens the area but may preserve enough visual information for skilled attackers. For high-sensitivity content like passwords and API keys, always use opaque cover.

Why API Keys Need Opaque Cover

API keys and tokens are equivalent to passwords. Even partially visible keys can be completed by attackers using pattern matching. Blur and mosaic preserve visual patterns that can be analyzed. Only a fully opaque cover makes key recovery impossible.

How OCR Helps Find Sensitive Text

The built-in OCR (Optical Character Recognition) scans your screenshot locally to find text, then applies pattern matching to identify emails, phone numbers, IP addresses, URLs, and API key patterns. All processing happens in your browser using Tesseract.js.

How to Hide Faces in Screenshots

Draw rectangles over faces using the rectangle tool, or use the optional face detection feature to automatically locate faces. The tool adds a safety margin around detected faces to ensure complete coverage.

How to Handle QR Codes

QR codes can contain URLs, contact information, payment data, or authentication tokens. Use the QR detection feature to find and decode QR codes, then add redaction to hide them completely. The decoded content is never sent to any server.

Why Clear Image Metadata?

Photos contain EXIF metadata including GPS coordinates, camera model, capture time, and sometimes thumbnails. When you export from this tool, a new image is created from scratch without any of the original metadata.

Local Processing vs Server Upload

This tool processes everything in your browser. Your images are never uploaded to any server. This means your sensitive data stays on your device and cannot be intercepted during transmission or stored on remote servers.

Use Cases

Common scenarios include: sharing error screenshots without exposing file paths, posting terminal output without revealing credentials, sharing chat screenshots while hiding personal information, creating tutorial screenshots without exposing real data, and preparing screenshots for AI analysis while protecting privacy.

Limitations

OCR may miss text or produce false positives. Pattern matching cannot find all sensitive information. Face detection does not work for all angles and lighting conditions. This tool cannot guarantee finding every sensitive item. Always review the output manually before sharing.

Data & Privacy

All processing happens locally in your browser. Images are never uploaded. OCR language packs and detection models are cached locally. No image content, filenames, OCR results, or detection data is sent to any server or analytics system.

Automatic detection, OCR and rule matching may produce omissions or false positives. This tool cannot guarantee that every sensitive item in a screenshot will be found. Review the result carefully before downloading or sharing. Use a fully opaque cover for passwords, keys, identity documents and financial information.

Frequently Asked Questions

Are my images uploaded to a server?
No. All processing happens locally in your browser. Your images never leave your device.
Can I paste screenshots directly?
Yes. Use Ctrl+V (or Cmd+V on Mac) to paste screenshots from your clipboard.
Are mosaic and blur secure?
For general visual hiding, yes. But for passwords, API keys, and financial data, use opaque cover instead. Blur and mosaic may leave recoverable patterns.
What is the best method for passwords and API keys?
Always use opaque cover (solid black or custom color). This completely replaces the pixels and makes recovery impossible.
Can the tool automatically detect faces?
Face detection is available as an optional feature. It uses local browser-based detection and does not identify who a person is.
Does the tool identify people?
No. Face detection only locates face positions. It does not perform any identity recognition or create biometric data.
Does OCR send text to a server?
No. OCR runs entirely in your browser using Tesseract.js. Recognized text never leaves your device.
Can QR codes be detected?
Yes. The tool can detect and decode QR codes. The decoded content is hidden by default and never sent anywhere.
Can the tool find all sensitive information?
No tool can guarantee finding everything. OCR and pattern matching may miss some items or produce false positives. Always review manually.
Does the exported image contain EXIF or GPS?
No. The exported image is created from scratch without any of the original metadata.
Can redacted content be recovered?
No. Opaque cover permanently replaces pixels. The original content cannot be recovered from the exported image.
Does it work on mobile browsers?
Yes. The tool is responsive and works on mobile browsers. Touch gestures are supported for drawing and panning.
Why does OCR need to download language packs?
OCR requires language-specific data files to recognize text. These are downloaded once and cached locally for future use.
Does it support batch processing?
The current version processes one image at a time. For multiple images, process them sequentially.