Do social networks remove EXIF data?
Mostly yes — and the answer is far less reassuring than it sounds.
Every large platform re-encodes the images you upload. They resize them, recompress them to save bandwidth, and generate several variants for different screen sizes. Metadata does not survive that process, partly by design and partly as a side effect. So the copy that appears in someone's feed is usually clean.
The problem is that people generalise from this into a much broader belief: my photos are stripped automatically, so I don't need to think about it. That belief is what actually causes leaks, because the protection is narrow and conditional in ways that are easy to miss.
The general picture
Broadly, the major platforms behave like this:
- Large social networks — Facebook, Instagram, X, LinkedIn, TikTok, Reddit — recompress uploads and the publicly served copies do not carry EXIF. The original you uploaded is still held on their servers; what is removed is what other users can download.
- Messaging apps, photo mode — WhatsApp, Telegram, Signal, iMessage and similar compress images sent as photos, which removes metadata in the process.
- Messaging apps, file mode — the same apps send the file byte for byte when you attach it as a document or file rather than as a photo. Nothing is removed. This is the single most common way metadata escapes in practice, and the interface difference is one tap.
- Email attachments — no processing at all. The recipient gets your exact file.
- Cloud storage links — Google Drive, Dropbox, OneDrive and the rest store and serve the original. Sharing a link shares the metadata.
- Smaller sites, forums and marketplaces — highly variable. Many never implemented stripping. Some display EXIF as a feature.
- AirDrop, USB transfer, direct file copy — nothing is removed, ever.
Platform behaviour changes without announcement. Treat any specific claim — including this page — as a starting point rather than a guarantee, and verify with your own files if the answer matters to you. The method is at the bottom of this article.
Why "the platform handles it" is the wrong mental model
Three things go wrong with relying on automatic stripping.
First, the exceptions are the normal cases. Selling something on a marketplace and sending photos directly to a buyer. Emailing pictures to an insurer. Sharing a folder link with a group. Sending a file to a colleague as a document because it preserves quality. None of these route through a stripping pipeline, and all of them are ordinary, everyday actions.
Second, you cannot see whether it worked. There is no indicator anywhere in any interface telling you whether the copy that reached the recipient carried coordinates. The failure is silent, and you find out only if someone tells you.
Third, stripping is not a promise. It is a side effect of an image-processing pipeline that exists for bandwidth reasons. Pipelines change. A platform that adds a "download original quality" feature has quietly changed its metadata behaviour for everyone, without anyone thinking of it in those terms.
The one that catches people most often
Marketplace listings. Somebody photographs an item at home, posts it, and a buyer messages asking for more pictures. The seller sends them directly through the chat — often as files, to keep the quality up — and the buyer, a stranger, now has coordinates for the seller's home.
The same shape recurs elsewhere: a rental listing, a lost-pet post with photos taken in the garden, an item swap arranged in a local group. In each case the public post is stripped and the direct message is not.
What to do instead
The reliable approach is to stop treating this as something the platform does and start treating it as something you do, once, before sharing.
- Turn off location for the camera app. This is the highest-value single change, because it prevents coordinates being recorded at all. On iOS: Settings → Privacy & Security → Location Services → Camera → Never. On Android: Camera app settings → Location → off. You lose the ability to browse your library by place, which some people miss and others never notice.
- Use the share-sheet toggle when you need it. iOS offers Options → Location off when sharing. It applies only to that share, so it is a per-share decision rather than a setting.
- Strip before sending anything that leaves a managed pipeline. Email, file transfer, cloud link, marketplace chat, anything sent as a document. This is where a metadata remover earns its place. Choose one that processes files locally rather than uploading them — otherwise you have handed the sensitive image to a third party in order to protect it, which defeats the purpose.
- Rename files. Metadata removal does not touch the filename, and filenames often carry dates, place names or descriptions.
- Look at the picture itself. House numbers, street signs, a view through a window, a screen showing an email client, a reflection in a mirror or a kettle. Visible detail locates images far more often than coordinates do.
Checking for yourself
Do not take anyone's word for how a given service behaves — including this page. Testing takes two minutes:
- Take a photo with location enabled.
- Send it through the route you are unsure about — a specific app, a specific sharing mode.
- Download the received copy on the other end. It must be the downloaded file, not a screenshot of it.
- Drop that file into the metadata viewer, or run
exiftoolon it, and see what survived.
Run this once for the two or three routes you actually use and you will have a genuine answer rather than a general belief. That is worth more than any platform-by-platform table, this one included, because it reflects how the services behave today rather than how they behaved when someone last wrote about them.