Metadata check troubleshooting

Photo Metadata Not Found: What Does It Mean?

“Not found” means this checker did not read a populated field matching that privacy category in the selected file. It does not prove that every metadata carrier is empty, explain what happened to the original, or certify that the picture is safe to share.

By Qingxin Studio, the developer of HushPic · Updated

No matching field is different from a failed check

A completed browser check reports four categories: location, dates and times, device details, and creator or notes. Not found means no matching populated field was read within the supported scope. The image can still contain other metadata, including information needed to display it correctly.

A file that cannot be parsed instead shows an error and no category result. Do not interpret an error, an unsupported file, or the 20 MB size limit as evidence that metadata was removed. Try a supported file without changing your original.

Why an original and an export can disagree

You may have selected an exported image, screenshot, messaging-app copy, or social-media download rather than the camera original. These are separate files and may carry different fields. Some capture or export paths do not record a particular category in the first place.

A missing field alone cannot distinguish information that was never recorded from information removed earlier. The browser checker reads the current file; it does not reconstruct its edit history, recover deleted GPS data, or look up missing details online.

A library location is not always embedded GPS

Google Photos says a photo location can come from the camera, a location you add, or an estimate based on landmarks and other photos. A place shown in a library therefore does not, on its own, establish that the downloaded file contains readable GPS coordinates.

Check the actual file you intend to send instead of relying only on a map pin or library information panel. A street sign, shipping label, distinctive building, or house number can reveal a place through the pixels even when readable location metadata is not found.

Check the parser’s scope

This website uses exifr to check supported EXIF, XMP, and IPTC fields in JPEG, PNG, and TIFF. The browser check covers supported EXIF/GPS fields in HEIC and AVIF, not their XMP/IPTC fields. It is a category check rather than a complete tag inventory, forensic report, or image-content detector.

A file extension does not guarantee every variant can be read. Unusual layouts, unsupported carriers, or damaged files may limit a check. Do not rename a file or silently convert it just to obtain a reassuring result; the new file would no longer be the original you meant to inspect.

Compare the files without uploading them

First choose the original in the browser checker and read the four category results. Next select the final exported file using Check another photo. Each selection replaces the previous result; neither file is edited. Repeat immediately before sharing if you generate another export.

If the copies differ, only conclude that this check read different categories. Do not infer who removed a field or treat the result as a complete audit. Clear result removes the displayed categories; the site does not save a photo or metadata history between visits.

Review the visible information too

Inspect names, addresses, account numbers, faces, codes, reflections, and background documents at a readable size. This website does not look for those details or create a cleaned image. A metadata-free-looking result can still expose everything printed on a parcel label.

For supported cleanup, HushPic runs the photo flow on your device, applies suggested masks and clears detected private metadata on a separate copy. Inspect the verified result, use Review / Adjust for missed or unwanted masks, and generate again after any change. Share the current checked copy, not the unchanged original. Verification is limited to the supported scope and does not replace your visual review.

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.

Privacy guides

Continue the privacy check.

View all guides