Practical guide
Remove metadata from multiple images and verify the ZIP
A ZIP containing several images is not proof that every input was cleaned. Use a mixed batch with a deliberate failure to check the removal policy, the per-file result and the downloaded archive before sharing any copy.
18 October 2026 · Check AI Free
Choose a removal policy before you run it
Open the existing metadata remover and use its Clean a batch and download verified copies in a ZIP section. The batch operation accepts at most 20 static JPEG, PNG or WebP inputs, 100 MiB total, and 20 MiB per image. It processes them one at a time and verifies each successful copy before placing it in the archive.
Whole metadata categories to remove is a shared policy, applied only where a category is supported by the actual format. Read the supported-format labels next to each checkbox. EXIF removal includes GPS and orientation, so it can change how a file is displayed. Keep embedded ICC color profiles is selected by default; dropping the profile is a separate choice. Other known PNG color chunks are retained.
APNG, animated WebP and multi-picture JPEG are rejected instead of being flattened. The remover copies retained compressed image segments or chunks; it does not perform Canvas re-encoding, erase words visible in pixels or re-sign Content Credentials.
Create and download the mixed sample
Step 1
Run the deliberate partial-success sample
Click Try synthetic removal batch. With the default removal policy, its JPEG, PNG and WebP inputs each become a verified cleaned copy. The fourth, truncated PNG fails. The result is three cleaned, zero unchanged and one failed.
Step 2
Inspect each result and its policy
Follow file-001 through file-004, not just the filename. For each successful row, inspect the actual removed categories, unsupported/not-applicable selections, ICC result and verified status. An error or cancelled row has no downloadable image entry.
Step 3
Keep names private unless you need them
The default archive uses generated local-ID filenames. If you enable preservation of original names or inclusion of original names in the manifest, review that choice before sharing the archive. The two same-name.img inputs must still remain distinct. Portable output names are de-duplicated rather than overwriting one file with the other.
Step 4
Preview the manifest and download
Expand Preview per-file manifest to review the result. Click Download per-file report for the standalone manifest, then Download ZIP (3 copies) for this default-policy sample. The archive is metadata-copies.zip; the manifest is batch-removal-manifest.json. The ZIP is checked locally before downloading.
What the default archive should contain
Extract the ZIP using your normal local archive tool. Reopen the three actual extracted images in the batch inspector or individual readers. The manifest's outputCount should be 3, while rows accounts for all 4 selected inputs. A valid ZIP alone does not establish that an image has no other identifying information.
Stored entries are used rather than recompressing the JPEG/PNG/WebP files inside the ZIP. The archive size is therefore close to the combined verified image sizes plus the manifest and archive headers.
| Archive entry | Expected role | Check after extraction |
|---|---|---|
| file-001-metadata-copy.jpg | Verified JPEG copy | Read supported EXIF/GPS again; default-selected containers should be absent. |
| file-002-metadata-copy.png | Verified PNG copy | The original Author/Description text is absent; image chunks remain. |
| file-003-metadata-copy.webp | Verified WebP copy | The original XMP author container is absent. |
| batch-removal-manifest.json | Four input rows, three outputs | file-004 has an error and no image output. |
- Reinspect the extracted copies — Check actual format, metadata presence, dimensions and per-file failures.
Unchanged, failed and cancelled are separate results
A valid file with none of the selected categories can produce an unchanged, verified copy. You can also test a no-removal policy by unchecking all removal categories and leaving the ICC profile kept. That does not clean anything; it makes a useful byte-preservation control.
Cancel batch preserves already completed verified copies and marks unprocessed rows cancelled. Downloaded archives contain only completed outputs, plus the manifest showing the rest. A damaged image does not terminate later files. Animation, unsupported format, size limits and failed output verification have visible errors rather than successful placeholder images.
Your disk originals are not edited or deleted. Choose the extracted copy when sharing, and inspect its visible content separately. Cleaning a local copy does not retract a file that was already sent.
Sources and reproducible inputs
- Download the JPEG used in the mixed batch — The same self-authored 4 × 3 fictional EXIF/GPS input as file-001; the built-in exercise deliberately names it same-name.img.
Continue with your file
- Build a per-file inspection report — Keep same-name files and reading failures separate before choosing a policy.
- Check a copy before sharing — Review supported stored fields and the limits of a no-findings result.
- Keep a limited JPEG camera record instead — The GPS-specific rebuilding policy differs from removing the whole EXIF category.