Removing photo metadata: what is actually in there
Every image file holds more than the image. What your camera and phone write along with it, how to look it up and how to remove EXIF data without uploading your photo to a stranger.
A photo is not only what you see. The same file carries a second, invisible part: when the picture was taken, with which device, at which settings and, if the camera app is allowed to, on which exact spot.
That part is called EXIF. It gets written the moment you press the shutter, nobody asks you first, and in most cases you never notice it. It becomes visible exactly when somebody receives the file and looks inside.
What travels along
Depending on device and settings, an image file contains:
- Date and time of the shot, down to the second.
- Device and lens, so manufacturer, model, sometimes the firmware, and on some cameras the serial number.
- The exposure values, aperture, shutter speed, ISO, flash yes or no.
- The software the picture was last edited with.
- The location, as coordinates, if the camera app has access to it.
- An embedded thumbnail, a small copy of the image inside the file itself.
Out of all that, location is the obvious problem. The combination is the more interesting one, because it works just like profile details do: time plus device plus editing software links two files to each other, even when neither of them shows anything revealing.
Two pictures with the same camera serial number belong together. That alone is enough to connect an anonymous account with a private one.
Look first, act after
Before you remove anything, it is worth checking one of your own files. Usually the situation is better than feared, sometimes worse.
Windows. Right-click the file, Properties, Details tab. Everything that is in there shows up, including GPS if present.
macOS. Open the file in Preview, Tools, Show Inspector. There are separate tabs for EXIF and for location.
iPhone. Open the picture in Photos and swipe up or tap the info symbol. If a map appears, the location is attached to the file.
Android. Open the picture in Google Photos and bring up the details. Here too a map means coordinates are in there.
What you do not need for this is a website that analyses it for you. More on that further down.
Location is where you start
The easiest fix is not per picture but once and for all: take location access away from the camera app. Then your pictures are created without coordinates in the first place and you never have to think about it again.
On iPhone that sits under Settings, Privacy & Security, Location Services, Camera. On Android it is in the app permissions of the camera app. A standalone camera usually has a "save location" or "geotagging" option right in its own settings.
This costs you almost nothing. The only downside is that your private photo library no longer has a map.
Getting it out of files that already exist
For the pictures that are already there, every system has a built-in route.
iPhone, while sharing. Tap "Options" at the top of the share sheet. There you can switch off "Location", and under "All Photos Data" you decide whether metadata travels at all.
Android. Google Photos has a setting to remove the location while sharing. For everything else, going through an edit and saving anew is the more reliable path.
Windows. Right-click, Properties, Details, then "Remove Properties and Personal Information" at the bottom. Windows creates a cleaned copy and leaves the original alone.
macOS. In Preview the location can be deleted through the inspector. When exporting from the Photos app you can uncheck location and other details.
And the route that always works, no matter the device or program: take a screenshot of the finished image and pass that on. A screenshot is a new file containing only what was on the screen. Everything that was in the file before is gone with it. You lose some resolution, and for paid work it is the wrong move, but for anything you upload somewhere in passing it is the fastest safe grab.
Newly created beats cleaned up afterwards. What was never written into the file cannot be overlooked either.
What platforms handle for you and what they do not
The big networks re-encode uploaded images, because they downscale and compress anyway. Metadata almost always falls away in the process. That only means the picture is clean there for other users. Whether the operator received the original file with everything in it is a different question, and the answer is usually yes.
And there are three routes on which everything survives:
Sending as a file instead of as a picture. Most messengers offer both. Picture mode compresses and cleans along the way, file mode delivers exactly the original.
Cloud links. A shared link to a file in your storage is the file. Nothing gets recalculated there.
A direct mail attachment. Same thing.
So the rule is simple: as soon as somebody receives a file rather than seeing an image in a feed, what is inside it is your decision.
The little preview image inside the file
A detail hardly anyone knows about: many image files also contain a tiny copy of the picture, so file managers can show a thumbnail quickly.
It used to happen that programs edited the image but left that thumbnail untouched. Anyone who had blurred out a face or cropped something away then had it gone in the picture and still present in the thumbnail. Today's programs update it, and still, I would not rely on that when it matters.
So if you have made something unrecognisable anyway, the screenshot pays off twice. What else counts there is in Hiding your face in photos: what actually works.
Videos and file names
Videos carry the same baggage. MP4 and MOV files hold capture time, device and, depending on settings, the location. The camera app's location access covers both, photo and video.
And then there is the layer that is not technically metadata but works exactly like it: the file name and the folder. IMG_4021.jpg says nothing. Summer_Croatia_Lisa.jpg says plenty, and it comes along in every chat. How quickly a name gets assembled from fragments like that is in Staying anonymous: what never belongs in your profile.
Why online removers are the worst idea
There are dozens of websites offering to remove or display EXIF data. The procedure is always the same: you upload the image, wait, download it back.
Think about what happens there. You hand the very file whose location worries you to a stranger on a server you know nothing about, together with your IP address and the time of day. To shrink one risk you have created a bigger one.
A picture too private for your own account is not one you upload to an unknown website just so it can delete two lines from it.
Everything listed above runs on your own device. That is enough.
How it looks on our side
Anything publicly visible gets recalculated here anyway. Profile picture and portfolio are written into a different format on upload, and the metadata falls away with it. The same goes for the protected previews before a purchase: downscaled, covered with a watermark, and no metadata left in them.
What somebody receives after a purchase is your delivery in full quality, which is exactly what they are paying for. That is why the camera app's location access is not a general hint but the switch that genuinely changes something for paid work. Flip it once, never think about it again.
We are not neutral here, we run the platform we are writing about. The rest above works everywhere regardless. What else stays private with us is in Earning without putting your face online.
Common questions
No. Only if the camera app has access to your location. On phones that is often the default, on a camera without a phone connection usually not.
Yes, as far as the contents of the old file go. The screenshot is a new file with only what was on screen. It does carry its own creation date and device type, though.
No. Metadata sits in its own area of the file, the image itself stays untouched. You only lose quality through the detour via a screenshot or by saving again in a compressed format.
No. The file name is one half, the data inside the file is the other. Both belong on the checklist.
You cannot pull those back. What makes sense is switching off location access now and checking, with the services that still hold the file, whether anything can be deleted there.
As a rule no, because the images get re-encoded on upload. You should not rely on it, and when sending as a file it does not apply at all.
