| Field | What we found / documented |
|---|---|
| EXIF storage | APP1 segment, defined by the CIPA EXIF specification |
| XMP storage | Separate APP1 segment, common in editing software |
| Effect of re-encoding | Fields can be dropped or altered depending on the tool |
| Common use | Camera make/model, capture settings, timestamps, GPS |
JPEG's EXIF support is the oldest and most standardized of the three formats covered here, governed by a specification maintained by Japan's camera and imaging industry association, which is why nearly every digital camera writes EXIF into JPEG by default. This is also the format most AI image detectors and metadata viewers, including this one, were originally built around.
Because JPEG is a lossy format, many tools re-encode the pixel data on save, and depending on the library used, that re-encode step can also rewrite or drop the EXIF and XMP segments. A JPEG with no camera fields is consistent with an export tool that stripped them, a screenshot, or an image with no camera origin to begin with, not proof on its own. Check any JPEG with our metadata viewer.
Questions this page answers
Does an empty metadata result mean the image is not from JPEG?
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 JPEG?
No. It describes documented or observed behavior for JPEG in general. To evaluate one file, inspect it with our metadata viewer and Content Credentials marker inspector and weigh the result alongside other context.