# Telegram photo vs. file: a metadata test you can reproduce

- Canonical: https://creatorprivacykit.com/blog/telegram-send-as-file-metadata-privacy
- Reviewed: 2026-09-15
- Category: Privacy field note
- Author: CreatorPrivacyKit Research

Telegram gives you more than one way to send an image. The useful privacy question is not whether Telegram “strips EXIF” in general. It is whether the specific delivery path you used preserved the original file or created a transformed copy.

## What we can verify

A source file can be measured before upload. Record its SHA-256 hash, dimensions, byte size, EXIF, XMP, IPTC, ICC profile, and any C2PA data. Send the same image through two paths — normal photo and file/document — then download both results and run the same checks again.

If a downloaded file has the same SHA-256 hash as the source, that specific test preserved the exact bytes. If the hash changed, something in the path transformed the file. That still does not tell you exactly what Telegram stored internally.

## A simple A/B test

1. Pick a non-sensitive JPEG with known metadata.
2. Save the source hash, dimensions, file size, and metadata dump.
3. Send it once as a normal photo.
4. Send the same source again as a file/document.
5. Download both received files.
6. Compare hashes, dimensions, encoding, and metadata.

Repeat the test when you change client, OS, file type, or upload route. Platform behavior can change.

## How to interpret the result

| Observation | Reasonable conclusion | What it does not prove |
| --- | --- | --- |
| Hash is identical | The delivered file is byte-for-byte identical in that test | That every Telegram client always behaves the same way |
| Hash changed | The delivered file was transformed | That only metadata changed |
| EXIF disappeared | The received copy does not contain those EXIF fields | That Telegram never received the source EXIF |
| Dimensions changed | The delivered image was resized | What happened to an internal original, if one existed |

## Privacy recommendation

If GPS, camera identifiers, authoring data, or provenance metadata is sensitive, remove it before upload. Keep the original in your archive and create a separate sharing copy.

That is safer than relying on undocumented server behavior because you can verify the outgoing file locally.

## About screenshots

A screenshot usually creates a new file and therefore drops the original container metadata, but it also changes resolution, color handling, and pixels. It is a crude privacy workaround, not a faithful full-resolution export.

## CreatorPrivacyKit

CreatorPrivacyKit processes supported files locally in the browser. For images, a fresh export can remove common container metadata before the file is sent anywhere else.

This article intentionally avoids claiming that Telegram always strips or always preserves metadata. The test above is the stronger claim because you can reproduce it yourself.