Glossary

A1111 parameters: the record behind “PNG info”

A1111 parameters is the plain-text generation record that the AUTOMATIC1111 Stable Diffusion web UI writes into a PNG text chunk named parameters, or into EXIF UserComment for JPEG and WebP, holding the prompt, an optional negative prompt and a settings line with steps, sampler, CFG scale, seed, size and model.

Controlled example PNG file that carries this record: Saved prompt found

parameters-tEXt.pngPNG file · controlled example

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

Saved prompt found

The generator wrote its settings into the file.

Prompt, negative prompt, seed, sampler and model are read word for word, with the field they came from.

Open the prompt extractor →
Saved prompt 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.

The layout

The record is one text block: the prompt, then a line beginning “Negative prompt:” if used, then a settings line that starts with “Steps:” and “Sampler:” and continues with comma-separated fields such as CFG scale, Seed, Size, Model hash, Model, Denoising strength and Schedule type. Extensions add their own fields. The web UI’s PNG info tab reads the same record back, and Civitai and similar galleries parse it. Fooocus can write the same scheme when configured.

It is unsigned text and can be edited with any tool.

How isGenAI reads it

isGenAI requires the settings line to be present and well-formed before treating the text as a record, splits prompt and negative prompt exactly, and reads seed, steps, sampler, scheduler, CFG scale, size and denoising strength into structured settings. For JPEG and WebP it decodes the UTF-16 UserComment that piexif writes, accepting either byte order with a fatal decoder so a corrupted comment is refused rather than mangled. The AUTOMATIC1111 guide shows a real example.

What it proves

A valid record proves that a compatible tool wrote those parameters into this file. isGenAI reports it as a declaration of moderate strength; it does not identify the person who generated the image.

How to use this term when checking a file

  1. Upload the original file to the AI image detector or the tool named on the page.
  2. Find the finding that uses this term under “How we checked” and read the source field it names.
  3. Weigh it by kind: a signed record, a declared field, a saved prompt and a matching copy are different strengths of evidence.
  4. Remember that absence of a record is not evidence of a human author.

Read the AUTOMATIC1111 guide

Frequently asked questions

Where does AUTOMATIC1111 store the prompt?

In a PNG text chunk named parameters, or in EXIF UserComment for JPEG and WebP, per its feature documentation.

How do I read A1111 PNG info online?

Upload the original file to isGenAI’s image prompt extractor; it shows the prompt, negative prompt and settings as saved.

Why was my parameters record refused?

The settings line was missing or malformed, the chunk failed its checksum, a duplicate key existed or the comment’s encoding was invalid.

Can a parameters record be faked?

Yes. It is plain text. isGenAI reports it as a declaration, not as a signed proof.

Sources

Definitions follow the published standards linked above; the isGenAI behaviour described is the deployed checker as of October 2026.