How to Make a History Lesson Video Students Will Watch
Students watch history videos that open on a problem, follow people who want something, and stop before six minutes. Here is the structure, a full scene list for the Trojan horse, and how to fold the 'how do we know' question into the story instead of bolting it on.
By openCanviz • October 11, 2026
8 min read
A history lesson video that students actually watch has four things: it opens on a problem rather than a date, it follows people who want something and are in the way of each other, it turns on a moment of choice, and it ends before six minutes. Write it as a story with a question in the middle, then use the last minute to ask how we know any of it. That last part is what makes it history rather than storytelling. Keep the visuals drawn and labelled rather than dramatised, pause the video at least once for students to predict what happens next, and they will remember the content and the reasoning.
Why most history lesson videos lose the room
The usual history lesson video opens with context. "In the 12th century BC, the Bronze Age kingdoms of the eastern Mediterranean..." By the second sentence half the class has decided this is background noise.
The problem is not the content. It is the order. Context before stakes asks students to hold facts with nowhere to put them. Give them a person with a problem first and the context becomes something they need, because it explains the problem.
There is also a length problem. In a well-known study of 6.9 million video sessions on edX, Philip Guo and colleagues found that median engagement time topped out at around six minutes regardless of how long the video was. Students did not watch a twelve-minute lecture for twelve minutes. They watched about six and left. That matches what most teachers see on their own analytics. If the lesson needs more time, make two videos.
The four-part structure
| Part | Share of the video | What it does | Trojan horse version |
| The problem | About 15% | A person or group is stuck, and the viewer sees why | Ten years of siege, Troy's walls have not fallen, the Greeks are running out of patience |
| The plan | About 35% | What they try, who opposes it, what could go wrong | Odysseus's idea, the hollow horse, the fake retreat, Sinon's story |
| The turn | About 25% | One decision that changes everything, ideally one students can argue with | The Trojans debate the horse, Laocoön warns them, they bring it in |
| How do we know | About 25% | Where the story comes from and how far to trust it | Homer mentions it, Virgil tells it in full, archaeology finds a real Troy but no horse |
The percentages are a guide, not a rule. The point is that the problem is short, the middle is the longest, and the source question is not a footnote. A quarter of the running time sounds like a lot to spend on "how do we know", but it is the part that teaches historical thinking, and students find it more interesting than you would expect because it reframes everything they just watched.
A full scene list: the Trojan horse in five minutes
At about 150 spoken words a minute, five minutes is around 750 words of narration. Here is how it splits across scenes, with the line that opens each one.
- The walls (40 words). "For ten years, a Greek army has camped outside the city of Troy. For ten years, the walls have held." Drawing: the city on its hill, tents spread across the plain.
- The cost (60 words). Soldiers dying, ships rotting, the leaders arguing. "Nobody wants to be the king who sailed home with nothing." Drawing: the camp thinning out, a tally of years.
- The idea (80 words). Odysseus proposes a giant wooden horse, hollow, with soldiers inside. Drawing: the horse built up stroke by stroke, a cutaway showing the hidden men.
- The trick (90 words). The Greek fleet sails out of sight. One man, Sinon, stays behind and tells the Trojans the horse is an offering to the goddess Athena. Drawing: empty beach, a single figure, a speech bubble.
- Pause point (20 words). "Stop here. You are a Trojan. Do you bring it inside? Write down one reason for and one against." Drawing: the horse at the gates, a question mark.
- The warning (80 words). The priest Laocoön says he fears the Greeks even when they bring gifts. Drawing: the Trojans split into two groups, arrows pointing different ways.
- The decision (90 words). They pull the horse into the city and celebrate. That night the soldiers climb out and open the gates, and the fleet, which had only hidden, returns. Drawing: the gates opening, the city burning.
- Where this comes from (130 words). The Iliad, Homer's poem about the war, ends before the horse appears. The Odyssey mentions it in passing. The full story, with Sinon and Laocoön, comes from Virgil's Aeneid, written in Latin around 700 years after Homer and more than a thousand years after any war. Drawing: a timeline with three labelled texts and a large gap.
- What we can find (100 words). In the 1870s, Heinrich Schliemann dug at Hisarlik in modern Turkey and found the ruins of a city built and rebuilt many times. Many archaeologists accept it as Troy. Some layers show destruction by fire. None show a horse. Drawing: a cross-section of layered cities, one layer marked with burn marks.
- The question to leave them with (60 words). "A real city, a real destruction, and a story written down centuries later. Which parts would you call history?" Drawing: three boxes labelled evidence, tradition, invention, with the story's parts sorted between them.
That last scene is the homework, or the first ten minutes of the next lesson.
For comparison, here is a two minute doodle version of the same story made with openCanviz: the siege, Odysseus's plan, Sinon, Laocoon's warning, the night attack and a closing scene on the sources and the excavation at Hisarlik. It is shorter than the five minute plan above and has no pause point, which is the first thing to add if you use it in class.
Write people, not periods
The single biggest change you can make to a history script is to put a named person in almost every scene. Not "the Greeks decided" but "Odysseus proposed". Not "the Trojans were suspicious" but "Laocoön warned them". Students follow people. They do not follow abstractions.
This does not mean inventing feelings or dialogue for real people. For a legend like the Trojan horse, the sources give you the speeches. For real history, quote what survives. A single line from a letter or a speech, read aloud, does more than three sentences of summary. Where nothing survives, say so: "we do not know what he thought, but we know what he did next."
Choose drawn scenes over dramatised ones
For a history lesson, a drawing that builds as you narrate has two advantages over generated period imagery or reenactment footage. It focuses attention on what you are saying, because the drawing appears with the words. And it does not make claims you did not intend. A generated image of a Bronze Age city will show the wrong clothes, the wrong walls and the wrong ships with complete confidence, and students will remember the picture over your correction. The trap is covered in more detail in how to make a history explainer video, which is written for students building their own.
Whiteboard style suits most history lessons. The painted style works well for the opening scene of a story, where you want atmosphere more than accuracy, as long as everything that carries a claim is labelled.
Make students do something halfway
A video watched straight through is a video half-forgotten by the next lesson. Build in one pause point, the way scene 5 does above, and ask for a prediction or a decision. It costs twenty seconds of running time and turns the second half into a test of what the student guessed.
Other pauses that work in history:
- Predict the consequence. "The treaty has just been signed. What do you think happens to the border towns?"
- Spot the bias. Read a short source and ask who wrote it and what they wanted the reader to believe.
- Rank the causes. Show three causes on screen and ask students to rank them before the narration does.
Make it
- 1
Write the problem first
One or two sentences: who is stuck, and why it matters. If your first line contains a date, move the date to the second line.
- 2
Name a person in every scene
Go through the draft and replace each group noun with the person who acted, where the sources allow it.
- 3
Add one pause point
Put it just before the turn, and ask students to predict or decide. Write it as its own short scene so the video holds on it.
- 4
Write the how do we know section
Name the sources, their dates, and what archaeology or other evidence adds. Give it a quarter of the running time.
- 5
Paste it into openCanviz and keep your wording
Set the length to five or six minutes and choose whiteboard style. Check every name, date and place label on every scene, and fix any that are wrong in the editor.
- 6
Watch it once as a student would
If any scene runs longer than 30 seconds with nothing new appearing, split it or cut it.
If you teach a unit as a series, keep the same drawn characters from video to video so students recognise Odysseus in the next episode. See how to keep the same character across a video series.
Common questions
Is it fine to teach a myth like the Trojan horse in history? Yes, and it is a good way to teach how historians work. The story is a legend, the city is real, and the gap between them is the lesson. Be clear in the video about which is which.
How long should a history lesson video be? Five to six minutes for a single story or a single question. That is about 750 to 900 words of narration. A topic that needs more should become two videos, each with its own problem and its own turn.
What about difficult topics like slavery or genocide? Drop the pause-point games and the clever hooks. Keep the structure (people, choices, evidence) but use survivor testimony and primary sources, and choose a plain, serious visual style. A drawn diagram is right for explaining a system. It should never make suffering look decorative.
Can students make these instead of me? Yes, and it is a strong assessment task, because writing the script forces them to choose what caused what. Give them the four-part structure and the requirement to name their sources on screen.
Move the date to line two
Take the history video or lesson you already have, find the first sentence, and rewrite it so it names a person with a problem. Put the date in the second sentence. Then paste it into openCanviz and see how the opening scene changes. It is free to start.
Turn any concept into an animated explainer
Type an outline, get a narrated, animated whiteboard video in minutes. No design skills, no timeline scrubbing. Free to start.
Keep reading
A home-made nursery rhyme video for a toddler should be slow, short and spoken, with one calm picture per line and the rhyme said twice so a child can join in. How to choose a traditional rhyme, script it, draw it, and use it in a way that fits the screen time advice for under-fives.
A good science video for young children answers one question they actually asked, in two or three minutes, with a simplification that is never false, and ends by sending them off to try something. A worked example on why the sky is blue, with the script, scenes and a kitchen experiment.
A child's birthday video works best as a one to two minute story with the child at the centre: their name, their age, the animals or things they love. A practical plan with a worked animal birthday party script, a scene list, and the privacy checks to make before you share it.
A homepage explainer has to work muted, make its point in the first five seconds, and not slow the page down. Here is the one-diagram structure for a 60 to 90 second video, the placement and embed settings that matter, and how to tell whether it is helping signups.