AI image detector by platform

Messenger AI image detector: photo sends versus file attachments

Pictures sent as photos in Messenger are re-encoded for delivery and, as widely reported, arrive without metadata, while a picture sent as a file attachment arrives unchanged, so the file attachment is the only Messenger copy that gives isGenAI something to read.

Controlled example PNG file that carries this record: No record in this copy

without-records.pngPNG file · controlled example

  1. Signature + IHDR
  2. iTXt XML:com.adobe.xmp
  3. tEXt parameters
  4. tEXt prompt / workflow
  5. tEXt invokeai_metadata
  6. eXIf
  7. caBX C2PA manifest
  8. IDAT pixels
  9. IEND

No record in this copy

Screenshots and re-exports often drop records.

A clean copy is not proof of a human author, so the report says what is missing and asks for the original.

Check an image →
Records like these are often removed when a picture passes through Messenger, so the report says what is missing instead of guessing. The picture is a code-drawn controlled example with no records; download it and check it yourself.

What Messenger strips and adds

Messenger belongs to Meta, whose labelling policy applies to Facebook, Instagram and Threads feeds rather than private chats; we found no Meta documentation of AI labels on Messenger images as of October 2026. Photos sent in a chat are resized and re-encoded, and independent reports agree that EXIF and XMP do not survive. Sending a picture as a file keeps the original bytes, with the recipient downloading it rather than seeing an inline preview.

Photos forwarded from Facebook posts into Messenger have been re-encoded at least twice.

What isGenAI shows for a Messenger image

The AI image detector reads the file you upload: a C2PA manifest if one survived, the IPTC DigitalSourceType in XMP, AI statements in metadata, saved prompts in the AUTOMATIC1111, ComfyUI and InvokeAI formats, and matching copies by hash and perceptual fingerprint. A platform copy with none of these returns “no evidence found”, and the report says plainly that absence proves nothing about the author.

A file attachment can carry everything the original had, including a signed manifest or a saved prompt, and is checked like the original.

What to do instead

Ask the sender to attach the picture as a file, or to share it from the generator’s own export. Confirm with the image SHA-256 checksum tool that your copy matches theirs when they can supply a hash.

The WhatsApp and Telegram pages describe the same distinction.

How to check an image from this platform

  1. Note the platform’s own label or credential icon on the post before you download anything; it does not travel with the file.
  2. Ask the poster for the original file, or trace the first upload. A platform download is a re-encoded copy on most services.
  3. Upload what you have to the AI image detector and read the report. A stripped copy returns “no evidence found” honestly.
  4. Use the matching-copy check: a hash or perceptual fingerprint match can tie the stripped copy to an original that still carried records.

Check the downloaded image

Frequently asked questions

Does Messenger remove image metadata?

Photo sends are re-encoded and arrive without EXIF or XMP in practice. A picture sent as a file attachment keeps the original bytes.

Does Messenger label AI-generated images?

We found no Meta documentation of AI labels inside Messenger chats as of October 2026. Meta’s labels apply to feed posts.

Can isGenAI detect AI in a Messenger photo?

A compressed photo usually returns no evidence found. A file attachment can be checked like the original.

How do I get a checkable copy on Messenger?

Ask the sender to send the image as a file rather than a photo, or to share the generator’s original export.

Sources

Where a platform documents its behaviour, the vendor page is linked. Where it does not, the page says the behaviour is reported, not documented.