Storyboard for social formats
A board for a feed answers different questions than a board for a film screened in a dark room.
What this is about
It has to prove three things on paper: that the opening frames work with the volume off, that the subject survives being cropped by an interface, and that the message still lands for the majority who never unmute. Text becomes a picture element rather than a post-production afterthought, because captions occupy real space and pull compositions off centre. And since the same material usually has to serve more than one aspect ratio, the board carries crop marks that keep the shoot honest about framing instead of leaving that argument for the edit.
The order matters more than the tools. Skip a step and you usually notice two steps later — by which point the fix costs several times as much.
What runs differently here
In planning terms, that means:
- Boards for feeds start with the hook: the opening frames get their own panels, because that is where most viewers decide.
- Interface elements sit over the top and bottom of the picture, so faces, text and logos belong inside the safe area.
- Sound-off is the default state. Every panel needs a note on what the caption or on-screen text is carrying.
- One board, several crops: mark what must stay inside 9:16, 1:1 and 16:9 when a single shoot serves all three.
Step by step
This order gets you there fastest:
- Decide platform and placement before drawing anything, because a feed post, a story and an in-feed ad reward different opening frames and different lengths.
- Board the opening as separate panels: what is visible in the first frames, what the caption says, and why a moving thumb would stop for it.
- Draw the safe zones onto every panel. Interface, captions and profile elements cover the edges, and a subject centred for 16:9 ends up under a button.
- Treat on-screen text as a picture element: sketch where it sits, how long it stays, and what the composition behind it is doing meanwhile.
- Plan the sound-off version first and treat sound-on as the bonus. If the message only survives with audio, the board is not finished yet.
- Note the crop on each panel when the material serves several ratios, so the shoot leaves room around the subject instead of finding the problem in post.
- Keep panels short and numerous rather than few and detailed. A feed edit changes shot every couple of seconds and the board should show that rhythm.
- Check the board against a real phone rather than a wide monitor. Composition and text size read completely differently at the size people actually watch.
Common pitfalls
What most often goes wrong in practice:
- Boarding a 16:9 film and cropping it afterwards, so every wide shot loses its subject to the edges.
- Saving the brand for the end, where a scrolling audience has already left.
- Designing text that only reads full screen, then publishing into a feed where the preview is thumbnail-sized.
With TillyGen
TillyGen boards from the concept and keeps every frame linked to the shot list, so the vertical version and the wide one come out of a single plan.
Change one constraint and the consequences travel through the whole plan: affected shots are flagged, the call sheet is regenerated, and nobody keeps working from yesterday's version.
Frequently asked
How detailed do social storyboards need to be?
Precise at the start, loose in the middle. The opening frames deserve exact panels; the rest can be simple sketches with clear framing notes.
Do we board every cutdown separately?
No. Board the master and mark which panels each short version keeps. Separate boards drift apart and produce shoots that miss half the material.
Where should captions sit?
Inside the safe area and clear of the lower interface strip. Assume the platform will put its own text exactly where you wanted yours.
How long does it take to get started with TillyGen?
A first project takes under an hour to set up. There is no configuration phase in which templates and fields have to be defined before the tool produces anything.
Can the results be exported?
Yes — as PDF for the crew, CSV for downstream systems and through the API for anything automated. The plan stays the source; the exports are views of it.