Plan Your Screenshot Set Like a Storyboard

There's a familiar way screenshot work goes wrong. You fire up the game and capture whatever looks good, pick the best shots, and bolt captions on at the end. Build a set this way and you tend to end up with two near-identical scenes, a message that's missing entirely, or captions forced to fit whatever happened to be on screen.

Just as you'd storyboard before shooting a video, designing the screenshot set on a single sheet before you capture anything makes both the shooting and the design go much faster. Choosing the one first image is covered in Planning Your First Screenshot; this post is about the storyboard as a tool for designing the whole set.

Why Design Comes Before Capture

Capture first, and you end up choosing from "what got captured." Scenes that happened to be on screen make it into the set instead of the scenes you actually need. Discover a missing scene at the design stage and you have to launch the build again, reproduce that state, and shoot it under the same conditions.

A planning sheet cuts down on that backtracking. With each image's role decided in advance, you also stop two images from saying the same thing. Working solo, the sheet becomes your task list; working with teammates or a freelance designer, it becomes the reference document that keeps everyone looking at the same picture. And months later, when an update means replacing a single image, you can see at once what that image was originally there to do.

The Columns of a Storyboard Table

Too many columns and you wear out filling them in. These six are enough for most games and apps.

ColumnWhat Goes In ItHow to Fill It
Number and stageWhich image this is and which stage of the flow it belongs toMark it as intro, core, expansion or closing
MessageThe one sentence this image should leave with the viewerFill this in before the scene
SceneWhat's on screen and in what stateA concrete state, not a menu name like "main screen"
Caption draftA first version of the copy that goes over the imagePolish later; the direction just needs to be right
PrepWhat it takes to produce the sceneSave file, dummy data, a specific character, hidden UI, and so on
StatusProgressKeep it short: not shot, shot, designed

The single most important rule is to fill in the message column before the scene column. Start with scenes and you fall straight back into the "capture and pick" trap. Decide what you want to say first, then find the scene that shows it best — and keep that order.

The Four Stages: Intro, Core, Expansion, Closing

Treat the set as one short story and each image's role falls into place on its own. The number of images varies from game to game, but the four-stage frame works for most of them as is.

With fewer images, merge expansion and closing into one; with more, add to core or expansion. Stretching the intro to two images is usually a sign that the first-image message isn't fully worked out yet.

Example: A Storyboard for a Hypothetical Cooking Puzzle Game

Here's the table filled in for a hypothetical puzzle game where you match ingredient blocks to complete dishes. The prep and status columns are left out to save space.

Image / StageMessageSceneCaption Draft
1 IntroMatch ingredients and a dish comes togetherThe moment blocks burst and a finished dish lands on the plateMatch it, plate it
2 CoreThe satisfaction of chain reactionsSeveral rows vanishing at once in a chainOne move, a cascade of combos
3 CoreFulfilling customer orders is the goalA customer's speech bubble with their order next to the puzzle boardCook what the customer craves
4 ExpansionRecipes keep growingA recipe book with a mix of locked and unlocked slotsMore recipes the more you collect
5 ExpansionDecorate your own restaurantA restaurant view with swapped tables and decorA restaurant styled your way
6 ClosingEnjoy it in short burstsThe star-rating screen after clearing a stageOne round is all the break you need

The approach is the same for an app. For a hypothetical reading-log app, the intro could be a shelf view with books on it; core, the add-a-book screen and the pages-read log; expansion, reading stats and notes; and closing, a reassuring feature like a widget or backup.

Thumbnail Sketches on Paper

Once the table is full, draw a row of small rectangles on paper, one per image, and pencil in only the big shapes in each. Where the protagonist is, whether the caption sits top or bottom, whether the screen is light or dark — that's plenty, and a minute or two per box is enough.

These sketches reveal what the table can't. Whether every protagonist sits dead center and the set turns monotonous, whether two dark scenes land next to each other, whether the caption position jumps around from image to image — all of it is visible at a glance. Draw the boxes on sticky notes and reordering is easy too.

Questions for Checking the Table

Before you start shooting, run through the table once with these questions.

From Table to Shooting and Production

Once checked, the table becomes your shot list. Group scenes that need the same save file or the same game state by their prep cells and you can shoot them in one batch. For an app, you'll need to prepare fake data to fill the screens beforehand; the principles are in How to Create Dummy Data for Screenshots. After shooting, polish the caption drafts with principles like the ones in Start Captions with a Verb.

At the production stage, move the table's caption drafts into a template and drop in the captured scenes. With a tool like StoreShot, which lets you produce several images from one template by swapping only the caption and image, each row of the table turns directly into one finished image.

A storyboard table isn't a grand document — it's a memo that pairs messages with scenes ahead of time. Make it once and there's less floundering on shooting day, and at the next update you'll have a record that explains which image you're changing and why.

PuffChip Studio Tools