Review what the delivered image contains
PNG Transparency and Redaction: Invisible Is Not Erased
A transparent PNG pixel can still store color information. Making an area invisible by changing transparency is not the same as replacing its sensitive image data. For a redacted delivery, use an opaque replacement rendered into a separate image, then inspect that export; a normal preview or metadata-category result cannot audit hidden pixel colors.
By Qingxin Studio, the developer of HushPic · Updated
Identify transparency, not just a pale-looking patch
Work on a duplicate in a local image editor with transparency controls. A checkerboard, an eraser, a layer mask, and a solid painted replacement can produce very different outputs. Establish which operation you used. W3C’s PNG specification stores alpha separately from color samples; an invisible preview is therefore not evidence that the underlying color samples were cleared.
Replace the private area instead of only hiding it
For material the recipient must not recover from the image pixels, replace the entire region with fully opaque pixels in the delivery image. Cover the edges and any repeated occurrence. Do not use reduced layer opacity, a transparency-only mask, or an eraser as your removal method. Preserve the editable original privately, rather than sending it alongside the export.
Inspect the exported file in a separate session
Reopen the saved file, not the still-open project. View it over light and dark backgrounds to spot unwanted transparency and edge gaps. This visual check is useful but does not prove that all hidden RGB samples, extra frames, metadata, or embedded previews are absent. If the image does not need transparency, a deliberately opaque export can simplify review; conversion by itself is not privacy cleanup.
Keep alpha inspection separate from the browser check
This website reports supported metadata categories only. It does not inspect alpha, reveal hidden pixels, apply redaction, or certify a new copy. HushPic can prepare supported photo copies on-device with bounded post-write checks; do not treat that as a universal audit of every PNG encoding. Review the actual output and any suggested masks. If the required pixel replacement cannot be confirmed, do not share that file.
Sources
This guide is published by Qingxin Studio, the developer of HushPic. Product claims describe our supported workflow, not independent certification. Our review checklists are practical first-party guidance; linked platform sources support only the mechanisms they describe. Automatic checks may miss details. Read our content and corrections policy.