How to make an AI video with voiceover and burned-in subtitles on Windows (2026)
Guide · · Maciej Głuszak · .md version · Polski
In short: A voiceover video is three layers: text, recorded voice and subtitles burned into the picture. Claude Code can run the whole pipeline while you only approve the script and the subtitle text.
Paste into Claude Code:
Make a vertical 9:16 video with a voiceover. First write a 60-second script and show it to me for approval. After I approve, generate the voice, transcribe it with Whisper, show me the subtitle text for corrections, and after my ok burn the subtitles into the video with FFmpeg.
Updated: · tested on: Claude Code 2.1, Windows 11, FFmpeg 7
A video with a narrator is three layers: text, voice and subtitles. The picture can be a still, a screen recording or a clip from a generator. Below is the way we do it ourselves in Bolek, an AI assistant for Windows built on Claude Code. Unlike the hosted avatar tools that top the search results, only the voice is a paid web service here – assembly and subtitles run on your own computer.
What you need
- an account with a voice service, for example ElevenLabs – it has many languages and can clone your own voice,
- FFmpeg – free, it joins picture, sound and subtitles,
- the Whisper speech recognition model – runs locally,
- Claude Code to chain these steps into one pipeline.
Step by step
- Script. Ask for a text of a specific length. About 150 words is roughly one minute of speech. Read it yourself – the voice repeats every mistake.
- Voice. Paste the text into the voice service and pick a voice. Short sentences and numbers written out as words help, because digits are sometimes read in the wrong language.
- Picture. Prepare a background or clips as long as the recording. Build a cheap preview from still frames first, and only turn the approved preview into expensive clips.
- Subtitles. Whisper turns the recording into text with timing in an SRT file. It gets most words right but mangles names – always read the subtitle text before burning it in.
- Assembly. FFmpeg joins everything. Burn subtitles with a command like this: `ffmpeg -i video.mp4 -vf "subtitles=subs.srt" -c:a copy result.mp4`.
- Check. Watch the finished video on a phone. Make sure subtitles fit the frame and do not disappear too quickly.
Traps we hit
- Lines that are too long. Two lines of about 35 characters read well on a phone; longer ones are cut off at the sides.
- Dangling short words. A one-letter word at the end of a line looks sloppy – break the line before it.
- Non-ASCII characters in paths. Name input files in plain ASCII, otherwise FFmpeg can refuse to work.
- Full path in the subtitles filter. The colon in a Windows path breaks the filter. Keep the SRT file next to the video and pass only its name.
What it costs
The voice and any generated clips are pay-per-use external services. Whisper and FFmpeg are free on your own computer.