Strip metadata from a whole batch at once.

Stripping metadata from one photo is a settings dialog. Stripping it from the eighty photos of a listing, a product line or a delivered gallery is where the one at a time methods collapse: nobody right clicks eighty files, and the person who starts does not finish. Batch cleaning is the difference between a privacy policy you have and a privacy policy you follow. Here is the one pass version, and the checks that make it trustworthy.

Why metadata is a batch problem

Metadata risk rarely arrives one file at a time. The situations that matter ship in sets:

• A photographer delivering a gallery. Every frame carries the camera serial and capture times; the client will repost freely. Sixty to six hundred files.
• A real estate listing. Twenty five photos of a home, each tagged with the coordinates of that home, headed for the open internet. The one category where GPS is not an abstract worry.
• A marketplace seller. Eight photos per item, taken in the seller’s living room, posted with contact with strangers as the explicit goal.
• A business publishing product or team photos. Metadata leaks staff device details and office locations one upload at a time.

One file cleaned out of a set is a set that leaks. This is why manual dialogs fail in practice: the method that costs a minute per photo gets skipped exactly on the busy days when the batch is biggest. The fix is making the whole folder cost what one file used to.

The one pass workflow

The Kepla metadata remover is built around the batch case:

1. Select everything at once. Drag the whole set in, JPG, PNG, WebP or HEIC, mixed formats welcome.
2. The strip runs locally. Each file is rewritten without its metadata block: EXIF, GPS, timestamps, serial numbers, editing history. The work happens in your browser on your own machine, so a two hundred photo batch does not spend an afternoon uploading, and the photos never touch a server.
3. Download the cleaned set and deliver or publish those copies. Your originals keep their metadata, which you want: capture times and settings are valuable in your own archive. The clean copies are for the world.

The pixels in every cleaned file are identical to the source, not similar, identical, because the remover never decodes and re-encodes the image, it only drops the metadata block. Quality is simply not part of the trade.

Habit worth forming: make clean for export the last step of any set that leaves your hands, the way exporting itself is a step. It adds seconds, not minutes, at batch speed.

Verifying, and choosing what to keep

Trust, then verify once. Pull two or three files from the cleaned batch and drop them into the EXIF viewer. You should see the technical block gone: no GPS, no serial, no capture time. Do this the first time you use any stripping method, and again whenever a tool updates; thirty seconds of checking is what turns probably clean into clean.

Then decide the one real judgment call: whether to add anything back. Metadata is not uniformly the enemy. Working photographers often want the IPTC ownership fields, creator name, copyright line, contact, present in published files, both for attribution and because stripped credit is a real dispute in licensing. The pragmatic pattern is two tiers: fully clean files for clients and casual publishing, and a credited tier for portfolio and press use where the ownership fields are written on purpose and everything else is still gone.

Either way, the decision is now yours and deliberate, made once for the batch, instead of eighty accidental decisions made by whatever app happened to touch each file last. That is the entire point of putting the strip into the workflow: privacy stops depending on memory.

FAQ