How to Verify Metadata Removal
Learn how to check if metadata was removed from a downloaded image or PDF. Verify EXIF GPS, PNG text, embedded C2PA and PDF properties.
The most reliable file to check is the one you’re about to share. Reopen the downloaded copy and compare it with the original. Confirm that the values you wanted to remove are gone from the locations you checked, and that the image or document still looks and behaves as expected.
Inspect, clean and reopen the downloaded copy
Inspect the original. In AiMetaOff’s Inspect File tool, choose your original file. Note which categories contain the values you want to remove, such as EXIF GPS coordinates, an XMP author or a PNG prompt. Keep the original for comparison.
Choose the categories to clean. Select the file and the relevant metadata categories, then use Clean selected. AiMetaOff works on supported categories or containers. If you choose EXIF to remove GPS, other EXIF fields can go with it. Check which information you need to keep before cleaning.
Save the processed copy. Use Download new copy when available. AiMetaOff creates a separate file in your browser and leaves the original intact. If you download a ZIP, extract the member you actually intend to share.
Inspect the saved file as a new input. In Inspect File, use Choose files to select the copy from your Downloads folder or the extracted ZIP. The original row can still be in the workspace. Compare the two inputs by filename and check the same categories on each.
Try it with the synthetic camera sample
The synthetic camera JPEG contains fictitious GPS coordinates, an embedded thumbnail and an orientation tag. Inspect it, clean the EXIF category and reopen the copy. Look for the GPS directory and thumbnail to disappear while the orientation tag remains. This gives you a quick way to recognize an intentionally retained field.
Verify EXIF and GPS removal
Compare the EXIF GPS group on both copies. Check latitude and longitude, their hemisphere references, and any altitude or other GPS values that were present. If the photo carried location in XMP or a caption, look for the original coordinates or place name there too. The same location can appear in more than one category.
On supported images, AiMetaOff can retain a minimal EXIF orientation record so the picture still rotates correctly in a viewer. Color information such as an ICC profile can also remain. Judge the result by the specific GPS or identifying fields you meant to remove. For general image cleanup, use the image metadata remover.
Verify XMP, IPTC and PNG text
XMP. Compare the original author, description, rights or location values with the copy. XMP can carry IPTC photo properties, so a caption may remain in XMP after a legacy IPTC block was removed.
IPTC in JPEG. AiMetaOff identifies supported Photoshop/IPTC APP13 resources and can remove the whole block. If you need to confirm an individual credit or caption, check the output in ExifTool and look for it in both IPTC and XMP.
PNG text. Check the Text and XMP categories on the downloaded PNG. PNG stores text in
tEXt,zTXtandiTXtchunks. A prompt, workflow or caption can be stored in text or XMP, and a PNG can also contain EXIF in aneXIfchunk. Text cleanup can remove ordinary captions along with generation records. The PNG prompt and workflow cleanup tool covers supported Text and XMP records.
Verify embedded C2PA Content Credentials
If the original contained a recognized embedded C2PA container, check the C2PA category again after using the embedded C2PA remover. A Not found result after a successful inspection means the viewer did not find that record in the structures it checked. If the file or credential could not be inspected, the check is inconclusive.
When Inspect File can read a manifest, it reports available checks for the claim signature, assertion hashes and binding to the file. A signature or binding failure is different from an absent container. Signer trust remains unverified in AiMetaOff. The tool does not fetch remote manifests, trust lists or revocation data.
Credentials can also exist in a separate file or an external provenance store, where supported tools may locate them through a soft binding. A local file without detected embedded credentials can still have external provenance, a watermark or an AI label attached to a platform post. The file inspection alone cannot establish how the image was made.
Check whether the image pixels changed
Open both copies in the same viewer. Compare their dimensions, orientation, color and transparency. For a more exact single-image check, compare decoded pixels at the same dimensions. With ImageMagick, run magick compare -metric AE -fuzz 0% "original.png" "cleaned.png" null:. A result of zero means that this comparison found no differing pixels. Check orientation and color rendering separately if the viewer applies metadata that changes how it displays the image.
AiMetaOff edits supported metadata structures without re-encoding the image. Existing tests compare compressed image data and independently decoded pixels for representative files. File headers and metadata can still change, so two images can have identical decoded pixels and different whole-file hashes. Preservation checks depend on the format and file variant.
Supported image inputs include single-image JPEG, static PNG and WebP, and a narrow single-image AVIF subset. HEIC has limited support. An animated or otherwise unsupported variant can fail inspection or cleanup even when its extension looks familiar.
Verify PDF metadata removal
Inspect the original and saved PDF for the document’s Info dictionary and document-level XMP. An author, title or keyword can appear in both. Check the report for XMP presence even if the viewer cannot display values inside a compressed packet. Reopen the exported PDF in your usual reader and compare the page count and layout.
The PDF metadata remover handles eligible unsigned, unencrypted PDFs without compressed object streams. Signed PDFs can be inspected when otherwise supported, and cleaning is disabled. Info/XMP cleanup leaves page text, annotations, forms, attachments and metadata inside embedded objects outside its removal scope. If an earlier revision or an embedded object could carry the value, a clean properties panel is insufficient to verify its absence.
Double-check locally with ExifTool
Run these read-only commands on your actual files, substituting their filenames or paths.
Original —
exiftool -a -G1 -s "original.jpg"Downloaded copy —
exiftool -a -G1 -s "cleaned.jpg"
-a shows duplicate tags, -G1 labels their locations and -s prints tag names. Compare the values and groups you noted earlier. For a PDF, use the same commands with your PDF paths and compare the document properties and XMP groups. File size, filesystem dates and calculated fields can appear in the report alongside embedded tags. If a sensitive value is missing from the report, describe the result in terms of the reader and groups you checked. Use a C2PA-capable verifier for signature and binding checks.
Troubleshoot an unexpected result
The same value still appears. Confirm you opened the saved copy, then compare the group labels. A value may have been duplicated in a different group or stored in a structure the cleaner does not handle.
The tool reports nothing to remove, a limited result or an error. No selected data means the selected records were not found for removal. A limited result leaves some checks incomplete. For example, HEIC cleanup is limited to an eligible single-image subset and lacks full in-browser decode verification. Unsupported files and failed checks do not establish that metadata is absent. See help with missing downloads and limited results.
The value disappeared and later returned. Check the newest export and, if applicable, the exact copy a service lets you download. An editor or converter can copy metadata from a source or write new values during export. A platform can display information from its own records, independently of the uploaded file.
FAQ
Why is EXIF still present after I removed GPS?
AiMetaOff may leave a minimal orientation tag. Check for the GPS fields themselves and look for the original location in other groups such as XMP.
Can I verify metadata removal without the original?
You can inspect the current copy for specific records. To establish that a value was removed, compare it with an original file or a report taken before cleanup. Without that baseline, you can only describe what the current inspection found.
Can a smaller file prove that metadata was removed?
File size cannot tell you which records changed. Inspect the saved file for the target records and use a pixel comparison if you also need to check image fidelity.
Related articles
Sources
Reviewed 14 November 2026.