Platforms
Does Instagram remove EXIF data?
Images downloaded from Instagram feed posts are widely reported to lack the original EXIF, but this site has not run a dated round-trip test; see how to check whether a platform strips image metadata for the method. Stripping happens after Instagram has your original file, so it protects you from other viewers and from nobody else.
Why it happens at all
Instagram reportedly processes uploads by resizing photos to the platform's display dimensions and re-encoding them to its own JPEG settings.
Re-encoding means decoding the picture to pixels and compressing it again into a brand-new file. The original container — the APP segments holding EXIF, XMP and IPTC in a JPEG, or the text chunks in a PNG — is not part of that operation. The new file gets whatever the encoder chooses to write, which is typically a JFIF header and a colour profile and nothing else.
This distinction matters because it predicts the exceptions. Metadata survives wherever a platform transfers the file instead of re-encoding it, which is exactly why "send as document" and "send as file" modes in messaging apps behave differently from the normal photo picker. The rule is not which platform, it is does this path re-encode or copy.
Why stripping on upload does not protect you
Work through the order of events.
- Your phone writes coordinates into the photo.
- You upload that file. Instagram now has the original, coordinates included.
- Instagram reportedly re-encodes it for display.
- Other people download the re-encoded copy, which is widely reported to have no original EXIF.
Step 3 protects you from step 4. It does nothing about step 2. Meta received the complete file with your location in it, along with the account, device and timestamp that came with the request, and the platform's retention of that upload is governed by its own policies rather than by what the public copy contains.
So "Instagram strips EXIF" is widely reported, but is not a reason to relax. If the location in a photo is something you would not tell the platform, the only step that helps is removing it before the file leaves your device.
There is a second reason not to rely on it. Stripping is reportedly a side effect of a display pipeline, not a commitment. It applies to the path you used — a feed post — and says nothing about a direct message, a file attachment, or whatever the product does next quarter.
What no platform removes
Metadata stripping operates on the file's container. It never touches:
- What the photograph shows. A street sign, a house number, a visible skyline or a reflection in a window survives every re-encode ever performed.
- Pixel-level watermarks. Provenance marks encoded into the image data itself, such as SynthID, are part of the picture rather than the container.
- What you typed. Captions, tags, and the location you attached in the app are the post, not the file.
- The upload record. Account, device, IP address and timestamp are the platform's data about you, not fields you can strip.
How to check any platform yourself, today
Published tables of platform behaviour go stale silently — the platform changes its pipeline and the article does not change with it. The reliable move is a five-minute test you can rerun whenever it matters:
- Take a photo with location services on, or use any file you know carries GPS. Confirm it does with our metadata viewer before you start.
- Upload it the exact way you normally would. The path matters: a feed post, a story, a direct message and a file attachment are four different tests.
- Download the result back — from the web interface, or by saving the image as a recipient would.
- Inspect the downloaded copy in the viewer, or run
exiftool -a -G1 -s downloaded.jpg. - Compare against the original.
Test the route you actually use. That is the whole method; the longer version is here, including why a "clean" result is weaker evidence than it looks.
Removing location before you upload
If the goal is that the coordinates never reach anyone — the platform included — it has to happen on your device, before the upload.
Two practical routes. On iOS, the share sheet has an Options control at the top where location can be switched off for the copy you are about to share. Or remove the coordinates from the file itself and keep the resulting copy for sharing.
One caveat specific to iPhone: MetaPurify reads JPEG, PNG and WebP, and an iPhone photo is usually HEIC. Share or export it as JPEG first, then clean that copy.
Check a photo for GPS coordinates