Check Images and Designs
Upload a PNG or JPG to catch spelling, legibility, and risky-claim issues, plus a directional read on how your audience reacts to the visual.
Studio checks images and designs the same way it checks copy, with one honest split: the mechanical problems it can verify, and the audience reaction it can only estimate. It labels the two differently so you never mistake one for the other.
Upload an image
Add an image with the Product design node, the Upload an image chip on an empty canvas, or by dragging a file in. Studio accepts PNG and JPG up to 3 MB. Anything larger is rejected.
An image node carries the label Visual · benchmark in progress in its header, a reminder that visual reactions are not yet validated on a public benchmark the way survey distributions are.
Two layers, two honesty labels
An image check runs two passes, and they carry different labels because they earn different amounts of trust.
| Layer | What it checks | Label |
|---|---|---|
| Mechanical pre-flight | Spelling in the image text, legibility, and risky claims in the text | Checked fact |
| Audience reaction | How the audience responds to the visual | Visual domain · benchmark in progress |
The mechanical layer is factual: a misspelling is present or it is not, so it is labeled a checked fact with no caveat. The audience-reaction layer is an estimate over a domain iMario has not yet benchmarked publicly, so every one of its findings carries the visual caveat, without exception.
Image variants
If a check finds fixable problems, Studio can generate revised images, each noting what changed. When a winning image is chosen, the results panel states the change directly, for example "What changed: tightened the headline for legibility", alongside the same "Visual domain · benchmark in progress" caveat.
The visual tournament
Image variants are ranked by three reviewers, the same way copy is. Two of them read the image directly, and the third works from a written description of it. The verdict tiers are identical to a copy check: Reviewers unanimous, Reviewer majority, Reviewers split, or Within noise. See How content checks work for the tournament mechanics.
Read every visual verdict with the caveat
The rule is simple: any judgment about how an audience reacts to a visual carries "Visual domain · benchmark in progress", in the node, in the findings, in the results panel, and on the shared results page. Treat those reads as directional. For a high-stakes creative decision, confirm with real people.
Next steps
- Read results and verdicts: where the "Download winning image" action and the visual caveat appear.
- Choose an audience: the audience your visual is judged against.
- Grade your predictions: close the loop with your real numbers once the design ships.
Choose an Audience for a Check
Pick a calibrated, census-framed, or model-estimated audience for your check, or describe your own, and see how each one is anchored and labeled.
Read Results and Verdicts
Understand the Studio results panel: the verdict line, the reviewer ranking, the locked prediction, the winning-copy export, and your three exits.