Why subtitles follow rules at all
Subtitles are read quickly, in passing, while the viewer is also watching a picture. Almost everything in a style guide exists to protect that limited attention. If the text is split awkwardly, flashes by too fast, or uses symbols the viewer has to puzzle over, the viewer stops following the story and starts decoding the text.
Style guidelines are the written-down habits that prevent this. They cover how long a line may be, where it may break, how many lines appear at once, how quickly text can change, how speakers are shown, and how numbers and punctuation are written. None of these rules is a law of nature. Different broadcasters, streaming services, film distributors, educators and clients publish their own guides, and the details differ from one to the next. What follows is the general shape of the common conventions, not a single official standard.
If a project comes with its own guide, that guide wins. The general principles below help you understand why such guides say what they say, and what to do when a guide is silent.
The core idea: one glance, one thought
A well-made subtitle can be understood in a single glance and then forgotten while the viewer returns to the picture. That goal explains most of the conventions.
- Text is short enough to read in the time it is shown.
- Each block holds one idea, or a clean part of one.
- Grammar is kept together so the eye does not have to jump ahead.
- Nothing needs to be decoded, such as an unusual symbol or an unclear speaker.
Line length and the number of lines
Subtitles are usually kept to a modest number of characters per line, and to no more than two lines at a time. The limits protect legibility and keep the text from covering too much of the picture. The reasoning is covered in more detail in the articles on how many characters fit on a subtitle line and on why subtitles usually stop at two lines. The exact figures vary by language, medium and client, so treat any single number you see quoted as one guide’s choice rather than a universal rule.
Breaking lines sensibly
When a sentence needs two lines, the break should fall where the grammar allows it. Keeping a short phrase, such as an article and its noun, together is far easier to read than splitting it. The topic of line breaks has its own article, but the principle is simple: break at natural pauses, and avoid leaving a one-word fragment stranded at the end of a line.
Reading speed and condensing
Viewers can only read so fast, and speech is often faster than reading. Two ideas follow. First, there is a limit on how much text should appear per second, usually discussed as reading speed. Second, when speech is too fast to be shown word for word, writers practice text condensation: trimming the wording while keeping the meaning. A good condensed subtitle sounds natural and loses little beyond repetition and filler. Both topics depend on how long text stays visible, which is the subject of display duration, and on the broader craft of subtitle writing.
Punctuation, italics and emphasis
Subtitle punctuation follows ordinary written conventions with a few specialized habits. Italics are commonly used for voices that come from off screen or through a device, and for some titles and foreign words. Ellipses and dashes signal interrupted or trailing speech. Because every character costs space and attention, writers tend to avoid decorative punctuation and clutter. Typical practices are laid out in the article on punctuation and italics.
Showing who is speaking
When more than one person speaks, the viewer needs a way to tell who is talking. Common methods include a dash at the start of each speaker’s line, a name label, a change of color, or placement of the text near the speaker. Each has trade-offs, discussed in the article on speaker identification. Sounds that are not speech, such as a door slamming or music, belong to a separate topic, non-speech information, which matters mainly for viewers who are deaf or hard of hearing.
Numbers, symbols and dates
Numbers are a place where guides differ a lot. Some spell out small numbers and use digits for larger ones; some prefer digits whenever space is tight. Units, currency, dates and time of day each have their own conventions. The important rule is consistency within a project, and a form that the audience reads easily in their own language. See the article on number formatting for the main choices.
Appearance on screen
Font, size, contrast and position affect how easily text can be read, and they depend on the screen. A phone held at arm’s length and a cinema screen are very different. Many of these choices are made by the player or the viewer rather than the writer, which is why subtitle appearance settings exist. File-level decisions about how styling is stored are a separate matter, covered under caption styling.
Language differences
A rule that works in one language can fail in another. Translated text is often longer than the original, which is why text expansion is a standing problem for translators. Some writing systems have no spaces between words, so breaking lines is harder, and right-to-left scripts bring their own display rules. General principles carry across languages, but the numbers and details need to be set per language.
How rules get checked
Style rules are only useful if someone checks them. Reviewers look for lines that are too long, text that stays up too briefly, awkward breaks and inconsistent number formats, along with other subtitle errors. Many teams turn the rules into a quality checklist, and some automated tools can flag limit breaches. A human still needs to judge whether a subtitle reads naturally, since a text can meet every numeric limit and still read badly.
Using the rules with judgment
The best way to read a style guide is as a set of defaults. A short exclamation may justify an unusual break; a fast exchange may need a slightly higher speed than usual; a screen with a different shape may need adjusted limits. Experienced writers know the reasons behind each rule and bend it only when doing so clearly helps the viewer. When in doubt, ask the question the whole guide is built around: can the viewer take this in at a glance and get back to the picture?