Which platforms strip EXIF metadata — and why it doesn't protect you

"Does Reddit remove EXIF data?" is one of the most-asked privacy questions about image uploads, and it has a comforting answer — yes, mostly — that leads people to exactly the wrong conclusion.

Before the table, the thing almost every article on this subject skips.

The distinction that actually matters

There are two completely different questions hiding inside "does this platform strip metadata":

1. Does the file other users download still contain my metadata?
2. Did the platform receive my metadata?

Every guide answers the first. The second is the one with consequences, and its answer is always the same:

Yes. You uploaded the original. Whatever was in it, they got it.

Stripping happens after upload, on the server, on the copy being served to viewers. Your original arrived intact — GPS, camera serial number, timestamps, the lot. What the platform then does with it is a matter of its retention policy, its legal obligations, and its commercial interests, none of which you control and none of which are undone by the stripped public copy.

So "Reddit strips EXIF" means other Redditors can't read your coordinates. It does not mean Reddit doesn't know them. If your threat model is strangers on the internet, platform stripping helps. If it includes the platform itself, a subpoena, a data broker, or a breach, it does nothing at all.

The only version that covers both is stripping before upload.

What each platform does with the public copy

Behaviour as observed in 2026. These change without announcement — the test method below matters more than the table.

Two rows deserve highlighting.

Telegram is the classic trap. Drag an image into a chat and it's sent as a compressed photo with metadata stripped. Attach the same image as a file — which people do deliberately, to preserve quality — and the original goes across untouched, GPS and all. The privacy-conscious choice and the quality-conscious choice are in direct opposition, and nothing in the interface warns you.

Discord surprises people because it feels like a chat app, so they assume chat-app behaviour. It's closer to a file host. Images posted to a public server are frequently retrievable with metadata intact, and Discord CDN links are notoriously durable.

Why stripping is usually a side effect

Almost none of these platforms strip metadata as a privacy feature. They strip it because they re-encode your image — to normalise formats, cut bandwidth, generate thumbnails, and apply their own compression. Metadata is discarded as a side effect of rebuilding the file from pixels, exactly the way a browser canvas does it.

This explains the pattern in the table with near-perfect accuracy. Services that re-encode strip metadata. Services that store files strip nothing. Photo feeds re-encode; file hosts don't. Once you see it that way you can predict a new platform's behaviour without testing it — though you should test it anyway.

It also explains why the behaviour changes without notice. Nobody announces a change to their image pipeline, because from their side it isn't a privacy change at all.

Test any platform yourself in two minutes

Don't trust the table. Don't trust the platform's help page. Run this:

1. Take a photo with location on, or use any file you've confirmed has GPS. Verify what's in it:

exiftool -a -G1 test.jpg

1. Upload it to the platform.

2. Download it back from a logged-out session — a private window, or another device. This step matters. Some platforms serve the original to the uploader and a processed copy to everyone else, so checking your own view gives a falsely reassuring answer.

3. Run exiftool on what you downloaded and compare.

No exiftool? The image metadata viewer does the same inspection in your browser, so you can run steps 1 and 4 on a phone.

Worth repeating step 3. Testing while logged in as yourself is the single most common way people get this wrong.

What metadata actually exposes

Worth being concrete about the stakes, because "EXIF data" sounds abstract:

• GPS coordinates — often accurate to a few metres. Modern iPhones even record their own error estimate. A handful of photos from home is a home address.
• Camera serial number. This is the quiet one. It's a stable identifier that links every photo from your camera to every other, across accounts, platforms, and pseudonyms. Anonymous account and real-name account, same camera, same serial — correlated.
• Timestamps with timezone — a movement pattern once you have a few.
• Software fingerprints — which editor, which version, sometimes which AI model, occasionally the prompt.
• Embedded thumbnails. Some editors update the main image on crop but leave the original thumbnail in place. The uncropped version can survive inside the cropped file.

That last one is not theoretical. It has burned people who cropped something sensitive out of a screenshot and shared what they believed was the cropped version.

The practical rule

Strip before upload, not after, and stop tracking which platform does what.

It's a single habit that covers every row in the table at once, holds when a platform silently changes its pipeline, protects you from the platform as well as from other users, and takes about three seconds. You can do it locally in your browser with the metadata cleaner — nothing is uploaded, so there's no server that needs trusting.

Then verify the cleaned file once, so you know the tool does what it claims. After that it's muscle memory.

The short version

Most photo feeds strip EXIF from the copy other people download; most file hosts don't. Telegram does both depending on how you attach the file, and Discord preserves. But all of them received your original, so platform stripping only protects you from other users — never from the platform. Clean before upload and the question stops mattering.