How to Remove EXIF Data From Any Photo, Anywhere

People ask the same privacy question with different nouns: batch cleanup, Instagram, free local tools, RAW, scans, screenshots, social media. The noun changes; the file problem does not. This page is the canonical guide to remove EXIF data from any photo, anywhere — one workflow that covers those use cases without seven thin duplicates.

MetadataWipe runs in your browser on a JPEG or PNG you choose. The image is processed locally on your device; you download a cleaned copy whose filename ends with -metadatawipe. No account. No remote “send us your photo” step required for the wipe itself.

The universal workflow (any device with a browser)

1. Finish the picture first. Crop, export from RAW, complete the scan, capture the screenshot — then wipe the final delivery file so later editors do not re-apply software tags.
2. Open MetadataWipe on phone or desktop.
3. Choose the JPEG or PNG and read the metadata panel (GPS, camera, dates, author strings when present).
4. Remove metadata so pixels are redrawn to a canvas-style export without copying typical EXIF/IPTC/XMP blocks.
5. Download and verify the cleaned file, then share only that export.

Keep originals in a private folder. Keep outbound files in a second folder. That two-folder habit matters more than memorizing seven article titles.

Batch removal (many photos, one habit)

Photographers and sellers often need dozens of cleans. MetadataWipe’s current tool handles one image per pass — by design for a simple local workspace, not a server-side bulk pipeline. For a batch:

• Line up final JPEGs/PNGs in a folder.
• Wipe → download → next file.
• Spot-check the first, middle, and last export in a viewer.
• Ship the whole cleaned set together so one dirty alternate angle does not undo the rest.

That is still “batch removal” in the practical sense: a repeatable local loop. It is not a promise of multi-file parallel select inside one dialog. If you use Windows Explorer’s multi-select Remove Properties feature for a first pass, you can still finish critical frames in MetadataWipe for a re-encoded copy.

Before posting to Instagram and other social apps

Instagram, Facebook, TikTok, X, and similar apps are distribution channels, not your privacy control plane. They may strip some header fields on their own re-encode — or preserve surprising data in downloadable originals, backups, or cross-posts. Behaviors change without notice.

Reliable sequence:

1. Export the exact crop and color grade you want.
2. Wipe that file locally.
3. Verify GPS and camera fields are gone.
4. Place only the cleaned file into the Instagram (or other) app.

Stories, Reels, carousels, and grid posts are still files entering an app. Clean each frame you care about. Location stickers and “add location” UI features are separate from EXIF — turning those off does not scrub the file header if you never wiped it.

Free local cleanup (no remote hand-off)

Many “free EXIF remover” searches are really a trust question: will this site keep a copy of my photo? MetadataWipe’s model answers that by processing in the browser on your device. You can load the page, choose a file, and complete a wipe without creating an account. For sensitive images, that local loop is the point — you are not shopping for the cheapest remote scrub API.

Free also means honest limits: JPEG and PNG in the current tool; one file at a time; everyday metadata, not a forensic lab certificate. Those limits are preferable to a vague unlimited claim.

RAW photos

RAW (CR2, NEF, ARW, DNG, and friends) is a develop-time format full of sensor and camera metadata. A browser EXIF cleaner is the wrong opener for proprietary RAW.

Correct pipeline:

1. Develop in Lightroom, Capture One, RawTherapee, or your camera maker’s app.
2. Export a delivery JPEG or PNG (sRGB is typical for web/social).
3. Run MetadataWipe on that export.
4. Archive the RAW + catalog privately; distribute only the wiped delivery file.

Export dialogs that say “include metadata” or embed copyright are useful for client hand-off — and exactly what you should disable or strip when the public version must stay unlinkable to your camera body and shoot time.

Scanned documents saved as images

Phone scanner apps and flatbeds often write software names, versions, and timestamps into JPEG/PNG (or into PDF wrappers — PDF is a different tool path). A scan of an ID, tax form, or medical letter can also reveal identity in the pixels.

Metadata steps:

• Save or export the scan as JPEG/PNG if you will share an image.
• Wipe with MetadataWipe before emailing or ticket attachment.
• Redact pixel-level secrets (account numbers, faces) in an editor before the wipe so you do not re-export dirty metadata afterward.

If your workflow produces PDF, use a PDF metadata tool for the PDF; do not assume an image wiper opened the PDF container.

Screenshots

Screenshots feel “harmless” because they lack DSLR lens EXIF. They can still include generator software tags, and they definitely include whatever was on screen — notifications, map pins, customer names, desktop paths.

• Crop aggressively before sharing.
• Wipe the screenshot file if it will be widely distributed or attached to public tickets.
• Remember: screenshotting a photo does not clean the original photo file still in your camera roll.

Social media beyond Instagram

Marketplace listings, Discord drops, Slack screenshots-as-files, Reddit posts, and dating-app prompts all accept image bytes. Some compress harshly (which may drop tags as a side effect); some store originals. The pattern that always works: wipe locally → verify → post. Platform hope is not a control.

For professional accounts scheduling tools, clean the asset before it enters the scheduler’s media library so every downstream network receives the same scrubbed file.

Platform quick links (OS-specific deep dives)

When you need built-in OS details:

• Mac — Preview Inspector, Photos export, Finder Get Info
• Windows — Properties → Details → Remove Properties
• Android — OEM fragmentation and Google Photos limits

Use those when you are auditing what the OS can do alone. Use this page when your question is “I have a file and I need it clean before it goes anywhere.”

What MetadataWipe claims — and what it does not

Creating a new browser-generated JPEG or PNG removes typical embedded metadata because those tags are not copied into the export. That matches everyday privacy needs: selling online, posting socially, emailing a scan, shipping a screenshot to support.

It is not a guarantee for classified workflows, court-grade evidence handling, or adversarial forensics. It does not blur faces or strip text from pixels. After you wipe, you still choose who receives the picture.

One checklist that replaces seven pages

• Final file format is JPEG or PNG.
• Pixels already show only what you intend (crop/redact done).
• MetadataWipe pass complete; -metadatawipe file saved.
• Verification glance shows no GPS/camera/author/date surprises.
• Every image in the set treated the same.
• Originals stay private; outbound folder is the only attach source.

Follow that list for batch galleries, Instagram posts, free local cleanups, RAW derivatives, scans, screenshots, and anything else social — and you do not need a different ritual for each keyword.

Edge cases worth thirty seconds

Live Photos / motion pairs: Clean the still you will actually publish. Companion video or motion files are separate containers with their own metadata.

Edited copies from chat apps: Saving an image back from a chat may already be recompressed — still wipe if you will recirculate it, because recompression is inconsistent.

Design exports from Figma or Canva: PNGs can carry textual metadata chunks and software labels. Same wipe applies.

Client proofs: Keep a credited master with IPTC intact offline; wipe only the public or buyer-facing derivative when anonymity or buyer privacy matters more than on-file bylines.