AI image detector by generator

InvokeAI image detector: the metadata record in the PNG

InvokeAI writes a JSON record named invokeai_metadata into each PNG, and isGenAI reads it to show the positive prompt, negative prompt, seed, steps, dimensions, model name and generation mode when the record is complete and consistent.

Controlled example PNG file that carries this record: InvokeAI record found

invokeai-record.pngPNG file · controlled example

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

InvokeAI record found

The app saved a JSON generation record.

Model, prompts and settings are read from invokeai_metadata exactly as stored.

Open the prompt extractor →
InvokeAI record found: where this record sits inside a PNG file and what the isGenAI report says about it. The picture is a code-drawn controlled example that carries this record; download it and check it yourself.

What InvokeAI writes

InvokeAI stores its generation record as a named PNG text chunk, invokeai_metadata, containing the app version, generation mode (such as txt2img, sdxl_txt2img or flux_txt2img), prompts, seed, steps, size and model. Its own import code reads that chunk back to rebuild a gallery, which is the reference isGenAI follows. A separate invokeai_graph record may also be present.

Like every PNG text chunk, the record is unsigned and editable.

How isGenAI validates the record

The checker requires a plausible app version, a recognised generation mode and complete numeric fields before it treats the record as a saved prompt. SDXL records with a style prompt that differs from the main prompt are reported as a workflow rather than one instruction, so no prompt is dropped silently. A partial or multi-prompt record is reported as a saved workflow.

When the record passes, the report shows the prompt, negative prompt, model name and settings, labelled as a declaration of moderate strength.

Sharing and conversion

Only the original PNG carries the record. Conversion to JPEG or WebP in another tool, screenshots and social uploads drop it. The InvokeAI metadata guide shows a worked example with a downloadable file.

Compare the original and a copy with the image metadata compare tool to see which fields vanished.

How to check an image from this generator

  1. Get the original download, not a screenshot or a copy saved from a chat or social feed.
  2. Upload it to the free AI image detector. Files up to 20 MiB in PNG, JPEG, WebP, AVIF or TIFF are read on the server and are private by default.
  3. Open “How we checked” and read each finding with its source field: signed record, declared source type, saved prompt, AI statement or matching copy.
  4. Treat a clean result as “no evidence found”, never as proof that a person made the picture.

Extract the saved prompt

Frequently asked questions

Does InvokeAI add metadata to images?

Yes. InvokeAI stores an invokeai_metadata JSON record, and often an invokeai_graph record, as PNG text chunks; its own import code reads them back.

What does isGenAI show for an InvokeAI PNG?

The saved prompt, negative prompt, seed, steps, size, model name and generation mode when the record is complete and consistent; otherwise a saved workflow.

Is an InvokeAI image detectable after a screenshot?

No. The chunk is gone and isGenAI does not infer origin from pixels. Use the original PNG.

Why is my SDXL InvokeAI image reported as a workflow?

Its style prompt differs from the main prompt, so there are two instructions. isGenAI reports a workflow rather than discarding one of them.

Sources

Vendor behaviour changes. These pages describe what the vendor documents and what isGenAI reads from a file; they do not test every release.