Nearly every explainer you have seen is one of six styles: diagrammatic motion graphics, screencast, character animation, whiteboard, 3D, or kinetic typography. The right pick depends on what has to be on screen for the viewer to believe you — a system, a screen, a person, an object, or a sentence. Every style also has a cheap version, so the second question is what the cheap version of your pick looks like and how you will avoid it.
We make diagrammatic videos built from the product's real UI, intercut with screen recordings, so that is our lens, and we will say plainly when the other styles are the better call. The same product runs through every style below: an invoicing tool where you draft an invoice, send it, watch it move from sent to paid, and chase an overdue list.
Diagrammatic motion graphics
A diagrammatic video draws the product as a system of blocks, panels, tables, and flows, and animates data moving through the structure: a draft invoice becoming a sent one, the sent one flipping to paid as money arrives, the overdue list shrinking as reminders go out. The style earns its place whenever the pitch is that parts interact — pipelines, workflows, APIs, integrations — because when two surfaces change in sync, the viewer reads "this did that" without a single label.
The cheap version: every concept gets its own color and none of the colors mean anything, chips float beside the diagram connected to nothing, the dashboard on screen is one the product does not have, and the frame resets after every scene so nothing accumulates. The honest version animates the product's real structure with real values, uses one accent color like a flashlight, and lets a surface visibly fill as the video progresses (the full failure catalog).
Cost sits in the middle of this page's range; honest numbers, including ours, are on the pricing page.
Screencast
A screencast is the real product, recorded, then cut, zoomed, and paced. Its job is proof and procedure: tutorials, onboarding, docs, feature announcements, every page whose visitor is asking "show me the actual thing." The invoicing tool's setup flow and send-an-invoice procedure should always be this style, because a diagram earns nothing in a walkthrough of a screen the user will operate themselves. It is the cheapest style here and the only one a team can credibly produce in-house this week.
The cheap version is raw, real-time capture: a cursor drifting across a full screen for four seconds, forms filled at typing speed, nothing pointing anywhere, the viewer's eye hunting. The fix is ruthless editing — cut the dead time, zoom into the region that matters, pace to the lesson instead of the software. The remaining limit is conceptual: a recording cannot teach an idea the viewer has no slot for yet, which is why screencasts pair well with a short animated open (product demo vs. explainer video).
Character and cartoon animation
Character animation tells the product's story through people: an illustrated freelancer drowns in unpaid invoices, the product arrives, her week visibly improves. The style carries emotion and situation, which fits products whose pitch is a human scenario rather than a mechanism — HR tools, insurance, health apps, consumer services. When the buyer needs to see themselves in the video, a character does that in a way a diagram never will.
The cost range is the widest of any style. Custom character work usually runs well above $10,000 and is worth it when the character becomes a brand asset. Template character work costs a tenth of that and looks like it: the stock figure shrugging at a laptop, the same flat character that appears in your video, a dentist's ad, and a crypto pitch. For software products, cheap character animation is the worst value on this page, because it costs real money and communicates "template." Fund the custom version or pick a different style.
Whiteboard
A whiteboard video shows a hand drawing sketches while a voiceover explains — a format that boomed in the early 2010s. It suits long-form verbal explanation for non-technical audiences (parables, step-by-step arguments, educational sequences), because the drawing hand creates a mild "what is it drawing?" pull that fits narration-heavy content. It is also cheap; template tools produce these nearly automatically.
That automation is the problem: the style has one move, and the move is identical in every video, so the format signals "explainer template" before your script gets a word in. In our experience it is the style most likely to make a modern software product feel dated. It remains fine for a school, a nonprofit, or a narrated essay, and wrong for a product that wants to look built this decade.
3D animation
3D renders three-dimensional scenes: objects, devices, environments, cameras moving through space. It exists for physical things — hardware, wearables, robotics, logistics — and any story that is spatial, like how a device fits in a hand or what is inside the casing. Done properly it is the most expensive style here; budget five figures for work that holds up.
It also looks cheap faster than any other style, because 3D quality lives in lighting and materials. Mid-budget 3D, with plastic surfaces and weightless motion, reads worse than a clean 2D video at a third of the price, so fund it fully or choose another style. For software with a screen-based UI, 3D is usually spectacle without explanation — a rotating laptop tells nobody what the invoicing product does. We do not make 3D; if your product needs it, hire a shop that specializes in it.
Typographic and kinetic text
A typographic video makes the words themselves the visual: statements animate on and off screen, timed to the voice or the music. When the message is one strong sentence, typography gives it weight, which is why the style works for manifestos, brand statements, launch teasers, and quote-driven social clips. It is the fastest style to produce and among the cheapest.
It looks cheap the moment it tries to explain. If the screen prints what the narrator says, the words compete with the voice and both lose — the tell is that you could watch muted and read the entire script. Kinetic text has no way to show a mechanism, a screen, or a result: a typographic treatment of the invoicing product could declare "get paid faster" with conviction and could never show an invoice getting paid. Strong for a twenty-second statement, weak for the ninety seconds where you explain what the product does.
The six styles in one table
| Style | Best for | Typical cost | The cheap tell |
|---|---|---|---|
| Diagrammatic | Software systems, workflows, APIs | Mid-range (numbers) | Rainbow colors, floating chips, invented UI |
| Screencast | Proof, tutorials, onboarding | Lowest, in-house possible | Real-time pacing, no zooms, a hunting eye |
| Character | Human-scenario products, brand emotion | $3,000–$25,000+ | Stock figures shrugging at laptops |
| Whiteboard | Narrated education, non-technical | Low | The style itself, in 2026 |
| 3D | Hardware and physical products | Five figures, done right | Plastic lighting, weightless motion |
| Typographic | Manifestos, teasers, social clips | Low | Muted video reads as a script |
How to choose
The deciding question is what must be on screen for the viewer to believe you.
- Pick diagrammatic when the proof is a system doing something. Add screencast beats for the moments that need to be visibly real.
- Pick screencast when the proof is the interface itself. Then edit it hard, because the editing is the style.
- Pick character when the proof is a person's situation. Fund it properly or pick something else.
- Pick 3D when the proof is a physical object. The same funding rule applies.
- Pick typographic when the message is one strong sentence. Keep it to the length of the sentence.
Style matters less than it seems, though. Across our produced videos, the failures that killed drafts were almost never style choices; they were structure choices — no single idea, invented surfaces, dead pacing. A well-structured video in a modest style beats a gorgeous style wrapped around nothing (what makes a good explainer video).
FAQ
Which style is cheapest? An edited screencast, then typographic. Match the style to the job first, though, because a cheap style that cannot show your product's value is expensive at any price.
Can I mix styles? Yes, and the best software explainers usually do: animate the concept, record the live product for the proof moments. Switching visual languages scene to scene without a reason reads as indecision.
What is the right style for a SaaS product? Diagrammatic with screencast beats, in almost every case. A SaaS product's value is a system and a screen, so it needs the two styles that can show systems and screens.
Does the style matter more than the script? No. Style only decides how the video looks in a paused frame. Whether anyone understands it comes from structure, so fix the one idea, the pacing, and the real product truth first.
When you're ready, send us your product's URL. We cut twenty short videos of it, and you keep whichever ones earn a full build.