Videos
Video captions best practices
Good captions are accurate to the word, broken at natural pauses, no more than two lines on a landscape frame, timed for about 160 to 180 words a minute, and placed low without covering faces or on screen text. Those rules come from broadcast subtitling and web accessibility guidance, and they hold for a 20 second social ad as well as a feature film.
Indunil Asanka · Co-founder
7 min read · Published
The best captions are accurate to the word, split into short lines at natural pauses, held on screen long enough to read at about 160 to 180 words a minute, and placed near the bottom of the frame without covering a face, a mouth or text that matters. Everything else, the font, the colour, the animation, is secondary to those four.
The detail comes from two sources that disagree on almost nothing: broadcast subtitling guidance, where the BBC publishes the most complete public rulebook, and accessibility guidance from the W3C and the Described and Captioned Media Program. This post takes their rules and applies them to the short promos, tutorials and creator ads most businesses actually make.
Why captions
WCAG 2.2 success criterion 1.2.2 is Level A, the baseline: prerecorded video with sound needs captions. The criterion exists for people who are deaf or hard of hearing, and the W3C adds people who take in written information more easily than audio. In practice there is a third group, the viewer scrolling a feed with the sound off or in a place where sound is not an option, and social video is built around that viewer.
Captions come in two kinds. Closed captions are a separate track the viewer can switch on and off. Open captions are drawn into the picture and cannot be turned off, which is what “burned in” means. Open captions are the only kind guaranteed to show on every platform and every placement, including ads and reposts. The price is that they are permanent: a typo ships in every copy.
Line length: two short lines, broken at pauses
A caption is read in a glance, so its shape matters more than its font. The BBC limits online subtitles to 68 percent of the width of a 16:9 frame and 90 percent of a 9:16 frame, and 37 characters for broadcast. It recommends a maximum of two lines on landscape and square video and three on vertical, where lines are narrower. The DCMP Captioning Key also prefers no more than two lines per caption.
Where the line breaks is the part most tools get wrong. Both guides say to break at a natural pause, ideally at punctuation, and never between words that belong together: an article and its noun, a preposition and its phrase, a pronoun and its verb.
The fitness app UGC video shows why. Its opening line is “Okay I have twelve minutes a day, that’s it, that’s the whole window.” That is 13 words, too long for one caption. Split at the first comma it becomes two readable captions: “Okay I have twelve minutes a day,” then “that’s it, that’s the whole window.” Split by character count instead, it might break between “the” and “whole window”, which is exactly the break both guides forbid.
Timing: plan for reading, not for speaking
The BBC recommends a subtitle speed of 160 to 180 words per minute and a target minimum of about 0.3 seconds per word, so a four word caption stays up for 1.2 seconds. The DCMP Captioning Key, written for educational media, sets lower ceilings: 130 words per minute for lower levels, 140 for middle and 160 for upper levels.
Check the scripts you have against those numbers. The fitness app ad has three talking beats of 6, 6 and 4 seconds. The first two carry 13 words each, 130 words per minute across the beat, which sits comfortably under the BBC range. The dashboard tour video is a tutorial with 7 second steps; “Break it down by channel; paid is the one that fell.” is 11 words, under 100 words per minute, so a viewer can read the caption and still look at the screen it describes.
When a line is too fast to read, slow the voice or lengthen the scene before trimming words. The DCMP guide also notes a small trick: a caption can borrow about 15 frames before or after the audio without viewers noticing, which helps a short line stay readable.
Placement: low, but never over a face
The DCMP Captioning Key places captions on the bottom two lines, and says they must not cover names, faces, mouths, or text and graphics needed to understand the video. When they would, captions move to the top of the frame, or elsewhere if the top is also busy. The BBC gives the same rule and adds a note for vertical video: subtitles usually sit a little higher, still in the lower third, because faces are generally in the top half of a tall frame.
Two situations make placement hard in short video. Creator ads put a face in the middle of the frame, so a caption that drifts upward can cover a mouth, which lip readers rely on. And offer videos print prices, codes and dates near the bottom, so a caption there can hide the one fact the ad exists to deliver. Decide which text owns the bottom of each scene before exporting. In the fitness app ad, scene 6 prints FREE WEEK with the price after the trial underneath it, so a caption on that scene has to sit clear of both lines, or that scene should carry its message in on screen text alone. For the platform overlays on top of all that, see vertical video safe zones.
Accuracy: automatic is a draft
The W3C is blunt: automatically generated captions do not meet user needs or accessibility requirements unless confirmed to be fully accurate. The errors are not only cosmetic; a missed “not” reverses a sentence.
Accuracy also covers what is not speech. WCAG expects captions to identify who is speaking and to convey meaningful sound effects. The BBC asks for a label when music is part of the action and warns against captioning every trivial sound. A creator ad with one voice needs no speaker labels. A tutorial where a notification sound tells the viewer something happened needs a short label for it.
Names and numbers deserve a second read: product names, prices, dates, codes and street names. The restaurant opening video is narrated in Spanish, and a caption that misspells Calle de Sagunto sends people to the wrong street.
The style rules in one table
The table below the article lists each caption rule with its value and its source, so it can sit beside an edit. The two rows that change most with format are lines per caption and line width: a vertical frame can take three narrower lines, a landscape frame should stop at two.
Common mistakes
- One long caption per sentence. Split it at pauses into captions of two short lines.
- Word by word pop captions for everything. They suit a punchy hook but are tiring across a 40 second tutorial.
- Captions over the price. Move the caption or move the price; never let one hide the other.
- Publishing automatic captions unread. Read every line against the audio before export.
- Burned in captions plus platform captions. Two caption tracks on top of each other is worse than either alone; with open captions, leave the platform’s automatic captions off.
- Timing captions to the edit. A caption should follow the speech, and stay long enough to read even if the cut comes early.
Build it
Captions in the video builder are derived from each scene’s narration text, so they match the script exactly and carry no speaker labels or sound descriptions of their own. They are on by default and toggled per scene in the voice dialog, where each scene also takes a voice speed of 0.85x, 0.9x, 1x, 1.1x or 1.25x and a delay in seconds. They are burned in as one dark pill centred at the bottom, typing on as the line is spoken, capped at 72 percent of the frame width, with 26 pixel type on landscape and 30 on vertical, inset 44 pixels from the bottom on landscape and 120 on vertical. The captions page covers how they are drawn, the voiceover languages post covers captions in other scripts, and the steps are in the tutorial on adding voiceover, captions and music.
| Rule | Value | Source |
|---|---|---|
| What captions must carry | Speech, who is speaking, and meaningful non-speech sound | WCAG 2.2, success criterion 1.2.2 (Level A) |
| Automatic captions | Not enough on their own unless confirmed fully accurate | W3C WAI, Captions/Subtitles |
| Reading speed, general audiences | 160 to 180 words per minute | BBC subtitle guidelines |
| Reading speed, educational media | Up to 130 wpm lower level, 140 middle level, 160 upper level | DCMP Captioning Key, presentation rate |
| Minimum time on screen | About 0.3 seconds per word, 1.2 seconds for four words | BBC subtitle guidelines |
| Lines per caption | Two on landscape or square; three on vertical | BBC subtitle guidelines; DCMP prefers two |
| Line width, online | 68% of a 16:9 frame; 90% of a 9:16 frame | BBC subtitle guidelines |
| Line width, broadcast | 37 characters | BBC subtitle guidelines |
| Where to break a line | At punctuation; never between article and noun, or preposition and its phrase | BBC subtitle guidelines; DCMP Captioning Key |
| Case | Mixed case; capitals only for shouting | DCMP Captioning Key |
| Type | White, medium weight, sans serif, with a drop or rim shadow | DCMP Captioning Key |
| Placement | Bottom of the frame; move up when covering faces, mouths or on screen text | DCMP Captioning Key; BBC subtitle guidelines |
| Vertical video placement | A little higher than landscape, still in the lower third | BBC subtitle guidelines |
A finished example
This fitness app UGC ad example is a 29 second creator style video where the proof is the app itself, shown twice as real screens, and the script with every scene and its seconds is published below. A creator who has twelve minutes a day shows the session picker that fits the gap and the streak screen that kept her coming back, then closes on the free week.
Read the fitness app ugc ad exampleQuestions people ask
How many words should be on one caption?
Fewer than most tools put there. On a landscape frame keep each caption to two lines, and each line to roughly two thirds of the frame width, which the BBC sets at 68 percent for 16:9 video online. That usually means six to ten words per caption. A long spoken sentence becomes two or three captions, split at its natural pauses.
Should captions be word for word?
Yes, as far as reading speed allows. The BBC notes that viewers tend to prefer verbatim subtitles and that the rate can rise to match the pace of the programme. Edit only when a speaker is too fast to read, and never edit in a way that changes the meaning. A dropped word like not is the classic automatic captioning error.
Are automatic captions good enough?
Not without checking. The W3C's accessibility guidance says automatically generated captions do not meet user needs or accessibility requirements unless they are confirmed to be fully accurate, and it points out that errors can reverse meaning. Treat automatic captions as a first draft: read every line against the audio, fix names, numbers and product terms, then publish.
Where should captions go on a vertical video?
Low, but not at the very bottom. The BBC notes that vertical video subtitles usually sit a little higher, still in the lower third, because faces tend to be in the top half of the frame and the platforms draw their own text along the bottom. Keep captions clear of the creator's mouth and of any price, code or date shown on screen.
Do captions need to describe sounds and music?
When the sound carries meaning, yes. WCAG success criterion 1.2.2 expects captions to identify speakers and convey meaningful sound effects. The BBC asks for a label when music is part of the action, and does not want every creak captioned. A background track under a promo usually needs nothing; a doorbell that starts the story does.
What is the difference between open and closed captions?
Closed captions can be switched on and off in the player. Open captions cannot, because they are drawn into the picture, which is what burned in captions are. Open captions reach every viewer on every platform, including feeds that never show a caption button, but viewers cannot resize or restyle them, so they have to be right in the file.
What reading speed should captions assume?
For a general audience, plan around 160 to 180 words per minute, which is the BBC's recommended subtitle speed, with about 0.3 seconds on screen per word as a minimum. For learning content aimed at younger viewers, the DCMP Captioning Key recommends slower rates of 130 to 160 words per minute depending on the level.
Written by
Indunil Asanka · Co-founder
Builds the generation pipelines behind OneCraft: the slide, flyer and poster layout engines, the document grid and the render workers that turn a written brief into a finished file.
LinkedIn profileWritten and checked by the OneCraft team. Last checked .
Make your own video
Describe what you need and the generator writes and designs it, then you edit anything you like.
See what it can makeRead next
AI voiceover voices by language
Every AI voiceover page promises a hundred languages and none of them tells you which voice you actually get in Marathi. This is the full mapping for one pipeline, read out of its source on 1 September 2026: 56 locales, eight named voices, and the four places where the quality drops or disappears.
Voiceover speed for videos
Research on recorded lectures puts the average speaking rate at about 156 words per minute, and a common rule of thumb is 160. A finished video carries far fewer words than that per minute of running time: across 20 example videos the median was 76 for promos, 84 for tutorials and 98 for creator style ads.
How to choose background music for a video
Choose background music by deciding the mood the video should leave behind, then matching the tempo to how fast the scenes cut, then confirming you are licensed to use the track where the video will play. Set it well under the voice, and for a step by step tutorial consider no music at all.
For the steps inside the builder, read the guideon this topic.