A storyboard template shows what the shot should look like. A shot list tells the crew how the shot will be captured. You usually need both, but they shouldn't duplicate the same work.
If you need the blank planning page first, download a template:
| Template | Download |
|---|---|
| 4-panel storyboard | |
| 6-panel storyboard | |
| Dialogue storyboard | |
| Vertical video storyboard |
The short difference
| Document | Main job | Best question |
|---|---|---|
| Script | what happens and what is said | What is the scene? |
| Storyboard template | what the viewer sees | What does this shot communicate? |
| Shot list | how the crew captures it | What do we need to shoot? |
The storyboard owns visual intent. The shot list owns production execution.
What belongs in a storyboard template
Put visual and story information in the template:
- panel sketch or generated frame;
- action;
- dialogue or sound cue;
- shot size;
- camera angle;
- camera movement;
- rough duration;
- continuity note;
- visual priority.
The template should answer what the viewer learns from the shot.
What belongs in a shot list
Put production information in the shot list:
- shot number;
- scene number;
- setup;
- lens or focal length if known;
- camera support;
- movement gear;
- location;
- cast required;
- props;
- estimated time;
- special notes.
The shot list should answer what the crew must prepare.
Where teams go wrong
Teams waste time when they turn both documents into the same table.
If the storyboard template has no image and only shot numbers, it is a weak shot list. If the shot list repeats every dialogue line and sketch note, it becomes hard to schedule. Keep the jobs separate.
How to move from template to shot list
Use this handoff:
- Fill the storyboard template with visual intent.
- Mark the shot size, angle, and movement.
- Add continuity notes for props, wardrobe, and location.
- Convert each panel into a shot-list row.
- Add production details only after the visual choice is approved.
Example:
| Storyboard panel | Shot-list row |
|---|---|
| Insert of wet key on table; elevator bell in distance | Shot 12B, insert, table prop, macro/close lens, static tripod, key must be wet |
The storyboard gives the why. The shot list adds the how.
What Story2Board can automate
Story2Board can help bridge the two documents because the storyboard already stores structured fields. A generated panel can carry action, dialogue, shot size, camera movement, duration, narrative purpose, and notes. That means the shot list can be derived from the board instead of rewritten from scratch.
But the creator still has to approve the intent. No tool should decide that a close-up is right just because the template has an empty box.
Which one should you start with?
Start with a storyboard template when the scene is visually uncertain. Start with a shot list when the blocking is already known and the main job is scheduling.
For most creative work, we start with the board. Seeing the shot reveals whether the list makes sense.
Read the broader storyboard vs shot list guide, then use shot lists and storyboards for the production handoff.