Guide
Narration Script Template for Video and Audio
A fill-in narration script template for video and audio, with a six-beat structure, a worked two-minute example, and a checklist for writing for the ear.
Free plan with Kokoro voices, scripts up to 1,500 characters · 3-day Pro trial, then $49 once
Direct answer: a narration script template is a beat-by-beat worksheet with one row per moment and four working columns: the spoken line, the visual or action it plays against, a timing target, and a production note for the editor. Write the opening, the body beats, and the close before you polish a single sentence. This guide gives you the fill-in template, a six-beat structure that fits both video and audio, and a worked example you can adapt.
A narration script is the spoken spine of anything heard rather than read: a video voiceover, an audiobook chapter, a course module, a podcast segment, a product demo. The mistake most writers make is treating it like an essay and reading it silently. Spoken language lives or dies on how it sounds at the moment it is said, one line at a time. A template fixes that by forcing you to plan the shape of the narration before you write the words inside it. If your source is a written article you plan to voice, the guide on turning blog posts into audio covers the rewrite a page needs before it can be read aloud; for a full-length book, the audiobook narration guide handles the longer form.
What a narration script template contains
Copy these columns before you write anything. The order matters, because the spoken line depends on the moment it sits against, and the timing depends on the line.
| Column | What goes in it | Rule of thumb |
|---|---|---|
| Scene or timecode | The moment this line belongs to: a scene number, a timestamp, or a slide. | One row per beat. If a row carries two ideas, split it. |
| Spoken line | The exact words the listener hears. | Readable in one breath. Two short sentences, not one long one. |
| Visual or action | What is on screen, or what happens in the audio, while the line plays. | If the line names a control or a step, the picture must show it. |
| Timing target | The seconds the line needs. | Spoken words divided by your pace, plus a pause. |
| Production note | Cues only the editor or narrator needs: emphasis, pause, pronunciation. | Never read aloud. Keep it in a column of its own. |
Keep the spoken line and the production note apart, because mixing them is how a script ends up reading its own stage directions out loud. “Pause here for the reveal” is an instruction; “Now watch what happens” is narration. Both belong in the document, but only the second belongs in the voice. A spreadsheet row can hold both, and so can a document with two labeled fields; the point is that they never collapse into the same line. Microsoft's help page on speaker notes makes the same split for presentations, describing the Notes pane as a box the presenter sees on their own monitor but the audience never sees.
The six beats that give narration its shape
Almost every piece of narration, from a thirty-second ad to a three-minute explainer, moves through the same six beats. The template is just a way of holding them side by side so you can see the whole thing at once.
| Beat | What it does | Example spoken line |
|---|---|---|
| Open | Names the situation the listener already lives in, so they lean in. | You have a script, but the recording still sounds flat. |
| Promise | States the one thing the listener will get by the end. | Here is a structure that fixes the pacing. |
| Setup | Gives the single piece of context the rest depends on. | Start with a beat sheet and one column per moment. |
| Steps | Delivers the working content in order, one idea per row. | Write the spoken line, then the picture it goes with. |
| Turn | Names the limit or the catch, so the claim stays honest. | Some lines read well on the page and still fail on the ear. |
| Close | Ends on one action the listener can take. | Read your lines aloud before you record a single take. |
The beats are a shape, not a script. You still have to write the words. But once the shape is on the page, a writer can see that a rambling middle is really three unsorted Steps, or that a piece has no Turn and therefore overpromises. If you are writing a demo rather than a general explainer, the product demo script template applies the same beats to a software or physical product walkthrough, where every beat has to be provable on screen.
Narration structure for video and audio
This is where a generic template stops being useful, because video narration and audio-only narration are not the same job. Video narration shares the listener's attention with a picture, so the words can point at something the viewer can see. Audio-only narration has no picture, so every line has to carry its own context.
| Decision | Video narration | Audio-only narration |
|---|---|---|
| Show or say | The picture can show the thing; keep the words lean. | Everything must be said, because there is nothing to see. |
| Describing visuals | Name what matters on screen instead of pointing at “this.” | Describe only what the listener needs to picture the scene. |
| Pacing | Leave room for the action to finish before the next line. | Pace is set by breath and sentence length alone. |
| Repetition | Do not read the on-screen text word for word. | Restate the key point once so a listener who drifts can rejoin. |
| Ambiguity | A gesture or a label can rescue a vague line. | A vague line is lost; there is no second channel. |
One rule ties both columns together: redundancy. W3C's guidance on audio and video content recommends against lines that depend on a single sense, such as “attach this to the green end,” and suggests saying “attach the small ring to the green end, which is the larger end” instead. The same habit helps an ordinary explainer. If a line only makes sense while pointing at a screen, it will confuse anyone who hears the audio on its own, and a listener who plays that audio without the picture has no screen at all.
A worked example: a two-minute explainer narration
Here is the template filled in for a short explainer about backing up a photo library. The spoken column is the finished narration; the other columns are planning aids. The row order is the order the beats play.
Scene 1, Open (about 4 seconds) Spoken: Your photo library lives on one drive, and one drive can fail. On screen: a single external drive on a desk. Scene 2, Promise (about 5 seconds) Spoken: Here is a two-step habit that keeps a second copy somewhere else. On screen: two drives side by side. Scene 3, Setup (about 6 seconds) Spoken: Start by deciding which folder is the library. In this example it is the folder called Photos, inside the Pictures directory. On screen: the folder selected, with its path visible. Scene 4, Step one (about 7 seconds) Spoken: Connect the backup drive, open it in the Finder, and drag the Photos folder into the empty space. On screen: the drag from Pictures to the Backup drive. Scene 5, Step two (about 6 seconds) Spoken: Wait for the copy to finish, then check that the folder size matches on both drives. On screen: the two folders shown with their sizes. Scene 6, Turn (about 5 seconds) Spoken: This copies the files once. For a habit that runs on its own, set a repeating backup instead. On screen: the manual copy, then a backup app window. Scene 7, Close (about 4 seconds) Spoken: Make the second copy today, then schedule the next one. On screen: the backup drive, safely unmounted.
Example narration script, fictional product setup
Total the spoken column and you get the planning estimate: about 230 words, or roughly 90 seconds of speech at 150 words per minute before you add pauses and on-screen waits. The example adds around 25 seconds of breathing room across seven rows, which lands close to two minutes. The purpose of the timing column is not to hit an exact number; it is to see, before you record, which row is quietly doing too much work. Scene 4 is the longest line and the one a viewer most needs to watch, which is exactly when the narration should slow down rather than race.
Write for the ear, not the page
Reading silently hides the problems that talking exposes. Run every line through these checks before it reaches a voice.
- Read the line aloud. If you run out of breath, cut it into two lines.
- Write numbers the way you want them said, such as two hundred thirty rather than 230, or check how the voice reads digits.
- Cut lines that only work while a cursor moves, such as as you can see here.
- Name the thing instead of pointing at it: open the Share panel, not click this.
- Give each proper noun one pronunciation note, and reuse the same spelling everywhere it appears.
- Mark deliberate pauses rather than trusting the reader to find them.
- Keep one voice for the whole piece, and describe it once in the notes.
W3C's guidance on writing script content for audio also recommends avoiding jargon, acronyms, and idioms that a listener cannot pause to look up. That is a harder constraint than a written article: a reader who meets an unknown term can search for it, while a listener simply loses the thread. When the same script will also become captions or a transcript, the W3C page on transcripts notes that captions are written to sit beside the picture, so a transcript usually needs the visual information added back, such as on-screen text and speaker names. The script is a starting point, not a finished transcript.
Once the lines are short and concrete, the narration has to be performed. If you are producing a full-length read, the Mac narration workflow covers the handoff from an approved script to finished audio, and the narration voice roundup compares the voices you might pick. For training or e-learning scripts, the training video narration guide covers the wider loop from outline to export.
Turn the script into audio
When the spoken column is final, generate the narration. Murmur is a local-first macOS voice studio for Apple Silicon and Intel Macs running macOS 15 or later that handles text to speech, voice cloning, voice design, and multi-speaker projects, and it runs the models on your own machine. That means no per-character fees and nothing uploaded to a cloud service, which matters when the script contains an unpublished product name or a client's details. Export at a level and format your editor accepts, keep the script and the audio files side by side, and name each file after its scene so a later edit maps to the right place.
Choose one voice before you generate anything and keep it for the whole piece. A voice that changes between scenes reads as a mistake even when the words are identical. Murmur costs $49 one-time, has a free plan and a 3-day Pro trial, and includes a 7-day refund policy. If you are not sure which voice fits, audition two against the same two lines and pick the one you can listen to for the full runtime. The audio export guide explains the difference between an editing master and a delivery file.
When Murmur is not the right choice
Murmur is a Mac app, so if you work on Windows, need live or real-time streaming speech, or want several people editing one project in the cloud at once, a cloud service will fit better. It also does not do speech to text, so it cannot turn a recorded interview into a script. And if a line needs a specific celebrity voice or an emotion a stock generated voice cannot carry, plan on recording a human narrator. Murmur is strongest when you want private, repeatable narration you can regenerate from the same script, line by line.
Frequently asked questions
Sources
- W3C WAI: Audio Content and Video ContentAccessed 2026-10-14
- W3C WAI: TranscriptsAccessed 2026-10-14
- Microsoft Support: Add speaker notes to your slidesAccessed 2026-10-14
Voice your narration script in Murmur
Murmur is a local voice studio for Apple Silicon and Intel Macs running macOS 15 or later. It makes the per-scene narration audio for a script and runs on your own machine. The website edition is $49 one-time, with a free plan and a 3-day Pro trial, and a 7-day refund policy. Listen to the public samples before you buy.
macOS 15+ · Apple Silicon and Intel Macs · Windows beta · 7-day refund policy