When you plan an explainer video, you need to decide how each part of the explanation will appear on screen. A storyboard is a visual plan that pairs the spoken words with the images, actions, and text viewers will see. It helps you spot unclear explanations and production needs before you finish the video.
Start with a working script, then divide it into visual moments and note what changes on screen. For a way to turn that plan into a narrated video, explainroo is a free, open-source kit that lets a coding agent create the script, scenes, and finished MP4 on your computer.
Turn the script into visual moments
First, decide who the video is for and what one idea viewers should remember. Write a working script around that takeaway. You do not need to finalize every word before planning visuals; the storyboard may reveal that a line is hard to show, too dense, or repetitive.
Break the script into visual beats: moments when the viewer needs to see a new action, example, comparison, or idea. A sentence can need several visuals, while several short lines can fit one image. Ask, “What should the viewer see while hearing this line?” This keeps each visual focused on the explanation. Storyboarding guidance for video and explainer-specific advice both emphasize matching each script segment with a useful visual.
For example, the line “Manual invoice tracking creates delays” could show someone switching between email, paper invoices, and a spreadsheet. The next line, “Our tool gathers every invoice in one workspace,” could show those items collected on a single screen. A rough sketch or written description is enough to make the idea clear.
Give each panel the details production needs
A storyboard panel is one planned visual moment, not necessarily one finished frame or camera shot. Use a sketch, screenshot, reference photo, or short description. The level of polish matters less than whether the next person can understand what to make.
For each panel, record the narration and describe what appears on screen and what changes. Add timing when it affects pacing. Note labels, sound effects, and transitions. List assets such as product screens and props. Number the panels so reviewers can refer to a specific moment. Adobe’s storyboard guidance also recommends adding production details when they help explain the planned scene.
A shot list is a separate, practical plan of what needs to be filmed or created. A rough animatic is a timed sequence of storyboard images, often paired with temporary narration. Read the script aloud while looking through the panels to catch lines that do not fit the visuals and moments that move too quickly. For live-action videos, use the storyboard to prepare the shot list. For animation, note the assets to create and the movements to animate. Vancouver Film School’s overview explains how these planning tools serve different purposes.
Review clarity and accessibility
Review the panels in order. Make sure each important line has a visual that clarifies it, each scene supports the main takeaway, and the timing leaves enough room to understand what appears. Cut visuals that distract from the explanation. Research on instructional multimedia supports pairing relevant words with graphics and removing material that does not help convey the message. Those findings do not guarantee results for marketing videos. Mayer’s review of multimedia learning focuses on learning, not sales or conversion.
Plan accessibility during storyboarding. Note where captions are needed, and make sure the narration explains the visual information viewers need to understand the video. In a product walkthrough, name controls and actions instead of saying “click here.” W3C recommends planning captions and descriptions as part of video production, and its guidance on narration describes ways to convey meaningful visual information through audio.
Make the video with explainroo
explainroo uses a coding agent that can run shell commands to turn a description into a narrated explainer or product demo. It works with Claude Code, Codex, Pi, OpenCode, Gemini CLI, and other agents; the project says it works best with Claude Code.
Paste this prompt into your agent, replacing the bracketed topic:
Make me a short explainer video about [your topic]. Use explainroo for it: clone https://github.com/vincentsch/explainroo, read its AGENTS.md and follow the steps.
The agent writes script.md, which contains the narration, and scenes.js, which describes the visuals. A drawing can appear on a chosen spoken word, so the visuals follow the narration. explainroo uses the open voice model Kokoro for English narration, Whisper to mark spoken-word timing, and Chrome to draw frames. The agent checks the result using scene stills, a contact sheet, a layout check for cut-off or overlapping text, and a speech check for mispronounced words. The finished video is an MP4.
You can ask for a product demo and point the agent to the product’s code or website. explainroo can rebuild its screens with matching colors, fonts, and button labels, then show a pointer clicking and typing as the narration explains. It also offers wide, tall, portrait, and square formats, plus six visual looks. See the documentation for setup and options, or watch example videos.
explainroo is free and open source under the MIT license. Optional AI illustrations through OpenRouter cost per image; the coding agent is a separate service with its own pricing. explainroo does not edit existing camera footage or create talking avatars, and it has no drag-and-drop editor. You describe changes to the agent instead.