Guides
Practical notes for hiding what a picture shows
These are not separate tools. They explain how to use the same local editor without leaking the details around the thing you meant to share.
Which guide should you read?
If you have not redacted an image before, start with how to redact a photo or image. If the text is a secret, read whether blur is enough. If you are about to post a photo, read the face and personal-data checklist. If the file should never be uploaded in order to hide it, read the local-versus-upload note. Then use the editor.
How to redact a photo or image
Paste a photo or screenshot locally, draw over what should stay private, then blur, pixelate, or black box and export a redacted PNG.
Is blur enough to hide text?
When a blur still leaves a password or ID readable, and when a black box is the cover you should draw instead.
Local editor or an upload tool?
When a browser canvas beats a cloud editor, what local redaction cannot do, and how to tell the difference without a fake ranking.
Redact faces before posting
A practical pass for faces, name tags, plates, and background screens before a photo goes on the internet.
Share a redacted image safely
Download versus paste, which file is the original, and the checks that stop you sending the unredacted shot.
Redact screenshots before a bug report
A practical pass for support tickets and bug reports: what to cover in DevTools, chat, and URLs, and what to leave so the bug is still reproducible.
Blur, pixelate, or black box
When a soft blur is enough, when a mosaic is the right signal, and when only a solid black box is honest enough for secrets.
What people forget to hide
A checklist for the details that survive a quick crop: sidebars, tokens in URLs, faces on a call, badges, and notification banners.
The editor itself is on the homepage. Paste a screenshot or drop a photo. Nothing is uploaded for editing.