The "parameters" chunk explained
A1111-family UIs write a single tEXt chunk called parameters. It has three parts: the positive prompt (first lines), an optional line starting with Negative prompt:, and a final settings line such as Steps: 28, Sampler: DPM++ 2M, Schedule type: Karras, CFG scale: 7, Seed: 1234, Size: 832x1216, Model hash: 31e35c80fc, Model: sd_xl_base_1.0, Lora hashes: "…", Version: f2.0.1. PNGMeta splits this into structured fields so you don't have to eyeball a wall of text.
What you get
- Prompt and negative prompt with one-click copy.
- Seed, steps, sampler, schedule type, CFG scale, size, denoising strength, hires-fix settings, ControlNet blocks.
- Model name + hash, VAE, LoRA hashes and the
HashesJSON used by Civitai to link resources. - The Forge/A1111 version string, useful when reproducing an image on a different install.
JPEG and WebP from the WebUI
If you set the WebUI to save JPEG or WebP, it stores the same parameters string in the EXIF UserComment tag (UTF-16). PNGMeta reads that too — see reading AI prompts from JPEG/WebP.
Send to txt2img / img2img
Copy the fields here and paste them into the WebUI prompt box, then press the ↙ (paste) button — the WebUI parses the same parameters format from the prompt field and fills every setting.
Frequently asked questions
Is this the same as the PNG Info tab in Automatic1111?
Yes — it reads the identical "parameters" chunk. The difference is that it runs in your browser without a running WebUI, and also parses JPEG/WebP EXIF.
Why does the model show as a hash instead of a name?
Older WebUI versions only wrote "Model hash". Newer versions write both. Search the hash on Civitai to identify the checkpoint.
Does it work with Forge, reForge and SD.Next?
Yes. They all write the A1111-style parameters chunk; Forge adds a "Version: f…" tag which PNGMeta uses to label the tool.