What Is an Animatic? Examples, Process, and How to Make One

An animatic is a storyboard cut to timing, usually with a voiceover and music underneath it, played back as a video. It shows how a piece will unfold in time before a single frame of animation is produced.

It sits fourth in the pipeline: script, storyboard, board-to-timing, animation. Its job is to expose pacing problems while they still cost hours instead of weeks.

That is the animatic definition we work to, and the animatic meaning is the same in any studio that uses the word.

We have built animatics for animation projects since 2015, from thirty-second spots to multi-part patient education series. Every example on this page comes from a finished client production, shown next to the board it came from or the animation it became.

If you have not built the storyboard yet, start with our guide to what a storyboard is, or grab a blank storyboard template.

The difference matters because the two catch different problems. A board catches structural problems: a scene in the wrong place, a step missing, an explanation that arrives before the thing it explains. An animatic catches timing problems: a beat that drags, a line of narration that will not fit the shot it plays over, a transition that lands half a second early.

Both are cheap to change, which is the whole reason to build them. Once animation starts, neither is.

An animatic is not the animation. It is the plan, timed. The panels are storyboard drawings held on screen for their intended duration, not finished frames.

The clearest way to see this is side by side. Below is an animatic for an organ donation awareness piece, and next to it the finished animation built from it.

The staging is the same. The compositions are the same. What arrived later is illustration, color and motion, and none of those decisions changed where a beat starts or how long it lasts.

That is the argument for building one. Every pacing decision in the finished film was made while it was still pencil sketches on a timeline, where changing your mind cost an afternoon.

Animatics do not all look alike, because boards do not all look alike. The three examples below are from different projects at three different levels of finish, each played through as a timed sequence.

The level of finish is a budget decision, not a quality one. A loose pencil board timed against real audio tells you as much about pacing as a detailed one does. Detail buys you certainty about what the finished frame will look like, which is a different question.

Our guide to what a storyboard is covers all five board types and when each is worth the effort.

Not every one of these is pencil. The example below is a color animatic for a Hackensack Meridian Health patient education piece on cancer risk, built in flat color before any animation started.

A color animatic costs more than a pencil one, so it earns its place in two situations: when sign-off needs to happen against something close to finished, or when the piece depends on interface screens and data that have to read correctly. Both were true here, because the middle of this video is a real risk assessment form.

What actually changed between the two was the wording inside the assessment form, which is exactly the kind of thing a color animatic exists to catch before it is baked into animation.

Pacing problems found at this stage cost hours. The same problems found in animation cost weeks, because the fix means re-animating rather than dragging a panel along a timeline.

Review is also more meaningful. People who cannot read a storyboard can watch one of these, so stakeholder feedback arrives against something close to the real experience instead of against a page of drawings. That single change is usually what converts a vague round of notes into a useful one.

It locks the voiceover. Built on the real VO track, it exposes lines that run long or read too fast before an animator builds to them.

And it catches runtime. For eLearning and training, the animatic is where you discover a module runs fourteen minutes when the brief said eight, at a point where cutting it is still easy.

This is the process we follow on client work. It scales down for a thirty-second spot and up for a multi-module series.

1. Lock the script. Every structural change invalidates timing you have already set, so time a script you have stopped rewriting. Our guide to writing a video script covers getting there.

2. Finish the storyboard. The animatic is those panels on a timeline, so the panels have to exist first.

3. Record the voiceover, or a scratch track. A scratch read by anyone in the office is enough. Timing against guessed durations is the single most common way this goes wrong.

4. Lay the panels against the audio. Drop each panel where its narration begins. At this point the piece is already watchable.

5. Set hold durations panel by panel. This is the actual work. A panel that reads instantly holds for two seconds; one carrying a data point holds for five.

6. Add basic motion only where timing depends on it. A pan that has to complete before the next line lands is worth roughing in. Anything else is decoration.

7. Add music and key sound effects. Music changes perceived pace more than almost anything else, so timing judged in silence will not survive contact with a track.

8. Review for pacing, not for art. Say so explicitly when you send it, or you will get notes on the drawings.

9. Revise, then hand to animation with the durations locked.

• Reviewing it for art quality. The drawings are deliberately rough. If you do not say what the review is for, you will get notes on the sketches instead of on the timing.

• Building it before the voiceover exists. Every duration becomes a guess, and the whole thing has to be re-timed once real audio arrives.

• Adding too much motion. It stops being a timing document and becomes a cheap animation, which nobody trusts and everybody critiques.

• Skipping it on short pieces. Thirty seconds has pacing too, and finding the problem during animation costs more than the animatic would have.

• Treating it as a deliverable rather than a decision point. The animatic is where you are allowed to change your mind. Approving it to keep the schedule moving wastes the one stage built for that.

Less than people expect. Any editing software that can hold stills on a timeline against an audio track will do it, and that includes the free tier of most editors. Presentation software with slide timings will get you most of the way for a simple piece.

There is dedicated animatic software, and it is useful if you board constantly. For a team making a handful of videos a year, the editor you already have is enough, and we would not tell you to buy software you will use twice.

If you would rather not build it at all, that is what we do. We can produce an animatic from a storyboard you already have, or handle the whole piece from script through explainer video production.

This is the last point in a production where changing your mind is cheap. After it, every pacing decision is baked into animation that somebody has to redo.

It does not need to be pretty. It needs real audio, honest hold durations, and a review that asks about timing rather than about drawings. Get those three right and the animatic pays for itself on the first problem it catches.