AI storyboard contact sheet: organize proposed shots before producing motion
An AI storyboard contact sheet is a planning artifact. It should help a team discuss shot order, camera intent, and missing information before producing motion. It does not prove that separately generated images will become a continuous sequence or preserve a character perfectly between shots.
Genace can produce image candidates for individual boards. Sheet layout, annotations, sequencing, and later editing belong to your own production workflow. Treat every frame as a proposed shot with an identifier rather than as an interchangeable picture.
Start with a narrative beat list
Write the purpose of each shot in one sentence. A product demonstration might establish the object, show a detail, show an action, and finish with a clear closing view. Record what the viewer must learn at each step.
Assign shot numbers before requesting images. Keep the number stable when a candidate changes so discussion does not depend on folder order. A replacement for shot three should remain shot three, with a new candidate revision beneath it.
Define a board record
| Field | Example purpose | Review question |
|---|---|---|
| Shot number | Sequence identity | Is this the intended position? |
| Beat | Information delivered | Does the image support it? |
| Camera intention | Wide, detail, or movement idea | Is the view plausible? |
| Continuity notes | Object orientation and setting | What must match later? |
| Candidate reference | Job and output index | Which exact image was selected? |
| Review status | Proposed, revised, approved | Is it ready for the next stage? |
These are local planning fields, not additional parameters for the generation endpoint. Keep the API request body limited to supported generation inputs.
Build the sheet for discussion
Use a consistent cell size and place shot numbers outside the images. Keep captions legible and avoid letting generated lettering become the authoritative shot description. A simple grid with clear annotations is more useful than an elaborate sheet that hides the sequence.
Review both the sheet and individual frames. The sheet reveals pacing and visual repetition, while the individual view reveals structural defects or unclear action. Neither replaces a written statement of what the shot must communicate.
Mark continuity uncertainty explicitly. A prop that changes shape or an inconsistent lighting direction should become a production note, not a hidden assumption that the video model will solve automatically.
Hand off to motion production
Separate approved story intent from final visual fidelity. When motion clips are produced, link each clip to its board and review it against the beat. A different composition may be acceptable if it communicates the same information and is approved.
Keep rejected boards with concise reasons. If reviewers repeatedly reject a shot because the action is ambiguous, revise the beat description instead of generating endless cosmetic variations.
Acceptance checklist
Check that every board has a shot number, readable beat, source reference, and explicit status. Walk through the sequence aloud, identify missing transitions, and confirm that continuity risks are recorded. Approve the planning document as a plan, not as evidence of a finished continuous video.
See product teaser production, campaign naming, and asset lineage.
Continue with creative workflows
Where these facts come from
- codebase: src/app/api/v1/images/generations/route.ts
- codebase: src/ai/providers/types.ts
- Application-owned workflow recommendations; human review and post-processing are outside the generation gateway
- Editorial keyword hypothesis; search volume not measured