Free tool
Image History Checker
Read supported EXIF, GPS and saved PNG prompts in seconds, right in your browser. These editable records power a real investigation of an image’s history, and we are precise about what they prove: never authenticity on their own. Add a separate signed-record check by uploading the original whenever you want it.
Inspection
Read a file on your device
JPEG, PNG, WebP or classic TIFF up to 20 MiB. Files stay on your device until you explicitly choose signature validation.
Your selected image is read locally first. It is uploaded only if you choose the separate signature check.
Need camera settings, capture dates or GPS? Read every readable EXIF field in your browser.
Checking an exported copy? Compare saved image details before and after export.
Looking for an editable ComfyUI graph? Inspect and download saved workflow JSON.
AI metadata checker: separate saved fields from signed records
AI image metadata takes three forms: saved instructions, generation settings and signed provenance records. This reader parses supported EXIF and GPS fields in your browser, and for PNG files it also reads the supported AUTOMATIC1111, ComfyUI and InvokeAI prompts, model names and settings still in the file. Missing or conflicting values are reported as unresolved, never guessed. It reads what is saved and infers nothing from the picture; XMP, IPTC and manufacturer-specific fields are separate territory.
How to check an image’s saved metadata
Pick the original and read the parsed fields, saved prompt and available settings. The SHA-256 file ID covers every original byte, so exact copies are identified instantly. Download the local JSON for your records, checking it for private GPS or prompt information before sharing. For signature validation, choose the separate upload action: its result separates C2PA signature validity from signer trust. Local metadata fields are editable and validate no signature.
Follow the evidence to the right reader
For JPEG/WebP prompts saved in EXIF UserComment, use the separate image prompt extractor; this on-device prompt reader covers PNG records. Use the examples above to compare camera fields with saved generation instructions. Neither missing metadata nor a valid signature proves human authorship, and we never claim otherwise. Local reading accepts up to 20 MiB; separate C2PA uploads are processed in memory without storage. Keep the original and your source notes while the image’s history is still open.
When the image history is incomplete
Can I recover metadata removed from a photo?
Records that are no longer in the file are gone from that file, so go to the source: ask for the original camera or generation file, or find an earlier copy you are allowed to inspect. Have both versions? Compare their saved records side by side. An empty result also covers unsupported or damaged records; it is never proof that the image had no metadata.
Can I check the original image using a screenshot?
A screenshot is a brand-new file, so this tool reads the screenshot’s records, not the original’s hidden fields, saved prompt or signed history. Keep the source link and request the original download wherever possible. Inspect the screenshot by all means, and describe the result as a reading of that copy.
Why do identical-looking images have different file IDs?
The SHA-256 file ID covers the file’s bytes, saved metadata included, so changing those records or re-encoding the image changes the ID while the pixels look identical. Our seven controlled metadata experiments include downloadable examples with matching pixels and different records. A different ID shows that the bytes differ; what changed, and whether AI was involved, are separate questions.