How to Remove EXIF Metadata from Photos Before Sharing

Every photo you take with a modern phone carries an EXIF block — Exchangeable Image File Format metadata — embedded invisibly in the image file. It records the camera model and lens, exposure settings, ISO and focal length, the date and time to the second, the orientation, the editing software that last touched the file, and, on most phones, the GPS coordinates where the photo was taken, accurate to a few metres.

None of this displays when you view the picture. It is not hidden in a sophisticated way, either — it is plainly readable by any tool that looks for it, including the "properties" panel of most operating systems and countless free websites. The mismatch between how invisible metadata feels and how accessible it is accounts for most real-world metadata leaks: people share photos believing they are sharing only the image, while the file quietly discloses when it was taken, on what device, and where.

The classic incidents follow a pattern: a photo of a new purchase shared to a marketplace, with home coordinates in the file; a photo of a child, with the school's location attached; a "working from home" photo, with the home address embedded. The image content is deliberate; the metadata is incidental — and it is the incidental data that does the damage. Use the File Metadata Viewer to inspect a file before you share it.

The reliable way to strip metadata from an image is also the simplest to explain: decode the image, draw it onto a fresh canvas, and encode a new file from that canvas. The new file contains only what was drawn — the pixels — because the canvas has no knowledge of the original file's EXIF block. Everything that was embedded rather than visible is left behind by construction.

This is why metadata removal is trustworthy in a way that "delete the GPS tag" operations are not always: rather than hunting through metadata structures and removing the sensitive fields one by one — a process that depends on knowing every field that exists — the redraw produces a file that structurally cannot contain the old metadata. The Metadata Remover on this site does exactly this, entirely in your browser.

The trade-off is re-encoding: the new image is re-compressed, typically at high quality, which is visually indistinguishable for photos but worth knowing about. It also flattens transparency, since the common output is JPEG. For documents that need a lossless or transparent result, choose PNG output where the tool offers it.

Metadata is not purely a liability. For photographers, embedded copyright and authorship information is a soft form of attribution that survives when the image is copied. For personal archives, timestamps and locations are exactly what make a photo library searchable years later — "all photos from the 2019 trip" is a metadata query. GPS on your own archive is a feature; GPS on a photo you publish is a disclosure.

The mature position is therefore conditional: keep metadata in your private originals, and strip it at the sharing boundary. That boundary is any moment the file leaves your control — a marketplace listing, a social platform, a forum, an email to a stranger. Once published, a file cannot be un-published, and the metadata went with it.

A practical habit that makes this effortless: run every image through a strip-metadata step as part of your normal "prepare for sharing" routine — alongside resizing and compressing — so the privacy protection is a side effect of a workflow you were doing anyway, rather than a separate decision requiring vigilance.

The companion skill is inspection. Before sharing a file whose origin you are unsure of, look at what it actually carries: a metadata viewer that reports name, size, type, and last-modified for files, and the EXIF fields for images, tells you in seconds whether there is anything to remove. This is also the honest way to check a removal tool — view the metadata, strip it, view the result again, and confirm the fields are actually gone rather than trusting the button.

Documents carry parallel concerns. PDFs embed a title, author, subject, keywords, creation and modification dates, and the producing application; a document exported from a work account may carry your name and organisation in fields you never typed. Office documents can carry comments, tracked changes, and author history. The discipline is the same as for images: inspect before sharing, and prefer a tool that shows you what is embedded over an assumption that a file is clean. The PDF Metadata Editor lets you view and clear those fields.

Take a photo straight from a phone and inspect it with the File Metadata Viewer. The EXIF block reports the camera model and lens, the exposure (1/120 second at f/1.8, ISO 64), the focal length, the exact timestamp to the second, the orientation, the editing software, and — on most phones — GPS coordinates accurate to a few metres. None of this is visible in the image; all of it travels with every copy of the file until someone strips it.

The disclosure is concrete. The GPS pinpoints the photo to a specific address — which, for a photo taken at home, is a home address. The timestamp combined with the location reveals a pattern of life: when you are there, when you are not. The camera model identifies your device. A single photo shared to a marketplace listing with intact EXIF hands a stranger your home address, your schedule, and your equipment — information you would never write into the listing itself, but which the file carries silently.

The remedy is the redraw: decode the image, draw it onto a fresh canvas, encode a new file. The new file contains only the pixels — the EXIF block is structurally absent, not selectively edited, which is why the removal is trustworthy. Run the same viewer on the result and confirm the fields are gone. The framework is simple but worth internalising: inspect before you share, strip at the sharing boundary, and verify the stripped result — because the metadata you cannot see is the metadata that does the damage.

One nuance worth knowing: stripping EXIF does not anonymise the image content itself. A photo that shows your face, your street, your house number, or a document on your desk discloses those things by being visible — no metadata operation changes that. Metadata removal eliminates the invisible channel; what the picture plainly shows is a judgment you make with your eyes.

Both channels deserve a thought before the file leaves your hands, and the second one is the one no tool can decide for you. The dependable workflow is: inspect, strip, resize and compress for the destination, then verify the stripped result one more time before you hit send.

The same redraw technique scales to batch processing: a folder of images can be run through the Metadata Remover one at a time, each producing a clean copy alongside its original. This is the workflow to adopt before publishing a set of photos — a marketplace listing, a social album, a press kit — because the risk is not any single image but the aggregate disclosure of a consistent location across many. Verifying the batch is the same as verifying one image: pick a sample, view the metadata before and after, and confirm the fields are gone. The trust in the tool comes from that check, not from the button label, and performing it once on a representative file is usually enough to confirm the workflow is working as intended across the whole set.

Beyond images, the same vigilance applies to documents you share. A PDF exported from a work account may carry your name, your employer, and the software version in its metadata fields — information you never typed but that travels with every copy. Office documents can retain tracked changes, comments, and author history long after you think you have cleaned them. The discipline is identical to image metadata: inspect before sharing, strip what you do not need to disclose, and verify the stripped result. Treating metadata removal as a standard step in your sharing workflow, not a special measure for sensitive files, is the habit that prevents the accidental disclosures that cause real harm, because the files you consider routine are the ones you share most freely.