Packaging is not privacy processing
Does Zipping Photos Remove Metadata?
No. Ordinary ZIP packaging bundles files; it is not a photo-metadata removal step. Prepare individual images first, build an archive from an explicit selection, then extract a local check copy and inspect its contents. Compression, password protection, and information inside an image answer different questions.
By Qingxin Studio, the developer of HushPic · Updated
Select contents before creating the archive
Create a dedicated folder containing only images intended for delivery. Review the count and names; exclude originals, companion JSON, editing projects, and earlier drafts unless explicitly needed. Do not zip your camera or export directory wholesale.
Open each chosen image at readable size and confirm the sharing version. An archive can carry a prepared copy or an accidental original equally faithfully. A neutral outer archive name does not rename or sanitize inner files.
Treat ZIP as a container, not a cleaner
Microsoft documents ZIP as a way to bundle files for transfer, with separate extraction operations. On Windows, select the intended files and use the available Compress or Send to → Compressed folder command for your version. Confirm the archive’s actual contents.
JPEGs are already compressed, so little size reduction is not a privacy warning or success indicator. Neither a smaller archive nor a changed archive timestamp tells you which private fields remain. Inspect images rather than judging the container’s size.
Check encryption as a separate requirement
Do not assume a normal file-manager ZIP is password-protected. Microsoft separately documents limits on encrypted-archive operations in Windows. If access protection is required, use a documented delivery method and verify recipient requirements; this guide does not recommend a cipher or certify an archive tool.
Even a protected archive reveals its contents to an authorized recipient after extraction. They can still read included images, filenames, and embedded fields. Access protection does not replace minimizing those contents before delivery.
Extract a local review copy before attaching
Extract into a fresh private destination without overwriting originals. Compare the count, inspect names and companion files, and reopen extracted images. If something is wrong, rebuild from the corrected selection and recheck that new archive, not yesterday’s extracted folder.
Our browser checker accepts supported individual images, not ZIPs; it reads local metadata categories without pixel inspection, cleanup, or verified output. HushPic prepares separate supported images on-device with bounded post-write checks; review suggestions and regenerate after changes. Neither tool certifies encryption or an entire package. Attach only the archive you reviewed.
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.