Labs · Test pending
Does Discord remove EXIF metadata from images?
Short answer
CreatorPrivacyKit has not published a dated test of this Discord upload path yet. A downloaded attachment can tell you what that copy contains. It cannot prove what Discord stored internally, and forum claims are not a substitute for a hash-checked run.
Test pending
- Published
- Last updated
- Last tested
- —
What we measured
No dated CreatorPrivacyKit result is published for this route yet. Fields below stay empty on purpose.
| Field | Delivered copy |
|---|---|
| GPS / location | Not yet tested |
| EXIF | Not yet tested |
| Camera information | Not yet tested |
| Timestamps | Not yet tested |
| Provenance / C2PA | Not yet tested |
| Recompression / resize | Not yet tested |
GPS / location
Not yet tested
EXIF
Not yet tested
Test environment
Environment details are recorded when a test is run: OS, app or browser version, device, and upload path.
How to test your own file
- Record SHA-256, dimensions, EXIF, XMP and any C2PA on a non-sensitive JPEG.
- Upload to a private test channel from a recorded client version.
- Download the attachment as another user would.
- Compare hash, size, dimensions and metadata.
- Repeat for file upload vs. image upload if the client exposes both.
Methodology
Every published result has to follow the same protocol: a known source file, a recorded hash, a specific upload path, and a downloaded copy. Folklore does not count.
Privacy implications
If a photo still has GPS, camera serials, or timestamps you do not want in a server, strip them before upload. Waiting for Discord to “handle it” is not a control you can verify.