A subtitling convention is a set of rules that govern subtitle segmentation, line length, reading speed, positioning, timing, punctuation, and character formatting for audiovisual content. They vary by platform, genre, and language and give subtitlers, editors, and QA reviewers a shared standard for producing consistent and compliant subtitle files; they often specify maximum characters per line, minimum duration, and how to treat speaker changes.
Angel Translation editorial reference · Confirm the rendering against your source and approved project terminology.
Check source meaning → confirm the preferred term → record approved variants and references.
Subtitling conventions appear in client spec sheets, platform style guides, and project-specific instructions for entertainment, e-learning, training, and marketing video localization projects. They are applied during subtitle translation, spotting or timing, and QA, and they determine whether deliverables will pass automated checks, platform validation, final client review, and downstream implementation.
A frequent mistake is applying generic subtitle rules instead of the client-specific convention, for example using a 42-character line when the platform limit is 37 or setting a minimum duration below the required threshold. This leads to automatic QC failure, downstream rework, and subtitles that are hard for viewers to read.
Creative and consumer content needs accurate meaning as well as tone and context. Subtitles, interfaces and voice scripts also require checks for timing, character limits and pronunciation.
Provide approved terms and previous translations with the source files. Agree how variants, ambiguous wording and revisions will be reviewed. Terminology maintenance and any termbase handback are confirmed in the project scope. See the 8-step AI + expert workflow.
Employee-training video transcription and dubbing.
Read the published project →Brand documentation.
Read the published project →Published scope shows related industry experience; it does not confirm that this specific term was used or reviewed in the project.
Include the source and target languages, file types, intended use, deadline and any approved termbase. Agree handling before sending sensitive files. Acknowledged in 4 hours, quoted in 24.
Prepare an inquiry email →Content Globalization solutions →File handling →A glossary entry is not an official standard or evidence of regulatory acceptance. Confirm current requirements for your project separately.