How to Remove Metadata from JPG in 5 Steps (Without Uploading)

You just exported a batch of JPGs and you're about to hand them off — to a client, a marketplace, a forum, or a friend. Before you do, check what's riding along inside the file. Camera model, lens, ISO, timestamp, and often GPS coordinates are tucked into the JPG's EXIF block. None of that is visible in the photo itself, and most people never look. Here's a five-step way to strip it in your browser, plus an honest look at the CLI alternative.

Step 1 — Drop your JPG into the EXIF Remover

Open EXIF Remover and drag your JPG onto the page, or click to browse. The tool accepts JPG, PNG, WebP, and HEIC (HEIC only when your browser can decode it). Nothing is uploaded to a server — the file is read locally on your machine. If you're on a shared or work computer and you're not sure about the browser's permissions, that's fine; the file never leaves the tab.

The free tier handles up to 10 photos per run. If you're processing a bigger shoot, Pro bumps that to 50+ per run and adds a privacy risk report plus CSV/JSON metadata export.

Step 2 — Read the grouped EXIF table

Once the file loads, you'll see a grouped table of what's actually inside the JPG. Typical fields:

GPS — latitude, longitude, sometimes altitude. This is the one that matters most for privacy.
Camera — make, model, lens, firmware.
Exposure — ISO, shutter speed, aperture, focal length.
Timestamp — original capture date and time, plus any edit timestamps.
Software — the app that last wrote the file (Lightroom, Photoshop, a phone camera app, etc.).

Skim it before you strip. If you see a GPS block with real coordinates, that's the moment to decide whether the photo should go out with the file at all. The tool reads this with exifr in the browser, so the table is built from the file on your disk — not from a copy on someone else's server.

Step 3 — Hit “Strip EXIF”

The button is labeled Strip EXIF. One click. Under the hood the tool draws the image to a Canvas and exports a fresh blob at JPEG quality around 0.92. That re-encoding is what removes the metadata — the new file simply doesn't carry the old EXIF block forward.

Two honest caveats:

Re-encoding is not lossless. A JPG that's been through Canvas at 0.92 will look essentially identical to the eye, but it is not bit-identical to the original. If you need pixel-perfect archival copies, keep the original file somewhere safe and treat the stripped version as the shareable one.
It's not forensic-grade wiping. The tool strips the standard EXIF/GPS channels by re-encoding. It doesn't claim to scrub every conceivable metadata channel that a specialized forensic tool might inspect. For everyday privacy — social posts, client previews, marketplace listings — that's more than enough.

Step 4 — Download the cleaned JPG

Click the download link and save the new file. The original on your disk is unchanged — the tool doesn't overwrite anything. You now have two files: the original with metadata, and the clean one without. Rename the clean one before you send it, or drop it into a separate folder so you don't mix them up.

If you're doing this often, a simple habit helps: keep a _clean suffix on the stripped versions. It's a small thing, but it saves you from accidentally emailing the original.

Step 5 — Batch the rest (if you have more than one)

For a single photo, steps 1–4 take about 20 seconds. For a folder of 30, you'll want to think about the free-vs-Pro line. The free tier caps at 10 photos per run; Pro handles 50+ and adds a privacy risk report with a score, plus CSV/JSON export of the metadata it found. That export is genuinely useful if you're auditing a batch and want a record of which files carried GPS before you stripped them.

If you're only stripping a handful, the free run is fine. If you're a freelancer shipping client galleries weekly, the one-time Pro license at $12.99 pays for itself the first time you avoid a location leak.

The alternative: ExifTool on the command line

If you'd rather not touch a browser, ExifTool is the classic answer. On macOS or Linux:

exiftool -all= -overwrite_original photo.jpg

On Windows (PowerShell, with ExifTool in your PATH):

exiftool -all= -overwrite_original .\photo.jpg

Trade-offs worth knowing:

ExifTool is more thorough and scriptable across thousands of files. It can strip channels the Canvas approach doesn't touch.
It's also easier to get wrong. -overwrite_original destroys the original. If you forget it, you get a photo.jpg_original backup — which is safer, but clutters the folder.
No install required for the browser route. If you're on a locked-down work laptop or a borrowed machine, opening a tab is faster than installing a Perl-based tool.

Neither approach is wrong. Pick based on whether you want a one-off fix or a repeatable pipeline.

A few edge cases that trip people up

Screenshots don't usually carry GPS. If you screenshot a photo and share the screenshot, the metadata is already gone — but so is the resolution. Don't use screenshots as a metadata-removal strategy for client work.
Some apps re-add metadata on export. If you strip a JPG and then run it through an editor that writes EXIF back, you're back to square one. Strip last, right before you send.
HEIC on older browsers. The tool lists HEIC support, but only when the browser can decode it. If your HEIC file won't load, convert to JPG first, then strip.
PNG and WebP work too. The same flow applies; the Canvas export just produces a different format depending on what you feed it.

If you want the broader picture on what's typically hiding in a photo and why it matters, the privacy page covers how Toolkite handles files (short version: it doesn't — they stay on your device). For a quick audit workflow, this checklist on photo metadata privacy risks is worth a skim before your next client delivery.

Ready to try it? Strip EXIF from your JPG here — free in the browser, with optional Pro upgrades if you need batch volume and metadata exports.

FAQ

Does stripping EXIF actually remove GPS coordinates from a JPG?

Yes. The EXIF Remover re-encodes the image through a Canvas and exports a new blob, which drops the original EXIF block — including GPS latitude and longitude — from the output file. The original on your disk is untouched, so you keep a copy with metadata if you need it for records.

Is the stripped JPG identical to the original in quality?

Not bit-identical. The re-encode uses JPEG quality around 0.92, which is visually very close but technically a recompression. If you need archival-grade copies, keep the original and treat the stripped file as the shareable version.

How many JPGs can I process at once for free?

The free tier handles up to 10 photos per run. Pro raises that to 50+ per run and adds a privacy risk report with a score, plus CSV/JSON export of the metadata that was found. Pro is a one-time $12.99 license, not a subscription.

Can I remove only GPS but keep the camera info?

No — the tool strips all metadata in one pass; there's no selective field removal mode. If you need granular control over which fields survive, ExifTool on the command line is the better fit, since it lets you target specific tags.

Are my files uploaded to a server when I use the tool?

No. Everything runs in your browser. The file is read locally with exifr and re-encoded with Canvas; nothing is sent to Toolkite or any third party. That's the main reason to use a browser-based tool over a random upload site.

What formats besides JPG does the EXIF Remover support?

JPG, PNG, WebP, and HEIC. HEIC only works if your browser can decode it — some older browsers can't, in which case convert to JPG first and then strip. The same one-click flow applies to all supported formats.