TL;DR: It depends entirely on how you send it. Attach a photo the default way — pick it from the gallery and send it as a photo — and Telegram re-encodes the image to compress it, stripping the EXIF block (the camera Make and Model, the DateTimeOriginal, and the GPS IFD holding your latitude and longitude) as a byproduct. But tap the same image in as a document using "Send as File," or drag it into the desktop client, and Telegram stores the original byte-for-byte: every EXIF tag, XMP packet and GPS coordinate rides through intact. The two options sit one tap apart in the same menu, with no warning about the privacy difference between them. Videos and documents sent as files keep their metadata too. The only dependable fix is to strip the file yourself before Telegram ever sees it.
Does Telegram remove photo metadata?
There is no single answer, and that is the whole problem. Telegram behaves in two opposite ways depending on which upload mode you pick, and the choice is buried in a one-tap distinction most people never think about. Send a photo the ordinary way — open the attachment menu, choose an image from your gallery, and let it go as a photo — and Telegram compresses it before delivery. That compression re-encodes the pixels into a smaller JPEG, and the EXIF metadata does not survive the rewrite. The camera make and model, the capture timestamp, the lens and exposure fields, and the GPS coordinates your phone quietly attached all disappear as a side effect of shrinking the file.
Choose the other path, though, and nothing gets removed. When you use "Send as File" (or "Send without compression" on some clients), or drag an image into Telegram Desktop, Telegram treats the image as an arbitrary document and transmits the original unchanged. The recipient downloads the exact bytes you uploaded — EXIF, XMP, embedded thumbnail and all. If the file was an untouched photo straight off a phone, that includes the nested GPS IFD that pins where the picture was taken, often to within a few meters of your front door. If the field names here are unfamiliar, our primer on what EXIF data actually is walks through everything a camera writes into a frame.
What Telegram's compressed "photo" upload actually strips
The compressed path is the one that helps you, and it is worth understanding why it helps so you know when to trust it. Telegram's photo mode is built for speed and small file sizes, not privacy — but the mechanism it uses to hit those goals happens to be destructive to metadata. When the server re-encodes your image into its own JPEG, it writes a fresh file from the decoded pixels and does not copy the original APP1 segment (the block that begins with the bytes Exif\0\0 and carries the entire EXIF payload). Because the GPS coordinates live inside that segment, they go with it. This is the same incidental-cleanup pattern we documented for platforms that re-encode everything, like Instagram's mandatory upload pass.
The catch is that "stripped as a byproduct" is not the same as "deliberately scrubbed." Telegram has never promised to remove your metadata, and it does not publish documentation describing this behavior, so the guarantee is only as durable as the compression pipeline that produces it. If Telegram ever changed how aggressively it compresses, or added a "keep original quality" toggle to the default photo flow, the incidental cleaning could weaken without any announcement. Relying on it means relying on an implementation detail, not a privacy feature. That distinction is exactly the one we pull apart in what metadata scrubbing actually removes — "stripped" is a verb that hides a lot of detail about which fields and why.
Photo by Moe Magners on Pexels.
Why "Send as File" keeps every byte of your EXIF
This is the trap that catches careful people. The reason "Send as File" exists is quality: Telegram's compression visibly softens photos, so photographers, designers and anyone sharing a high-resolution shot deliberately reach for file mode to avoid the re-encode. But avoiding the re-encode is exactly what preserves the metadata. There is no separate "strip metadata but keep quality" option — the single act of skipping compression keeps both the full pixels and the full EXIF block, GPS included.
The desktop habit makes this far worse. On a computer, dragging an image straight into the chat window is the natural motion, and on Telegram Desktop that gesture defaults to sending the file uncompressed — as a document. People who would never knowingly broadcast their home coordinates do it routinely by dragging in a "quick photo," assuming the app cleans it the way a messenger "should." Telegram's own bug tracker carries reports from users surprised to discover their GPS data arriving intact through file-mode sends, which tells you how counterintuitive the split is even to attentive users. The GPS tag is the stubbornest field of the set, which is why we gave it a dedicated explainer on how GPS coordinates get embedded in photos — it survives more handling paths than any other piece of EXIF.
It is worth contrasting Telegram with a messenger that made a firmer choice. WhatsApp strips metadata on its normal photo path because it re-encodes images by default and does not offer a casual "send full quality" toggle in the same tap. Telegram, by design, hands you the uncompressed option front and center — a genuinely useful feature for sharing quality, and a genuinely sharp edge for privacy. Neither behavior is something to lean on blindly, but Telegram's leaves the decision, and the risk, in your hands.
What about videos, voice notes, and documents?
The photo split repeats itself across every media type Telegram handles. Send a video the normal way and Telegram transcodes it, which tends to drop the container metadata; send it as a file and the original moov/udta atoms survive — the recording timestamp, the device make and model, and the GPS coordinates the camera app baked in if location services were on when you filmed. A phone video sent as a file is often more revealing than a still, because it records the same location across a longer span of time. We break down exactly what a phone writes into a clip in what metadata iPhones add to videos.
Documents are the clearest exception, because Telegram is heavily used as a file host. A PDF keeps its author, creator and producer fields. An Office file keeps its revision history and last-saved-by name. An MP3 keeps its ID3 tags. Telegram does not inspect any of these; a file sent as a file is stored as you gave it. Metadata Cleaner handles the images, video and audio you would share in a chat, but document formats like PDF carry their own author and producer fields that live in the file's own structure — those are best cleared in the app that made them (for a PDF, the "sanitize" or "remove hidden information" tools in Acrobat or Preview) before you attach them. The point is simply that "Telegram cleaned it" is never true for anything sent through the file path, regardless of type.
Photo by cottonbro studio on Pexels.
Does encryption or "Secret Chat" change the metadata story?
It is easy to assume that Telegram's security features cover this, and they do not. Telegram encrypts messages in transit, and Secret Chats add end-to-end encryption so that not even Telegram can read the contents. But encryption protects a file from outsiders while it moves — it does nothing to the metadata inside the file. When your recipient decrypts and opens a photo you sent as a file through a Secret Chat, the EXIF block is right there, GPS and all, because encryption scrambled the delivery, not the payload. The coordinates were embedded by your camera long before Telegram touched the file, and end-to-end encryption faithfully delivers them to the other end.
This is the same misconception that trips people up on every "private" messenger. A locked envelope does not blank the letter inside it. If the goal is that the person you are chatting with — or anyone who later gets the file from them — cannot read where the photo was taken, encryption is the wrong tool. The metadata has to be removed from the file itself. The EFF's work on privacy makes the broader case well: metadata is a category — location, timestamps, device identifiers, software fingerprints — and securing the transport layer leaves that category untouched.
What stripping still doesn't protect
Even when Telegram's compressed path does drop your EXIF, two limits are worth stating plainly. The first is that the clean version is only the copy you sent through that specific path. If you also forwarded the original as a file, emailed it, or backed it up elsewhere with metadata intact, the compressed Telegram copy being clean does nothing for those. Stripping is per-file and per-copy; it is not a property that follows a photo around.
The second limit is that metadata is not the only thing a photo reveals. A compressed image with its GPS removed can still show a street sign, a house number, a reflection, or a recognizable skyline that places it just as precisely as any coordinate. And redaction applied to pixels — a blur over a face or a crop around an address — is a separate discipline from clearing EXIF; a downscaled or re-encoded copy can sometimes leak detail the uploader believed was gone. Removing the GPS IFD while the capture time and device serial number survive is not anonymity either. This is the through-line of the whole question: Telegram dropping coordinates on its compressed path is a real convenience, but it is a convenience with edges — wrong upload mode, wrong media type, or a second uncleaned copy, and the protection evaporates. The same lesson applies on Discord, which also strips metadata only on some paths.
How to remove photo metadata before sending on Telegram
The dependable fix is to clean the file on your own machine, before it ever reaches Telegram's servers, so the two-mode inconsistency simply stops mattering. Metadata Cleaner does this in the browser: drop in a photo or a video, and it rewrites the file without its EXIF block, GPS IFD, XMP and IPTC records and embedded thumbnail, then hands you back a clean copy. Because it handles video as well as images, it closes the exact gap Telegram leaves open on the file path — the phone clip whose location data compression would never have touched. The processing happens locally and the file is never uploaded to us.
Once you have the stripped copy, send that instead of the original, and it no longer matters whether you tap "photo" or "Send as File" — there is nothing left to expose either way. If you want the longer walkthrough across desktop and phone, our guide on how to strip EXIF data from a photo covers the platform-by-platform steps. And if you are curious whether the app you are using is quietly the safe path or the leaky one, Telegram's own site documents its features but not its metadata behavior — which is why the reliable move is never to depend on any messenger to do this for you.
Telegram removes photo metadata on the path most people use most of the time, and preserves all of it on the path many people reach for deliberately. That is a fine description of a flexible chat app and a poor foundation for a privacy decision. Strip the file yourself and the question stops mattering. Try Metadata Cleaner free and send the clean copy.