Guide

Does Instagram, WhatsApp or Facebook strip image metadata?

The file you download is often a different file from the one that was uploaded. Whether a particular camera field survives depends on the app, the year, the client and the way the picture was saved. We have not run that upload test.

17 October 2026 · Check AI Free

Searches for “does Instagram strip image metadata,” and the same question about WhatsApp and Facebook, usually come from a blank EXIF panel. A blank panel means those fields are not in the copy you opened. It does not, by itself, say that a platform deleted them, that the picture is AI-generated, or that the picture is a photograph. This guide separates three kinds of evidence: a local experiment we did run, third-party tests other people published, and official descriptions of how the apps transform images.

What we measured

The image metadata experiment used eight photographs by Thomas Bresson, licensed CC BY 2.0, from Wikimedia Commons. They are one photographer’s work. None of the eight was a generated image. For each original we made two local derivatives: a JPEG exported with Pillow 12.3.0 after resizing, with no metadata passed to the encoder, and a browser screenshot of the original in an 800 by 600 viewport.

Camera make, camera model, capture time, editing-software text and an XMP container were present in all eight originals. Each of those fields was absent from all eight JPEG exports and from all eight screenshots. Generation text was absent from the originals as well, so that row does not measure retention. The page records the method, the denominators, the source links and the SHA-256 hashes. A repeat run in an isolated environment reproduced the field-presence counts.

The result is still the right analogy for a screenshot of a post. Once you photograph the screen, or let a browser capture it, you are holding a new image. In our batch, the camera fields did not come along. If someone sends you a screenshot and asks you to recover the camera, the prompt or the C2PA manifest, the bytes in front of you do not contain them.

What Instagram’s own help has said about the pixels

An Instagram Help Center page, archived by the Internet Archive on 20 September 2020, told people that shared photos are uploaded “at the best quality resolution possible (up to a width of 1080 pixels).” Photos wider than that were sized down. Photos with an unsupported aspect ratio were cropped. Photos already between 320 and 1080 pixels wide could keep their resolution when the aspect ratio was supported. The live help URL returned an error when we requested it while writing this page, so this paragraph describes the archived text, not a 2026 guarantee.

Resizing and cropping rewrite the image. They do not, in that archived page, list EXIF, XMP, PNG text or C2PA field by field. A promise about dimensions is not a promise about metadata. Treat the archived page as evidence that Instagram has documented a resize-and-crop step, and inspect the file you downloaded if you need to know what that file still contains.

What IPTC reported in 2019

The IPTC Photo Metadata Working Group tested social sites in spring 2019 with a reference image that contained known values in many fields. Their results table is their test, on their image, in that year. It is not our measurement and it is not a current policy statement.

For Instagram, IPTC’s summary says that only posting or uploading was supported, that Save As and download were not available, and that no embedded metadata was displayed. Compared with their 2016 round, they recorded no change. Because they could not save the file, that row does not inventory the metadata inside a downloaded Instagram image. It says the site did not show the embedded fields, and that their testers had no download to inspect.

For Facebook, the same table says no embedded metadata was displayed, Save As files had no XMP, a few rights-related fields were retained in IIM and Exif, and two IIM fields contained data IPTC attributed to Facebook. Their July 2019 write-up names the retained rights fields and says all XMP was removed. They also say the 2016 round had removed all Exif, so the 2019 Save As result was a change, not a permanent rule. Anyone generalizing from 2019 to a file downloaded today should test that file.

WhatsApp does not appear in that 2019 table. We did not find an IPTC field inventory for it, and we did not run one.

What WhatsApp’s help distinguishes

WhatsApp’s help article on sending media describes photos and videos as one attachment path, with a choice of standard or HD quality before sending, and documents as another path. The article we read states a 2 GB maximum for documents, and it says HD media was not available for status updates or profile pictures. It does not publish a field-by-field EXIF policy. Quality settings and a document attachment are different ways to transmit a picture. Which embedded fields arrive depends on the path and the client versions at both ends. Read the file that arrived. Do not infer the path from the picture’s subject.

Check the copy you have

1. Step 1

   Name the copy

   Write down whether you have the sender’s original, a download, a “save image” result or a screenshot. A screenshot is already answered by the local experiment: expect the earlier embedded fields to be gone.

2. Step 2

   Record size, type and a hash before you edit

   Note byte size, format and, if you can, a SHA-256 hash. Opening the file in an editor and exporting again creates yet another copy. Our JPEG step is an example of an export that drops metadata because the encoder was told not to write it.

3. Step 3

   Read the fields that are actually present

   For a PNG that might be a Stable Diffusion or ComfyUI export, use the PNG info reader. For a general source-clue check, use the image checker. Absence is a property of this copy. The Instagram guide is the place to start when the picture came from that app and you still want a check of the file in hand.

4. Step 4

   Keep Content Credentials on a validator

   A resize can leave you without a manifest even when the upload had one. Check Content Credentials on the earliest file you can obtain. This site will not verify the signature.

5. Step 5

   Do not convert a missing EXIF block into an AI verdict

   The eight originals in our experiment were photographs, and their screenshots had no camera fields. A generated PNG can also be exported with a full parameters block. Metadata and generation are different axes. If you need a model estimate, read it as an estimate and see why detectors disagree.