Explainers that
land on the word
Give it a topic or your own script. It writes, narrates, measures where every spoken word actually lands, and generates the animation against those measurements. No manual timing, anywhere.
Built for teacherswho would rather explain than keyframe
0 of 4 cues fired · beat “layers”
For people whose job is making something click
Lecturers
Turn a week's reading into a ninety-second primer students actually watch before the seminar.
YouTubers
Ship the diagram-heavy explainer without spending three days nudging keyframes in an NLE.
Teams explaining themselves
Onboarding, architecture, incident write-ups — the things everyone means to animate and never does.
The idea everything rests on
Audio is the clock
The naive way is to animate first and hope the voiceover fits. Here the order is inverted: narration is synthesized first and becomes the single source of truth. Every word is measured, and both the animation and the captions are written against those measurements.
What the engine measured
- Cue times
- 0 / 4 fired
- Alignment quality
- 96.8%
- Now speaking
- TCP/IP
Nothing here is a guessed run_time. The scene asks the timeline when “TCP” happens and animates to that number. Rewrite a sentence and every cue moves with it.
How it works
You write one sentence. It does the rest.
Five steps, and you can watch every one happen. If something goes wrong it tells you what — in words, not a stack trace.
- 01
It writes the script
Give it a topic and it writes narration to fit the length you asked for. Bring your own script instead and it uses that, word for word.
- 02
It records the narration
The voice is recorded first, on purpose — that recording becomes the clock everything else is measured against.
- 03
It listens back
Every spoken word is timed to the millisecond, so the animation knows exactly when each one lands.
- 04
It animates and renders
Diagrams are drawn against those measurements, one scene per sentence, then rendered at the quality you picked.
- 05
It hands you a video
Narration, animation and captions muxed into one mp4, checked, and dropped in your library to download.
Close the tab if you like. It keeps going without you, and the finished video is waiting in your library.
Why AI video usually looks like slop
Generic AI video tools
- Stock footage loosely related to the words
- Narration recorded first, animation guessed after
- Captions drift a beat behind the voice
- Edit one sentence, re-time the whole video
- You cannot see why it chose anything
Loooped
- Diagrams generated from the actual explanation
- Every word measured before a frame is drawn
- Captions cut from the same measurements
- Edit a sentence, the timing moves itself
- A finished video, not a project file to fix
Describe the thing. Get the explainer.
Start with a topic and let it write the script, or paste your own and keep every word.