ImgShrink
ImgShrink

Batch Metadata Remover

Clean metadata from many photos in one local browser queue, then download individual cleaned files or a ZIP.

Multiple image queueMetadata cleanup without recompressionClean copy exportZIP download

Batch metadata remover

OriginalOriginal size: -
Choose images to clean metadata.
ResultResult size: -
Result
Before cleanup

Metadata scan

After cleanup
After cleanup

Need to clean many photos?Use Batch Metadata Remover.

Only need one image?Use Remove Metadata from Image

How it works

  1. 1Choose or drop multiple images.
  2. 2Keep original format for JPG, PNG or WebP metadata cleanup without recompression when possible.
  3. 3Process the queue locally and download each cleaned file or a ZIP.

Privacy and limits

  • Files stay in your browser and are not uploaded.
  • Original-format JPG, PNG and WebP cleanup avoids recompressing pixels when supported.
  • AVIF and cross-format output may create re-encoded copies and can change quality, transparency, animation or color profile behavior.

Batch metadata removal behavior

This page applies the metadata cleanup workflow to many images in one queue.

JPG, PNG and WebP can keep the original format without recompressing pixels when direct metadata removal is available; unsupported paths create re-exported cleaned copies.

Common use cases

  • Cleaning a photo set before sharing
  • Removing GPS data from many phone photos
  • Preparing metadata-light image folders for publishing

Format notes

  • Original-format cleanup avoids recompression for supported JPG, PNG and WebP files.
  • AVIF and cross-format output may be re-encoded by canvas.
  • This is practical privacy cleanup, not forensic metadata erasure.

Original test sample

  • Clean several phone photos with original-format output, then inspect one result in Image Metadata Viewer.
  • Use ZIP download after all queue rows finish successfully.

Frequently asked questions

Are my images uploaded?

No. ImgShrink processes selected images in your browser and does not upload them to a server.

Do batch tools upload files or save history?

No. The queue runs locally in your browser, and ImgShrink does not create an account, database record or saved image history.

Why is an output format unavailable or different?

The browser controls image decoding and export support. Some browsers may not export AVIF or may flatten unsupported transparency.

Source and compatibility notes

Batch limits are based on the current local browser workflow and are set to reduce memory failures on typical devices.

Last checked: 2026-09-07

Notes
  • Files are processed locally in the browser queue.
  • Large batches depend on available browser memory.
  • Downloaded ZIP files are created on the device.