Client delivery
How to batch remove image metadata before client delivery
Use the batch tool to process supported JPEG and PNG files locally, review each result and download completed copies in a ZIP. Pro is required for your own batches and ZIP exports. A ZIP can include partial results, so check the images and batch-results.json before handing the archive to a client. Originals remain unchanged.
| Plan or limit | Allowance | Delivery implication |
|---|---|---|
| Guest | 1 single-image clean per day. | No personal-file batch processing or ZIP export. |
| Free with Google sign-in | 5 single-image cleans per day in total. | No personal-file batch processing or ZIP export. |
| Pro Monthly and Yearly | Unlimited daily image count; up to 10 images per batch. | ZIP export included. |
| Pro Yearly session | Up to 30 images across three batches. | Available within device capacity; not a 30-image single batch. |
| Device queue | 30 files / 200 MB at 768 px or wider; 10 files / 100 MB below 768 px. 25 MB per file. | The lower device or plan limit applies. |
Prepare a delivery ZIP
1. Try the built-in batch first
Open Batch Metadata Remover and choose Try a safe batch. These synthetic one-pixel files demonstrate cleaned, unchanged and partial results without using your own allowance.
2. Prepare the client copies
Keep a master folder of originals. Use JPEG or PNG files within your plan and device limits. HEIC and TIFF are not accepted; WebP is inspection-only.
3. Set one cleaning policy
Choose whether capture details or embedded PNG Content Credentials should be kept. The settings apply across the selected images; changing them rebuilds copies from originals.
4. Review every result
Check which images are complete, unchanged, partial or failed. Remove partial files from the queue if they should not be delivered. A failed image is not included as an image in the ZIP.
5. Download and inspect the archive
Choose Download completed images (ZIP). Open the archive locally, review batch-results.json, and spot-check the actual output files in Metadata Checker. Confirm which files are included before sharing.
The summary is a checklist, not a clean certificate
The ZIP contains completed images and batch-results.json. Each summary entry includes the original filename, detected format, result, counts of removed/preserved/unresolved fields and whether the image is included.
The built-in batch has three files: one cleaned, one unchanged and one partially cleaned. All three can be included. Its needsReview count is 1; that is intentional. A failed or inspection-only file is listed but excluded from the image set.
Check filenames as well as image metadata
The summary and ZIP entry names can reveal original filenames, including client or project names. Review them before sending the archive. If necessary, rename copies before selecting them or prepare a separate delivery folder from the processed images.
The summary is created locally and packaged into the ZIP. Sharing the archive shares that summary too; browser-local processing does not make the document invisible to its recipient.
Do not mistake device capacity for paid entitlement
A wide-screen queue can hold 30 images, but Pro processing uses groups of at most 10. Yearly can process a session across three groups; Monthly is limited to 10 images per processing session. On a narrow screen, the queue capacity is 10 even for Yearly.
If you encounter a quota or size message, reduce the selection and check the current plan. Free allowances reset at 00:00 UTC. Unlimited daily Pro image count does not remove file-size, device-memory or per-batch limits.
Verify the actual output before delivery
Supported encoded image data and dimensions are checked during processing. The downloadable experiment below deliberately leaves oversized compressed text unresolved while preserving image data. It explains why a successful download may still require review.
There is no real client material in these examples. They do not establish compatibility with every generator export, all image sizes or all mobile browsers.
What this tool cannot promise
- Partial copies can be included in a ZIP and may still contain private metadata.
- Failed files are excluded; do not assume the selected count equals the delivered count.
- The ZIP summary and entry names can disclose original filenames.
Common questions
Will one failed file prevent every download?
No. Completed copies remain available. Review the summary for excluded files and the partial results that still need attention.
Can I download the demo ZIP without Pro?
The tool’s built-in safe batch is free to try. Processing and exporting your own batches requires Pro.
Primary sources: AI Metadata Remover: batch results and device limits