Runware · seed reproducibility

One identical Runware request, sent 9 times

The exact same Runware call — same model, prompt, reference, same seed 2439154 — sent 9 times across three separate sessions (Batch A / B / C below). Each frame shows its phash fingerprint (bottom-right).

[{ "taskType": "imageInference", "model": "google:4@3", "seed": 2439154, "width": 1536, "height": 2752, "outputFormat": "PNG", "positivePrompt": "<identical 6701-char string>", "inputs": {"referenceImages": ["<same ref>"]} }]  — byte-identical every call (wire-verified)

Batch A · main artifact

454e56277d2e454e56277d2e
ccade94fcc9cccade94fcc9c
b3804e30fb83b3804e30fb83

Batch B · backend probe

acbaab2edae1acbaab2edae1
5f67577299915f6757729991
dc04e7d6efe2dc04e7d6efe2

Batch C · fresh, just now

3ec38874d80c3ec38874d80c
29da77cee89f29da77cee89f
5ba6df4c4c0c5ba6df4c4c0c

Provider Runware, model google:4@3 (Nano Banana 2 / Gemini 3.1 Flash Image). Batch A = main 5-provider comparison, B = same-seed backend probe, C = generated fresh for this panel. Same request + same seed throughout. Click any frame to enlarge.

zoom