A practical metadata removal workflow before you share files.

Step 1: separate originals from public copies

Keep original files in a private folder. Originals can contain useful records such as capture time, editing history, device details, location history, licensing fields, or internal workflow notes. Those details may matter for creative archives, legal records, business documentation, or personal memories. A public copy has a different purpose: it should show the image or video without carrying more hidden context than necessary.

Step 2: rename files before sharing

Filenames are easy to overlook. A cleaned file can still reveal private information if the filename includes a client name, project code, home address, internal campaign, legal matter, or private date. Use clear names that help the recipient understand the file without exposing unnecessary context. This is especially important for marketplace photos, client previews, school files, support screenshots, and public media kits.

Step 3: clean the final export

Clean the version you actually plan to share. If you clean an early draft and then export a new version from an editor, converter, compressor, captioning app, or phone gallery, the new export may add metadata again. The safest point to clean is after the last edit and before the first public upload.

Step 4: verify the output

Open cleaned images and play cleaned videos before sharing. Confirm that orientation, transparency, colors, audio, timing, and playback still work. For important work, test the file in the same place it will be used: a marketplace upload form, client portal, website CMS, social scheduler, or video platform. Verification matters because a privacy workflow is only useful when the output remains usable.

A reproducible before-and-after check

Use a disposable copy named original.jpg and keep the downloaded original-clean.jpg beside it. With ExifTool installed, run these read-only commands locally. They do not upload or modify the files.

exiftool -a -G1 -s original.jpg
exiftool -a -G1 -s original-clean.jpg

Compare the groups, not just the number of lines. FileSize and FileModifyDate can describe the new file on your disk; ImageWidth and ImageHeight describe the image. Their presence is not evidence that camera GPS survived. Look for the specific field you meant to remove, such as GPSLatitude, Artist or UserComment, and its group. If it remains, do not treat the output as verified.

Accept or stop?

• Accept for your intended use only when the targeted fields are absent and the image displays correctly.
• Stop if orientation changes, a color shift appears, audio disappears, or your required metadata field remains.
• A message saying no common metadata was found means the cleaner did not find its supported fields. It is not a complete inventory of every possible field.

For an independent starting point, ExifTool reads metadata from many formats. The result still needs interpretation; no single empty search proves anonymity.

Read the report as an observation, not a certificate

After cleaning a supported file, open Before / after report next to its result. For a PNG containing one text comment, the tEXt row should move from 1 to 0. That number counts containers, not words or personal details. One EXIF container can contain many fields, so an APP1 count is not a count of GPS coordinates.

Compared media blocks unchanged means the inspector compared selected encoded-media blocks from the input and output. It does not mean it decoded the file, checked every checksum, or examined visible details. A JPEG can retain identical compressed image data while losing an orientation field; that is why you still open the downloaded copy.

Example handoff: three product photographs

1. Place the private originals in an Originals folder and select the final edited exports.
2. Clean the three files, then read each result rather than assuming one passing result covers the batch.
3. Open every downloaded photograph and check product colors, orientation and visible labels.
4. Save each JSON report alongside the public copy if you want a local record of this operation. The report does not contain the original field values.
5. Send only the cleaned copies. Download all creates a ZIP of completed items; a failed item is excluded.

If the batch is incomplete

Count the completed items before sending the ZIP. A selection may exceed your five-file guest limit or ten-file account limit, and a file can fail processing. Do not fill a missing position with the original just to finish the delivery. Resolve that item separately or explain that it was withheld. Batch completion and privacy verification are separate decisions.