Social networks and metadata: what gets cleaned and what does not

Updated: September 4, 2026

The most common argument against cleaning goes like this: «I downloaded my own photo from the feed, checked the properties, and they were empty — so the platform already stripped everything». The test is honest; the conclusion is not. Empty properties only tell you that the copy handed back to you was cleaned.

Let us look at the mechanism: why metadata disappears on platforms, why that is not a privacy promise, and how to test a specific service without relying on anyone's claims, including ours.

Why metadata disappears at all

Large platforms do not keep your file the way you sent it. An uploaded image gets rebuilt: resized to their dimensions, recompressed to their weight targets, rendered into several versions for different screens. A clip gets re-encoded for their player.

During that rebuild the service block usually just is not carried over — it is not needed for display. In other words, the disappearance of metadata is a side effect of bandwidth optimisation, not a protection feature. Two consequences follow, and both are unwelcome.

First: what gets rebuilt is the copy shown to visitors. The platform received your original with every field intact and handles it under its own rules. Second: because this is a side effect rather than a promise, the behaviour can change with any update — and nobody will tell you, since formally nothing was promised.

Where the file almost certainly travels untouched

Rebuilding happens where a platform displays the content itself. The moment a file is passed along as a file, there is no reason to rebuild it — and it reaches the recipient byte for byte:

• messengers set to send as a file or without compression — no compression is applied and the service block survives in full;
• email attachments — the mail server does not touch the content;
• cloud storage links and file hosting — the link downloads exactly what you uploaded;
• zip and rar archives — nobody processes what is inside an archive;
• classifieds boards and forums that keep the original available for download;
• direct device-to-device transfer — over a local network, by cable, or through wireless sharing;
• forwarding: if the recipient sends your file on to a third person, the metadata travels with it.

How to test a specific platform yourself

Services behave differently and change over time, so testing once beats hunting for someone else's table. The check takes five minutes and needs nothing installed.

1. Take a phone photo that definitely has service data — one shot with location enabled.
2. Look at its properties before uploading: on Windows right-click, Properties, the Details tab; on macOS open the file in Preview and show the inspector. Note what is there.
3. Upload the file to the platform the ordinary way, exactly as you always do.
4. Download it back from there — download the actual file, do not take a screenshot — and open the properties again. The difference is what the platform removed.
5. Repeat for the second sending method — as a file, or as an attachment. This is where the result most often differs from the first run.

Test each channel separately. The same messenger can behave differently when sending as a photo and as a file, and that is the single most common source of surprises.

What this means in practice

The conclusion is not that platforms cannot be trusted, but that their behaviour is not yours to control. You govern neither what happens to the original on their side, nor whether the processing changes in the next update, nor where the recipient forwards the file next.

You control exactly one thing: what leaves your device. If the file went out already cleaned, the rest of the details stop mattering — there will be nothing to strip regardless of how any given service behaves.

Frequently asked questions

• So social networks lie about removing metadata? No. Most platforms never promise anything specific — the rebuild is done for load speed, and the cleaning falls out of it as a by-product.
• Does a screenshot instead of the file solve it? The source service block is indeed lost, but you lose quality and gain the metadata of whatever device took the screenshot. Cleaning the original is simpler.
• If the platform cleans anyway, why clean myself? Because you hand it the full original, and half of all transfer channels clean nothing at all. Cleaning before sending covers both cases at once.
• How do I tell whether a file goes as a photo or as a file? Usually it is a choice in the attachment menu — items like Photo and Document, or a separate «no compression» toggle. The second option sends the file untouched.
• Do file properties show everything? Not everything: the system displays only the fields it knows how to read. Empty properties are a good sign, not a strict proof.