Official source
Meta: How AI Info labels work
Explains industry-shared indicators, disclosure, and the generated-versus-edited distinction.
Already downloaded a cleaned image, but still seeing AI Info or another AI label? Check the copy and publishing step before repeating cleanup.
Quick Answer
A verified download confirms supported changes in one local file. If a label remains, check which copy you shared, whether it was exported again, and whether the notice belongs to an existing post or account. Metadata cleanup cannot control every platform signal.
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?
Content reviewed October 12, 2026 File scope: verified local copy and export workflow Platform scope: official Meta documentation; no promise about a future upload
The original and the cleaned copy can look identical. Locate the file ending in -clean and compare its filename with the attachment you selected. A screenshot of a labeled post or a file downloaded from a social app is not necessarily the export you checked.
For a carousel, identify each attachment separately. One successful report cannot explain every image or the platform's decision about a whole post.
Select the downloaded copy in the tool above. Compare it with the first report: supported targets that were removed should no longer appear as confirmed findings. Read warnings rather than assuming every field in every format is covered.
| What the second check shows | Action |
|---|---|
| No supported target found | Keep the result as file evidence. Move on to export history and the location of the label instead of repeatedly cleaning the same copy. |
| A confirmed target is present | Confirm this is the downloaded copy and whether another app saved it again. Inspect that final export; do not treat an earlier report as evidence about a later file. |
| Review needed, unsupported, or failed | Read the explanation and format limits. No verified clean result has been established for this operation. |
An editor, converter, or sharing workflow may create a new file and write different metadata. A report for the downloaded copy does not describe that later export. Check the final file after the last editing step.
Keep the original export and the cleaned copy separately. If camera details or copyright matter, review what was preserved before using a privacy-cleaning option. Repeated cleanup does not make a platform outcome more certain.
A notice on an already-published post is stored on the platform, not inside a local image you are now editing. This tool cannot relabel that post. A profile notice is an account question, while a new-upload label may involve file indicators, disclosure, or other systems.
Meta describes using industry signals and creator disclosure in its labeling approach. An embedded Content Credential and a pixel-level watermark are different mechanisms. This tool removes supported metadata; it does not remove SynthID or change an independent visual classifier.
When the correct final file has no supported targets, more passes through the same metadata cleaner do not address a live-post label, disclosure, or a signal outside the file. Use the platform's current help or available review route for the notice you see.
Keep the filename, first report, final export, and platform notice together when investigating the problem. Do not delete a post just to test whether metadata was the cause.
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 indicators, disclosure, and the generated-versus-edited distinction.
Official source
Describes watermarking beyond ordinary file metadata; removal is outside this tool.
No. Verification covers supported changes to that local file. It does not control a platform's classification, disclosures, or records about a published post.