Conflicting records · Controlled example
A PNG with conflicting saved generation settings
Two parameters records disagree on seed and step count. The reader does not select an arbitrary original prompt.
Which prompt should a reader return when saved records conflict?
The current reader returns no supported saved prompt for this conflict. Both records exist, but one records seed 42 and 20 steps while the other records seed 84 and 30 steps.
How the case was made
We attach a second parameters record to the known reference PNG, changing only the seed and step values in that record. An assertion checks that extraction returns null.

Files and observed output
- parameters-tEXt.png · 13,371 bytes
SHA-256: e76d2af4e6c273e1ba8ca6cf2b5b7885ceda2321bce893f0bb5f9e64ace17c9f - conflicting-records.png · 13,563 bytes
SHA-256: c9b84254ad464f9a3cb73ebceca1d5377d96e09376ff1ee3e234caf0ef0d5f8b
Recorded result
{
"reference": {
"format": "automatic1111",
"prompt": "Controlled example: a paper boat on a blue table",
"negative_prompt": "text, blur",
"recorded_model": "demonstration-only",
"settings": {
"seed": "42",
"steps": 20,
"sampler": "Euler",
"cfg_scale": 7,
"width": 1024,
"height": 768
}
},
"conflicting_records": null
}Observations recorded 2026-09-19 using Node v23.11.0 and sharp 0.35.4. JSON seed values are strings to retain integer precision. A null prompt means the reader did not return a supported saved prompt.
Reproduce this result
- Download the files above and verify their SHA-256 hashes.
- Open the linked isGenAI tool and choose the corresponding file, or the before/after pair for comparisons.
- Compare the returned fields with the recorded output. Different tool versions or altered files can produce different results.
The standalone reproduction script creates the fixture variants and compares bytes and pixels. The complete JSON observations also include parser results. Use the workflow and comparison API examples to inspect downloaded files programmatically.
Read the format guide and its primary sources.
What this result does not establish
No returned prompt is not the same as no metadata. The result applies to this deliberate conflict and this reader's rules; it does not prove tampering or identify an author.
Files and observations: CC0-1.0. Cite this case URL and include its method and limits. Report a reproducibility issue.