Clean Image Metadata Before Client Delivery — Browser Tool vs ExifTool

You've got a folder of selects, the client approved the shots, and now you're about to send them out. Before that email leaves your outbox, think about what's riding along inside each JPEG: your camera body, your lens, the exact GPS coordinates of the shoot, and often your editing software and a timestamp. For a wedding photographer, that's a home address in a file that gets forwarded around. For a real estate shooter, it's a client's property pin. Cleaning that metadata before delivery isn't paranoia — it's basic client care.

The question is how you do it. Two paths dominate: a browser-based tool like EXIF Remover, or a command-line approach like ExifTool. Both remove metadata. They differ in where your files go, how much you can script, and how much control you get over individual fields.

Quick comparison

That table is the honest version. The browser tool is faster to start and keeps files off any server. ExifTool gives you surgical control and scriptability, but you have to install it and learn its flags.

When the browser tool wins

If you're a freelancer delivering a handful of images per client, the browser route is almost always the right call. You drag files in, you see the metadata laid out in a grouped table — GPS coordinates, camera model, lens, timestamp, ISO, software — and you click Strip EXIF. Then you download the cleaned image.

A few things worth knowing about how this actually works:

• The tool reads metadata with exifr running locally in your browser. Nothing is sent anywhere.
• Stripping happens by drawing the image to a Canvas and exporting a fresh blob, so the output is a new file. Your original on disk is untouched.
• Because it's a re-encode, JPEG output is recompressed at roughly quality 0.92. That's visually fine for client delivery, but don't expect a bit-identical file.
• HEIC works only if your browser can decode it. If it can't, you'll need to convert first.

The workflow, step by step

1. Drop your photo onto the page — JPG, PNG, WebP, or HEIC — or click to browse. Nothing uploads.
2. Review the EXIF fields in the grouped table. This is your last chance to spot a GPS tag you didn't know was there.
3. Click Strip EXIF and download the clean image.

If you're delivering to a client who cares about privacy (or you just don't want your home studio coordinates floating around), that's the whole job. Ten photos per run on the free tier; Pro bumps it to 50+ per run and adds a privacy risk report with a score, CSV/JSON metadata export, and removes Toolkite branding. It's a one-time $12.99 if you want it — the free tier is genuinely usable without it.

One caveat: the tool strips all metadata. There's no GPS-only mode and no "keep the lens info" option. If you need that granularity, see the next section.

When to use alternatives

ExifTool is the right tool when you need precision. Say you want to keep the copyright tag but kill the GPS block, or you're processing 400 images from a corporate shoot and want it scripted into your delivery pipeline. A typical command looks like:

exiftool -all= -overwrite_original *.jpg

That wipes everything. For selective removal you'd use flags like -gps:all= to drop only GPS, or -XMP:all= for a specific block. The trade-off is you need to know which tags matter and test on copies first — it's easy to nuke something you wanted to keep.

Other alternatives worth mentioning honestly:

• OS-level export options. Some photo apps strip metadata on export, but the behavior varies and isn't always obvious. Check before you trust it.
• Desktop batch utilities. They work, but you're installing software and often clicking through more UI than the browser tool requires.
• Online upload-based strippers. These exist, but you're handing your client's photos to someone else's server. For client work, that's usually a non-starter.

If you're also watermarking before delivery, that's a separate step — Watermark handles batch watermarking in the browser too, so you can strip metadata and brand images without either file leaving your machine.

Edge cases that trip people up

A few things I've run into that are worth flagging:

• Screenshots and PNGs. These often carry less metadata than camera JPEGs, but they can still hold software tags. Strip them anyway if they're going to a client.
• Re-encoding artifacts. If you're delivering a JPEG that's already been through several edits, another re-encode at 0.92 is usually invisible, but for print-critical work, keep a master copy.
• HEIC from iPhones. These are the ones most likely to carry GPS. If your browser can't decode HEIC, convert to JPEG first, then strip.
• Metadata isn't only EXIF. XMP and IPTC blocks can carry author names and edit history. The browser tool removes metadata by re-encoding, which handles the common channels — but if you need forensic-grade certainty across every possible channel, that's an ExifTool job, not a browser one.

A practical delivery checklist

Before you hit send on client files:

1. Strip metadata on every image in the batch.
2. Spot-check one file by re-opening it in the tool to confirm the GPS and camera fields are gone.
3. Watermark if your contract requires it.
4. Keep your originals — the stripped versions are new files, so your archive stays intact.

That's it. No uploads, no accounts, no server round-trip. If you want to see what's actually inside your photos before you decide, the tool shows you the full metadata table first — which is often the moment people realize how much their camera was recording.

FAQ

Does stripping metadata with a browser tool change the image quality?

Slightly, yes. The browser tool removes metadata by drawing the image to a Canvas and exporting a new blob, which re-encodes JPEG at roughly quality 0.92. For client delivery and social media that's visually indistinguishable, but it's not a bit-identical copy of the original. Always keep your master files.

Can I remove only the GPS data and keep the camera info?

Not with the browser tool — it strips all metadata in one pass, so there's no GPS-only mode. If you need selective removal, ExifTool supports granular flags like -gps:all= that target specific tag groups. The trade-off is a steeper learning curve and the need to test on copies first.

Is it safe to strip metadata from client photos in a browser?

Yes, because the processing happens locally on your device. The tool reads metadata with exifr in the browser and never uploads your files to a server. Your originals on disk stay unchanged, and the cleaned version downloads as a new file.

How many photos can I clean at once before delivery?

The free tier handles up to 10 photos per run. If you're delivering larger batches, the optional Pro license raises that to 50+ per run and adds a privacy risk report with a score, CSV/JSON metadata export, and removal of Toolkite branding. It's a one-time purchase, not a subscription.

What about HEIC files from an iPhone?

HEIC is supported only if your browser can decode it. If it can't, convert the HEIC to JPEG first and then strip the metadata. iPhone photos are among the most likely to carry GPS coordinates, so this step matters for client work.

Does the browser tool wipe every possible metadata channel?

No, and it doesn't claim to. Re-encoding through Canvas removes the common EXIF, GPS, and camera channels, but it isn't forensic-grade wiping of every possible metadata container. If you need certainty across XMP, IPTC, and obscure channels, use ExifTool and verify the output.