Documentary explainers · portrait 9:16
How to make an animated map video
An animated map video works by revealing one place at a time and giving each one a single surprising fact. Fly between locations rather than cutting, label each with a bold overlay, and let the narration carry the argument. With baz, the Historical Map Animation skill produces this as a narration-led short-form documentary reel — aerial flyover footage, bold typographic pill overlays and a warm editorial palette — built from a subject list and the key facts you supply.
The shortcut: run a skill instead of starting from scratch
A skill is a context file that teaches an AI agent one specific video style — its structure, pacing, typography, motion grammar and sound design. Hand an agent the skill plus your product, and it rebuilds that video for you. The steps below are what the Historical Map Animation skill already encodes, so you can follow them by hand or let the skill carry them.
baz is a library of video skills: context files that teach an AI agent a specific motion-graphics style, so it can rebuild that video for your product, with your brand, from your inputs. Run a skill inside your own coding agent — Claude Code, Codex — or directly in the baz editor.
What you need before you start
Required
- A script — this skill is narration-led and expects one
- The subject list: the places or items you are revealing, in order
- The key facts for each one, with sources
Makes it materially better
- The geographic or contextual relationships between subjects — what connects them
- Aerial or contextual footage, if you have specific locations in mind
- Your channel identity, so the reel matches the rest of your series
How to make an animated map video: step by step
Find the fact that makes people say "wait, what?"
Map videos live or die on the surprise. A tour of five interesting places performs far worse than one genuinely counterintuitive fact explored properly. Lead with the strangest thing you know.
Order the subjects to escalate
Put the second-best item first to earn attention, then build. The final subject should be the strongest — that is what people comment on, and comments are what get the reel distributed.
Write the script before touching the visuals
This format is narration-led: the word timings drive every overlay, label and flyover. A script written after the visuals will not sit properly on them. Write it, read it aloud, cut it to time, then build.
Fly, do not cut, between locations
Moving across the map between subjects gives the viewer a spatial model of how the places relate. Hard cuts between aerials lose that entirely and turn a documentary into a slideshow.
Label with pills, at pace
Bold typographic pill overlays name each place and its key number the moment the narration says it. Keep them short — a place name and one figure. Overlays that need reading compete with the voice.
Verify every fact before it goes on screen
Geography and history content attracts corrections faster than any other format, and a wrong border or date will be the top comment. Check each claim against a real source, and do not let a generated script assert something you have not confirmed.
What the finished video actually contains
Approximate timings for a 45–90 seconds cut. Treat them as a shape to hit, not a spec — the exact durations shift with your script and your music.
| Time | Beat | What is on screen |
|---|---|---|
| 0:00–0:04 | The hook fact | The counterintuitive claim, stated over the first aerial before any setup. |
| 0:04–0:20 | First subject | Flyover to the location, pill overlay names it, narration delivers the fact. |
| 0:20–0:60 | Escalating reveals | Each subsequent subject reached by a flyover, stamped and explained. |
| 0:60–0:80 | The connection | What links them — the point the whole reel was building toward. |
| 0:80–0:90 | Channel outro | Identity resolve and the follow prompt. |
Mistakes that cost you the view
Burying the surprise
Do this instead: Open with it. In a portrait feed you have about two seconds — a slow build to a great fact means nobody reaches the fact.
Hard-cutting between maps
Do this instead: Fly between locations. The movement is what communicates the spatial relationship, which is the only reason to use a map at all.
Overlays too dense to read
Do this instead: A place name and one number. If the overlay needs reading, it is competing with the narration and both lose.
Publishing an unverified claim
Do this instead: Source everything. Geography and history audiences correct errors immediately and publicly, and one wrong border undermines the whole channel.
Ending flat
Do this instead: Save the strongest subject for last. The final reveal is what earns the comment and the share.
Run it from your own agent
Skills are designed to run inside a terminal agent like Claude Code or Codex, against a project you control. The same skill produces the same style whether it runs in your agent or in the baz editor.
npm install -g bazaar.it@latest
# Install this skill into your agent (Claude Code, Codex or Cursor)
baz skill add geographic-enclave-explainer
baz project create --name "Historical Map Animation for my product"
baz prompt "make an animated map video" --stream-json
baz review --summary --json
baz export start --wait --format mp4 --jsonOperations draw from a prepaid balance. See the CLI reference for the full command set.
Common questions
Do I need a script?
Yes. This skill is narration-led and requires a voiceover — the word timings drive the overlays and flyovers. That is a deliberate constraint: the format does not work as a silent reel.
Where does the aerial footage come from?
You can supply your own footage, or work from public-domain and contextual sources. Check the licence on anything you did not shoot, particularly if the video will run as an ad.
Can I use this for non-geographic subjects?
Yes. The grammar — reveal one subject at a time, stamp it, connect them at the end — works for any list-based explainer. The flyover is the geographic version of a transition that could be something else.
Do I need video editing experience?
No. The skill carries the editing decisions — shot order, pacing, type treatment, transitions, sound design. You supply the raw material and the facts about your product; the agent assembles the cut. You review it and ask for changes in plain language.
Can I run this in my own coding agent instead of the baz editor?
Yes. Skills are designed to be run from a terminal agent like Claude Code, Codex or Cursor. Install the CLI with `npm install -g bazaar.it@latest`, then `baz skill add <slug>` to pull the skill into your agent. The same skill produces the same style whether it runs in your agent or in the baz editor.
What does it cost?
baz bills against a prepaid dollar balance rather than a seat subscription — you top the balance up and each operation (generation, voiceover, render, export) draws a listed amount from it. There is no per-seat fee to make a video, and the price of each operation is published.
Can I change the video after it renders?
Yes, and this is the point of doing it as code rather than as a flat render. Every scene is a real component you can edit — ask the agent to re-time a beat, swap a screenshot, rewrite a line, or change the accent colour, and only that part rebuilds. You are not re-rendering from scratch each time.
Will every video from this skill look the same?
The grammar is the same — that is what makes it a skill and not a template. The content is not: your brand colours, typography, screenshots, copy and data all come from your inputs. Reusing one skill across a series is a feature, because episode three lands in the same visual language as episode one instead of being rebuilt from scratch.
Related guides
Pick a skill. Get the video.
Run the Historical Map Animation skill in your own coding agent, or in the baz editor. Usage comes out of a balance you top up, with a listed price per operation — no seat subscription to make a video.