How to Remove EXIF and Document Metadata Before Sharing

DevOkk’s Metadata Remover is designed to process the file in the browser. No account. The matching habit is inspect → strip → inspect the output → send the output, not the original.

Inspect, then strip

What File Metadata Reveals About You is the look step. This page is the cut step.

Why both:

• You may not need to strip. A screenshot with no GPS and a generic software tag might be fine for an internal ticket.
• You may need to strip more than you thought. GPS plus an embedded thumbnail plus an author.
• You need a before/after. If the remover reports “GPS” and the viewer still shows a latitude, you stop and do not send.

Skipping inspect is how people run a cleaner, attach the original from the Downloads folder, and wonder why the recipient still has coordinates.

Keep the original on purpose. Name the output something like hero-clean.jpg so muscle memory cannot pick the wrong file in the mail compose window.

What typically comes off

DevOkk’s remover exposes classes you can keep or drop:

• EXIF - the usual camera block: device, settings, orientation, often the GPS pointer
• GPS - coordinates and related location fields (worth enabling even if you also strip EXIF)
• IPTC / XMP - captions, keywords, rights, and a lot of “professional” photo junk that can include names
• Timestamps - taken-at / created / modified style fields
• Author - document and image creator fields
• Comments - free-text tags people forget they added

Preserve quality should stay on unless you also wanted a smaller, lossy image. Metadata removal is not image compression. If the attachment is still too big after a clean strip, use image compressor or PDF Compressor on the cleaned file, then inspect once more. Compressors can add a producer tag or, rarely, keep a chunk you thought was gone.

What will not come off here:

• Text and faces in the raster
• An extra page in a PDF
• A filename (interview-notes-acme.docx)
• Watermarks you can see
• Encryption. A password-protected PDF is a different problem; if the tool cannot read the file, stop. Do not upload it to a shadier site.

How to strip in the browser

1. Inspect the original in Metadata Viewer. Note GPS, author, camera, dates.
2. Open Metadata Remover. Leave the privacy-related boxes on unless you have a reason to keep a caption or a timestamp (photojournalism workflows sometimes keep IPTC; a casual share usually should not).
3. Add the file. Run the strip. Download the cleaned copy to a different name.
4. Open the cleaned file in the viewer. Confirm the fields you cared about are gone. Confirm the image still looks right at 100% and that a PDF still has the right page count.
5. Attach the cleaned file. Leave the original in a folder that is not your desktop dump.

If the remover cannot parse a format, that is a stop sign. Raw camera files, some HEIC variants, and odd PDFs fail closed. Convert to a mundane JPEG or PDF with a tool you already trust, then inspect and strip that - knowing conversion itself can drop or add tags.

Do this on the machine that already has the file. A cloud EXIF cleaner is an upload of the sensitive version. The algorithm does not require a server.

Verify, because tools and exporters lie

Phone share sheets sometimes “remove location” and leave camera model. Desktop “Save for web” sometimes drops EXIF and writes a new software tag. Print-to-PDF sometimes keeps the Word author.

Verification is one more local inspect, not a feeling. If GPS is gone and author is gone and you still do not want the camera model public, strip again with EXIF on, or export a new JPEG from an editor that rewrites the file.

Embedded images in PDFs are the footgun. If the packet is a PDF of phone photos, consider extracting or recompressing pages, or flattening through a print-to-PDF path you then inspect. A single pass over the wrapper is not always a pass over every embedded JPEG.

Thumbnails: if the viewer still shows an old preview after a crop-and-strip, the embed survived. Recreate the file from the cropped pixels rather than trusting a tag delete.

What stripping does not fix

Content. A badge in the photo, an email in the screenshot, a national ID in the scan. Crop, redact with a real redaction tool that removes the pixels (not a black box that can be lifted), or do not send.

The story the pixels tell. Nighttime EXIF gone, but the window in the background still shows a recognizable skyline.

Recipients who already have the original. You cannot unsend metadata. This process is for the next copy.

Policy. “Processed in the browser” reduces extra copies. It does not replace a rule that certain files may not leave a managed device.

If you need a repeatable habit rather than a one-off strip, use the privacy checklist and run it even when you are in a hurry. The hurry is when GPS files get sent.

Inspect, strip, inspect the download

Inspect with Metadata Viewer, strip with Metadata Remover, inspect the download, then attach only that download.

If you do not yet know what you are looking for, read What File Metadata Reveals About You first. The remover is fast. The mistake is being fast on the wrong file.