| Field | What we found / documented |
|---|---|
| Original EXIF/camera fields after upload | More often preserved than on feed platforms |
| GPS location after upload | May be preserved if present in the original file |
| Large image resizing | Can still occur, which may affect metadata |
| Best way to confirm current behavior | Upload a test photo with known metadata, then re-download and inspect it |
Discord is a useful contrast case: unlike platforms built primarily for public photo feeds, Discord functions closer to a file-sharing and chat tool, and its attachment storage tends to keep more of the original file intact, including metadata that other platforms routinely discard. This is exactly the kind of file-level source Midjourney images circulate through, since Midjourney runs largely inside Discord.
Preservation is not guaranteed for very large files, which Discord may resize, and any client-side sharing step (screenshotting, re-saving) can still strip metadata regardless of the platform. Verify the specific file with our metadata viewer and Content Credentials marker inspector rather than assuming based on the platform alone.
Questions this page answers
Does an empty metadata result mean the image is not from Discord?
No. A missing field can mean the metadata was never written, was stripped by an export or upload step, or was not inspected by this tool. Treat it as inconclusive, not as proof either way.
Does this page verify a specific image is from Discord?
No. It describes documented or observed behavior for Discord in general. To evaluate one file, inspect it with our metadata viewer and Content Credentials marker inspector and weigh the result alongside other context.