AI image-to-video production benchmark
Turn one approved product still into a controlled six-second campaign shot.
Compare Runway, Veo, Kling and Pika using the same licensed image, motion brief and acceptance rules. No quality, speed or value winner is established here; record usable output, retries, editing time and complete cost before choosing.
The evidence table.
Weights describe the proposed evaluation. Unknown or test-pending evidence receives no score and no total. Until every tool has complete evidence, row order is an editorial shortlist—not a performance ranking. Approved user runs remain separate.
Fixed protocol.
- 01Upload the same licensed 16:9 product image.
- 02Use one fixed prompt describing camera movement, subject movement and negative constraints.
- 03Allow three attempts per tool and retain every result.
- 04Record generation time, retries, export limits and final editing minutes.
What counts as usable.
✓ Product identity remains recognisable
✓ No major edge or motion artefacts
✓ Requested camera move is present
✓ Output can enter a commercial edit workflow
Open comparison library →Approved same-task runs
Structured observations make the protocol challengeable. Every submission is moderated; supplier claims and editorial results remain separate.
No approved community runs yet. No completed comparative result is claimed; use the protocol to collect your own evidence.
Test one tool under the published rules.
Report completion, elapsed time, retries, correction time and cost. Upload an output screenshot only when you own it or have permission.
The editorial table is a transparent decision model built from HubAI profile data. Community runs are shown only after moderation and never presented as a controlled HubAI laboratory result.
Editorial disclosure →