Privacy and publishing · Reference
Social media and EXIF: what survives sharing?
Metadata retention depends on the upload and download path, not just the platform name. A displayed preview, an original attachment, and an account export may carry different information. Test the exact file your audience can obtain before making a privacy or attribution claim.
By ExifGrabber · Sources reviewed · Editorial standards
What published tests actually establish
IPTC’s 2019 tests distinguished browser Save As from platform downloads. They reported stripped metadata in Twitter Save As files, some retained fields in Facebook files, and original-file delivery through Google Drive. These are historical observations, not current platform guarantees.
Compare delivery paths, not brand names
The following is a test-planning matrix, not a live pass/fail comparison.
| Path | File to examine | Question |
|---|---|---|
| Instagram feed or story | Actual audience-accessible image | Which fields survive this specific rendition? |
| Facebook or X post | Saved rendition at the tested size | Does another rendition behave differently? |
| Messaging photo upload | Recipient’s saved photo | Was it re-encoded? |
| Messaging file attachment | Recipient’s downloaded attachment | Does its hash match the original? |
| Cloud original download | Downloaded original | Were the bytes preserved? |
| Account data export | Exported file and accompanying data | Is metadata in a separate file? |
A repeatable retention test
- Make a harmless test image with known fields. Use invented descriptive values and a non-sensitive location. Save a baseline dump and hash.
- Record the platform, date, app or browser version, upload method, and settings.
- Retrieve the image as an ordinary recipient through the path under test.
- Save a second dump and hash, compare field values, and record any conversion of file type or dimensions.
- Repeat for each delivery path you intend to make claims about.
exiftool -G1 -a -s -j original.jpg > before.json
exiftool -G1 -a -s -j received.jpg > after.jsonHow to report a result responsibly
Report “GPS fields absent from the downloaded feed rendition tested on [date]” instead of “the platform deletes all location data.” Include the artifact type and retrieval method. Different hashes establish that bytes changed; they do not identify which metadata changed.
A platform can read metadata before making a public rendition. Meta’s use of IPTC metadata for AI labeling is one documented example of metadata being consumed during processing. Public-file inspection cannot establish what the service retained internally.
Related references and tools
To cite this reference, link to this page or a section heading and include the source-review date. Examples are illustrative; they are not measurements from a camera or a live platform test. Send a correction with the affected section and supporting evidence.