To explain a map in a video, decide what single question the map answers, then draw only what that question needs and reveal it in the order the narration mentions it. Start wide so the viewer knows where they are, move in over two or three scenes rather than one dramatic zoom, and let each label appear the moment its name is spoken. Use arrows for movement, shading for extent, and dots for distribution. Leave out every place the narrator does not say aloud. A map on screen is not a reference document the viewer can study at leisure; it is gone in ten seconds, so it has to make one point clearly and then get out of the way.

A map answers a question, so name the question

Most bad map scenes have the same cause: the map was put there because the topic has a location, not because the claim needs one. A detailed political map of Europe behind a sentence about the causes of the First World War is wallpaper. The viewer's eyes go to it, find nothing to do, and the narration loses them.

Before you draw anything, write the question the map answers in one line. Then pick the device that answers it.

If you cannot fill in the first column, you do not need a map. A timeline or a causal chain may carry the claim better. The history explainer guide covers when each of those wins.

Draw less than feels right

A printed atlas map is designed to be read for minutes. A video map is read for seconds, often on a phone. So the rule is harsh: if the narrator does not say it, it is not on the map.

That means a simplified coastline rather than every inlet, no country borders unless borders are the point, no rivers unless a river is the point, and no city you do not name. Students resist this because a bare map feels less accurate. It is the opposite. A map with twelve labels and a narration that mentions three of them leaves the viewer hunting for the right three, and they will often find the wrong one.

The same goes for colour. Two colours plus the outline is usually enough: one for the thing being explained, one for context. Colour on a map should mean something, and if everything is coloured nothing does.

The zoom is three scenes, not one move

The "map that zooms in" is the most requested map effect and the most commonly overdone. A long smooth zoom from space to a street looks impressive and teaches nothing, because the viewer spends the whole move waiting to find out where it ends.

Build the zoom as a sequence of separate scenes instead, each with its own sentence of narration:

1. The establishing frame. The continent or the country, with a small box around the area you are about to visit. One sentence: where we are.
2. The region. The boxed area now fills the screen, with the two or three places that matter labelled. One or two sentences: what is here.
3. The detail. The specific thing: the river mouth, the mountain pass, the city. This is where the actual explanation happens.

The box in the first frame is doing the important work. It tells the viewer where the next frame is before they see it, so when the cut comes they are already oriented. Without it, a cut to a closer map is disorienting, and a smooth zoom is just slow.

Going back out is equally useful and almost never done. After the detail, one return to the wide frame with the new information drawn on it closes the loop: here is the small thing, and here is why it matters at the large scale.

Worked example: why the monsoon reaches Kerala first

Here is a short map sequence for a geography class question, roughly 90 seconds, with the narration written as it would be spoken. Every label is introduced in the sentence that names it.

Notice what is not there: no state borders, no Mumbai, no Bay of Bengal branch (that would be a second video, or a second sequence). The one question is why Kerala gets it first, and everything on screen serves that. Check dates like these against a current source before you hand in; the India Meteorological Department publishes the normal onset dates, and drafts of any kind get them wrong.

Arrows, timing and labels

Give each arrow one job. An arrow means "this moved from here to there". If it also means "this influenced that", the viewer cannot tell which you mean. Keep influence arrows for diagrams and movement arrows for maps.

Number the legs of a route. A trade route or a migration with four legs should draw its arrows in order, one per sentence, and a small number on each leg helps anyone who looks back at the frame. Arrow thickness can show volume, but only if you say so once.

Time labels to speech. A label that appears before its name is spoken is read early and then forgotten. A label that appears after is late. Aim for the label to arrive on the word. In a drawn video this is natural, because the drawing builds while the narration runs, but it only works if your script names places in the same order you want them drawn.

Keep labels horizontal and large. Atlases curve labels along rivers and mountain ranges. On a phone, curved small text is unreadable. Put the label flat, next to the feature, with a short leader line if needed.

The projection trap

Every flat map distorts the globe somehow, and the most familiar one, the Mercator projection used by most web maps, distorts area badly towards the poles. On a Mercator map Greenland looks about the size of Africa. Africa is in fact around fourteen times larger.

This matters the moment your video makes any claim about size. "Russia is enormous" drawn on Mercator is exaggerated. "Canada is bigger than the United States" is true, but the Mercator picture makes the gap look several times larger than it is. If your point is about area, use an equal-area projection (Gall-Peters and Equal Earth are the usual ones) or say on screen which projection you are using. If your point is about direction or route, Mercator is fine, because that is what it was designed for.

A drawn map made from a reference you choose gives you control over this. A map generated from a vague description gives you whatever projection the drawing happened to resemble, usually a squashed Mercator.

When a map needs a key, a scale, or a north arrow

Not always. A north arrow is only worth adding when direction is part of the explanation ("the winds come from the southwest") or the map is rotated from the usual orientation. A scale bar matters when distance is part of the claim ("India runs about 3,200 kilometres from north to south" is easier to feel with a bar). A key is needed the moment you use more than one colour or symbol to mean something, and should be on screen for the whole scene, not flashed at the start.

Checklist before you export

• The question the map answers is written down in one line.
• Every label on screen is a word in the narration for that scene.
• The zoom is two or three scenes, with a box showing where the next frame is.
• Arrows only mean movement, and they draw in the order they are mentioned.
• No area comparison is drawn on Mercator without saying so.
• Every place name is spelled correctly and sits in the right place. Drafted drawings put cities on the wrong side of rivers; check each one against a real atlas.
• The final scene returns to a wider view, so the detail lands in context.

Make it

1. 1

   Write the question and the place list

   One line for the question the map answers, then the three to six places the narration will name, in the order it will name them. That list is your entire label set.

2. 2

   Script the zoom as separate beats

   Write one or two sentences for the wide frame, the region, and the detail, and a closing sentence for the return to the wide view. Name each place in the sentence where you want it to appear.

3. 3

   Paste the script in and draft the scenes

   In openCanviz, paste the script, choose Keep my wording if you want the narration exactly as written, and pick a style. Whiteboard and poster both suit maps because they draw clean outlines and flat labels.

4. 4

   Check every place against an atlas

   Open each map scene and compare it with a real map. Fix any label that is misspelled or misplaced, and redraw any scene that added places you did not name.

5. 5

   Watch it with the sound off

   If the map scenes still make sense from the labels and arrows alone, they are doing their job. If you cannot tell what a scene is pointing at, it has too much on it.

Common questions

Can I use a screenshot of Google Maps? For a class video, a screenshot with attribution is often accepted, but check the brief and the map provider's terms. More importantly, a screenshot carries every road, label and border at once, which is exactly what a video map should not do. A simplified drawn map is usually clearer.

How long should a map stay on screen? Long enough for the narration about it and no longer, typically 8 to 20 seconds per scene. If a single map needs a minute of narration, it is really three scenes and should be split.

What about maps that change over time? Draw the same outline at each date as separate scenes, so the change is a cut between two states rather than a morph. The viewer compares the two frames, which is easier than tracking a moving edge. That is the same idea as a split comparison; see how to explain a comparison in a video.

My topic is abstract. Can a map still help? Sometimes. Concept maps and "maps" of ideas borrow the spatial idea without geography, and they follow most of the same rules: few labels, revealed in order. How to illustrate abstract ideas covers the alternatives.