The “AI info” or “AI-generated” label is missing on Instagram or Facebook because Meta’s automated detection pipeline either could not find the cryptographic C2PA or IPTC metadata markers in your file, or your edits did not meet Meta’s threshold for synthetic content. If an image was created or edited with generative AI, Meta checks for specific digital signatures during upload. When intermediate software strips those signatures, or when generative tools are used solely for minor touch-ups (like object removal), the platform suppresses the automatic label.
Fast Fix
Export directly from Photoshop using Export As with Content Credentials set to Publish to Content Credentials cloud. This preserves C2PA provenance headers against metadata stripping. If your image only used minor generative adjustments, Meta will not label it automatically; you must manually enable the AI label toggle on the final post sharing screen.
Diagnostic Snapshot
| Condition | Ingestion Behavior | Automated Label Applied? |
|---|---|---|
| Pure Text-to-Image Generation (Firefly/Midjourney) | C2PA / IPTC flags full synthetic generation | Yes (Automated) |
| Generative Fill (Minor Retouching / Cleanup) | C2PA records generative tool as secondary edit | No (Classified as AI-assisted, not AI-generated) |
| Saved via “Save for Web” or Legacy Tools | JUMBF and IPTC metadata blocks stripped | No (Provenance metadata missing) |
| Uploaded via Third-Party Schedulers | Intermediate API re-encoding scrubs headers | No (Requires manual post-level tagging) |
Diagnostic Path: Why the Automated Tag Failed
Use this sequence to isolate why Meta’s ingestion engine did not apply the badge:
Was the image generated or modified using an AI engine?
│
├─► NO: The platform correctly skipped the label.
│
└─► YES: Inspect the file's export and metadata structure.
│
├─► Did you use a legacy export routine (Save for Web / screenshot)?
│ └─► Metadata was stripped before upload. The ingest parser found no markers.
│
├─► Was generative AI used only for minor repairs (Remove Tool / small Gen Fill)?
│ └─► Meta's threshold criteria ignores minor inpainting. Manual tagging is required.
│
└─► Was the file uploaded via desktop browser, mobile app, or scheduler?
└─► Some third-party schedulers strip C2PA containers via automated compression.
Understanding Meta’s Ingestion Criteria
Meta does not evaluate the raw visual contents of an image to decide if it is AI-generated. Instead, its systems scan for standardized industry metadata established by the C2PA (Coalition for Content Provenance and Authenticity) and IPTC photo metadata standards.
1. Inpainting vs. Full Synthetic Generation
Meta distinguishes between assets that are completely synthetic and those that are human-captured photos with minor generative retouching.
- Full Generation: A text-to-image prompt (e.g., Adobe Firefly standalone, Midjourney, DALL-E) creates an asset where 100% of the pixel data is synthetic. Meta flags this automatically.
- Minor Edits: Using Photoshop’s Generative Fill to remove a background distraction, extend a canvas border by 5%, or patch a blemish creates a composite file. The C2PA manifest records that a generative model was used, but Meta’s parser treats it as an edit rather than a synthetic image, bypassing the automated label. For details on how Adobe tracks these changes, see Why “Generative AI” is Tagged Even After Manual Edits.
2. Local File Stripping
If your file was routed through intermediate editing utilities, chat messaging apps, or legacy export dialogs, the C2PA JUMBF container was likely stripped. Without that container, Meta’s servers read the file as an unauthenticated standard JPEG or PNG. To understand how platforms handle these blocks, review Troubleshooting “Provenance Not Found” in Social Media Uploads.
3. Stripping by Third-Party Social Schedulers
Social media management platforms (like Buffer, Hootsuite, or Sprout Social) frequently optimize images on their own servers to ensure compliance with API size limits before pushing them to Instagram or Facebook. This optimization step routinely discards non-standard metadata, severing the C2PA chain before the file reaches Meta.
How to Ensure Proper Attribution
Step 1: Verify the C2PA Manifest Before Uploading
Confirm that your image actually contains the cryptographic AI assertion before you upload it:
- Open a browser and visit the verification portal at How to Verify an Image Using the Adobe Verify Website.
- Upload your exported
.jpgor.png. - Check the Digital Source Type or Ingredients section.
- If it does not list “Trained Algorithmic Media” or “Synthetic Media,” the AI marker was never written to the file.
+-------------------------------------------------------------+
| Adobe Verify Manifest Check |
| |
| Digital Source Type: compositeWithTrainedAlgorithmicMedia |
| Issued By: Adobe Inc. |
| Status: Valid C2PA Signature |
+-------------------------------------------------------------+
Step 2: Use Modern Export Methods in Photoshop
Do not use “Save As” or “Save for Web (Legacy)” if you want to preserve AI metadata tags:
- Go to File > Export > Export As…
- In the right-hand panel under Content Credentials, ensure the setting is set to Publish to Content Credentials cloud or Attach to files.
- Confirm that the export summary includes generative assertions. If your settings prevent this, consult Why “Save As” Strips Credentials vs. “Export As”.
Step 3: Manually Apply the AI Label on Mobile
If your edits fell below Meta’s automated threshold, but platform community guidelines or local regulations require disclosure:
- Open the Instagram or Facebook app and prepare your post.
- On the final caption screen, scroll down and tap Advanced settings.
- Locate the Add AI label toggle.
- Turn the switch to On, then return to the main screen and tap Share.
Hard Stops and Policy Limits
- Regulatory Compliance: Platforms in certain jurisdictions require disclosure of realistic synthetic media representing public events or people. Do not rely exclusively on automated metadata parsers if local law demands disclosure; apply the manual tag.
- Anonymized Metadata: If you purposely anonymized your export, you may have stripped the specific tool assertions needed by Meta’s parser. Review Why “Anonymized” Credentials May Still Flag Your Work as AI.