Why DropMeta verifies after stripping metadata

At a glance

  • A strip that does not re-check can still leak GPS or XMP.
  • DropMeta re-parses after strip; if verification fails, download is blocked.
  • For PDFs, if Catalog XMP cannot be removed cleanly, DropMeta errors instead of shipping a partial clean.

One-pass removers can claim success while leftover GPS or XMP still rides along. Without a re-check, “trust the button” is not enough for private files.

DropMeta re-parses after strip. On images it looks for location residue; on PDFs it fail-closes if Catalog XMP cannot be removed cleanly. If verification fails, download is blocked.

In the UI you see an error and the cleaned file is not offered for download. Re-parse runs in the same browser tab — verification does not upload your file.

FAQ and limits

What happens if verification fails?

You see an error and the cleaned file is not offered for download.

Does verification upload my file?

No. Re-parse runs in the same browser tab.

Is verification perfect for every format?

It targets the leftovers DropMeta knows how to detect (e.g. location on images; Catalog XMP on PDFs). It is not a claim of zero bytes of every obscure chunk in every container.