Photo metadata when the person you're worried about already knows you
Almost every metadata guide on this site is written against a stranger: a scraper, a random viewer, a marketplace browser, someone who learns whatever they learn from the file itself. A targeted situation inverts that. When the person you are worried about is an ex-partner, a former housemate, a family member, or someone who has been following you for months, they already have your face, your history, your car, your habits, and the names of people close to you. They do not need EXIF to work out who you are. They need one current fact — where you are now — and that is a much narrower, much sharper problem than the one most privacy advice is aimed at.
Ready to clean a photo? MetadataWipe processes JPEG and PNG files locally — no account and no server transfer.
Open MetadataWipe toolThis page is about one technical layer of a situation that is much bigger than file formats. It is not a safety plan and it is not legal advice. If you are in immediate danger, contact emergency services. If you are dealing with an ongoing pattern of stalking, harassment, or abuse, a local advocate, legal aid service, or hotline will know things this page cannot — including which steps are safe to take first, and which ones a person watching your accounts might notice. What follows assumes you are already getting that kind of help, or are about to, and want to understand what stripping metadata does and does not do for you in the meantime.
What changes when the viewer already knows you
Identification is free, so only novelty has value. The usual argument for stripping EXIF is that it turns an anonymous photo into an identified one: a stranger who had nothing now has a camera serial, a name in an author field, and a set of coordinates. None of that is a gain for someone who already knows exactly who you are. What is a gain for them is anything current — a new address, a new workplace, a friend's house you are staying at, a route you take on a Tuesday. This is why the most important files are not your old holiday photos but the ones taken since things changed. If you have limited time and attention, spend it there.
They can read the picture, not just the header. An intimate adversary has reference material that no stranger has. They recognise your kettle, your bedding, the tree outside the old flat, the colour of a neighbour's door, the make of a car that is usually parked two spaces along. Stripping metadata does nothing to any of that, because it does not alter the image. A cleaned photo of a room they have stood in is still a photo of a room they have stood in.
They may not be reading files at all. A person who has ever had your passwords, set up your phone, shared a family plan, or stayed on a shared album has a far better channel than metadata: the library itself, including the photos you never published. Cleaning an outbound file changes nothing about that channel. The mechanics of how libraries and their metadata propagate across accounts, backups, and handed-down devices are covered separately in how metadata survives cloud sync and device transfers, and in a targeted situation that access question comes before anything you do to individual files.
Your circle leaks on your behalf. Photos of you taken by friends, relatives, and colleagues carry their metadata, not yours, and are posted on their schedule, from their accounts, with their tagging habits. A picture of you at a birthday dinner, geotagged by someone who has never heard of EXIF, is outside your control entirely. Asking people for a specific behaviour — do not tag me, do not post anything from today until next week, do not post pictures of the front of the house — works far better than asking them to be careful.
Deleting can cost you something. This is the part that has no equivalent in the rest of this site's advice. In a targeted situation, some of the files around you are not privacy risks but potential evidence: the messages and images the other person sends, the screenshots of what they posted, the pictures of damage or of an incident. The instinct to scrub everything can quietly destroy the record you may need. Cleaning your own outbound photo and deleting received material are completely different acts, and only one of them is safe to do on reflex.
A sequence that reflects the real risk order
- Deal with access before files. Shared albums, family sharing, devices still signed in, a laptop left behind, backup destinations, recovery email and phone numbers, password reuse, an old tablet that still syncs. A cleaned JPEG is worth very little if someone can open the source library.
- Split your photos into two piles. Outbound — anything you are about to send, post, or hand to a third party, which should be cleaned. Received or incident-related — anything from or about the other person, which you preserve untouched and store where they cannot reach it. Never let the second pile become the first by accident. The custodian logic for received files is worked through in should you strip metadata from photos other people send you.
- Clean at the moment of sharing, not in bulk. Stripping a whole library in one evening is both more visible and less useful than cleaning each file as it goes out. The outbound copy is the one that matters, and it is the one you can check.
- Read the frame before you read the header. Before posting, look at the picture the way the other person would: what is visible through the window, on the wall, on the uniform, on the packaging, in the reflection. No tool does this step for you.
- Break the real-time signal. Coordinates are one way to answer "where is she right now"; posting habits are another. Delaying a post, or not posting from a place while you are still in it, removes the timing advantage even when a platform has already stripped the file. It does not make the location secret afterwards — it just stops the photo from being a live location update.
- Brief the people around you. Specific requests, to specific people, about specific behaviour. Include anyone who runs a group, a team page, a club newsletter, or a school gallery that might publish a photo with you in it.
- Keep a plain record. What you changed, when, and what you preserved. If this ends up in front of an advocate, a lawyer, or the police, a boring timeline is far more useful than a memory.
Where the browser tool fits is deliberately small. MetadataWipe takes one JPEG or PNG at a time from your own device, runs a fast heuristic check of the front of the file for metadata markers, redraws the image to build a cleaned copy, and lets you download it with -metadatawipe appended to the filename. It all happens locally in your browser — no account, no server transfer. That covers step three and nothing else. It has no view of your accounts, cannot see what someone else posted, does not process HEIC or video, and cannot judge what is visible in a photograph. Its built-in check is a quick screen rather than a forensic audit, and in a situation with real stakes the honest framing is that stripping metadata is one small control in a much larger plan.
Common mistakes and misconceptions
"I stripped the EXIF, so the photo is safe to post." Safe against one channel. The picture content, the caption, the account, the time of posting, and whoever comments with your name are all untouched by any metadata tool.
"It is an old photo, it does not matter." Old photos are usually the lower priority, which is not the same as no priority. A place from two years ago can still be a place someone goes to look for you, and old images of a friend's home may put that friend on a list. Prioritise the recent, but do not assume the archive is harmless.
"I turned off location in the camera app, so I am covered." Only from that point forward, on that device, for that app. Everything already in your library kept whatever it was given, and other apps that touch photos have their own permissions and their own behaviour.
"I will delete everything and start clean." A sweeping deletion is both the most tempting and the most double-edged move available. It does not reach copies already in someone else's hands, it may remove things you will later wish you had, and in some setups it is itself visible to a person with account access. Slower and more selective is usually better.
"They would need special software to read metadata." They would not. Free viewers, built-in file information panels, and ordinary phone photo details are enough for most of it, and none of it requires skill. Assume anything in the file can be read casually.
"A private account or a VPN handles this." Those address who can see a post and what your network reveals. They are different layers from what is written inside the file, and none of the three substitutes for the others.
Related guides
See also:
- How metadata survives cloud sync and device transfers
- Should you strip metadata from photos other people send you?
Frequently asked questions
I think my photos are how they are finding me. What should I do first?
Not the files. Start with access, because a person who can open your account or your backup does not need to read EXIF at all — they can see the whole library, including the photos you never posted. Work through who is still on shared albums and family plans, which devices are signed in, where backups land, which recovery email and phone number are on the account, and whether an old device they once held still syncs. Only after that does cleaning individual files before you share them start to be the thing that matters. If there is any chance of danger to you, this is also the point to bring in a domestic violence advocate, a legal aid service, or a hotline where you live, because order of operations matters and some steps can be noticed.
Should I delete the photos and messages this person sends me?
Be careful here, and do not treat deleting as tidying up. Material someone sends you can matter later to a protective order application, a police report, a lawyer, a school, or an employer, and once it is gone it is usually gone. The safer habit is to keep received files exactly as they arrived, in storage the other person cannot reach, and never clean the original. If you need to pass something on to a third party, clean a copy and send the copy. Preservation obligations and what helps a case vary by place and situation, so ask an advocate or lawyer before deleting anything that relates to what is happening to you. This page is not legal advice.
Does removing metadata stop someone from recognising where a photo was taken?
No, and this is the gap that matters most when the viewer already knows you. Stripping removes the coordinates and timestamps written into the file's header. It does not change the picture. A person who knows your life can read a kitchen backsplash, a view out of a window, a car in a driveway, a school crest on a jumper, a street sign reflected in a shop front, a neighbour's dog, or the pattern of a bedspread — none of which any metadata tool touches. Treat the header as one channel among several. The visible content of the frame, the caption, the account you posted from, and the moment you posted are all still carrying information.
Can MetadataWipe help in this situation, and is it safe to use on a shared device?
It does one narrow job: it takes a single JPEG or PNG you pick from your own device, runs a quick heuristic check for metadata markers, and builds a cleaned copy locally in your browser, with no account and no server transfer. That is useful for the outbound copy of a photo you are about to share. It cannot help with account access, tracking apps, someone else's posts about you, or what is visible in the picture. It is also worth thinking about the device itself: the cleaned file is saved to your downloads folder with -metadatawipe added to the name, and browser history, downloads, and the original file all stay on that machine. On a device or account another person can reach, the leak may be the device rather than the photo, so prefer one only you control.
Remove EXIF data, GPS location, and common photo metadata in your browser — one file at a time, before you share it.
Try MetadataWipe free