Platform · pre-upload
Snapchat metadata and compression
A normal Snapchat send compresses and re-encodes, but exporting from Memories or sharing as a file can let the original through with its metadata complete.
On-device/No upload/Quality unchanged/No sign-up
Drop images here, or click to choose
JPG, PNG, WebP, AVIF, HEIC · 15 MB each · up to 30 per batch
You can also paste a screenshot with ⌘V / Ctrl+V
Cleaning options
Want to look first? Themetadata inspectorlists every field in the file, so you can see exactly what is there before deciding what to strip.
Normal sends compress; export paths may keep the metadata
The same image in different slots — feed, story, cover — may be three separate files, and each one has to be handled.
What the platform reads
| Entry point | Notes |
|---|---|
| Normal snap | Re-encoded; most metadata lost |
| Memories export | May be the original file |
| File sharing | Treated as a file, metadata preserved |
Pre-upload checklist
- 11. Inspect once after exporting
- 22. Clean before sharing a file
- 33. Watch for GPS
- 44. Upload that copy, with no editor or forwarding in between
Common traps
- Assuming every path compresses
- Remembering the metadata problem only after exporting
If it is still flagged after cleaning
That means the trigger was never in the file metadata. It could be an invisible pixel-level watermark, the platform's own visual classifier, or history held on the platform side. None of those live in the metadata layer, and cleaning again will not change them.
The full boundaries are in thedisclaimer; if you just want to confirm the file really is clean, use thewatermark check.
Common questions
Does Snapchat keep metadata?
A normal send compresses it; export and file-sharing paths may keep it.
Can I check after exporting?
Yes — run it through the inspector and you will see.
Does it affect quality?
Platform compression does; cleaning locally does not.