What the Local File Can Show
- Supported embedded provenance and AI-related metadata
- Prompt or workflow text stored in supported PNG fields
- Whether the verified copy preserved expected EXIF, orientation, and ICC data
A photo can be real and still carry AI-related provenance or editing information. Separate what is inside the file from what the platform decides after upload.
Quick Answer
AI Info can come from an embedded file signal, a disclosure made during posting, or a platform system outside the file. A local scan answers only the file question, so an already-clean result cannot explain every label.
Drop, paste, or choose image files
JPG & PNG · WebP inspection only · Up to 25 MB each · No image upload
iPhone photo in HEIC? Save or export it as JPG first.
No file handy?
Reviewed September 3, 2026 Platform claims: Meta and Adobe documentation File behavior: local format tests Platform behavior may change
Start with the exact local export used for your photo. These results describe that file, rather than the platform's reason for labeling it.
| Result | Next step |
|---|---|
| File-level clean copy ready | Review what was removed and preserved. Download that separate copy and select its new filename when sharing. |
| Already clean | No supported target was found. Check that this is the final export, then consider disclosure and platform-side explanations. |
| Review needed / unsupported | Read the reason in the result. Check the format limits; the tool has not offered a verified clean download. |
| Failed | Keep the original and follow the error message. A failed operation is not evidence that the file was cleaned. |
The notice can have several causes. Keep them separate so a file scan is not mistaken for a full explanation of the platform's decision.
First confirm that you scanned the same source or export you intended to upload. A social-media download may not contain the same metadata as your local master.
If the correct local file is already clean, stop treating metadata as the only possible cause. Review disclosure choices and the platform's current help or appeal options instead.
01
Identify the exact local source or final export used for the post.
02
Scan it for supported embedded signals.
03
Keep the original and use a verified copy only when removing those fields fits your purpose.
04
If the file is already clean, review disclosure and platform-side explanations separately.
Official documentation supports the platform and file-format claims below. Community posts show reported questions, not proof of platform behavior.
Official source
Explains industry-shared signals, self-disclosure, and Meta's changing treatment of generated versus edited content.
Official source
Documents current JPG and PNG export choices for attached, cloud-published, or omitted Content Credentials.
Official source
Defines the manifest, provenance, validation, and storage model used by C2PA Content Credentials.
No. A software tag such as Photoshop does not show that the whole image was generated. The scanner keeps confirmed targets separate from general metadata.
Check the downloaded copy, later exports, and where the remaining label appears.
Guide →Check supported file signals before posting a lightly edited real photo.
Guide →Inspect Photoshop exports for embedded credentials and AI-related metadata.
Guide →Review file-level signals before you publish a cleaned local copy to Facebook.
Guide →