Subtitle translation: from transcript to bilingual output
Most subtitle quality is decided before translation starts: how accurate the transcript is, and how consistent the terminology is.
The chain
- Transcript. Start from a proofread transcript with timing (see the subtitle generation guide).
- Context grouping. Translate a few neighbouring lines together — line-by-line translation breaks tone and pronouns.
- Terminology. Fix names, brands and technical terms once, then apply them across the whole file.
- Translate. Produce the target language and keep line length readable.
- Lay out bilingual output. Original on top, translation below; check size so the picture is not obscured.
Common pitfalls
| Pitfall | Symptom | Fix |
|---|---|---|
| Line-by-line translation | Broken tone, ambiguous pronouns | Translate in context groups |
| Terminology drift | The same term translated differently | Build a term list and enforce it |
| Timing shift | Text out of sync with speech | Keep the original timing; replace only the text |
| Overlong lines | Viewers cannot read fast enough | Cap characters per line and wrap sensibly |
Bilingual layout
- Default to original on top, translation below.
- Slightly smaller type than body text so it does not dominate the frame.
- On busy backgrounds, a subtle outline improves legibility.
Frequently asked questions
What causes the worst subtitle translations?
An inaccurate transcript and inconsistent terminology. If the source text is wrong, the translation will be too.
Why not translate one line at a time?
Line-by-line translation loses context, so tone and pronouns drift. Translating a few neighbouring lines together reads far better.
How should bilingual subtitles be arranged?
Original on top, translation below, slightly smaller, with a sensible character limit per line.
More topics on the guides hub, or see what Lumasce does.