Telegram: “photo” and “file” are different privacy questions
If you send the same JPEG two different ways, do not assume the recipient gets the same bytes. Measure both routes.
The useful experiment is A/B, not folklore
Telegram exposes more than one way to send media. That is enough reason to treat “send as photo” and “send as file” as separate cases instead of publishing one universal sentence about Telegram and EXIF.
Use the same source image for both tests. Send one copy through the normal photo picker and one through the file/document route. Download both on the receiving side and compare them with the original.
Your source file can be hashed and inspected before it leaves your device.
The two received files can be compared for bytes, dimensions, encoding, and metadata.
A clean delivered copy does not reveal every intermediate copy Telegram may have processed.
Run the comparison
- Pick a JPEG with a few harmless but easy-to-recognize metadata fields.
- Record SHA-256, dimensions, byte size, EXIF/XMP/IPTC, and ICC profile.
- Send it as a photo.
- Send the same source as a file/document.
- Download both results from a second account or device and inspect them.
Three outcomes that mean different things
| Result | What it suggests |
|---|---|
| Photo changes; file is byte-identical | The media path transformed the image while the file path preserved the source in that test. |
| Both change | Both routes produced a different delivered artifact. Compare the diffs rather than assuming the cause. |
| Both are identical | That client/version/test preserved the bytes on both routes. Repeat after meaningful app changes if this matters operationally. |
Why “send as file” can be worse for privacy
People sometimes choose a file route because they want maximum quality. If that route preserves the original file, it may also preserve metadata you did not intend to share. Quality preservation and privacy cleanup are different goals.
Keep the conclusion narrow
A recipient-side download tells you what was delivered to the recipient. It does not prove what Telegram stored, logged, or discarded internally. We deliberately do not turn a file diff into a claim about a private backend.
Preserve quality without forwarding your history
Use CreatorPrivacyKit to inspect the source and create a cleaner sharing copy locally.
Inspect a file →