Metastrip

Guide

How do I batch-strip image metadata in the browser?

Portfolios, client delivery packs, event albums—when the count climbs, stripping one file at a time is misery. Change the goal: multi-select, strip once, ZIP download, then spot-check a few properties. Clearer than parking originals on an upload site. Doing it the night before delivery beats scattered catch-up.

Metastrip handles the batch in the browser. Concepts and format boundaries: remove GPS and EXIF. Why strip before social: strip metadata before social.

1. One-by-one isn’t enough for deliveries

Dozens or hundreds of JPG/PNG/WebP in a handoff folder make “open → strip → download” both slow and leaky. Miss one geotagged frame and the whole pack feels unfinished.

Batch fits: pre-delivery cleanup, public drive staging, phone-import tidy nights. Missing one location-tagged image is often more painful than re-running the set.

Agencies and solo freelancers ship the same failure mode: a beautiful select, late night, ZIP uploaded, one outdoor portrait still carrying GPS. Batch strip the night before. Sleep better.

2. Multi-select → strip all → ZIP

  1. Open Metastrip.
  2. Multi-select JPG / JPEG / PNG / WebP.
  3. Strip all.
  4. Download singles or a ZIP; clear the list when finished.

Per product design: local processing, not uploaded to our servers. Keep originals and stripped exports in separate folders so you do not re-upload uncleaned files. Support: [email protected].

Label the ZIP with the project name and date. Future-you will thank present-you when a client asks “which pack was cleaned?”

3. Short format table (same as MS-1)

Do not assume every field on every format is gone. WebP especially: EXIF/XMP cleared does not mean the container holds zero ancillary data—that matches the live product boundary.

4. Not compression; no recompress pitch on JPEG path

Batch strip reduces common location/device/time-style baggage. It is not “make the file smaller.”

Need smaller files? Use a compressor. Need less metadata exposure? Use Metastrip. On the supported JPEG path, no pixel re-encode means you are peeling information—not baking a softer re-export. If you need both steps, sequence them deliberately. Do not mistake “file got smaller” for “metadata is gone.”

5. Large sets: split batches, spot-check; not forensic

How many files per run follows device and browser capacity. No invented cap. If the tab struggles, split.

After download, open a few files from the ZIP and check properties. This tool lowers common exposure. It is not forensic-grade. For public portraits or address-adjacent shots, spot-checks cost less than a public recall.

Spot-check pattern: first file, last file, and one from the middle. Plus any shot you know was taken at a sensitive place.

When memory pressure shows up—slow tab, frozen progress—pause and split. Pushing through a struggling browser session is how partial ZIPs happen. Two clean half-batches beat one ambiguous mega-run.

6. Pipeline: HL-2 → here → Stampdrop; social angle MS-2

Ogmake stays on the marketing-card track: free Open Graph image. Do not dump OG cards into the same ZIP as client proofs.

For mixed folders (JPEG + PNG + WebP), strip in one pass if the tool accepts the set, then spot-check each type. Do not assume PNG behaved like JPEG. Read the boundaries above once, then trust your spot-checks more than memory.

If a delivery includes HEIC still sitting beside JPEGs, convert the HEIC first. Stripping applies to JPG/PNG/WebP here—not to “whatever is in the folder.”

FAQ

How many files?
Device/browser limits. No invented number.

Upload?
No.

WebP caveat?
EXIF/XMP can go; other container data may remain (live product).

Strip then post immediately?
Prefer a quick spot-check; for public shares read MS-2. Unzip, open two files, then upload the pack.

JPEG recompressed?
No—per product, JPEG strip without recompressing pixels.

Related reading

Disclaimer

Not forensic-grade. Verify exported files before sharing. Support: [email protected].