Does Instagram Strip EXIF Data?

Yes — Instagram strips EXIF data from the photos and videos you post. When an image is uploaded to a feed post, a carousel, a Story, or a Reel, Instagram decodes and re-encodes the file server-side and discards the original metadata block: GPS coordinates, capture timestamps, camera make and model, lens details, exposure settings, and serial numbers do not survive into the copy that other people see or download. Your original file on your phone is untouched and still contains everything.

That is the short answer, but three exceptions matter in practice: files shared as documents rather than as photos, posts published by third-party apps that upload the original file themselves, and the fact that Instagram’s own mobile app reads your metadata on your device before the server strips it.

What Instagram actually does to your file

The important detail is that Instagram does not “filter out” a few EXIF keys. It rebuilds the image.

The upload pipeline

1. Your original JPEG/HEIC is uploaded as-is.
2. The server decodes it into raw pixels.
3. The pixels are normalised — cropped to the feed’s allowed aspect ratios, resized to fit the platform’s limits (feed photos are capped in the region of 1920 px on the long edge), and often colour-adjusted.
4. A brand-new JPEG is encoded from those pixels.

Because step 4 writes a fresh file, the EXIF APP1 segment, XMP packet, IPTC block, ICC profile, and embedded thumbnail are never copied forward. There is nothing to strip — the header is replaced wholesale. The practical consequence: what you download from Instagram is a different file, not your file.

What survives and what is removed

Item	Status after an Instagram photo upload
Pixel content	Survives — re-encoded, recompressed, colour-adjusted, possibly cropped
GPS latitude / longitude	Removed
GPS altitude, GPS timestamp, GPS direction	Removed
DateTimeOriginal (capture time)	Removed
Make, model, body serial number	Removed
Lens model, focal length, aperture, shutter speed, ISO	Removed
Orientation tag	Removed — rotation is baked into the pixels instead
Embedded thumbnail (TIFF IFD1)	Removed
XMP / IPTC / ICC profile	Removed, or replaced by platform-generated fields
Original filename	Not carried over; CDN assets are served under hashed names
Caption, hashtags, alt text, location sticker, account	Not file metadata. These are platform database records, and they persist

The last row is the one people get wrong. A caption, a hashtag, the geotag you attach to a post, and the link between the image and your account are not EXIF and are not affected by any stripping behaviour. They live in Instagram’s database, are visible to anyone with access to the post, and are retrievable through the API. The EXIF question and the location-sticker question are separate problems needing separate answers.

Feed, Stories, and Reels: same answer, different machinery

• Feed posts and carousels — the server-side re-encode described above. EXIF is gone from the served copy.
• Stories and Reels — the upload is transcoded into a video stream (H.264/HEVC), and the still image becomes a video frame. There is no EXIF container to begin with, so “stripping” is structurally irrelevant; the frame is just pixels.
• Downloads — a downloaded Story or Reel is a video file, not a photo. If you want a still, you are extracting a frame, and that frame carries no original EXIF either.

The “document” loophole

Instagram’s direct messages allow you to send a file rather than a photo. When a file travels as a file, it is delivered as an uploaded attachment, and the metadata inside it — including GPS — is generally still there. This is also true of a PDF built from your photos: PDFs embed the original image streams, and those streams can still contain their EXIF blocks even if the PDF viewer displays nothing.

Treat “sent as a file” as assume the metadata survives and verify on the receiving end, because delivery behaviour for attachments has changed over time. If the recipient can see coordinates in an EXIF reader, the metadata is intact regardless of what the chat UI suggests.

Third-party apps that post for you

Scheduling tools, social managers, and some gallery editors take the file from your library and upload it to Instagram on your behalf. Whatever they upload, Instagram still strips before publishing, so the end result is the same. But the app now has access to the original file and its metadata before Instagram ever sees it, and if it stages the photo in its own cloud storage to schedule the post, that copy sits outside Instagram’s stripping entirely. The metadata risk with third-party posting tools is therefore not “Instagram failed to strip” — it is “a third party now has your coordinates and a copy of the file”.

Instagram reads metadata on your device

Instagram’s mobile app parses the photo’s metadata locally at selection time. That is how it offers location suggestions and distinguishes a screen recording from a camera photo. The stripping happens later, server-side. “Instagram strips EXIF” therefore describes what is published, not what was read — and any app on your phone with photo library access can read the same fields without uploading anything.

Your original file on your phone is unchanged

Nothing Instagram does modifies the copy in your camera roll. To remove location there you need a separate step:

• iOS — Photos → select the image → info (i) → Adjust → No Location.
• Android (Google Photos) — ⋮ → Edit with pencil → Remove location.

For a broader wipe across many photos, the freexifdata EXIF viewer and remove EXIF data tools run entirely in your browser, so the file never leaves the device. Start with the GPS photo checker if location is your main concern, and use the EXIF tag reference to see what a field such as GPS coordinates, date time original, camera model, lens model, serial number or orientation actually reveals.

How to verify it yourself in four steps

1. Open the original file in the EXIF viewer. Confirm what is in it.
2. Download the posted copy (right-click → “Save image…” on desktop; long-press → Download in the app).
3. Open the downloaded copy in the viewer. Expect zero metadata fields on a normal feed upload.
4. If coordinates still appear, the copy did not come through the standard upload path — check whether you posted via a third-party app, sent the image as a document, or copied it from a scraper site.

This test is also the honest way to answer “does Instagram strip EXIF” for your own workflow, because platform behaviour changes and we do not run a live test suite against Meta’s pipeline.

Caveats and honest limits

• As of the time of writing, standard Instagram photo and video uploads are re-encoded without EXIF. That is well established, but it is a behavioural property of a service, not a guarantee, and it can change without notice.
• Third-party Instagram downloaders and mirror sites serve the platform’s copy, and some write their own metadata back into the file (a “downloaded by X” tag, a new filename, a source URL). That is not original EXIF, but it still leaks information about who obtained the file and when.
• Some photo apps deliberately preserve or re-inject EXIF when they export, so the file you pick in the share sheet may not be the file the camera wrote.
• If a post must carry no metadata at all and you cannot verify the destination’s behaviour, strip the file before it leaves your device. That is the only approach that does not depend on someone else’s pipeline.