Crop, export, and privacy
Does Cropping a Photo Remove Its Metadata?
Do not treat cropping as metadata removal. A crop changes the visible frame; the exported file may still contain supported location, date, device, or creator fields. Check the saved crop, not just its preview, and keep the original separate from the copy you intend to share.
By Qingxin Studio, the developer of HushPic · Updated
A smaller frame is not a metadata report
Cropping can exclude a parcel label at the edge of a photo or an unrelated conversation below a message. It does not tell you which hidden fields the editor writes into the export. A preview showing only the useful scene answers a visual question, not a metadata question.
Treat the original, the editable project, and the exported crop as different sharing choices. Before doing anything else, identify which one the recipient will receive. A file with a new aspect ratio or a smaller size is not, by itself, evidence that private metadata was removed.
Reversible edits deserve a separate sharing decision
Apple Photos allows saved edits to be reverted to the original. Apple also describes an All Photos Data share option that includes the original with editing information and metadata. This is different from deliberately sending only a prepared image copy.
If the purpose is to exclude a private detail, avoid sending an editable project or the original alongside the crop. Read the share options for the actual destination. Do not conclude that a cropped view means the recipient can never obtain earlier content through the sharing method you choose.
Export first, then check that exact file
Save a separate cropped image using your editor's documented export flow. Open the saved file independently and check that its corners, borders, and intended subject match the crop. Keep the original rather than overwriting it merely to prepare a public post.
Choose that saved export in the browser metadata checker. A completed check reports the presence of supported privacy categories; an error provides no result. You can check the original next with Check another photo, but differences only describe the files read by this check, not the editor's full behavior.
Check what remains inside the frame
A crop may remove the obvious label yet leave its reflection, a second label, or a readable address on another object. Inspect the remaining image at a readable size. Check background papers, windows, screen reflections, partial names, and visible codes—not just the cropped boundary.
Keep context that the audience needs. For an item listing, do not crop out damage in a way that misrepresents its condition. For a support screenshot, preserve the relevant error and sequence. If private detail overlaps necessary context, consider a separate masked copy rather than an increasingly tight crop.
Use cleanup only when the file can be checked
The web checker does not crop, remove fields, inspect pixels, or produce a new image. Not found means a matching populated field was not read within its scope. It does not certify the export or explain whether a field was never present, removed, or unreadable.
For supported files, HushPic processes a separate copy on your device and checks the written metadata within its supported scope. Review the visible result and use Review / Adjust for missed or unwanted masks. Regenerate after an adjustment; a previous result is not the current shareable version.
Verify the attachment rather than the thumbnail
Attach the prepared copy, then inspect the destination's preview for the intended frame and complete masks. Do not attach the original, an editable version, or a second uncropped image by mistake. Similar thumbnails can hide important differences between versions.
If you export again or use another editor after checking, inspect the new file again before sending. Cropping, metadata cleanup, and selecting the correct attachment are separate steps. When you cannot confidently separate a private detail from the useful scene, choose another photo or omit the image.
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.